1code Privacy Policy

Who we are

This policy lives at 1code.uk/privacy. It covers 1code Studio (1code.studio), 1code ID, 1code Mail and the 1code phone app. The part for everyone applies to you wherever you live, and the section for your country adds what is different there.

1CODE X LTD is a company registered in England and Wales, company number 12828341, at 2 Centurion Way, Credenhill, Hereford HR4 7FF, United Kingdom. It operates 1code ID and 1code Mail for everyone, runs 1code Studio, and publishes the 1code phone app on Google Play. It decides what personal information is collected and why. That makes it the controller of your information, wherever you live.

You contract with 1CODE X LTD for 1code, wherever you live. Selling on 1code Store has its own terms and its own privacy policy, which you accept when you set up your store. They say who you contract with and pay for selling, and who is responsible for what you give Store to sell: your identity checks, payout account, Store subscription and payouts.

In this policy, "1code", "we" and "us" mean 1CODE X LTD. "You" means the person using 1code.

This policy applies to all of 1code: Docs, Sheets, Slides, Pdf, Drive, Mail, Channels, Rooms, Calendar, Project, Store, Books, 1code ID and the 1code phone app. It also covers the 1code connector and the developer API.

When you are in charge of the information

Sometimes you, not we, decide what happens to other people's information. Then you are the controller and we handle that information for you, only on your instructions. Our Terms of Service contain the data processing agreement for this, under Article 28 of the GDPR and the UK GDPR.

This applies to:

• Company mailboxes. Addresses like name@company.1code.email belong to the company. The company can see and close them.
• Your audience in Rooms. The people who sign up for, join or pay for your presentations, meetings and rooms, and the people who watch what you share.
• Your shoppers in Store. The people who buy from your online store, sign up for your events or fill in forms on your website.
• Your clients in Books. The people and businesses you send invoices to.
• Your workspace. The people you invite and the content they add, where you run the workspace for your organisation.

If you are in someone else's audience, mailbox, store or client list and have a question about your information, ask them first. If they do not answer, write to us and we will help.

What we collect

We collect only what each app needs to work. Here it is, app by app.

Your 1code account and 1code ID

You sign in to every 1code app with 1code ID. There is no password. In the 1code phone app, you sign in with your phone and your fingerprint or face. The app does not create accounts. To set it up, you can enter your username and the email address your account is registered under, and then the code we email to that address. On the web, you may get a one-time code by email, or a request to approve the sign-in on your phone.

