Privacy Policy

What Unlabelled knows about you, why, and what you can do about it.

Effective: 16 October 2026

Who We Are

Unlabelled is operated by Unlabelled SL (NIF ESB65395956), registered at Font de Cabrera 17, 08348 Cabrils, Spain.

Contact: privacy@unlabelled.cc

The Parts of Unlabelled

Unlabelled is made up of separate parts: the public website, the tools you use, and the service that handles sign-in. They use separate systems and collect different information, so we explain each one separately below.

Below, “the CMS” means Unlabelled CMS, “the Inbox” means Unlabelled Inbox and “Radar” means Unlabelled Radar.

The tools are separate from each other. Each has its own storage, and access to one does not give access to the other: the CMS cannot see your mail, and the Inbox cannot see the websites you edit. The public website can see neither.

Unlabelled is designed as a growing collection of tools. New tools will be added over time. We will update this privacy policy before a new tool starts collecting or processing information in a way that is not already described here.

The Short Version

• If you are only reading unlabelled.cc, we do not collect anything about you beyond what is technically necessary to deliver the website. There are no advertising trackers and no analytics cookies.
• If you have an account, we hold your name and email address to run it.
• If you use the CMS, what you publish is saved in the source code repository of the website you edit, and your name and email address become part of that repository’s history.
• If you use the Inbox, it reads the mail in the mailboxes you connect so that it can show it to you, and acts on that mail only as you instruct. What your mail provider hands us to reach a mailbox is stored encrypted.
• We do not sell personal data, we do not use it for advertising, and we do not use your content or your mail to train AI models.

Part A: The Website, unlabelled.cc

Unlabelled SL is the data controller for everything in this part.

Visitors

The website uses no cookies for analytics or advertising, and no analytics service is active on it. The only thing stored in your browser is your light or dark appearance preference. It stays on your device and is never sent to us.

Like every website, the servers that deliver these pages process your IP address and basic details of each request in order to deliver the page and protect the site from abuse. Those servers are operated for us by Cloudflare.

We keep no log of individual visits ourselves.

The website has no forms. If you write to us by email, we use what you send only to answer you.

Part B: Unlabelled CMS, cms.unlabelled.cc

This part applies when you use Unlabelled CMS to write or edit the content of a website.

Our Role, and the Role of Whoever Runs the Website

For your Unlabelled account, meaning your name, email address, sign-in and permissions, Unlabelled SL is the data controller.

For the content of a website, meaning its posts, pages and images, the company or person who runs that website decides what is published and who may edit it. Where that content contains personal data, for example a person named in a post or visible in a picture, we handle it on their behalf and only in order to provide the tool.

We do not look through website content for our own purposes, and we do not use it to train anything.

If your company needs a data processing agreement under Article 28 GDPR for its use of Unlabelled, write to privacy@unlabelled.cc.

What an Account Holds

• Your name, email address and username
• A record of the permissions you have been given, meaning which websites you may edit
• Session information needed to keep you signed in

What the CMS Holds

The CMS has no database of its own. What you write and upload is saved directly in the source code repository of the website you edit, which is hosted at GitHub:

• Posts and pages, with their titles, text, tags and search-engine settings
• The images and documents you upload
• A history of every change, recording who made it and when

Publishing Writes Your Name Into the Website’s History

This is the part most services like this do not have, and we would rather be upfront about it than bury it.

When you publish or edit a post or page, the change is saved to the website’s repository, and the change is recorded under your name and the email address on your account. If that repository is public, your name and email address on that change are publicly visible, in the same way as on any public GitHub repository.

This is fundamental to how the CMS works. Every change is a recorded version, which is also why nothing is ever silently lost, so we cannot offer editing without it. If this is a concern, use an email address you are comfortable having attached to public changes, or ask us about a display name that is not your legal name at privacy@unlabelled.cc.

Who Can See It

