What we hold, and what we refuse to hold.
Plain language, because that's how we write everything. Last updated August 30, 2026.
FleetRegistry
FleetRegistry ("we") operates the registry of record for AI agents at fleetregistry.ai. Questions or requests about this policy: hello@fleetregistry.ai.
The minimum a registry needs
Your account email and workspace name; the fleet and agent metadata you register (names, statuses, evidence rungs); hash-chained decision and event records (kinds, statuses, payload fingerprints — SHA-256 hashes, not contents); and the public half of passkeys you enroll. The relay collector's schema is deliberately narrow: it has no field that could carry a prompt, an output, a document, a customer name, or a credential. The safest data is the field that doesn't exist.
Secrets, prompts, outputs, private keys
Passkey private keys never leave your device. Relay tokens authenticate your collector and are never shown to our support staff or AI systems. Proposal payload text is hashed on your machine; the registry stores the fingerprint.
Gmail, only on your say-so
If a workspace connects a Gmail account, FleetRegistry uses the Gmail API for exactly two things: sending messages that a human in that workspace has explicitly authorized with a passkey signature over the exact message payload, from that workspace's own account; and reading message metadata needed to confirm delivery and observe replies to messages it sent. Google user data is not used for advertising, not sold, not transferred to third parties except as required to provide these two functions or comply with law, and not used to train AI models. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Append-only, by design
The record is hash-chained and append-only: corrections are new entries, not silent edits. That is the product. Registry records persist while your account is active. If you close your account, contact us and we will delete your workspace's data, subject to legal retention requirements; anchored public checkpoints contain only hashes.
We don't sell data. Full stop.
No advertising, no data brokers. We use infrastructure subprocessors (hosting, database, email delivery, model inference for the concierge) bound by their own confidentiality terms. Nothing from a member workspace appears on our public pages; the marketing site shows only our own showcase fleet.
Access, correction, deletion
Email hello@fleetregistry.ai to access, export, or delete your data, or to ask anything this page didn't answer. We'll respond as quickly as a small, focused team can — usually within days.
Updates land here
Material changes to this policy will be posted on this page with a new date. During Early Access, expect this document to get more formal as the product does.