Privacy Policy

Who we are

Delegus, Inc., a Delaware corporation ("Delegus", "we"). This policy covers the delegus.ai website and the Delegus service (the API, SDK, CLI, and console). Contact: hello@delegus.ai.

What we collect

The website

Privacy-preserving, cookieless analytics (aggregate page views, no cross-site tracking, no advertising profiles), and anything you choose to send us, for example your email if you write to us or apply to the pilot program.

The service

• Verification inputs you send to /verify: the signed grant, the per-request proof, and the action metadata (for example a resource identifier and amount). These are the technical facts a decision is computed from.
• Decision Receipts and evidence: the signed record of each decision and the hashes of what it referenced, stored as tamper-evident evidence.
• What was checked: since September 23, 2026, with each decision (approved or refused) we also keep the action the service sent us to check: its type, the item or resource, and for a purchase the amount and currency (for an API call, the request method). We keep it so your dashboard can show what was bought and for how much, and so usage can be measured by value. It is kept with the decision record for seven years. After that, Delegus clears these details (what was asked, the amount and the currency) automatically. The signed receipt itself and its evidence stay available for verification, as the retention section describes. It is shown only to the service that sent it, its organization, and Delegus staff. It is not published, and the signed receipt itself still holds only a fingerprint of it. We do not store the company’s permission or the agent’s signed request, and this adds nothing about the buyer’s identity.
• Account information for a tenant: organization name, a contact email, and API keys (we store only a hash of each key, never the key itself), plus usage counts.
• Domain and identity checks: for each domain or organization identity you claim, the domain, the verification token we give you, whether it is verified, and when it was first verified and last checked. We re-check a verified domain every 24 hours through its DNS TXT record or its /.well-known file. At signup we also keep the email address you signed up with, its email domain, and a salted hash of your IP address (never the address itself). If someone reports misuse of a name, brand or domain to hello@delegus.ai, we keep the report and what we did about it. We keep all of this to stop impersonation and squatting (see acceptable use in our Terms), and to be able to show who proved control of what, and when.
• Passkey approvals, if your company lets Delegus hold its signing key: for each approver, the name your admin gives them and an id your admin chooses (no email, phone or other contact detail); for each of their passkeys, its public key, an identifier the device chose, its algorithm, a signature counter and when it was added and last used. We don’t keep the device’s attestation, its model or a device name. For each grant you prepare, we keep the unsigned grant (the agent, what it may do, its limits and dates) and, once approved, who approved it and when. For each approval we keep an approval record: the grant, the approver, the passkey’s public key and its full signature over the grant’s exact bytes. We never receive a fingerprint, face data, a PIN or anything else that unlocks the device, and never the passkey’s private key.

We do not require personal information about your end users to operate. If you choose to place personal data inside an action payload, you are the controller of it; keep it to what the decision needs.

How we use it

• To provide the service, which means evaluating verifications and returning decisions.
• To create and retain the signed receipts and referenced evidence (this is the product, not a side effect).
• Security, abuse prevention, rate limiting, and support.
• Billing, for paid tiers.

We do not sell your data, and we do not use it to build advertising or cross-customer profiles.

Google user data in EnterpriseWorld

EnterpriseWorld can connect to a customer’s Gmail and Google Drive, but only when a person at that company turns a connection on and agrees on Google’s own consent screen. Each connection asks for one thing and nothing more.

What we read

• Gmail, read only. We look for the mail that matters to the company’s own work: messages to or from people on its records, or that name one of its order or invoice numbers. We don’t read the rest of the mailbox, and we can’t change or delete anything in it.
• Gmail drafts, a separate connection that is off until you turn it on. EnterpriseWorld prepares reply drafts in your Gmail. An agent can only draft. A message is sent only when a person sends it.
• Google Drive, only the files you pick. When you choose a Google Sheet or Doc in Google’s file picker, we read that file and nothing else in your Drive.

What we use it for

To show your company its own work in EnterpriseWorld: the orders, invoices and conversations it’s handling, and the drafts waiting for a person. We don’t use it for anything else. Anything EnterpriseWorld writes back to Google, like a draft or a sent reply, happens only when a person acts.

We never sell Google user data and never use it for advertising. Our code keeps everything read from Gmail and Google Drive out of training, so it is never used to train any AI model of ours. People at Delegus read it only when you ask us to, when security requires it (for example to look into abuse), or when the law requires it.

