Privacy Policy

Last Updated: 9 September 2026

This Privacy Policy explains how Lumman Ltd handles information in connection with this website, lumman.co. It covers this website only. Other Lumman products and services have their own privacy policies.

1. Who We Are

lumman.co is operated by Lumman Ltd, a company incorporated in England and Wales (Company Number: 15425759) with its registered office at 86-90 Paul Street, London, EC2A 4NE, United Kingdom. For the purposes of UK data protection law, Lumman Ltd is the data controller for this website.

You can reach us at in [at] lumman [dot] co.

2. The Short Version

The public pages of this website are static and informational. They have no accounts, no sign-in, no forms, no payments, and no chat: we do not ask you for personal information there and we do not build a profile of you. We use privacy-friendly, cookieless analytics to understand aggregate traffic, and nothing more. The account and connectors in sections 3.4 to 3.5 are a separate, signed-in service, and what they hold is set out there.

3. What We Collect

3.1 Anonymous Usage and Performance Analytics

We use Vercel Web Analytics and Vercel Speed Insights to measure aggregate page views and page-load performance. These tools are privacy-friendly: they do not set tracking cookies, do not use cross-site identifiers, and do not collect information that identifies you personally. The data we see is aggregated (for example, how many visits a page received), not individual.

3.2 Information Stored on Your Own Device

