LogicNodes Security Team - PGP Key

Purpose: This page provides the PGP/GPG public key for encrypted communication with the LogicNodes security team.

Last Updated: April 24, 2026

When to Use This Key

Use this PGP key to encrypt sensitive security reports or communications to the LogicNodes security team, including:

Security vulnerability reports (see Responsible Disclosure Policy)
Data breach notifications
Confidential security inquiries
Sensitive partner security information

Note: PGP encryption is optional. You may also send unencrypted email to kontakt@logicnodes.ai for non-sensitive communications.

PGP Public Key

Email: kontakt@logicnodes.ai Key Type: RSA 4096 Key ID: 707941C4 Fingerprint: FD15 E817 5925 8403 5F53 0A4A 389B 966F 7079 41C4 Created: April 24, 2026 Expires: April 23, 2028

ASCII-Armored Public Key

How to Use This Key

1. Import the Public Key

Using GPG (Command Line):

# Download and import the key directly
curl https://legal.logicnodes.ai/en/pgp.txt | gpg --import

# Or download first, then import
curl https://legal.logicnodes.ai/en/pgp.txt -o logicnodes-security.asc
gpg --import logicnodes-security.asc

# Verify the fingerprint
gpg --fingerprint kontakt@logicnodes.ai

Using Keybase:

keybase pgp pull kontakt@logicnodes.ai

Using Email Clients:

Thunderbird with Enigmail: Tools → OpenPGP Key Manager → Import
Apple Mail with GPGTools: Open GPG Keychain → Import
Outlook with Gpg4win: Kleopatra → Import Certificates

2. Verify the Fingerprint

Always verify the fingerprint before encrypting sensitive data:

Published Fingerprint: FD15 E817 5925 8403 5F53 0A4A 389B 966F 7079 41C4

Check via Multiple Channels:

This page: /en/pgp
Security.txt: /.well-known/security.txt
Keybase: https://keybase.io/logicnodes (if published)
Contact us directly: kontakt@logicnodes.ai (we’ll confirm via signed email)

3. Encrypt Your Message

Using GPG (Command Line):

# Encrypt a message
gpg --encrypt --armor --recipient kontakt@logicnodes.ai message.txt

# This creates message.txt.asc - send this file via email

Using Email Clients: Most email clients with PGP plugins will automatically offer to encrypt when you compose an email to kontakt@logicnodes.ai.

4. Send Your Encrypted Message

Email To: kontakt@logicnodes.ai Subject: [SECURITY] Brief description Body: Paste the encrypted message (including -----BEGIN PGP MESSAGE----- header)

Example:

To: kontakt@logicnodes.ai
Subject: [SECURITY] SQL Injection Vulnerability Report

-----BEGIN PGP MESSAGE-----

[Your encrypted message here]

-----END PGP MESSAGE-----

Verifying Our Responses

All responses from kontakt@logicnodes.ai will be PGP signed to verify authenticity.

To verify our signature:

# Check the signature on a signed message
gpg --verify message.asc

Expected output:

gpg: Good signature from "LogicNodes Security Team <kontakt@logicnodes.ai>"

Warning: If you see “BAD signature” or a different fingerprint, do not trust the message. Contact us via another channel immediately.

Key Management

Key Rotation

This key will be rotated according to the following schedule:

Standard rotation: Every 2 years
Emergency rotation: Immediately if compromised
Advance notice: 60 days before planned rotation (announced via this page and email)

Key Revocation

If this key is compromised or needs to be revoked:

A revocation certificate will be published on this page
Email notification sent to all registered security contacts
New key published within 24 hours
All signed communications will reference the revocation

Check for revocations:

gpg --refresh-keys kontakt@logicnodes.ai

Alternative Secure Communication Methods

If you cannot use PGP encryption, consider these alternatives:

1. Signal

Contact: [TO BE ADDED - IF AVAILABLE] Verification: [TO BE ADDED - SAFETY NUMBER]

2. Encrypted Form

URL: [TO BE ADDED - IF AVAILABLE] Note: Uses HTTPS + end-to-end encryption

3. Keybase

Profile: [TO BE ADDED - IF AVAILABLE] Note: Encrypted chat and file sharing

4. Unencrypted Email

Email: kontakt@logicnodes.ai Note: Use for non-sensitive communications only

Security.txt

This PGP key is also published in our security.txt file per RFC 9116:

URL: /.well-known/security.txt

Contents:

Contact: mailto:kontakt@logicnodes.ai
Encryption: /en/pgp
Expires: [TO BE ADDED]
Preferred-Languages: en, da
Canonical: /.well-known/security.txt
Policy: /en/responsible-disclosure

Frequently Asked Questions

Q: Do I need to use PGP to report security issues? A: No. PGP is optional. You can send unencrypted email to kontakt@logicnodes.ai. Use PGP for sensitive information like proof-of-concept exploits.

Q: How do I know this key is authentic? A: Verify the fingerprint via multiple channels (this page, security.txt, signed email from us). We will also confirm via alternative communication methods if requested.

Q: What if I lose your public key? A: It’s always available at /en/pgp. You can also request it via email.

Q: Can I send you my PGP key? A: Yes! Include your public key or key ID in your first email. We’ll encrypt all replies to you.

Q: How long do you keep the key? A: This key is valid until [TO BE ADDED - EXPIRY DATE]. We’ll rotate it at least 60 days before expiration.

Q: What if the key expires? A: A new key will be published before expiration. Check this page for the latest key.

Download Options

Copy from this page: See ASCII-armored key above Text-only version: Change .html to .txt in the URL: /en/pgp.txt QR Code: [TO BE ADDED - IF DESIRED]

Contact Information

Security Team: Email: kontakt@logicnodes.ai PGP: This page Response Time: Within 24 hours for critical issues

Company: LogicNodes ApS Sletvej 2D, 8310 Tranbjerg, Denmark CVR: DK45318362

Responsible Disclosure Policy - How to report vulnerabilities
Security Architecture - Available on request
Data Processing Agreement - GDPR compliance
Security.txt - RFC 9116 security contact

Version: 2.0 Last Updated: April 24, 2026 Next Review: October 2026