Privacy Policy

This policy covers both the Flybrite website at flybrite.co.uk and the Flybrite iOS app. Where a particular type of data only applies to one of those, we say so.

The personal data we hold falls into the following categories:

• Account details: your name (first, last, and the display name shown in the app), email address, and a hashed password. Phone number and postal address (house number, city, county, postcode) are optional. We use your postcode to show community groups near you; your address does not appear on Local Authority reports.
• Children you add: the child’s display name, age or birth date, interests, and an optional profile photo. You enter this; we do not gather it from any other source.
• What you record: diary entries, learning notes, observations, photos and videos you attach to moments, and any voice recordings you choose to log. Voice recordings are transcribed to text on our server and the resulting transcript is stored; the original audio is not retained.
• AI categorisation output: when you log a moment, we replace your child’s name (and any other family member’s name we recognise in the text) with a placeholder, then send the de-identified text (and any photo URL) to OpenAI for categorisation and short narrative generation. We swap the real name back in once OpenAI responds. The output (learning areas, categories, a written summary) is stored alongside the moment.
• Conversations: messages you send and receive in the in-app chat, including any attachments.
• Subscription state: if you subscribe to Flybrite we store your plan, status, and trial dates. We do not store your card number. That lives with Stripe (web) or Apple (iOS in-app purchase).
• Customer support: emails, in-app feedback, and any attachments you send when you contact us.
• Technical identifiers: your Flybrite user ID, your session tokens, and an Expo push-notification token tied to your device. We only collect your device’s advertising identifier (IDFA on iPhone, advertising ID on Android) if you say yes to ad measurement in the app, and only so Meta can measure our adverts (see “Cookies & tracking”).
• Bug reports: if you report a problem in the app, we collect what you write, a screenshot, and a set of technical details about your device and the build. The screenshot is attached by default. You see it before anything is sent, and you can switch it off. The next few paragraphs set out exactly what goes with a report.

You can report a problem in the iOS app either by shaking your phone or from Me → Settings → Report a problem. Alongside the words you write, a report carries:

• A screenshot of the screen you were on, taken at the moment you asked to report. It is attached by default. We show it to you in the report screen before anything leaves your phone, you can tap it to see it full size, and you can switch it off and still send the report. This is the one part of a report that can show your family’s details, which is why we put it in front of you first.
• Your device and the build you are running: platform (iOS or Android), operating system version, device model, app version, build number, runtime version, and the over-the-air update id, which tells us precisely which version of the code you were on.
• The situation at the time: your network state (for example “wifi, online”), your device language, and the screen you were on.
• A short trail of the last few screens you opened and any technical errors the app recorded in the minute or so before you reported.

That trail is a developer diagnostic rather than a copy of your record. It holds screen addresses and error text; it does not carry your diary entries, your photos, or your children’s profiles. We do not put family details into it deliberately, but we would rather be straight with you than over-promise: a screen address can contain the internal id of the item you were looking at, and an error message can occasionally quote a fragment of what the app was working on when it failed.

We use a bug report to find and fix the problem you reported, and for nothing else. It is not used for marketing, it is not shared with anyone outside the people who fix Flybrite, and it is not used to train any AI model. If you would like a report and its screenshot deleted, email [email protected], tell us roughly when you sent it, and we will remove it.

We do not track your location. The only place information we use is a place you choose for a moment, or one we suggest from a photo’s location data (see Mapbox below). We do not collect your contacts, browsing history outside Flybrite, health or fitness data, biometric data, or any data about people other than you, your children, and people you choose to chat with. On the public pages of the website, Meta’s advertising pixel only runs if you say yes to marketing cookies, and never in Kids mode or when you are signed in. In the app, Meta’s ad measurement tool only runs if you say yes to it. On the website, Google Analytics runs only if you say yes to analytics cookies. In the app, anonymous usage analytics (Google Analytics for Firebase) is on unless you switch it off in the app. See “Cookies & tracking” below for both.

We use your data to run the service and, where you choose, communicate with you:

