Get in touch

Connect with entityOS.

Two ways to reach us. Send a confidential message to our team, encrypted end‑to‑end with our public PGP key — or report a security vulnerability through the entityOS Security Reward Program.

PGP Encrypted Email Ed25519 / Curve25519 support@ibcom.biz Responsible Disclosure
The Core Idea

Reach us securely.

We treat the public internet as hostile — and that applies to how you reach us too. For anything sensitive, encrypt it with our public key so only ibCom can read it, in transit and at rest.

End‑to‑end

Encrypted on your machine, decrypted only by ibCom. No one in between can read it.

Verifiable

The key file’s hash is published in DNS, so you can confirm you got the real thing.

The right channel

Confidential mail one way; vulnerability reports through the Reward Program the other.

CONTACT 01 Confidential Contact

Send an encrypted message.

For confidential correspondence, encrypt your message to the ibCom public PGP key and send the ciphertext to support@ibcom.biz. Only holders of the ibCom private key can decrypt it — not your mail provider, not ours, no one on the wire.

Key typeEd25519 · Curve25519
IdentityibCom Support <support@ibcom.biz>
Key ID0xFE469071EDBC4B2D
FingerprintC3BB B955 902C 4386 70BF  9DA9 FE46 9071 EDBC 4B2D
Verify the download

Don’t trust the key until you’ve checked it. Compute the SHA‑256 hash of the .txt you downloaded and compare it to the hash published as a DNS TXT record at pgp.ibcom.biz. If they match, the file is authentic; if they differ, stop — discard it and let us know.

sha256sum ibcom-pgp-public.txt # Linux shasum -a 256 ibcom-pgp-public.txt # macOS dig +short TXT pgp.ibcom.biz # the published hash

How to send it

The quickest path is our in‑browser message tool — it encrypts to this key entirely on your device, with nothing to install and no message ever leaving your machine unencrypted. Prefer the command line? Four steps with GnuPG follow (or a graphical client — GPG Suite, Gpg4win, Thunderbird, Mailvelope — does the same thing).

  1. 1

    Get the public key

    Download ibcom-pgp-public.txt above, or copy the block at the foot of this section — then verify it with the SHA‑256 check described above before you trust it.

  2. 2

    Import it into your keyring

    gpg --import ibcom-pgp-public.txt
  3. 3

    Encrypt your message

    Encrypt to the ibCom key and write ASCII‑armored output you can paste into an email.

    gpg --encrypt --armor --recipient support@ibcom.biz message.txt

    This produces message.txt.asc — ciphertext that begins -----BEGIN PGP MESSAGE-----.

  4. 4

    Send it to support@ibcom.biz

    Attach or paste the armored ciphertext into an email to support@ibcom.biz. If you’d like an encrypted reply, include your own public key in the message.

ibCom public key — PGP / Ed25519

-----BEGIN PGP PUBLIC KEY BLOCK----- xjMEaoz1ZxYJKwYBBAHaRw8BAQdAC0C9idvajtGYZG96V/qHrDsjvrtUaNix bit48JNqpUbNIWliQ29tIFN1cHBvcnQgPHN1cHBvcnRAaWJjb20uYml6PsLA GQQTFgoAiwWCaoz1ZwWJA8JnAAMLCQcJEP5GkHHtvEstRRQAAAAAABwAIHNh bHRAbm90YXRpb25zLm9wZW5wZ3Bqcy5vcmdKKV/2F5LWLOXzmPgrVaK8HE9i hlFzZhiPgmiYPv7sYAUVCggODAQWAAIBAhkBApsDAh4BFiEEw7u5VZAsQ4Zw v52p/kaQce28Sy0AAC8MAQCqrI/I+Brc660oCGKA/0E5AfSGo4lP/gVuyGAi DdXZwwEAxIsMBc/s/gNQDqyhgJjzrn5z1l95WVdWqqZ4yRt42A/OOARqjPVn EgorBgEEAZdVAQUBAQdAtHREeORZid5UBx2PAQpwjnknOWwsz+6mh6qLcFL2 t3ADAQgHwsAEBBgWCgB2BYJqjPVnBYkDwmcACRD+RpBx7bxLLUUUAAAAAAAc ACBzYWx0QG5vdGF0aW9ucy5vcGVucGdwanMub3JngoCArHI/3MxClybMbyBe pzMQfF/4Rj41D/7BSlVEC4ICmwwWIQTDu7lVkCxDhnC/nan+RpBx7bxLLQAA cVIBANL1x9OSFPQUcmrhyCugvXWUMBDR2c5Knlgv98B1luh5AQDKBKjDVsTL 7pUi7pXMVE+LFQEAHQkcDTuZPo3kQfdWBw== =IXRn -----END PGP PUBLIC KEY BLOCK-----
CONTACT 02 Responsible Disclosure

Found a vulnerability?

Security research goes through the entityOS Security Reward Program — a single reporting form, not email. Report it there and we’ll acknowledge, triage, remediate, and reward eligible findings, with safe‑harbour for good‑faith research.

Please don’t send vulnerability details by email. The Reward Program form keeps reports tracked, triaged and credited from the moment they arrive. Encrypted email is for confidential correspondence; the form is for security issues.
Get in touch

We’re ready when you are.

Confidential message? Encrypt it to our public key and send it to support@ibcom.biz.

Security issue? Report it through the entityOS Security Reward Program.