• Other editors of the same website can see the content, and your name on the changes you made.
• Anyone, once content is published, can read it on the website it belongs to. If the website’s repository is public, anyone can also see its history.
• We can access website content when that is necessary to keep the service running or to help you at your request.

Cookies and Browser Storage in the CMS

The CMS uses only what is strictly necessary to sign you in and keep you signed in, so there is no cookie banner. At present it uses:

• tcm_session, which keeps you signed in for up to 12 hours or until you sign out
• a second cookie that exists for a few minutes while you are signing in

Your appearance preference is stored in your browser’s own storage. It stays on your device and is never sent to us.

Legal basis: performance of the contract between you, or your company, and us. We cannot provide an editing account without this information. For the history of changes, we also rely on our legitimate interest, and the website owner’s legitimate interest, in being able to follow who changed a shared website.

Part C: Unlabelled Inbox, emee.unlabelled.cc

This part applies when you use Unlabelled Inbox.

Our Role, and Your Role

For your Unlabelled account, Unlabelled SL is the data controller.

For your mail, you decide which mailboxes to connect and what is sent from them. Mail naturally contains personal data about the people you exchange it with. We handle it on your behalf and only in order to provide the tool to you.

We do not read through your mail for our own purposes, and we do not use it to train anything.

If your company needs a data processing agreement under Article 28 GDPR for its use of the Inbox, write to privacy@unlabelled.cc.

The Mailboxes You Connect

You choose which mailboxes to connect. For each one we store:

• its email address and its provider;
• what the provider gave us to reach it. For Gmail, that is an access token issued by Google after you give permission on Google’s own page. For iCloud, it is the app-specific password you created for the Inbox.

We never receive the password of your Google or Apple Account.

These credentials are encrypted before they are stored, with a key that is kept apart from the database. They are never sent to your browser and never written to logs.

What the Inbox Holds

To show, search and organise your mail, the Inbox reads the messages in the mailboxes you connect, through the provider, and keeps a copy in its database:

• senders and recipients, subjects and dates;
• the content of messages;
• information about attachments;
• whether a conversation is read, archived, snoozed or muted;
• the labels you create or bring in from Gmail, and which conversations carry them;
• the notes you write to yourself on a conversation or about a person you exchange mail with, and your own name for a conversation if you give it one;
• the snippets of text you save to reuse;
• the notes you write for a day in the calendar’s journal;
• messages you are writing, until you send or discard them, including those you have set to be sent later;
• the signature you set for a mailbox;
• the rules you set for sorting your inbox into Important and Other, which can name the addresses or domains of people you exchange mail with;
• the colours and the style sheet you choose for how the Inbox looks;
• files you attach to a message you are writing, until it is sent or discarded.

Files attached to mail you receive are not copied into the Inbox. When you open one, the Inbox fetches it from your mailbox at that moment and passes it to your browser.

When you reply, forward, archive, label, delete or mark a message, the Inbox makes that change in your mailbox on your instruction, and sends what you ask it to send. Snoozing or muting a conversation, renaming it for yourself, your notes and snippets, and asking to be reminded are kept in the Inbox only: your mail provider is not told. Deleting moves a message to your mailbox’s own bin. The Inbox never deletes mail permanently.

Messages are shown with their own formatting. Pictures that a message links to on someone else’s server are loaded when you open the message. Your browser fetches them directly from that server, which can tell the sender that you opened the message, when, and from which internet address. You can switch this off in the Inbox’s settings; such pictures are then not loaded until you ask for them in the message. Pictures that travel inside a message itself are fetched from your mailbox, not from the sender.

If you switch on pictures of people in the Inbox’s settings, the Inbox asks Gravatar, a public service of Automattic Inc. in the United States, whether it holds a picture for the address of each person whose mail you open. It sends only a scrambled form of that address (a hash), from our server, and nothing about you or your mail. Someone who already knows an address can recognise its scrambled form. This is off unless you switch it on.