• Provide the product. Show you your own diary, your children, your moments, your reports, and your messages.
• Authenticate you. Email and hashed password let you sign in; session tokens keep you signed in.
• Generate Local Authority reports. Your name and your child’s name appear on the report header (your address does not); your moments become the report’s evidence.
• Categorise what you log. The text and any photo URL you attach to a moment is sent to OpenAI to identify learning areas and write a short summary, so your diary becomes useful evidence rather than a pile of notes. Your child’s name (and any other family name in the text) is replaced with a placeholder before it is sent, and swapped back to the real name once OpenAI responds.
• Take payment. Your subscription status comes from Stripe (web) or Apple (iOS). We never see your card.
• Send push notifications. If you grant the iOS permission, your push token is used to remind you about logged moments and weekly summaries. You can turn this off in iOS Settings.
• Offers and news pushes, only if you turn them on. These are off unless you switch on “Offers and news” in Settings › Notifications or answer “Yes, tell me about offers” in the app. We record when and where you said yes. At most one a week. Switch it off there at any time and they stop straight away. Reminders about your own record are not offers and are not affected.
• Service email. Important account, security, trial and subscription messages. These are necessary to perform our contract with you, so they are not optional while you hold an account.
• Marketing email. A reminder as your trial ends, plus occasional tips and offers, for Flybrite’s own similar services only. Our lawful basis is legitimate interests, relying on the soft opt-in in regulation 22(3) PECR, or your explicit consent where you have given it. Every marketing email includes an unsubscribe link, and refusing stops future marketing emails without affecting essential service emails.

We hold your address for marketing on one of two footings, and we record which one applies to you. Most people are on the soft opt-in: you started a free trial, which is a negotiation for a sale, and you did not untick the box we showed you at signup. That footing only ever covers Flybrite’s own similar services. We do not send third-party marketing, and we never sell, rent or share your address for anyone else’s marketing. If you instead give us explicit consent, for example by telling us in person, by phone or in writing, we store it alongside a note of who you told, when, and what was said, so we can demonstrate how it was given.

You can refuse when you sign up by unticking the box, from the unsubscribe link in any marketing email, or by emailing us. Accounts created before this notice was introduced were not enrolled on the soft-opt-in footing, because no refusal was offered to them at the time their details were collected. You can ask us what we hold for you, or have it removed, at [email protected].

We do not use your data to train any AI model. The OpenAI calls we make are per-moment and stateless: OpenAI’s API does not retain your prompts for model training (this is a contractual commitment under their API terms, separate from ChatGPT consumer behaviour).

Flybrite is run by a small UK team. To deliver the service we use a handful of named sub-processors. We share only the data each one needs to do its job. None of them use your data to advertise to you.

• DigitalOcean: hosting (UK region) for our application servers and database. Receives everything you store with Flybrite, encrypted at rest and in transit.
• DigitalOcean Spaces: encrypted object storage (UK region) for photos and other attachments.
• OpenAI: runs the categorisation, narration, and Local Authority report-drafting calls. Before anything is sent, we replace your child’s name (and any other family member’s name we recognise, including yours) with a placeholder token; OpenAI only ever sees the placeholder, and we swap the real name back in once the response comes back. Receives the de-identified text and image URLs you log, plus child age, and (for Local Authority reports) the substance of any SEN details you have added — never under a real name. Bound by OpenAI’s API terms which prohibit training on your data.
• Stripe: processes web subscriptions and stores card details. Receives your email and subscription preferences; we receive a Stripe customer ID back.
• Apple: processes iOS in-app subscriptions via StoreKit. Receives the data Apple requires for IAP; we receive a transaction receipt.
• Mapbox: powers the place search when you add a place to a moment in the app. It receives the text you type as you search and, if a photo you attach has location data, that photo’s coordinates, so it can suggest a place name. The request goes through our server, never straight from your phone, and we keep only the place name on the moment, not the coordinates.
• Expo: relays push notifications from our server to Apple’s push service. Receives your push token and the notification payload.
• RevenueCat: manages in-app subscriptions on iPhone and Android. Receives your Flybrite user ID and your subscription and trial status. If you said yes to ad measurement, it also passes Meta your trial and subscription events (see below).

