Identity Verification & Trust Signals
Ensure you are communicating with the authentic DeTechtive team. Check PGP credentials, cryptographic hashes, and official channels.
PGP Public Key
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mQINBGPzR9MBEADUp5p1tI9r7Jg2Gv5H... [PLACEHOLDER: Replace with actual ASCII-armoured public key block before launch] -----END PGP PUBLIC KEY BLOCK-----
Verification Steps
Compare the fingerprint above with fingerprints published elsewhere (e.g. social profiles) before transmitting sensitive files. Use standard PGP command lines to encrypt reports or intake logs.
- Import our public key (`security.asc`) into your PGP client.
- Verify that the fingerprint in your client matches:
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX - When drafting an email to `security@detechtive.io`, select the option to encrypt and sign.
- (Optional) Export your own public key and attach it so we can write back securely.
Signed Commitments & Statements
We periodically publish cryptographically signed commitments (such as warrant canaries or operational declarations). You can verify their integrity using our public key.
| Date | Statement Description | Status | Action |
|---|---|---|---|
| 2026-06-03 | Initial Warrant Canary (No requests received to date) | Active | Verify Signature |
Official Communication Channels
Only communication originating from or encrypted to the channels listed below should be considered authentic DeTechtive correspondence. If someone contacts you claiming to represent us via other channels, please verify their identity using PGP before responding.
Secured Email
security@detechtive.io
Signal Messenger
Signal number shared upon PGP triage
Threat Intelligence Substack
GitHub Repository
github.com/detechtive-io