• Account: your name, and your 1code address (such as name@company.1code.email), which is also your username. The name of your company, or "Just me" (the company then takes your name), or, if you were invited, the company you join. An email address, which you confirm with a code when you create your account. The country you are based in: when you create your account on the web, the sign-up page suggests one from your browser's language settings, or from where your connection appears to come from, and you confirm or change it. It decides which country section of our policies applies to you. The app shows it but does not change it. Your language and time zone: the phone app sends your phone's settings each time you save your profile in the app. You can change them on your account page on the web. Your name appears on invitations you send.
• Your profile, if you fill it in: your surname, a postal address and a company name. Only you see them, in the app and on your account page.
• Checks on new names: every new username and company name, and every address a company asks 1code Mail to create, is checked by an AI model for names that try to pass as 1code, a bank or a system mailbox. The model sees only the name. If it flags one, a person on our team decides whether to clear it, suspend the account or close it.
• Your phone: the public half of the key your phone creates, the certificate we issue for it (serial number and dates), the type of phone, and what protects the key. The app also sends the name, model and system version your phone reports (for example "Galaxy A24 · SM-A245F · Android 14"), and we use them as the phone's name. You see it in your list of phones. A company's owners may see it when you change that company's people, leave it, or delete your account while you are its admin or owner (see "Your company's people" below). The private key never leaves your phone.
• Sign-in approvals: which app or website asked, when, which of your phones approved it (or that it came from a sign-in with an email code), the identifier we released for you, and what you agreed to share. We also record which phone approved each AI agent you connect, which phone answered each request from an AI agent, and which phone approved each admin you invite to a company. When you remove a phone, every sign-in and AI connection it approved ends at once.
• Connections: the people you are connected with. You send a request to someone's username, and they accept or decline it. They see your username and email address as soon as you send it. Once they accept, you each see the other's. You choose your key holders from your connections.
• Recovery: the people you choose as key holders, the invitations you send, and any recovery requests with who confirmed them and when. We give you and each of your key holders the other's username and email address. When a recovery of your account starts, we warn every phone on your account, and we email the address your account shows (the email address you confirmed, or your 1code Mail inbox) with a link that can only stop the recovery. We keep only a one-way fingerprint of that link. If you refuse a recovery on your phone, we keep the reason you type there, or the one the app suggests, with the request.
• When you use the app: when you last used it, and when you last answered the weekly check-in. We use this to keep your account reachable for recovery. If you are someone's key holder, their app shows only whether you last used the app in the last 7 days, 7 to 30 days ago, or 30 days ago or more. You are told this when you become one.
• Security and activity records: the time, device and action for sign-ins and important changes, such as adding or removing a phone, choosing a key holder or starting a recovery. Some changes need a fresh fingerprint on one of your phones, such as removing a phone, choosing or removing a key holder, adding an email address, or making someone a company admin or owner or removing one. For these we keep which change it was and a one-time number, so the approval can never be used twice. When a browser asks to remove a phone, we keep the request, how that browser was signed in, and which phone said yes or no. We also keep when your account first used a phone, and whether each phone has used its key yet, to decide when a phone may be added as your account's first phone.
• Where a sign-in comes from: each time a browser shows a code to sign in, to your account page or to an app, we record the country, city and network (internet provider) its connection appears to come from, the kind of browser (such as "Chrome, Mac"), a scrambled form of part of its network address, and the random number in that browser's short sign-in cookie. This happens before anyone signs in. We use them to spot a sign-in code passed on from somewhere else, and to limit how many codes one browser or network can ask for. When your phone approves, we compare them with where your phone's connection appears to be at that moment. We do not keep your phone's. Your phone receives the browser's kind, city and country, and the app shows the kind of browser once you are signed in. When a browser asks to remove a phone, we record its country, city and kind of browser, and show them on your phone.
• Places: the places (a country with a city and a network) where you confirmed a sign-in, by saying it was you or by matching its number. A browser in one of these places is not asked for the number. A place stops counting, and leaves your list, 90 days after you last confirmed it. You can see and remove the places that still count in the app. Saying a sign-in was not you removes its place.
• Identity checks: the app photographs your identity document, and you holding it, only when a business registered with 1code ID asks you through 1code ID to prove who you are. Today the only business registered to ask is our own store service, 1code Store, when you set up selling. The app first shows the name and web address the business is registered under, and sends the photos straight to it. 1code ID keeps no copy on its servers. The app deletes its own copy once the photos are sent, or the next time it opens. Store keeps the photos as "Store and free sites" below says.
• Your company's people: if you are in a company, your role in it, and its history. The history records every person added or invited, every change of role, everyone who is removed, leaves, or closes their account and so leaves, and everyone in it when the company is closed: who did it, to whom, the roles before and after, when, and how it was done, such as "their phone “Galaxy A24 · SM-A245F · Android 14”", "a browser signed in by their phone", "an email-code sign-in", "1code Mail" or "1code". Only the company's owners can read it. Every owner also gets a phone notification and an email when someone is added or invited, when anyone's role changes, and when an admin or an owner is removed, leaves or closes their account. Anyone removed or lowered by someone else is told too, by phone notification and email. If 1code support closes an admin's or an owner's account, the owners are told that.
• Apps you register as a developer: if you register an app to sign people in with 1code ID, its name, its web addresses, and that it is yours.

We never receive your fingerprint, or the face your phone checks when you unlock it. See "The 1code phone app" below.

Docs, Sheets, Slides, Pdf, Drive and Project

• Your content: documents, sheets, decks, PDFs, videos, recordings, pictures, notes, boards and Kanbans, with their titles, folders, comments, checklists, due dates and earlier versions.
• Sharing: who you share with and what they may do.
• Storage use: how much room your files take.
• Workspaces: your workspaces, their members and their roles, and your settings.

