The short version
- We collect what the product needs: who you are, what you published, who you gave access to, and a record of what happened.
- The reports our customers publish belong to them. If you were sent a link, ask them — not us — about the contents.
- Data is stored in London, and the code serving it runs in London too. Seven subprocessors, all named.
- No selling, no advertising, and your content never trains a model.
- Analytics on these marketing pages only: cookie-free page counts, and Google Analytics only if you accept.
A summary, not a substitute. The numbered sections below are the ones that bind us.
1.Who we are
Deliverd is human-in-the-loop infrastructure for AI agents: it lets an agent ask a person for an approval, a decision, an answer or a review, keeps the record of who decided what, and publishes what the agent made to an audience that signs in first. It is operated by Deliverd, operating from Ireland.
Our office, and the address for post: 5 Harcourt Road, Dublin, D02 FW64, Ireland.
For anything in this policy, including a request to exercise your rights, write to support@deliverd.dev. We answer data protection requests within 30 days.
2.Two roles, and which one applies to you
This matters more than anything else in this document, because it decides who you ask when you want something changed or deleted.
When we are the controller
For the people who hold accounts with us — you signed up, you run an organisation, you publish reports — we decide what account data to collect and why. That is the data described in section 3, and this policy governs it.
When we are a processor
The reports our customers publish, and the audiences they publish to, belong to them. If you were sent a link and signed in to read something, the organisation that published it is the controller of that report and of the record that you opened it. We host and serve it on their instructions and do not decide what goes in it.
So if you want a report corrected, taken down, or your access to it removed, ask the organisation that published it — they can act immediately and we cannot act on their content without them. If you cannot reach them, write to us and we will pass the request on and tell you that we have.
3.What we collect
We collect what the product needs to work and to be auditable. There is no advertising network, no data broker, and nothing here is sold.
Account and profile
Your email address, your name if you or your identity provider supply one, the organisations and workspaces you belong to, and your role in each. Sign-in itself is handled by Supabase Auth; where your organisation uses single sign-on, we receive the identity assertion your provider sends.
Content you publish
The HTML, Markdown and files you publish, and every prior version. We do not read published content except as automated safety checks require: at publish time we scan uploads for path traversal, unsafe file types, embedded secrets such as API keys, and scripting patterns worth flagging. Those checks are automatic and their findings are stored on the version. Nobody at Deliverd reads your reports as a matter of course.
Access and audience data
Who you granted access to, the workspaces and groups involved, share links and their settings, and the email addresses of external guests together with the one-time codes used to verify them.
Activity and audit history
Who published, opened, shared, changed or was denied access to what, with a timestamp. Audit records include the IP address the action came from; records of a report being viewed include the browser user agent. This history is insert-only by design — see the Security page — because an audit trail an administrator can quietly edit is not an audit trail.
Billing
On paid plans, Stripe processes the payment. Card numbers go to Stripe directly and never reach our servers; we store the customer and subscription identifiers, your plan, and the invoice history Stripe reports back.
Email delivery
A log of the transactional email we sent you — recipient, template and whether it was delivered — so that a missing invitation can be diagnosed.
Approval requests, if your organisation screens them
On Business and Enterprise, an administrator can switch on the ethics model screen. While it is on, each approval request an agent makes — its title, description, action and input — is sent to Anthropic for a model to suggest concerns for the approver. Fields an action marks restricted are never sent, and nothing is sent while the screen is off, which it is by default.
The chat assistant on these pages
If you ask the chat assistant on our public pages a question, the conversation, and the address of the page you are on, is sent to Anthropic for a model to answer it. We do not store the conversation: it stays in your browser tab until you close it. It reaches us only if you send it to the team with your name and email, and then it is kept as a contact message, like one sent through the contact form.
Guides you request
If you ask for a guide on our website, we keep your name, email, organisation and role if you give them, whether you asked for product news, the campaign tags and referring page you arrived from, and your IP address and browser for abuse checks. We use them to email you the link, to count whether the link was opened, and to follow up about the guide. We send product news only if you ticked the box. To be removed, write to support@deliverd.dev.
Slack, if your organisation connects it
When an administrator adds the Deliverd app to a Slack workspace, we keep the workspace's id and name, and the app's token for it; each approver's Slack member id, once they first press a button; where each request was sent: the direct message and the message's timestamp. The token is encrypted at rest. To find an approver and to confirm who pressed a button, we look up a member’s email address in Slack; we do not store it beyond the link to their account. Slack also sends, with each button press, details such as the member’s display name and the message itself; we read only which button, which request and which member, and keep none of the rest. The app cannot read messages, channels or files, and does not. Removing the app from the workspace deletes all of the above. See the Slack app page.
Marketing-site analytics
On these public pages we count visits and measure page speed with Vercel Web Analytics and Speed Insights. They set no cookies and store nothing on your device: each visit is counted by the page address, referrer, country and device type, without identifying you, and the count runs only on these pages.
Google Analytics, only if you accept. Nothing is loaded from Google until you do, and it covers these public pages alone: never the product, never a published report. Besides page views, it records a few interactions: clicks on a sign-up button, and where on the page it was; copying a code sample; the words typed into the docs search; whether a docs search found nothing; that the contact form, the chat assistant's form for reaching a person, or the guide request at /ebook was sent (never what was in it); reaching the pricing section; which of the two buttons at the top of the home page was clicked; whether the developer or the business starting point on the home page was followed; how far through the home page walkthrough a visitor stepped; clicks on a plan's button, and which plan; clicks on a button to book a governed AI pilot, and where on the page it was; clicks on a comparison page's sign-up button, and which comparison; that the partner application was sent (never what was in it); that the chat assistant was opened (never what was asked). Nothing you type into a form is sent, apart from the words you type into the docs search. See the Cookie Policy.
4.Why we are allowed to hold it
Under the GDPR, each of the above rests on one of these bases.
| Data | Legal basis |
|---|---|
| Account, profile, organisation membership | Performance of our contract with you or your organisation. |
| Published content, versions, access grants | Performance of that contract — this is the service itself. |
| Audit history, IP addresses, safety scanning | Our legitimate interest in a service that can be secured, audited and defended against abuse, and our customers' legitimate interest in proving who saw what. |
| Guest email addresses and verification codes | Performance of the contract with the customer who shared with you, and our legitimate interest in verifying that a link reached the right person. |
| Billing records | Contract, and legal obligation for tax and accounting records. |
| Approval requests sent to the ethics model screen | Performance of the contract with the organisation that switched it on, on whose instructions we send them. |
| Marketing-site page counts and page speed (Vercel) | Legitimate interests: knowing which pages are read and keeping them fast. Nothing is stored on your device. |
| Marketing-site analytics (Google) | Your consent, withdrawable at any time. |
Where we rely on legitimate interests we have weighed them against your rights, and you can object — see section 8.
6.Where your data is processed
Accounts, access grants, audit history and published files are stored in the United Kingdom (London), and the application code that serves the product and streams reports runs in London too. Static files — scripts, styles and images — are served from Vercel’s global edge network. Some subprocessors are in the United States: payments (Stripe), email (Resend), analytics on the marketing pages if you accept it (Google Analytics), the ethics model screen if your organisation switches it on (Anthropic), and the product tour on the home page if you start it (Supademo).
Transfers out of the European Economic Area rely on the European Commission’s Standard Contractual Clauses with each provider, and on the UK adequacy decision for storage in the United Kingdom. If your organisation needs processing confined to a particular region, write to us before you commit — we would rather tell you what is true than have you discover it in a questionnaire.
7.How long we keep it
| Data | Kept for |
|---|---|
| Account and organisation records | As long as the account exists, then deleted within 30 days of a verified deletion request. |
| Published reports and their versions | Until you delete them, or the organisation is closed. |
| Audit history and view records | Your plan's retention window — 7 days on Free, 90 days on Team, 180 days on Business Starter, 365 days on Business and Enterprise, or longer on Enterprise where an administrator sets it (up to ten years). Never less than 7 days, whatever the setting. |
| Security and billing audit events | Exempt from the window above and kept for the life of the account, because they are the records most needed after an incident. |
| Share links and guest verifications | Until the link expires or is revoked. Verification codes are short-lived and single-use. |
| Slack workspace tokens, member links and message records | Until the app is removed from the workspace or its token is revoked, then deleted at once. |
| Billing records | Seven years, as tax and company law require. |
| Marketing-site page counts and page speed (Vercel) | Aggregated by Vercel, for the period its analytics service keeps them. |
| Marketing-site analytics (Google) | Google Analytics' own retention, up to 14 months. Stops being collected the moment you withdraw consent, and its cookies are deleted from your browser. |
8.Your rights
If you are in the EEA or the UK you have the right to access a copy of your personal data, to have it corrected, to have it erased, to restrict or object to how we use it, and to receive it in a portable format. Where we rely on consent you can withdraw it at any time, and withdrawing is as easy as giving it.
Email support@deliverd.dev and we will respond within 30 days. We may need to confirm who you are first, and we will only ask for what is necessary to do that.
Remember section 2: if your request concerns a report someone published to you, the organisation that published it holds the decision. We will tell you who they are where we are able to.
You can also complain to a supervisory authority. Ours is the Data Protection Commission in Ireland (6 Pembroke Row, Dublin 2, D02 X963, Ireland), and you may instead complain in the country where you live or work.
9.How we protect it
Published content is treated as untrusted and served from a separate origin that never sees your product session. Access is re-evaluated on every single request rather than once at the door, credentials are stored as hashes, and the audit trail cannot be edited — including by us.
The Security page sets all of this out in detail, along with the things the product does not do yet.
10.Children
Deliverd is a business product and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, write to us and we will delete it.
11.Changes to this policy
When this policy changes in substance we update the date at the top of the page, and for changes that materially affect account holders we email the administrators of each organisation at least 14 days before the change takes effect. Continuing to use the service after that date means the new version applies.
Questions about any of this go to support@deliverd.dev.