When you choose to unsubscribe from a mailing list, the Inbox uses the way that list itself offers: your browser sends the request straight to the sender, or the Inbox prepares a message for you to send, or it opens the sender’s own page. In each case the sender learns that you asked, and from which internet address or mailbox.

The Inbox has an assistant that you can give instructions to in your own words, such as “reply that Thursday works and file this under Receipts”. It is off unless you switch it on. When you give it an instruction, the Inbox sends that instruction, the text of the conversations you selected for it, the names of your labels and your own addresses to an AI model: Claude, a model made by Anthropic, run for us by Google Cloud inside the European Union, in the same Google Cloud account the Inbox itself runs in. The model answers with the steps it proposes, and the Inbox carries them out with the same actions its buttons use. Filing, such as labelling, archiving or snoozing, happens at once and can be undone. A message is only prepared as a draft, and an event as a filled-in form: nothing is sent or added until you do it yourself. The Inbox does not keep what it sent to the model or what came back, beyond the drafts and changes you can see. Under Google Cloud’s terms for this service, what is sent is used to produce that answer, is not used to train AI models and is not passed on to others. Nothing is sent to the model while the assistant is switched off, or before you give an instruction.

Information From Google

For a Gmail mailbox, the Inbox asks Google for one permission: to read, compose and send mail, without the ability to delete it permanently. With it, the Inbox:

• reads your messages and their labels so that it can display them;
• creates labels, changes labels and read status, and archives messages or moves them to the bin, when you ask it to. A label you create in the Inbox is also created as a label of the same name in your Gmail mailbox;
• creates drafts and sends messages that you write.

If you choose to connect your calendar, the Inbox asks Google for one further permission: to see the events of your calendars and to add or change events. With it, the Inbox:

• reads the events of the day you are looking at, from Google, at that moment, so that it can show them beside your mail. It does not keep a copy of your events;
• adds an event to your calendar, or changes or deletes one, when you ask it to. If you choose to invite people or to tell them about a change, Google sends them the message.

The Inbox does not share your calendars or change their settings. You can use the Inbox without connecting a calendar.

the Inbox’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• we use Gmail and Google Calendar data only to provide and improve the mail and calendar features you see in the Inbox;
• we do not transfer it to others, except to the providers listed below as needed to run the service, where the law requires it, or, only if you switch on pictures of people, the scrambled address described above to Gravatar. If you switch on the assistant, the conversations you select for an instruction are processed by the AI model described above, at Google Cloud, which is one of those providers;
• we do not use it for advertising, and we do not sell it;
• we do not use it to develop, improve or train generalised AI or machine-learning models. The assistant uses a model to work out what you asked for; your mail is not used to train that model or any other;
• no person at Unlabelled reads your mail, unless you ask us to for support and give explicit permission for the specific messages, or it is necessary for security purposes or to comply with the law.

Who Can See It

• You. A mailbox you connect is visible only in your own account.
• We can access the data the Inbox holds when that is necessary to keep the service running, within the limits set out under Information From Google above, which we apply to every mailbox, not only Gmail.

Disconnecting a Mailbox

• Disconnecting a mailbox in Settings deletes its stored credentials and everything the Inbox copied from it. Your mailbox at the provider is not changed.
• Withdrawing permission at the provider stops the Inbox’s access at once. For Gmail, do this under “Third-party apps and services” in your Google Account. For iCloud, revoke the app-specific password in your Apple Account.

Cookies and Browser Storage in the Inbox

The Inbox uses only what is strictly necessary to sign you in, keep you signed in and connect a mailbox, so there is no cookie banner. At present it uses:

• emee_session, which keeps you signed in for up to 12 hours or until you sign out
• emee_idt, kept for the same time, so that signing out of the Inbox also ends your sign-in
• emee_pkce, which exists for at most ten minutes while you are signing in
• emee_gconnect, which exists for at most ten minutes while you are connecting a Gmail mailbox