Mail

• Account: your 1code ID identifier, your name and your addresses.
• Your mail: messages you send and receive, attachments, drafts, scheduled and snoozed mail, labels, filters, signatures and templates.
• Searches: what you type to search your mail. We use it to find your messages and do not keep it with your mail. It appears in our service's technical logs, which are kept for 7 days.
• Address suggestions taken from your own mail, and your settings (time zone, language, region).
• Sender checks: the results of SPF, DKIM and DMARC checks on incoming mail, spam reports and the senders you block.
• A sending record for each message: when it was sent, from which address, how many recipients were inside and outside 1code, and whether it was delivered. For mail sent outside 1code, also the sender's 1code ID identifier. We do not keep recipient addresses in this record. We use it to stop abuse and to apply the sending limits in our Acceptable Use Policy.
• Contacts: the name and address of people who write to an address in a workspace, when the sender checks show the mail really came from them, and addresses members add by hand. Addresses on 1code.email write only inside 1code. Addresses on your own domain can write outside 1code only to these Contacts, or reply to an email someone sent them.
• Vacation replies: which senders got your automatic reply, so each gets it only once in a while.
• Companies: the company's name and subdomain, its people and roles, invitations (including the personal email an invitation is sent to), aliases, groups, shared-mailbox access and a log of admin actions.
• Keys for mail apps and AI agents: stored only as one-way fingerprints that cannot be turned back into the key.
• Imports: if you bring old mail across, read-only access to your Google or Microsoft account, stored encrypted and deleted when the import ends, or a mail file you upload, also deleted when the import ends.
• DMARC reports that other mail providers send us about mail using our domains. They include the addresses of sending servers.

Channels

• Your messages, replies and reactions, the files you share, the channels you belong to and who else is in them, and which messages have been read.
• What you type to search channels and their posts. We use it to find the results.

Rooms

• Sessions: the rooms you open, the names people type to join, when they joined and left, the chat and questions in the session, and a recording when the host records.
• Your audience: sign-ups (name, email and the answers to questions you set), which session they signed up for, and unsubscribes.
• Paid rooms: who paid, for what and when, and whether the payment went through. Card details go straight to our payment provider. We never see full card numbers.
• Viewing numbers: when someone watches a video you share, we count the view without storing anything on their device. We record the page it was watched on, which parts were played, and the country their connection appears to come from. No name or account is attached.
• Camera, microphone and screen: used only while you are in a meeting with them on, or while you record after pressing record. Everyone in a session is shown when it is being recorded. Live sound and video pass through our provider's real-time network. When a session is not recorded, any short pieces of it that passed through our storage are deleted within a day. When a presenter shows a web page to the room, the page passes through our servers and we keep nothing of it.

Calendar

• Your calendars and events (titles, times, places, notes, repeats and reminders), your settings, and the dates other 1code apps put there for you, such as due dates and scheduled rooms.
• Calendars you add by web address. We fetch them every few hours and show them to you.
• If you turn on a calendar's subscribe link, anyone with that link can see that calendar's events. Replace the link to stop the old one.

Store and free sites

• Your business: your name, email, phone number and business details.
• Identity checks before you can sell: you must pass identity checks (KYC) and add a payout account before you can sell. We ask for an identity document, a company registration certificate where you trade as a company, a bank letter and proof of address. When we ask for it through 1code ID, you can also photograph your identity document, and yourself holding it, in the 1code phone app. These are kept in private storage. Only you and our compliance staff can see them. 1code Store's payment provider, Paystack, never receives them or a link to them. To check your bank account and pay you, it receives only the account number, the bank code, the account holder's or company's name, the company registration number where you trade as a company, and your store's name.
• How identity documents are checked: you type in the details from your documents (your name, ID number, company and bank details). Fixed rules then check those details against each other. A person on our team checks your documents by eye and approves every application, so no decision about selling is made by a computer alone. No AI reads your documents.
• Your shoppers' orders: name, email, delivery address and what they ordered. You are in charge of this information (see above).
• Your event attendees: name, email, the tickets they take and, if they give it, a mobile number, so you can send them messages about the event by email or SMS. You are in charge of this information (see above).
• Free sites at <name>.1code.host: what you publish. Anyone can see a published site. We count visits from Cloudflare's own server records, without scripts or cookies in your visitors' browsers. If your site collects information from visitors, such as through a form, you are in charge of that information.