Meta (Facebook and Instagram) is not one of our processors. If, and only if, you say yes to ad measurement in the app, Meta Platforms Ireland receives the install, trial and subscription events and the device details set out under “Cookies & tracking”, and uses them as an independent controller under its own privacy policy. We never send Meta anything about your children.

We will only disclose your data outside this list if we are legally required to, for example by a UK court order or a valid request under the Data Protection Act 2018. We do not sell your personal data to any third party, ever.

You can choose to connect an external assistant, such as ChatGPT, to your adult Flybrite account. You sign in to Flybrite and review the requested permissions before access is granted.

With your permission, the assistant can read names and IDs of learner profiles you own, read saved lessons and learning assessments, create private lesson plans and assessments, assign lessons to the child app, schedule lessons at a chosen time, and submit answers you supply for Flybrite scoring. The connector does not provide access to other families, photos, messages or billing. Saved records remain subject to the sharing you already have in Flybrite.

The data returned to an assistant is handled under that provider's terms, privacy policy and your account settings. Do not connect an assistant unless you are comfortable sharing the permitted records with it. Lesson drafting can happen in your chosen assistant. Assigning a lesson to the child app uses Flybrite's existing AI pipeline to prepare interactive activities; submitting assessment answers uses Flybrite's existing AI scoring, which provides estimates.

Access lasts up to 90 days. You can revoke it at any time from your assistant connections. Revoking stops future access through that connection; it does not remove copies already held by the assistant provider. Contact that provider to manage those copies.

Your account, diary, and attachments are stored on DigitalOcean servers in the London (LON1) region. They are encrypted at rest by our infrastructure provider and travel between your device and our servers over HTTPS.

Two narrow exceptions cross UK borders:

• OpenAI processes the categorisation, narration, and Local Authority report-drafting calls on US infrastructure. We send the minimum needed (text, image URL, child age) per call, with your child’s (and any other named family member’s) name replaced by a placeholder before it leaves our servers. OpenAI is bound by EU/UK data-transfer Standard Contractual Clauses.
• Stripe and Apple process payments on their own infrastructure (Stripe: EU/US; Apple: US). Both are bound by the same SCCs.

We retain your data for as long as your Flybrite account is active. When you delete your account, all of your personal data is removed from our systems within 30 days, except where we are legally required to retain it (e.g. financial records for HMRC, which are retained for the statutory 6 years).

Under UK GDPR you have the right to:

• Access the personal data we hold about you.
• Correct inaccurate or incomplete data. Most fields are editable directly in the app under Me → Settings.
• Delete your data. You can delete your account from Me → Settings; this removes your profile, children, moments, photos, reports, and messages within 30 days. Email [email protected] if you’d rather we handle it.
• Object to or restrict certain processing.
• Take your data with you. Email [email protected] and we’ll send you a structured JSON export of everything tied to your account, free, within 30 days.
• Withdraw consent at any time without affecting prior lawful processing.
• Complain to the ICO. See “Contact us” below.

To exercise any of these rights, email [email protected]. We will respond within 30 days.

We use strictly-necessary cookies on flybrite.co.uk: the ones that keep you signed in and protect against cross-site request forgery. They expire when you sign out. These are on for everyone — there’s no way to switch them off without breaking sign-in.

Everything else is optional, and sorted into two groups: Analytics and Advertising. A small banner asks whether we can turn on Google Analytics, to see which pages, posts and emails bring parents to Flybrite, and whether we can turn on advertising measurement from Meta (Facebook and Instagram), Google Ads and LinkedIn, to measure which adverts lead to sign-ups and purchases and to show our adverts to people likely to be interested. Both stay off until you say yes, and “Reject all” is as easy as “Accept all”. Saying yes to one does not turn on the other. If you said yes before, we ask again once, because Advertising now covers Google Ads and LinkedIn as well as Meta. You can change your mind any time with the “Cookie settings” link in the footer of every page.