Your preferences, such as light or dark appearance and whether the sidebar is shown, are stored in your browser’s own storage. They stay on your device and are never sent to us. The colours and style sheet you choose for the Inbox are the exception: they are kept with your account, as described above, so that they apply on every device, and your browser keeps a copy so that the Inbox looks right before it has loaded.

Legal basis: performance of the contract between you, or your company, and us. We cannot provide the inbox without this information.

Part D: Signing In

Signing in is handled by an identity service that we operate ourselves using Keycloak. It is separate from the individual tools. A tool never sees your password. It only learns from the identity service who you are.

• What it holds: your name, email address, username and password. Your password is stored only in a scrambled form that cannot be read back by us or anyone else.
• How accounts are created: by you, when you register, or by us. A new account has no access to any tool until we grant it. Registering does not give any permission by itself.
• Cookies: the identity service sets cookies on its own address to recognise that you are signed in and, if you choose “Remember me”, to remember your sign-in. These cookies are strictly necessary and are not used for anything else.
• Where you will see it: while you sign in, the address bar shows the address of the identity service instead of the address of the tool you are opening. This is expected.

Unlabelled SL is the data controller for this part.

Legal basis: performance of the contract.

Part E: Unlabelled Radar, radar.unlabelled.cc

Radar is in development. What it shows today is a demonstration with sample data. It has no accounts, sets no cookies, stores nothing in your browser, and does not ask for or keep anything about you.

Like the website, the servers that deliver Radar process your IP address and basic details of each request in order to deliver the page and protect it from abuse. Those servers are operated for us by Google Cloud.

We will update this page before Radar opens accounts or connects to the data of your website.

Unlabelled SL is the data controller for this part.

Where the Data Is and Who Handles It

The tools use separate storage. The CMS cannot read your mail, and the Inbox cannot read the websites you edit.

Cloudflare, Google, Microsoft and Neon are based in the United States. Where personal data leaves the European Economic Area, the transfer relies on the EU–US Data Privacy Framework and/or Standard Contractual Clauses.

There is currently no payment provider. We will update this page before that changes.

How Long We Keep It

• Account data is kept for as long as your account is active, plus a reasonable period afterwards in case you return.
• Website content in the CMS is kept for as long as the website’s repository exists. Its history of changes is, by design, permanent. This is a genuine limit on our ability to erase past entries in that history without damaging it for everyone else who uses the same repository. We will always remove what we can, meaning your account, your access and future data, even where individual past entries cannot be rewritten.
• Mail in the Inbox is kept for as long as the mailbox stays connected. Disconnecting a mailbox deletes its stored credentials and everything the Inbox copied from it. Deleted data may remain in short-lived recovery copies of the database, which expire on their own.
• Sign-in sessions end after 12 hours, or when you sign out.

To have your account erased completely, write to us and we will do it within one month.

Your Rights

Under the GDPR you have the right to:

• Access the personal data we hold about you
• Rectify inaccurate data
• Erase your data, subject to the limit on a website’s history of changes described above
• Restrict or object to processing
• Port your data to another provider
• Complain to a supervisory authority. In Spain, that is the Agencia Española de Protección de Datos.

To exercise any of these rights, email privacy@unlabelled.cc.

If your request concerns material that belongs to somebody else, for example a post on a website run by another person, or a message in another person’s mailbox, the decision belongs to that person. We will pass your request to them and help them act on it.

Data Protection Officer

Given the scale of our processing, we are not required to appoint a Data Protection Officer under Article 37 GDPR. Send any data protection question to privacy@unlabelled.cc.

Children

Unlabelled is not directed at children, and we do not knowingly collect personal data from anyone under 16.

Changes to This Page

As Unlabelled grows, this policy will be updated when new tools introduce new ways of collecting or processing personal data.

If this policy changes materially, we will update the effective date above and, where we reasonably can, tell account holders directly.