Books

• The invoices you create: your clients' names, contact details, billing addresses and tax numbers, what you sold, the amounts and whether they are paid. You are in charge of your clients' information (see above).

Domains

• If you buy a domain for your store in 1code Store, Store passes your name and contact details to the registrar (domains.co.za) and the registry for that domain. Some of it may be published in public domain records where the registry's rules require it.

Billing

• Your plan, your invoices, your billing name and address, and whether each payment went through. Paid 1code plans are not on sale yet; when they are, card details will go straight to Stripe. A 1code Store subscription, or a domain bought for your store, is billed by 1code Store under its own terms, and card details go straight to Paystack. We never see full card numbers.

When you contact us, give feedback or accept a policy

• Contact form: your name, email, company if you give one, your message, and the country your connection appears to come from.
• Feedback: what you post, the name shown with it, and your votes.
• Acceptance records: which version of each policy you accepted, the country you gave, and when. In 1code ID, also the network (IP) address and the browser or app you accepted from. In Store, also the network (IP) address.

Security records and connection data

• Records of sign-ins, failed attempts and changes to your account.
• Where a sign-in appears to come from: the country, city and network, the kind of browser, and a scrambled form of part of the network address, recorded each time a browser asks for a sign-in code, even before anyone signs in. For a request to remove a phone, only the country, city and kind of browser. We keep them with the record of the sign-in or request. Where your phone's connection appears to be is compared at that moment and not kept.
• To limit repeated attempts: a scrambled form of part of the network address that asks for an email code or checks names at sign-up, and the full network address of a phone that enters a code to add itself to an account. "How long we keep it" says for how long.
• Our hosting provider sees connection details (IP address, browser, time) as it delivers and protects the service, and keeps them only briefly.
• Our service writes technical logs as it runs, such as part of an account's identifier, a company's name and what happened. In Mail they also hold the web address of each request, which can name the mailbox, the folder or label, your time zone and the words of a search. Our hosting provider keeps them for us for 7 days.
• Until you give your country, we use the country your connection appears to come from to choose which country section and prices to show. We do not store it, except where this policy says so.

Cookies and your browser

We set only what 1code needs to work:

• a sign-in cookie, for up to 30 days unless you sign out;
• a short cookie while you sign in, for up to 10 minutes;
• a cookie that holds the access a shared link gives you, for up to 12 hours;
• a marker that tells a page you are signed in;
• your theme, language and similar choices, kept in your browser.

These do not track you across other websites and are not shared with anyone. We have no advertising or analytics cookies and no tracking scripts from other companies. We count views of shared videos without storing anything on your device. The Cookie Policy (1code.uk/cookies) lists every cookie we use and everything our apps keep in your browser.

Where we get it from

Most of it comes from you. We also get information:

• from other people on 1code, when they share something with you, invite you, add you to a company, change your role in it or remove you, send you a connection request, or choose you as a key holder;
• from people who write to you, when their mail or messages reach your 1code address;
• from services and AI agents you connect, such as Google, Microsoft or Slack;
• from Paystack, for 1code Store: whether a payment or payout went through, and whether its checks on a seller are complete. Once paid 1code plans are on sale, also from Stripe: whether a payment went through;
• from domain registrars and registries, about domains you buy through us;
• from other mail providers: sender checks, bounce notices and DMARC reports;
• from your phone and browser, as you use 1code (see "Security records and connection data" and "Cookies and your browser").

Do you have to give it to us?

You choose what you give us. Some things are needed for a service to work:

