data in transit
- ✓TLS 1.3 on every endpoint; HSTS preload enforced
- ✓Perfect forward secrecy via X25519
- ✓Certificate transparency monitored; CAA locked to issuers we approve
posture—linkfetch / § security
rev.2026.04
§ security
Security posture, plainly stated.
What we do today, what we're working on, and how to report a vulnerability.
§ 02 · today
Four layers, itemised.
data at rest
- ✓Postgres 16 with at-rest encryption (AES-256)
- ✓Daily encrypted backups, 30-day retention, geo-replicated
- ✓API keys stored hashed (SHA-256); plaintext shown once on creation
access control
- ✓Human access via SSO + hardware MFA (YubiKey)
- ✓Production access audited; all queries logged
- ✓Least-privilege roles; zero ambient production access
operations
- ✓Incident response playbook · 60-minute customer notification SLO
- ✓Quarterly disaster-recovery drill; RPO 15min, RTO 4h
- ✓All infra-as-code via Terraform; no console changes
§ 03 · compliance track
Where we are, where we're going.
- GDPRalignedsince launch
- CCPA / CPRAalignedsince launch
- SOC 2 Type Iin progressaudit Q3 2026
- SOC 2 Type IIplannedtargeted 2027
- ISO 27001plannedafter SOC 2
§ 04 · vulnerability reporting
Responsible disclosure.
Bounty + acknowledgment
We acknowledge every report within 12 hours. In-scope issues are paid per severity (critical $5k, high $2k, medium $500). We publish a security acknowledgments page and credit you by name unless you opt out.
- ▸In scope: *.linkfetch.io, Chrome extension, MCP server
- ▸Out of scope: rate-limit bypass, missing headers alone, DoS