When you choose a light or dark appearance, your browser saves that preference locally on your device (in your browser's local storage). This preference stays on your device and is never sent to us.

3.3 Hosting and Security

The website is hosted by Vercel. To deliver and protect the site, our hosting provider processes standard technical request data (such as your IP address) transiently, as any web host does. This is handled under Vercel's own privacy and security terms and is not used by us to identify you.

3.4 The Lumman Mail Connector

Lumman Mail Connector - A connector that gives your AI client your own Gmail accounts. This section covers everything it touches.

What it reaches, and why. If you connect a Gmail account to a Lumman account, we ask Google only for the permissions the connector needs to act for you: reading and searching your mail, composing and sending it, organising it with labels and filters, and reading and changing your signature and vacation responder. Each of those is asked for because your AI client can be asked to do it for you, and for no other reason. We never ask for the permission to delete mail permanently, and no tool here empties a bin.

What is kept, where, and for how long. We keep no copy of your mail. Messages, threads, attachments and drafts are read from Google when you or your AI client ask for them, and nothing read that way is kept here.

What we do keep is held in our database, which is operated for us by Supabase and hosted in London:

  • the credential Google issues for that mailbox, encrypted, together with the minimal technical state a durable connection needs - the address, the name you gave it, the permissions Google granted, and whether the connection is one of the ones in use. It is kept until you disconnect that mailbox or delete the account, and no longer;
  • a record of what the connector was asked to do - the tool, the mailbox, Google's own identifier for whatever the call touched, how many recipients a send named, and whether it succeeded. That record never holds a subject, a body, a recipient or an attachment, and it is kept until the account is deleted.

Which AI clients it is passed to, and on whose approval. What the connector reads is passed to the AI client you approved for this connector, and to no other. This release supports two of them: Claude, made by Anthropic, and ChatGPT, made by OpenAI. Neither reaches a mailbox of yours until you have approved it yourself on our own approval screen, and taking that approval back stops it at its next request.

Screening. Before anything moves, its words are screened for prompt attacks by Check Point AI Guardrails, a security service acting as our processor: what a mailbox answers, before it reaches your AI client, and what a message would carry, before it is sent. It receives the words being screened - subjects, message text, the addresses a message names, and the words of a text file your AI client asks for - and nothing we hold about you or your account; it processes them in Ireland and is configured to keep no copy of them, so nothing of what it screened is retained there or here. Every other file a message carries, and every file a send carries, is passed on unscreened. Content it screens as an attack is refused, and a screening that cannot be completed closes that call rather than moving anything unscreened.

Disconnecting. Disconnecting a mailbox withdraws the authorisation at Google and deletes the stored credential. We never discard a Google credential on our own initiative, and a connection that is not in use keeps everything it holds until you disconnect it.

Google's Limited Use requirements. Lumman's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In full, that means:

  1. Use. We use what the connector reads from your mail only to provide and improve the features of the Lumman Mail Connector that you can see on this site, and for nothing else.
  2. Transfer. We transfer it only where that is necessary to provide those features - to the AI client you approved, and to the screening service above - or where the law requires it, or in connection with a merger or acquisition, and then only after telling you and obtaining your agreement.
  3. Human reading. No person reads it, except where you ask us to for a specific message, where it is necessary for security, such as investigating abuse, or where the law requires it.
  4. Prohibited uses. We never use it for advertising of any kind, we never sell it, we never use it for credit decisions or any assessment of creditworthiness, and we never use it to train a generalised artificial-intelligence model. Your own AI client acts on your mail at your request; that is the only model use there is.

3.5 Your Lumman Account

Anyone may create a Lumman account by signing in with Google. From that sign-in we receive only what it carries: the address of the account and Google's own identifier for it. Beside that identifier we store what the account has been opened for.

Holding an account is not access. Connections, purchases and AI-client approvals work only once we have opened the account for them, which we do by hand. Until then the account reaches nothing, and it is told so when you sign in.

You can close the account yourself at any time, on the connector page, and closing it deletes everything. From that moment it reaches nothing; every subscription it pays for is stopped, every authorisation it gave is withdrawn, and everything held here that names you is destroyed. It cannot be undone. Section 8 sets out what survives that and for how long, and the Data Deletion page at lumman.co/data-deletion carries the steps.

3.6 Payments

Paid capacity is sold through our payment provider, Polar, which acts as merchant of record and takes the payment. Your card details go to Polar and never to us: we neither see nor store them. Two Gmail connections cost nothing; beyond them one plan covers this connector, charged by the number of connections paid for, renewed once each period at a period chosen once when the plan is opened, and an addition made mid-period to a yearly plan is settled when it is made. From Polar we keep only what a subscription needs - its identifier there, the connector and account it is for, its state, the capacity it confirms, its interval, and when we last agreed with Polar about it - along with the notifications Polar sends us about it.

4. What We Do Not Collect

Because the public pages have no accounts, forms, payments, or chat, we do not collect or store through them: names, email addresses, passwords, payment or billing details, account or subscription data, chat or conversation history, or advertising and cross-site tracking data. If you email us at in [at] lumman [dot] co, we will of course see that message - but that is your direct choice, not data this website gathers.

5. Cookies

This website does not set tracking or advertising cookies. The appearance preference described in section 3.2 uses your browser's local storage, not a cookie. Our analytics provider is cookieless.

6. Sharing and Disclosure

We do not sell, rent, or trade personal information. Every party that processes what the connector reaches is named here: Vercel, which hosts this website and provides the privacy-friendly analytics above; Supabase, which operates the database described in section 3.4; Polar, our payment provider, for the subscriptions in section 3.6; and Check Point AI Guardrails, the screening service in section 3.4. Each acts as our processor, and there are no others. What the connector reads is also passed to the AI client you approved for it, as section 3.4 sets out. We may disclose information if required to do so by law.

7. International Transfers

Our hosting and analytics provider may process technical data on servers outside the United Kingdom, and the screening service in section 3.4 processes what it is sent in Ireland. Where that happens, it is covered by appropriate safeguards under that provider's terms.

8. Data Retention

The public pages leave no personal records tied to you, and aggregate analytics are retained by our analytics provider in anonymized form under their retention terms. What the account and connectors hold is kept while they exist, and sections 3.4 to 3.5 set out what that is.

You can have everything deleted at any time, without asking us: close the account on the connector page, and the deletion is carried out on its own. The Data Deletion page at lumman.co/data-deletion sets out the steps and what they destroy. One record survives a deletion, and it names nobody - for each subscription the account held, a one-way digest of that subscription's own identity at our payment provider and the moment the deletion completed, with one line for each notification that provider sent about it. It exists so that a late notification about a deleted account is recognised and refused rather than acted on. Nothing in it can be turned back into you, and all of it is destroyed thirteen months after that moment.

9. Your Rights

Under UK GDPR you have rights to access, correct, erase, restrict, and object to the processing of your personal data, and to data portability. The public pages collect nothing that identifies you, and what an account and its connectors hold is set out in sections 3.4 to 3.5. If you have a question or a request, contact us at in [at] lumman [dot] co and we will help. You also have the right to complain to the Information Commissioner's Office (ico.org.uk).

10. Children's Privacy

This website is not directed at children, and its public pages collect no personal information from anyone, including children.

11. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last Updated" date at the top reflects the latest version.

12. Contact Us

Questions about this Privacy Policy or our data practices for this website:

  • Email: in [at] lumman [dot] co
  • Address: Lumman Ltd, 86-90 Paul Street, London, EC2A 4NE, United Kingdom