Where it’s kept

In a Postgres database hosted by Neon in the United States, with one database for each company. Mail bodies, the Docs and Sheet rows you picked, and the access token Google gives us are encrypted when stored (AES-256-GCM). Attachments aren’t stored; we fetch one from Gmail only when it’s needed. We keep what we read while the connection stays on.

Who else sees it

Two services help run EnterpriseWorld’s assistant, and only they see any of this data besides Neon:

• Anthropic runs the assistant. To answer a question it may receive short excerpts: a thread’s subject and the start of its latest message, contact names and email addresses, file names and record names. This is processed in the United States. Anthropic’s commercial terms say it may not train models on this content.
• ElevenLabs reads the assistant’s answer aloud when a person asks it to, and that answer can quote the excerpts above.

Nothing goes to advertisers, analytics services or anyone else.

Disconnecting and deleting

You can disconnect Gmail or Drive in EnterpriseWorld at any time. When you disconnect, we revoke our access with Google and delete what that connection read. If access to your Google account is withdrawn or runs out, we delete it too. One thing stays: anything that already became one of your company’s own records, such as a row from a Sheet, a ship date confirmed in an email, or a bill made from a PDF that came by mail. Those stay in your workspace until your company deletes it, and they are never used for training either. You can also remove our access from your Google Account, and write to hello@delegus.ai to ask us to delete anything we hold.

Delegus's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Retention

The evidence a Decision Receipt references is kept for seven years in write-once storage, as the protocol specifies; no one, including Delegus, can change or delete it in that time. Account information, including domain and identity checks, signup records and misuse reports, is kept while your account is active and for a reasonable period afterward for legal and audit purposes. Note that receipts are signed when they are issued, so a copy that has been changed no longer verifies, and we keep historical decisions rather than altering or deleting them.

Approval records are kept with that evidence for seven years in the same write-once storage, and only your company receives them. Approvers, their passkeys and prepared grants are kept while your organization exists; your admin can disable an approver, remove one for good, or revoke a single lost passkey, which stops those passkeys approving; the records stay, marked as disabled or revoked. The signing key Delegus holds for your company is never deleted, so every grant it signed keeps verifying.

Who we share it with

We use a small number of service providers to run Delegus on our behalf. Each works under contract and only to provide its part of the service:

• Render runs the Delegus API (United States, Virginia). Its network edge is Cloudflare, so traffic to the API passes through Cloudflare.
• Google Cloud holds our signing keys, and the keys we hold for companies that choose it (United States, us-east4).
• Backblaze keeps the write-once evidence store (United States, us-east-005).
• Vercel hosts this website and the console at app.delegus.ai.
• Neon is the Delegus API’s database and the console’s database (United States, us-east-1): organization names, contact emails, sign-in records, usage summaries and account settings.
• Resend sends our email, such as sign-in links and replies to pilot applications.
• Upstash is the Delegus API’s cache (United States, us-east-1). It also stores pilot applications sent through this website and counts clicks on our tracked links.
• Anthropic powers an internal assistant our staff use to run the business. It may process business contact details and account usage summaries; it is never given your verification inputs, receipts, evidence or keys.
• Google Workspace handles our own email and correspondence, for example when you write to hello@delegus.ai.
• Stripe handles billing, for paid tiers.

We disclose data if required by law, and we would tell you unless legally prohibited. We do not sell data.

Security

Signing keys are held in a managed key service and can't be exported; API keys are stored only as hashes; access is restricted and audited. More detail, including what is planned but not yet in place, such as a SOC 2 report, on the security page.

Your choices

Write to hello@delegus.ai to access, correct, or delete account information, or to ask a question about this policy. We honor applicable privacy rights (including under GDPR and CCPA where they apply). One limit to be honest about: signed receipts are immutable evidence by design, so we cannot alter a past decision record, but we can delete account and contact information.

International

The Delegus API, its evidence store and the console’s database are hosted in the United States. Additional regions are available to enterprise customers on request.

Changes

We will post any changes here and update the date above. Material changes affecting customers will be communicated directly.

Contact

Questions, requests, or complaints about this policy:

Delegus, Inc.
Attn: Jane Hagger
400 Concar Dr, San Mateo, California 94402
Email: hello@delegus.ai

Your use of the Site is also governed by our Terms of Use, which include how disputes are resolved.