Privacy Policy
Last updated 12 October 2026
This policy explains how adminn (“we”, “us”, “our”) collects, uses, discloses, and protects personal data in connection with the adminn dashboard and connected-mailbox processing (together, the “Service”). It is written for two audiences: businesses that hold an account with us, and the individuals whose enquiry email a business's connected mailbox receives. Please read it alongside our Terms of Service, which governs use of the Service itself.
1. Scope & definitions
This policy applies wherever adminn determines the purposes and means of processing personal data — principally, account and billing data for the businesses we contract with. Where a business uses adminn to process its own customers' enquiries, the business is separately responsible for its own privacy notices to those customers; see “Controller and processor roles” below.
In this policy:
- “Business” means any business — of any kind — that holds an account with us.
- “End Customer” means a person who emails a Business's connected mailbox.
- “Customer Data” means the data a Business or its End Customers submit through the Service — email conversation transcripts, extracted lead fields, mailbox content, and contact details.
- “Personal Data” has the meaning given in applicable data protection law (e.g. UK and EU GDPR) — broadly, any information relating to an identified or identifiable individual.
2. Controller and processor roles
We are the controller of Business account data — the information a Business's users give us to create and administer an adminn account (see §3.1 below) — and we decide how that data is used to operate, secure, and improve the Service.
The Business is the controller, and we are the processor, for Customer Data relating to End Customers. Businesses decide what qualifying questions to ask, what to do with a qualified lead, and how to respond to End Customers; we process that data only on the Business's instructions, as set out in our Terms of Service and this policy. If you are an End Customer and want to exercise a data protection right over your enquiry, the Business you contacted is usually the right place to start — see §14.
3. Data we collect
3.1 Business account data
When a Business signs up and configures its account: the signing user's email address and authentication credentials (handled by Supabase Auth — we never see a plaintext password), business name, branding (colour, logo URL, tone of voice), the qualifying questions configured for its two enquiry categories, a Calendly link if provided, and notification preferences.
3.2 Connected mailbox data
If a Business connects a mailbox — Gmail or Outlook through OAuth, or any other email account (such as Yahoo, iCloud, AOL or a work address) through IMAP/SMTP with a password or app password the Business enters — we access, scoped to that single mailbox only, incoming enquiry emails (sender name and address, subject, body, and thread identifiers) needed to draft a qualifying reply, and the ability to send a reply once a Business's agent approves it. From that correspondence, our AI also extracts structured fields (e.g. budget, timeline, and whatever else the Business has configured) and any contact details volunteered (name, email, phone number, and a reference for what the person is enquiring about). We request read and send scopes only; we do not read calendar, contacts, or any other data in the connected account, and we never send an email without a human clicking “Approve & send.” For IMAP/SMTP connections we only read new messages in the inbox, and file a copy of each reply you send in your Sent folder. The OAuth refresh token issued for a connection (or, for IMAP/SMTP, the server settings and password the Business entered) is encrypted at rest with AES-256-GCM and used solely to keep that connection working.
3.3 Technical & usage data
Standard web server and hosting logs generated by our infrastructure providers (e.g. Cloudflare) — request timestamps, response codes, and IP addresses — retained by those providers under their own standard log-retention windows, and used by us only for reliability, diagnostics, and abuse prevention.
4. Sources of data
We collect data directly from Businesses (account setup, configuration forms) and directly from End Customers as they email a Business's connected mailbox. Where a Business connects a mailbox, we also receive data from that mailbox provider (Google or Microsoft) via OAuth, strictly limited to the inbox the Business authorised.
5. Legal bases for processing
Where UK/EU GDPR applies, we rely on the following legal bases:
- Performance of a contract — processing Business account data and Customer Data to provide the Service a Business has signed up for.
- Legitimate interests — securing the Service, preventing abuse (e.g. rate limiting), diagnosing faults, and improving reliability, balanced against individuals' rights.
- Legal obligation — where we must retain or disclose data to comply with the law.
- Consent — where an Business or End Customer has separately given consent, for example to receive a specific communication.
Where we act as a processor for Customer Data, the Business is responsible for identifying its own lawful basis for collecting and using its End Customers' data.
6. How we use data
We use the data described above to:
- run the qualifying conversation and generate the next question or reply;
- extract structured lead fields and compute a lead's hot/warm/cold score;
- draft — and, once approved, send — email replies on the Business's behalf;
- notify a Business's team by email when a new enquiry arrives or a lead qualifies;
- display leads, transcripts, and extracted fields in the Business's dashboard and inbox;
- authenticate users and enforce tenant isolation between Businesses;
- monitor, rate-limit, and secure the Service against misuse; and
- diagnose faults and improve the Service's reliability and features.
We do not use Customer Data to serve advertising, and we do not sell personal data.
7. AI processing & automated decisions
Conversation and email content is sent to an AI provider (currently Google Gemini, with Anthropic as a configurable fallback) solely to generate the next question or reply and to extract structured fields from the conversation. We do not use Customer Data to train our own models, and our AI providers process requests under their standard API terms, which do not permit using API inputs to train their consumer models.
A deterministic scoring rule — not an AI call — turns extracted fields into a hot/warm/cold score. This scoring, and the AI-drafted reply, are decision-support tools for the Business's human agents: no email is ever sent, and no lead is rejected or actioned, without a person reviewing it. If a scripted, non-AI fallback is in use (for example because no AI provider is configured), the same principle applies — a human always makes the final call on outbound replies.
8. Where data is stored
By default, Business and lead data is stored in adminn's shared Supabase database (Postgres), isolated per Business with row-level security policies enforced at the database layer, so that one Business's authenticated users can never read or write another Business's data — including via a direct API call.
Businesses may optionally connect their own, separate Supabase project (Settings → Data storage). Once configured, that Business's lead and transcript data is written directly to the Business's own project instead of ours, and we do not retain a copy on our infrastructure. In that configuration, the Business becomes responsible for that project's own security, availability, backups, and applicable data protection obligations as the operator of that database.
10. International transfers
Our sub-processors operate infrastructure in multiple regions, which may include locations outside the United Kingdom or European Economic Area. Where personal data is transferred internationally, we rely on the transfer mechanisms our sub-processors make available — such as the UK International Data Transfer Addendum or the EU Standard Contractual Clauses — to ensure the data continues to receive an equivalent level of protection.
11. Data retention
We keep Business account data and Customer Data for as long as the Business's account remains active, so Businesses retain a usable history of their leads and conversations. Specifically:
- Account & configuration data — retained until the Business deletes its account, or asks us to delete it.
- Leads, transcripts & extracted fields — retained for the life of the Business's account, unless the Business has configured its own separate database (in which case we hold no copy), or the Business asks us to delete specific records.
- Mailbox OAuth tokens — deleted immediately when a mailbox is disconnected, or on account deletion.
- Rate-limiting records — held in memory only, and expire within minutes.
We will delete or anonymise data that is no longer needed for these purposes, subject to any legal obligation to keep it longer.
12. Security
We apply technical and organisational measures appropriate to the risk, including: database-level tenant isolation via Postgres row-level security, so cross-tenant access is blocked even if an application bug were to attempt it; encryption of mailbox OAuth refresh tokens and IMAP/SMTP credentials at rest (AES-256-GCM); encryption in transit (TLS) for all traffic to the Service; rate limiting on public-facing endpoints (sign-up, sign-in, password reset) to reduce automated abuse; and least-privilege access to production systems. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security, but we design and operate the Service to reduce this risk throughout. If we become aware of a data breach affecting your personal data, we will notify affected Businesses and, where legally required, relevant supervisory authorities and individuals, without undue delay.
14. Your rights
Depending on where you are located, you may have some or all of the following rights over your personal data, for example under UK/EU GDPR:
- to be informed how your data is used (this policy);
- to access a copy of the data we hold about you;
- to have inaccurate data corrected;
- to have your data erased, in certain circumstances;
- to restrict or object to certain processing;
- to receive your data in a portable format, in certain circumstances; and
- to withdraw consent, where we rely on consent, at any time.
To exercise any of these rights over data we control directly (see §2), contact us using the details below. If your request concerns your enquiry with a specific Business, we may need to direct you to that Business, or process the request on their instructions, since they control what happens with their leads' data. If you are in the UK and believe we have not handled your data lawfully, you also have the right to lodge a complaint with the Information Commissioner's Office (ICO), ico.org.uk.
15. Children's privacy
adminn is a business-to-business tool, and the Service is not directed at children. We do not knowingly collect personal data from anyone under the age of 16 through the Service, and if we become aware that we have, we will take steps to delete it.
16. Changes to this policy
We may update this policy from time to time as the Service, our sub-processors, or applicable law change. We will update the “Last updated” date at the top of this page whenever we do, and where a change is material we will additionally notify Business account holders by email. Continued use of the Service after a change takes effect constitutes acceptance of the revised policy.
17. Contact us
For any question or request about this policy or how your data is handled — including data subject access requests — contact us at admin@adminn.co.uk. We aim to respond to legitimate requests within one month.