Privacy Notice
Last updated: 26 October 2026
This notice explains what personal data ByteBloom Compliance uses, why, how long we keep it and what your rights are. It covers only this service, at compliance.bytebloom.tech.
1. Who we are
ByteBloom Limited is the controller of your personal data. We are a company registered in England and Wales, company number 12119259. Our registered office is 341 Rayners Lane, Pinner, Greater London, England, HA5 5EN.
Contact us about anything in this notice at hello@bytebloom.tech. We don't have a data protection officer. Our director, Hisham El-sayed, deals with all data protection questions.
2. What we collect
Account details. Your name, email address and role (member or administrator), when your account was created and your password last changed, and when you agreed to our Terms and which version. If a booking in your mailbox uses another spelling of your name and you tell us it was you, we keep that spelling so we recognise your bookings. We never store your password. We keep only a scrambled version (a hash) that can't be turned back into it.
Invites. If someone invites you, we get your email address from them. We keep a record of the invite: your email address, who invited you, when, and whether it was used.
Access requests. If you ask for an invite, your name, email address and what you tell us about who referred you.
Sign-in sessions. When you sign in, we put a random code in a cookie so you stay signed in. We store only a scrambled version of the code, linked to your account.
Password resets. A record of each reset link we send you and whether it was used.
Security records. The email address and IP address used for each attempt to sign in, reset a password, set up the service or request access.
Trips and flights. The dates you arrived in and left the UK, flight descriptions, any notes, and whether each trip was entered by you or found in a mailbox. For flights you type in: the flight number, departure and arrival airports and dates.
Residence answers. Your starting point (leaver or arriver), your yes or no answers about each tie, and your choice for the 90-day tie.
Review items. Prompts the service creates for you about gaps or questions in your travel history.
Gmail, if you connect it. Your mailbox address, an encrypted access key from Google, the flight details found in your travel emails, and a list of which emails have already been checked. Section 4 explains this in full.
Technical data. When you use the site, our hosting provider records your IP address, browser details, the page you asked for and the time.
Emails we send you. Our email provider keeps a record of each email (address, subject and whether it was delivered).
You need to give us your name, email address and a password to have an account. Everything else is optional, but the estimate depends on what you record.
3. How we use it, and our lawful basis
| What we do | Our lawful basis |
|---|---|
| Run your account and the service you asked for, including counting your UK days and estimating your residence position | Contract: it is needed to provide the service under our Terms |
| Find flights in your Gmail, only if you connect it | Contract: it is an optional feature you ask us to turn on. You can turn it off at any time |
| Keep you signed in | Contract |
| Send service emails: invites, setup links, password resets, password-changed notices and confirmation that your account is closed | Contract, and our legitimate interest in keeping accounts secure |
| Send invites and deal with access requests | Our legitimate interest in running an invite-only service for people who are referred to us or who ask to join |
| Protect the service, for example by limiting repeated sign-in attempts and keeping short-term logs | Our legitimate interest in keeping the service and your data secure |
| Meet legal duties and respond to lawful requests, for example from HMRC or a court | Legal obligation |
Where we rely on legitimate interests, we have checked that our interest is not outweighed by your rights. You can ask us for details.
We don't ask for special category data, such as health, religion or sexual orientation. Your residence answers are yes or no answers about your ties, and are not special category data. Please don't put sensitive details in notes.
We don't use your data for advertising, we don't sell it and we don't build profiles about you. The residence estimate is for your information only. We don't use it to make any decision about you.
4. Gmail and Google user data
What Google asks you to allow. Google's screen asks you to let the service "view your email messages and settings". This is Google's read-only permission. Technically, it covers your whole mailbox.
What the service actually reads. The service searches only for travel emails: emails in Gmail's Reservations category, emails with booking-style subjects (such as "flight", "booking", "itinerary", "e-ticket", "boarding pass", "check-in", "refund", "cancellation", "schedule change", "PNR" or "your trip"), and emails from a list of airlines, travel agents and the systems that send their tickets. On the first sync it looks back to 1 January 2022: trips are counted from 1 January 2023, but flights early in 2023 were often booked in 2022. After that it checks new mail. When we widen the search, it looks back once more, but only reads emails it hasn't checked before.
The service reads each matching email automatically, looking for flight booking data in the standard format airlines use. Many booking emails don't include that format. For those, the service sends the email's visible text (not its attachments or images) to Anthropic's Claude, an AI service, which returns only the flight details the email contains. It does this only when the text looks like a booking (it gives a flight number, booking words such as a booking reference or e-ticket, and a date) and Gmail hasn't filed the email under Promotions or Social. The one exception is an email that a known airline provably sent and that also gives your booking reference, because Gmail files some check-in reminders under Promotions. Sales emails and newsletters are never sent. Some matching emails may not be about flights, for example a hotel booking or a shop's refund. The service keeps nothing from an email unless it contains flight details. It never stores the email itself.
Checking a sender it doesn't know. A booking only counts without you confirming it when it comes from a known airline or travel agent. When a genuine booking comes from a sender the service doesn't know yet, it sends Anthropic's Claude only that sender's web address and one flight from the booking (its flight number, airports and date), never the email, and Claude may search the web to check whether the address belongs to an airline or travel company and whether the flight runs that route. The answer is kept for that web address and used for everyone's bookings from it. Until a sender is found genuine, its bookings wait for you under To check.
What the service keeps. Your mailbox address, the IDs of emails already checked, and, for each flight found: the flight number, airline, departure and arrival airports, dates and times, booking reference, passenger name and whether the booking is confirmed or cancelled. If a booking includes other travellers, their names may be kept with the flight. We use passenger names only to spot bookings made for someone else, so that they don't count as your trips.
When it runs. When you open the app (at most once an hour), when you press Sync now, and once a day in the background.
What it never does. It never sends, labels, moves or deletes anything in your mailbox. Google's access key is stored encrypted and is used only to read new travel emails.
Google's Limited Use requirements. ByteBloom Compliance'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. In practice:
- we use Gmail data only to provide the flight-finding feature to you;
- we don't use it for advertising and we don't sell it;
- we don't transfer it to anyone, except our hosting and database providers and Anthropic (to read flight details from travel emails and check unknown senders, as above) so that we can provide the feature, where it is needed for security, or where the law requires it;
- we don't use it to create, train or improve any artificial intelligence or machine learning model, and Anthropic doesn't use it to train its models; and
- nobody reads it unless you ask us to (for example, to look into a problem you report), it is needed for security (for example, investigating abuse), or the law requires it.
If ByteBloom Limited's business were ever sold or restructured, we would not transfer your Gmail data without asking you first.
Disconnecting. You can disconnect a mailbox at any time on the Mailboxes page. That deletes the flight details found in it and the list of checked emails, rebuilds your trips without them, and asks Google to remove our access. You can also remove our access in your Google Account, under third-party connections.
Google's role. Google runs your Google account and its consent screen under its own privacy policy. Google is not one of our service providers.
5. Who we share it with
We use these service providers to run the service. They act only on our instructions.
| Provider | What it does | Where your data is |
|---|---|---|
| Vercel Inc. (United States) | Hosts the website and runs the app's code. Its network handles each request and keeps short-term logs | The app's code runs in London. Requests may pass through Vercel's global network, and Vercel may access data from the United States |
| Neon (Databricks, Inc. and its subsidiary Neon, LLC, United States) | Our database | Stored in London on Amazon Web Services. Neon may access it from the United States for support and operations |
| Mailgun Technologies, Inc. (part of Sinch, United States) | Sends our emails | Mailgun's EU region |
| Anthropic, PBC (United States) | Its AI service, Claude, reads the text of travel emails that don't include the standard booking format and returns their flight details. It also checks booking senders we don't know yet, from only the sender's web address and one flight, and may search the web to do so. It doesn't use this data to train its models | Processed in the United States. Anthropic deletes it within 30 days, unless it needs it longer to enforce its usage policies |
We also share data:
- with Google, if you connect Gmail (see section 4);
- with HMRC, a court, the police or another authority, if the law requires it. We will tell you if we are allowed to; and
- with a buyer or successor, if ByteBloom Limited's business is sold or restructured. We will tell you first.
Who at ByteBloom can see your data. In the app, only you can see your trips, flights, answers and mailboxes. The administrator can see the email addresses of people who have been invited, the name, email address and referral in each access request, and the names and email addresses of members, so that accounts can be managed. Our director can also access the database to run and support the service. He does this only when needed: to fix a problem, for security, to act on your request, or where the law requires it.
6. International transfers
Our database and the app's code are in London, and email is sent from the EU. Our providers are United States companies and may access data from there. The text of travel emails sent to Anthropic to be read is processed in the United States.
Where personal data goes to the United States, we rely on one of these:
- the UK-US data bridge, for a provider certified under the UK Extension to the EU-US Data Privacy Framework; or
- the International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, in the provider's data processing terms.
Transfers to the EU are covered by the UK's adequacy regulations for the European Economic Area.
You can ask us for details of these safeguards.
7. How long we keep it
| Data | How long |
|---|---|
| Account details, trips, flights, residence answers and review items | Until you delete them or your account is closed |
| Gmail flight details, checked email IDs and Google access key | Until you disconnect the mailbox or your account is closed |
| Travel email text sent to Anthropic to be read, and the sender and flight sent to check a sender | We don't keep it. Anthropic deletes it within 30 days, unless it needs it longer to enforce its usage policies |
| Sender checks | The answer for each sender's web address, with nothing about you or your bookings, kept while the service runs |
| Sign-in sessions | Until you sign out, you reset your password or 30 days pass |
| Password reset links | Each link works once, for 60 minutes. The record stays with your account until it is closed |
| Invites | Each link works once, for 7 days. If you join, the invite record is kept with your account. If you don't, it is deleted 30 days after it expires or is withdrawn |
| Access requests | Deleted 30 days after we approve or dismiss the request |
| Security records | Up to 24 hours, and cleared when you sign in successfully |
| Hosting logs | Up to 1 day, then deleted by our hosting provider |
| Email delivery records | Up to 30 days, then deleted by our email provider |
| Database backups | Our database provider keeps restore history for up to 30 days, after which it is overwritten |
You can close your account at any time from the account menu (Close my account). We disconnect any mailbox first, so Google is asked to remove our access, then delete your data straight away and email you to confirm. You can also email hello@bytebloom.tech and we will close it within one month. Copies in our database provider's restore history are overwritten within 30 days.
8. Keeping it safe
All connections to the service are encrypted. Passwords are hashed with scrypt. We store only scrambled versions of sign-in codes. Google access keys are encrypted with AES-256-GCM. Invite and reset links work once and expire. Repeated sign-in attempts are limited.
No system is completely secure. If a security incident is likely to put you at high risk, we will tell you without undue delay.
9. Your rights
Under UK data protection law, you can ask us to:
- give you a copy of your data;
- correct data that is wrong or incomplete;
- delete your data;
- restrict how we use it;
- stop using it where we rely on legitimate interests (you can object); and
- give you the data you provided in a format you can reuse, or send it to someone else.
Email hello@bytebloom.tech. It is free. We will reply within one month. If your request is complex, we may need up to two more months, and we will tell you why. We may ask you to confirm who you are, or what you are looking for. The time limit pauses until you reply.
10. Complaints
If you are unhappy with how we handle your data, please complain to us first. Email hello@bytebloom.tech with "Data protection complaint" in the subject. We will acknowledge your complaint within 30 days, look into it and tell you the outcome without undue delay.
You can also complain to the Information Commission (the ICO): ico.org.uk, or 0303 123 1113.
11. Children
The service is for adults aged 18 or over. We don't knowingly collect data from anyone under 18, except that another traveller's name, which may be a child's, can appear in a flight booking found in your email (see section 4).
12. Cookies and our emails
The service uses one cookie, which is strictly necessary to keep you signed in. Our Cookie Notice explains it.
Our emails don't track whether you open them or click links. When your email app shows images, it loads the ByteBloom logo from our website, and our hosting provider logs your IP address and device details.
13. Changes to this notice
We will update this notice if what we do with your data changes. We will tell you about significant changes by email or in the service before they take effect.