If you say yes, Analytics sees which pages you visit, roughly how you move between them, your device and browser, an approximate location (from your IP address, which Google then discards), and how you arrived — including any campaign link you followed. It sets two cookies to do this: _ga and _ga_SVN3GTTS68, our GA4 property’s own cookie, each kept for up to 2 years unless you clear them sooner.

If you’re signed in when you say yes, we also link your Analytics identifier to your account, so we can see which sign-ups, trials and purchases came from which visit — without that link, we’d only see anonymous page views, not which visit turned into a customer. If you withdraw consent, whether right away or later from “Cookie settings”, we remove that link from your account immediately.

In the Flybrite app, we use Google Analytics for Firebase to see which parts of the app help families, for example how many people add a child, log a first moment, or open a report. It is on by default, and you can switch it off at any time under Me, then “Usage analytics”. Switching it off stops it straight away on that device. It records which screens and features are used, your device model and operating system, your app version, and an approximate location from your IP address. It uses a random identifier that Firebase creates for the app on your device. We never attach your name, email address or account to it, we never collect your phone’s advertising identifier, and it never includes what you write, your photos, or your children’s details.

Google Analytics is for measuring our own pages. Advertising cookies and tags are used only by the advertising partners named above, and only if you say yes. They never run on a child’s sign-in or in Kids mode, and never on pages you see when you are signed in. We don’t run TikTok Pixel or any other advertising tracker on the website, and we don’t sell data to anyone.

Meta Pixel on the website (Advertising cookies). We advertise Flybrite on Facebook and Instagram. If you choose “Advertising” in the cookie banner, Meta’s pixel runs on our public pages, so we can tell which adverts bring people to Flybrite and only pay for adverts that work. It is off unless you say yes. If you say yes, Meta receives the pages you visit, when you click a link to the App Store, Google Play or our “get the app” page, your device and browser details, and your IP address. Meta also sets its own cookie, _fbp, on our site, which it keeps for up to 90 days. Meta may match this to a Facebook or Instagram account and uses it under its own privacy policy. We never send Meta your name, your email address, your phone number, anything you write, your photos, or anything about your children. The pixel never runs in Kids mode, and never on pages you see when you are signed in to your account. To withdraw, choose “Cookie settings” in the footer of any page and switch Advertising off. Meta then receives nothing further, and we remove its cookie from our site.

LinkedIn and Google Ads (Advertising cookies). If you choose “Advertising”, LinkedIn’s Insight Tag runs on our public pages so we can tell which LinkedIn adverts bring people to Flybrite, and Google Analytics signals about sign-ups and purchases can be used to measure our Google Ads. LinkedIn receives the pages you visit, your device and browser details and your IP address, and sets its own cookies under its own privacy policy. We never send them your name, email address, anything you write, your photos or anything about your children. To withdraw, choose “Cookie settings” in the footer and switch Advertising off; the tag then stops loading on our site.

Ad measurement in the app (Meta). We advertise Flybrite on Facebook and Instagram. After you sign up, the app asks whether you’re happy for us to tell Meta when someone installs Flybrite and starts a trial, so we only pay for adverts that work. It is off unless you say yes, and on an iPhone Apple then asks you to confirm too. If you say yes, Meta’s software in the app sends Meta that the app was installed and opened, that an account and trial were started, your device’s advertising identifier, and basic device details (model, operating system, app version, IP address). Our subscription provider, RevenueCat, also tells Meta when a trial turns into a paid subscription. Meta may match this to a Facebook or Instagram account and uses it under its own privacy policy. We never send Meta your name, your email address, anything you write, your photos, or anything about your children. You can switch it off at any time under Me, then “Ad measurement”, and on an iPhone also in Settings, Privacy & Security, Tracking. If you say no, nothing is sent to Meta.

Google is our data processor for this analytics data (see “Who we share with” above), and some of that processing happens outside the UK on Google’s infrastructure, under Google’s standard data-transfer safeguards. We keep analytics data for 14 months, after which Google deletes it automatically.