• An account needs your name, your 1code address, your company's name (or "Just me", or the company that invited you), the country you are based in, and an email address you confirm with a code. Without them we cannot give you an account. To use the 1code phone app, you also need a phone with a fingerprint, or a face unlock that the phone rates as strong.
• Paying for a plan or a domain needs billing details. Without them you cannot buy.
• Selling needs identity checks and a payout account. Without them you cannot sell.
• A domain needs true contact details, because the registry requires them.

Everything else, such as your surname, a postal address or a connected service, is up to you. Leaving it out only means the feature that needs it will not work.

Why we use it

Some laws ask us to name a legal reason (a "lawful basis") for each use. These are ours.

Where we rely on legitimate interests, we weigh them against your rights, and you can object (see "Your right to object" below). Where we rely on your choice (consent), you can withdraw it at any time. That does not undo what we did before you withdrew it.

What we do not do

• We do not sell or rent personal information.
• We do not show ads or use your information for advertising.
• We do not use your content to train AI, and we do not let our providers train on it.
• We do not add tracking scripts from other companies. The 1code phone app reads codes with an open-source part that works entirely on your phone and sends nothing anywhere. It uses Google Firebase Cloud Messaging only to deliver notifications, and only once notifications are allowed on your phone (see "The 1code phone app").
• We do not make decisions about you by computer alone that have legal or similarly serious effects. Automated checks may block a single message, file or page that matches known malware, phishing or child sexual abuse material. A person reviews every pause or removal, and you can always ask a person to look again.
• We do not send marketing or bulk email, and we do not let anyone send it through 1code. Emails to a Rooms audience are limited to confirmations, links and reminders, and 1code Studio has no way to connect an email-marketing service.
• People at 1code do not read your content, unless you ask us to (for support), we must look into abuse or a security problem, or the law requires it. Automated systems check mail for spam, fake senders and malware.

AI agents you connect, and the activity log

You can connect your own AI agent, such as Claude, ChatGPT or Gemini, to 1code. You do this through the 1code connector (MCP) or our developer API, using your own subscription or your own keys.

• Your AI account stays yours. We never ask for, store or pass on the sign-in details of your AI account.
• You choose what it can do. Nothing is connected until you connect it. You choose its access, for example read, draft or send. You can disconnect it at any time.
• What your AI provider receives. Your AI provider receives what you let your agent read, and handles it under its own terms. It is your provider, not ours, so its privacy policy applies to what it receives.
• Sensitive actions wait for you. When an agent asks to send something outside 1code, pay, publish something publicly, or delete something for good, we ask you to approve it on your phone first. This is on by default. Sending inside 1code and moving something to Trash do not ask by default. You can change each of these settings.
• The activity log. We keep a log of what each connected agent did, when, and what you approved or refused. You can read it at any time. We keep it for one year.
• Keys. The keys we issue for a connection are stored only as one-way fingerprints.

The same rules apply to apps that developers build on our API. An app gets only the access you approve, and you can remove it at any time.

Our own AI features

Where 1code itself offers an AI feature, it runs on our own API keys with our AI providers. It never uses your personal AI subscription. Our AI providers act only on our instructions and may not train on your information. We name them on request.

The 1code phone app

The 1code phone app is published on Google Play and operated by 1CODE X LTD, which is the controller of the information in it.

• Fingerprint and face. Your phone checks your fingerprint or face itself. The app asks only "is this the right person?" and receives yes or no. What your phone checks never leaves it: we never see or store your fingerprint, or the face your phone uses to unlock. A photo of you holding your identity document is something else: see "Identity checks" above.
• Your key. The private key that approves your sign-ins is made on your phone, kept in its protected storage behind your fingerprint or face, and never leaves it.
• Notifications. If you allow notifications, we send them through Google Firebase Cloud Messaging. Google receives a token for your phone and the notification itself. A notification carries only what is needed to show it, such as a sender's name and the subject of new mail. "Remove a phone?" and "Someone is recovering your 1code ID" name no phone and no person. A notice to a company's owners carries the line that describes the change, with the people's addresses and the phone it was made from.
• Camera. Used only to scan codes (to pair a phone, approve a sign-in or confirm a recovery) and, if a business asks you to prove who you are, to photograph your identity document and you holding it. Never in the background.
• Meetings. Join meeting opens the meeting in your phone's browser. The app itself never uses your microphone.
• What the app does not touch. The app does not look through your phone's address book, text messages, photos or files. It opens a file on your phone only when you pick it in Docs or Sheets, shows it there, and sends nothing of it to us. When you edit a file from your Drive in Docs or Sheets, the app saves your changes back to your Drive. Apart from that, the only files it sends are the photos it takes for an identity check (see "Identity checks" above).
• Google's part of the app. The app reads codes with an open-source part that works entirely on your phone and sends nothing anywhere. It gets notifications through Google Firebase Cloud Messaging, and registers with it once notifications are allowed on your phone: they are on by default in the app; Android 13 and later asks you first, older Android allows them unless you turn them off. Firebase Cloud Messaging then receives an identifier for this installation of the app, and the make and model of your phone and the versions of its system and of Google's part, to deliver notifications. Google does this for us, as our processor. Turning notifications off, or signing out, removes this phone from it.
• Google Play. Google collects its own information when you download the app, under its own policies. An iPhone app is planned.

Services you connect

You can connect other services to 1code. Each one is your choice, and you can disconnect it at any time. Each handles your information under its own terms.

• Google Calendar (in Calendar). We read the list of your calendars and the events of the calendars you choose, and show them to you. If you ask, we keep your 1code events in one calendar named "1code Calendar" that we create in your Google account. We touch nothing else. Unlinking removes that calendar, ends our access and deletes what we hold.
• Google or Microsoft mail (to import old mail into Mail). Read-only, and only while the import runs.
• Slack (in Project). We keep your Slack workspace's name, the key Slack gives us (encrypted) and which Slack person is which 1code account. We read a Slack message only when you choose to make a card from it.
• Your AI agent. See above.

We keep the keys these services give us encrypted. We never sell what we receive from them, use it for advertising or train AI on it.

1CODE X LTD'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. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Who processes it for us

These providers handle personal information for us, or for 1code Store where the row says so, only on instructions. Each does so under a written data processing agreement.

Paystack, Stripe, the domain registrars and registries also use some information for their own legal duties, such as fraud checks, anti-money-laundering checks and registry rules. For that use they decide what happens to it themselves, under their own privacy policies.

We also share information:

• with the people you share content with, and the services you connect;
• with the business you are dealing with, when you buy from a store or join a room;
• with the owners of a company you are in: the company's history, which names you when you add, invite, change or remove someone, when someone does that to you, and when you leave or close your account, with the phone or kind of sign-in used. Every addition, invitation and change of role, and every removal, leaving or closed account of an admin or owner, also reaches the owners by phone notification and email;
• between you and your connections and key holders: each other's username and email address (the person you send a connection request to sees yours as soon as you send it), and, for the person a key holder protects, whether that key holder used the app in the last 7 days, 7 to 30 days ago, or 30 days ago or more;
• with authorities, only where the law requires it. We push back on requests that are not lawful, and we tell you unless the law forbids it.

We will tell business customers at least 30 days before we add or replace a provider that handles the information they put in our care.

Transfers between countries

Your information is stored in Western Europe. 1CODE X LTD is in the United Kingdom. Our team works from South Africa. Some providers are in the United States. So your information crosses borders. This is how we protect it:

You can ask us for a copy of these safeguards at privacy@1code.email. We may hide business details in it that are not about your information.

How long we keep it

We keep information only as long as we need it. When you close your account, we delete your data 30 days later, except what the table below keeps longer: what the law requires, records kept in case of a claim, records kept for security and to prevent fraud and abuse, and the names that are never given out again. The table names each one.

We delete data on these schedules automatically.

Security

• Everything is encrypted on its way to and from us, and our storage provider encrypts it at rest.
• There are no passwords to steal. You sign in with your phone or a one-time code, and your phone's private key never leaves it.
• Keys that other services give us are kept encrypted. Keys we issue to apps and AI agents are kept only as one-way fingerprints.
• Private videos are served only through short-lived links.
• KYC documents are kept in private storage that is never public.
• Only people who need it for their work can reach systems holding your information.
• If a breach puts your information at risk, we tell you and the authorities your law requires, in the time it requires. If it affects information you put in our care, we tell you so you can tell the people concerned.

If you find a security problem, please tell us at privacy@1code.email.

Scanning and pausing

To keep people safe, we scan published free sites for phishing, malware, impersonation and other harm. We may pause an account, site or app that causes harm. When we do, we tell its owner why, unless the law or a safety risk stops us, and we tell people who use an app we pause that it is paused. A person reviews every pause or removal. If we pause something at once to stop harm in progress, a person reviews it straight after. Nothing with serious effects is decided by a computer alone.

Children

1code is for people aged 18 or over and is not designed for children. You must be 18 or over to have a 1code account. We do not knowingly collect children's information for an account. If we learn a child has an account, we delete it.

Rooms audiences who join without an account are not targeted at children. If you invite anyone under 18 to a room, you are responsible for having their parents' or school's consent. If you sell to children in your store, you are responsible for any consent their law requires.

If you think a child's information is in 1code without that consent, write to privacy@1code.email.

Your rights and how to use them

Wherever you live, you can ask us to:

• tell you whether we hold information about you, and give you a copy;
• correct it;
• delete it;
• give it to you, or to another service, in a common format;
• stop or limit using it, where the law allows;
• stop using it where we rely on legitimate interests;
• withdraw a choice you made, at any time;
• have a person look again at a decision made by computer, hear your view and let you challenge it.

Your right to object. Where we rely on legitimate interests, you can object at any time, for reasons about your own situation. We then stop, unless we have strong legitimate grounds that outweigh your interests, rights and freedoms, or we need the information to make or defend a legal claim.

You can also do much of this yourself: download a copy of your files and of your 1code ID account, remove a phone, remove a place, disconnect a service or AI agent, and close your account. The download does not hold everything we keep: for the rest, write to us.

Closing your account. In the 1code phone app, go to Settings, then Delete account, and confirm with your fingerprint or face. You are signed out on every phone and in every app at once, and your key holders, connections and AI agents end. We delete your data 30 days later, except what "How long we keep it" says we keep longer. If you are the only owner of a company that other people are in, make someone else an owner first. If you no longer have your phone, the app no longer opens, or you prefer not to use it, write to privacy@1code.email from your account's own email address, with the subject "Delete my account". Your account's own email address is the one you confirmed, or a 1code Mail address your account holds. We confirm it is you before we delete anything, and we answer within one month. We then delete your data 30 days after we confirm it is you, except what "How long we keep it" says we keep longer. To check it is you, we send a one-time link to that address, or, if you still have a phone on the account, ask you to approve on it. The page 1code.uk/delete-account explains these steps.

How to ask. Write to privacy@1code.email. It is free. We may ask you to confirm it is you by approving on your phone with 1code ID. We answer within one month, or sooner where your law requires. If a request is complex, we may need longer, and we will tell you why within that month.

If your information is in a company mailbox, an audience, a store or an invoice, we may pass your request to the business in charge of it, and help them answer.

If we cannot do what you ask, we tell you why.

Complaints

Please tell us first at privacy@1code.email. We acknowledge a complaint within 30 days and tell you what we did about it.

You can also complain to a regulator at any time:

• United Kingdom: the Information Commissioner's Office.
• European Union: the data protection authority where you live, work or where the problem happened.
• Elsewhere: your national data protection authority, where there is one.

Contact details are in the country sections below.

Changes to this policy

When we change this policy, we change the date and version at the top. We tell you by email or in 1code at least 30 days before a significant change applies. We keep a record of which version and which country section you accepted. Accepting this policy means you have been shown it. It is not consent, and we do not rely on it as consent. Where we need your consent, we ask for it separately.

This policy lives at 1code.uk/privacy.

Contact

1CODE X LTD, 2 Centurion Way, Credenhill, Hereford HR4 7FF, United Kingdom.

• Privacy, security, reports of abuse or illegal content, appeals and authorities: privacy@1code.email
• Help, billing and complaints: support@1code.studio

We have not appointed a data protection officer, because the law does not require one for what we do today.