Analytics is never switched on for the pages a child uses to sign in and do their own lessons (“Kids mode”, at flybrite.co.uk/kids), or in the app while a child is signed in to their own account. See “Children’s data” below.

Questions about cookies? Email [email protected].

Flybrite is designed for use by parents and guardians of home-educated children. A parent sets up and manages each child’s profile: name, age or birth date, interests, and an optional photo. If a child has special educational needs, a parent can optionally add details so lessons suit them — you choose whether to add this, and it’s never required.

Some children also sign in themselves, in “Kids mode” (flybrite.co.uk/kids and the equivalent screen in the app), to do the lessons a parent has set and see their own progress. A child signs in with a username and a short code a parent generates for them — never an email address or a password, and never anything we ask the child to choose themselves.

In Kids mode we collect: the answers a child picks in a lesson or practice quiz (which option, not anything typed or written), a tracing/handwriting score for letter-practice games, how they say a lesson felt (loved / fine / boring), and the stars and badges they earn. We do not record audio or video of a child, and Kids mode never asks a child to type free text.

To generate a lesson, we send OpenAI only a minimised set of signals: the child’s age (or age band), their interests as topic words (e.g. “dinosaurs”, never any name or identifying detail), and — only if a parent has added special educational needs details — a small fixed set of learning-adjustment flags we derive from what you told us (for example “prefers simpler language”, “needs extra time”, “short, varied activities”). We never send your child’s name, sex, or the SEN details themselves (the specific condition or your own words) to OpenAI — those stay on our servers and are converted to the flags above before any AI call is made. OpenAI processes this minimised data only to generate that lesson; it is never used to train OpenAI’s models (OpenAI’s API terms prohibit this), and OpenAI keeps it for up to 30 days for abuse and safety monitoring before deleting it — see “Who we share with” above for how we handle OpenAI generally.

A parent can see everything a child does in Kids mode from their own account: lesson results, practice history, and progress. A parent can also send a short note or sticker to a child (“praise”), which is stored so the parent can see it was read. Nobody outside your family sees any of this.

We never run analytics, tracking, or advertising in Kids mode — see “Cookies & tracking” above.

Under UK GDPR you are responsible for the lawful basis for entering your child’s data. In most home-education contexts that lawful basis is parental responsibility combined with the child’s vital interests in having an educational record. We are the data processor for the child’s data and you are the data controller; we process it only as instructed by you, the parent.

The child is the subject of the record. One day they will also be its reader. A parent can switch off or reset a child’s Kids mode sign-in at any time from Settings. Removing a child’s profile deletes everything about that child — their sign-in, reward/practice data, diary entries, lessons and Local Authority reports — permanently; it does not affect any sibling’s record or the rest of your account. You can export one child’s data on its own from Settings before removing them, or export your whole account at any time. Email [email protected] if you need help with either.

We keep Kids-mode data for as long as your account is active, and delete it automatically 12 months after your account was last used, if you have not deleted it or your account sooner yourself.

Some children use their own sign-in (“Kids mode”, at flybrite.co.uk/kids) to view lessons their parent has set and record their own practice. We never run Google Analytics (on the website or in the app), the Meta pixel, the cookie-consent banner, or any other tracking or advertising tool on a Kids mode page, or during a child’s own sign-in session — a child can’t give or withhold consent, so none is asked for, and none is collected.

We will update this policy when our practices change, for example if we add a new sub-processor, change where data is stored, or start collecting a new type of data. We will:

• Update the “Last updated” date at the top of this page.
• Email you in advance if the change materially affects your rights or how your data is used.

Continued use of Flybrite after a change implies you accept the updated policy. If you don’t accept, you can export your data and close your account at any time (see “Your rights”).

Flybrite is a trading name of Skyla's Choice Ltd, a company registered in England & Wales (company number 16059710), which is the data controller. To exercise any of the rights described above, or to ask any privacy question, email [email protected].

If we don’t resolve your concern, you have the right to complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk.