Trust

Privacy notice

Last updated: 18 November 2026

This notice explains what personal data RALPH collects, why, where it is kept, how long for, and what you can do about it. It covers RALPH’s app, the connections that let an AI assistant act for you, and RALPH’s website at ralphops.ai.

Who we are

RALPH is run by Agnelli Ltd (“RALPH”, “we”, “us”), a company registered in England and Wales under number 08128078, whose registered office is at 51 Keeling House, Claredale Street, London, E2 6PG.

You can reach us about anything in this notice at hey@ralphops.ai.

Two kinds of data, two controllers

RALPH is used by flight schools, flying clubs and other aviation organisations. What RALPH holds falls into two parts, and a different organisation is responsible for each.

  • Your organisation’s records. Bookings, people, aircraft, flights, calendar feeds and the other records your organisation keeps in RALPH belong to that organisation. The organisation is the controller of the personal data in them, and RALPH processes it on the organisation’s instructions, as its processor, under the terms agreed with that organisation. If you have a question about those records, or want to use your rights over them, contact your organisation. We will help them answer you. The exception is improving RALPH, where RALPH is the controller.
  • Your sign-in. To let you sign in, and to know which organisations you belong to, RALPH keeps a record of you that sits outside any one organisation, because one person can belong to several. For this data, and for the data our website collects, RALPH is the controller. The rest of this notice is about that data.

Signing in with Google

You sign in to RALPH with your Google account, directly with Google; RALPH uses what Google sends only as described below. Google sends RALPH your Google account’s id, its email address and whether Google has verified it, your basic Google profile (such as your name, profile picture and language), and, for a Google Workspace account, its domain. RALPH keeps only:

  • the id Google gives your account, which never changes;
  • your email address, when Google confirms it belongs to you;
  • your name.

RALPH doesn’t keep your profile picture, stores no password, and keeps no Google token once you are signed in.

We use this to sign you in, to recognise you each time you return, to show your name in RALPH, and to link you to the organisations that have given you access, including an invitation addressed to your email address. We use it for nothing else. We don’t sell it, use it for advertising, or use it to train AI models.

RALPH’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Some people signed in to RALPH before it had its own Google sign-in, through Neon Auth, a sign-in service run by Neon. Neon Auth holds its own record of those sign-ins until RALPH finishes moving off it.

Invitations. When an organisation invites you before you have signed in, RALPH keeps the email address it invited, and the organisation it invited you to; the organisation gave us that address. When we set up an organisation for you, we keep the name and email address of the person it is for in the same way. When you first sign in with that address, the invitation becomes your access. When an admin adds you through RALPH’s API, RALPH can keep a copy of its reply (your email address and, if you have one, your account id) with the admin’s account, so a repeated request isn’t recorded twice. That copy is kept until the admin’s sign-in record is deleted.

You can’t use RALPH without signing in, so without this data we can’t give you access.

Lawful basis: our legitimate interest in giving you secure access to the organisations that use RALPH, and, where you have a contract with us yourself, performing that contract.

Signing in with Email

You can also sign in with your email address and a second step: an authenticator app, a text to a UK or EU mobile number, or a backup code. RALPH keeps your email address, the key for an authenticator app you set up, a mobile number you give for texts, and your unused backup codes. We use these to let you sign in, protect your access and help you get back in if you lose your second step. RALPH stores no password.

We keep your Email sign-in details until you ask us to delete them, even if your organisation is deleted. A second step’s details are removed when you replace it or reset it. Each backup code works once and is removed when used; any unused codes are removed when replaced, when your second step is reset, or when your Email sign-in details are deleted. Codes sent by email or text work for 10 minutes, and their stored records are deleted after use or expiry.

Lawful basis: our legitimate interest in giving you secure access to the organisations that use RALPH, and, where you have a contract with us yourself, performing that contract.

Your session

When you sign in to the app, your browser gets a session cookie. It holds a random value that means nothing on its own, and your browser sends it only to RALPH.

With each session RALPH keeps:

  • a label for the device, such as “Safari on iPhone”;
  • when the session started, and when it was last used.

A session ends after 7 days without use, or 30 days after you signed in, whichever comes first. You can see your sessions and end any of them, and signing out ends the session and tells your browser to clear what it holds for RALPH. RALPH deletes a session’s record as soon as it is ended early, and an expired one within a day.

While you sign in, RALPH also sets a short-lived cookie and keeps a matching record, to complete the sign-in securely. Both expire after 10 minutes, and the record is deleted within a day. If you use the link in a sign-in email, your browser keeps what it needs to finish that sign-in for the same 10 minutes.

RALPH doesn’t store your IP address. The app uses no analytics and no third-party scripts.

Lawful basis: our legitimate interest in keeping your account secure, and these cookies are strictly necessary for the service you asked for.

Your preferences. The app keeps a few preferences on your device, in your browser’s local storage, and signing out tells your browser to clear them:

  • your theme, whether the sidebar is open and whether single-key shortcuts are on, once you change them;
  • the organisation you last opened, so it can take you back there;
  • for each organisation, the corner style you picked if you are one of its admins;
  • for each organisation, on a phone-sized screen, the resource you last viewed on its Schedule, so it opens there again.

Lawful basis: our legitimate interest in remembering your choices.

Unsent drafts. If your session ends while you are part-way through some forms, such as a booking decision, an aircraft or your organisation’s settings, the app keeps what you had typed on your device, in your browser’s storage, so you can pick up where you left off after signing in again. Each draft records your account, the page and a one-line summary of it, and holds the organisation’s records you were editing. A draft is deleted once you send or discard it, when it is 24 hours old (the next time the app is open), or when you sign out, which tells your browser to clear it.

Lawful basis: our legitimate interest in not losing your work; for your organisation’s records in a draft, RALPH acts for your organisation.

Your upcoming bookings, for offline use. So that Today still shows what’s next for you where there is no signal, the app keeps your own bookings for the next 14 days on your device, in your browser’s storage, each time Today loads them: each booking’s times, status, title, aircraft and instructor’s name, with your account, the organisation and when they were loaded. Bookings that have ended are deleted the next time the app is open. They are all deleted when your session ends, however it ends, or when someone else signs in on the device; and, even with no connection, 7 days after Today last loaded them or when your session would end at the latest, whichever comes first.

Lawful basis: our legitimate interest in showing you your own bookings when your device is offline; for your organisation’s records, RALPH acts for your organisation.

Connecting an AI assistant or an agent

You can let an AI assistant, such as Claude or ChatGPT, or a script, act for you in RALPH.

  • Connected apps. When you approve a connection, RALPH records the grant: which app, for which of your organisations, with which permissions, and when. A grant ends after 90 days at most, or sooner: after 30 days without use, when your access to that organisation ends, or if RALPH sees a sign that it isn’t safe. RALPH doesn’t yet let you end a connection yourself.
  • RALPH’s command-line tool. If you sign in with “ralph login”, the tool keeps its credentials on your computer until you run “ralph logout”. They stop working when the connection ends. Logging out removes them from your computer, but doesn’t end the connection.
  • Access keys. For an access key, which lets an agent or script act for you, RALPH keeps its name, its permissions, who created it, whom it acts for, when it expires (a year ahead unless set otherwise) and when it was last used. A staff member or admin of your organisation can also create a key that acts for you, within your permissions; its actions are recorded as done for you by that key, and the key records who created it.

While you approve a connection, RALPH sets short-lived cookies and keeps a record of the request: which app, for which organisation if the app names one, with which permissions, and, once you have signed in, your account. The cookies and the record expire after 10 minutes at most, whether or not you approve, and the record is deleted within a day. When you approve, RALPH gives the app a one-time code, deleted within a day, to complete the connection.

The assistant you connect works under your own account with its provider, whose terms and privacy notice cover what it does. RALPH’s own servers use AI models to read photos of tech-log pages and to map spreadsheets an admin imports. What we send to them can include personal data.

To test and choose the model that reads tech-log pages, we read a small set of sample pages through candidate models in the UK. They are real pages, so they show names. We hold them in storage in the UK, and RALPH’s staff and the AI coding tools they work with can see them. Lawful basis: our legitimate interest in reading pages reliably.

Lawful basis: our legitimate interest in providing the connections you, or your organisation’s staff or admins, ask for, and keeping them secure.

Improving RALPH

We use what people upload to RALPH and correct in it to test and improve RALPH. This can include names and handwriting. An organisation’s admin can turn this off for its tech-log pages in Settings, and you can turn it off for tech-log pages with your name or handwriting in Settings › Privacy.

Lawful basis: our legitimate interest in improving RALPH.

Emails and texts from RALPH

RALPH sends email and texts to tell people what they need to know about their access and their bookings:

  • an invitation to an organisation, to the email address or mobile number the organisation gave, and, when it’s needed to accept the invitation, a one-time code to that address;
  • notices about access keys and connected apps, such as one being created, changed, revoked or about to expire;
  • sign-in codes by email, and codes by text for your second step;
  • notices about the security of your sign-in, by email and, where applicable, text, including a backup code being used or a second-step reset waiting or finishing; your organisations’ admins are also emailed when a reset finishes;
  • a one-time code, when you ask for one, to the mobile number you gave, to show the number is yours;
  • texts about a booking you are on, when it’s made, changed or cancelled, if your organisation has turned texts on and has ticked texts for you.

RALPH writes each message itself, and a provider delivers it: Resend for email and Twilio for texts. The provider receives the address or number, and the message: who it’s from, the organisation, an admin’s note on an invitation, and any link or code it carries. A booking text also gives the booking’s date and time, its aircraft and the names of the other people on it. It never includes a booking’s notes.

RALPH keeps a record of each message: where it went, what kind of message it was and what it was about, who caused it, the provider’s reference for it, and whether it was delivered. It doesn’t keep the message’s text. It holds a message’s link or code only until the message is sent or given up. RALPH keeps an organisation’s message records until the organisation is deleted. Records of RALPH’s own sign-in messages are kept indefinitely. A delivery receipt RALPH can’t match to a message is deleted within a day.

Resend keeps each email, with its delivery events and logs, for 30 days, and backups for 7 days. By default, Twilio keeps a record of each text, with the number and the message, until we ask it to delete it, which RALPH doesn’t yet do.

If you reply STOP to a text from RALPH, your number gets no more texts from any organisation using RALPH. RALPH keeps the number and when it replied, on its own and not tied to anyone’s record, so the choice lasts if an organisation or a person’s record is deleted. Replying START removes it. RALPH reads a text sent to its number only for those words, and doesn’t keep it.

Lawful basis: our legitimate interest in letting organisations invite the people they choose, and in keeping access secure; for an organisation’s records in a message, such as an invitation’s note, RALPH acts for that organisation. For a number that replied STOP: our legitimate interest in honouring that choice.

Feedback you send us

When you send feedback from RALPH’s app, we receive your comment and, if you add one, a screenshot, with what the app knows about where you were: the page, the app’s version, your browser and operating system, your screen’s size, your theme and language, and the reference numbers of the app’s last requests that failed. RALPH adds your name, your email address, your organisation’s name and internal id, and the version of RALPH’s servers, so we can reply and find the problem. RALPH sends only a screenshot’s picture, and nothing else its file carried, such as a location. A screenshot can show your organisation’s records: send one only when you’re happy for us to see what it shows.

RALPH keeps none of it itself: it sends it to Linear, where we track our work, as an issue for us to look at, and records your organisation as the customer who asked. RALPH’s logs record that feedback was sent, not what it said. We keep your feedback in Linear for as long as we need it to act on it. An organisation’s admin can turn feedback off for their organisation.

Lawful basis: our legitimate interest in answering your feedback and improving RALPH.

If you set up an organisation

When an organisation is set up for you, RALPH keeps a billing account for it and records:

  • that you can manage the organisation’s subscription, and delete or restore the organisation;
  • the subscription’s plan, status and renewal date;
  • the setup itself: the organisation’s name, its short name in RALPH’s addresses, its home region, and who set it up, or who it was set up for;
  • once RALPH takes payments, the payment provider’s references for the billing account, the subscription and the checkout.

We use these to know who may manage the organisation and its subscription, and to keep a history of it. We keep them while the organisation’s billing account exists, and afterwards for as long as we need them to meet our legal, accounting and tax obligations or to settle a dispute.

Lawful basis: our legitimate interest in knowing who manages each organisation and its subscription, and, where you contract with us yourself, performing that contract.

A record of changes to access

RALPH keeps a security record of changes to its shared data, such as an access key being created or revoked, or a person’s access to an organisation being removed. It records who did what, and when, by internal id, and not the details that changed. RALPH’s service can only add to it, never edit or delete it, so it is kept for as long as RALPH runs. Once your sign-in record is deleted, the ids that belonged to it no longer link to you. The record can also hold ids that lead to you through an organisation’s records: your person record there, your access to that organisation, or an access key that acts for you. Those ids link to you for as long as that organisation’s records still identify you.

Lawful basis: our legitimate interest in keeping RALPH secure and being able to show who did what.

RALPH’s logs

RALPH’s servers write operational logs, which Fly holds for us. They can include the internal ids of your sign-in record and your organisation, and your organisation’s short name, but not your IP address. They are held by Fly in the United States for about 7 days; we don’t copy them anywhere else.

When RALPH’s staff act on an organisation or an account, we record who acted and the reason they gave, which may mention you, and, where the action names you, your email address. That record stays with the staff member who acted, and we don’t copy it anywhere else.

Lawful basis: our legitimate interest in running RALPH securely and being able to account for what our staff do.

Our website

Our website at ralphops.ai collects very little.

  • Analytics, only if you accept them. The site uses PostHog’s EU Cloud to count visits. Nothing loads unless you choose Accept on the site’s banner; Reject, or no answer, loads nothing. If you accept, PostHog sets a cookie and a matching entry in your browser’s local storage holding a random id for your browser, and receives the pages you visit and whether you click a link to request early access (including our email address on the Contact page) or to sign in, along with details your browser sends, such as its type and your IP address. It records no session replays, heatmaps or other clicks. We keep this data only for as long as we need it to understand how the site is used. Lawful basis: your consent.
  • Your choice. The site remembers whether you accepted or rejected in your browser’s local storage, not in a cookie, so it doesn’t ask you again. You can change your mind at any time with “Cookie settings” at the foot of any page. Choosing Reject later stops PostHog, but doesn’t delete what it already stored in your browser; clearing your cookies and site data for the site removes it.
  • Early access. “Request early access” takes you to a short form on the site. It asks for your email address, your organisation, how many aircraft you have, how many bases you fly from, where you fly, the types of aircraft you fly, your types of operation, and how many people run your operation. Every field is required. We use your answers to reply to your request. The form sends them through RALPH’s own servers, on Fly.io in the UK, to RALPH’s Google Workspace, which records your answers and the time they arrived, and nothing else. Those servers keep no copy and log none of your answers. Google Workspace then emails us that a request has arrived, and the email may include your answers. Only the RALPH staff who answer hey@ralphops.ai see them. We delete your request, its earlier versions and that email, once we have answered it and you have joined or declined, or twelve months after it arrived, whichever comes first, and at once if you ask us to. If you accepted analytics, PostHog counts your visit to the form’s thank-you page as it counts any page view, and receives none of your answers; if you didn’t, it isn’t told. You can also email us at hey@ralphops.ai instead. We use what you send to reply, keep it while we’re in touch with you about early access, and delete it when you ask us to. Lawful basis: our legitimate interest in answering you.
  • Server logs. The server that hosts the site logs each request it answers: your IP address, the page, the time, the page you came from and your browser’s user agent. They are held by Fly in the United States for about 7 days; we don’t copy them anywhere else. Lawful basis: our legitimate interest in running the site securely.

The site loads its fonts and everything else from itself. Without your consent, it makes no request to anyone else.

Where your data is kept, and who helps us

Each organisation’s records are kept in the home region chosen when it is set up, and can’t be moved from within RALPH. Today every organisation’s records, RALPH’s servers and RALPH’s shared data are in the UK.

We use these services to run RALPH:

  • Fly.io runs RALPH’s servers and the website, in the UK. It holds their logs and metrics in the United States.
  • Neon hosts RALPH’s databases, in the UK, including Neon Auth for the sign-ins described above.
  • Amazon Web Services stores the files an organisation uploads to RALPH, and runs the AI models that read them, in the UK.
  • Google provides sign-in. You sign in with Google directly, and Google is the controller of your Google account, under Google’s privacy policy.
  • Google Workspace holds the early-access requests sent through the website’s form, the emails that tell us of each one, and the email you send to hey@ralphops.ai. We’ve set it to store these in the EU. Google may still process all of this, and store other data about it such as logs, outside the EU, under Google’s data processing terms and the transfer safeguards in them.
  • Resend sends RALPH’s email, from its region in Ireland. It stores each email, its delivery events and its logs in the United States.
  • Twilio sends RALPH’s texts. It handles and stores them in the United States.
  • Linear holds the feedback you send us from the app, as described in “Feedback you send us”. It processes it mainly in the United States.
  • PostHog provides the website’s analytics, in its EU Cloud, only if you accept them.
  • Lemon Squeezy will be the merchant of record when RALPH starts taking payments, which it doesn’t yet. It will then handle checkout, payment and tax for an organisation’s subscription as its own controller, and receive the payer’s email address, the organisation’s name, short name and home region, and an internal reference that links the payment to the payer’s RALPH account. RALPH keeps Lemon Squeezy’s references for the customer and the subscription. We’ll update this notice before any other payment provider receives your data.

Amazon Web Services, Fly.io, Neon, Lemon Squeezy, Linear, Resend and Twilio are US companies. Where they handle your data outside the UK, they do so under the transfer safeguards UK and EU data protection law require, set out in our agreements with them.

An organisation can also connect its own accounting system. That system is the organisation’s, used under its own account with its provider, whose terms and privacy notice cover it. RALPH exchanges the organisation’s records with it on the organisation’s behalf.

Copies and backups

RALPH keeps short-lived copies of its data, so a failed release can be undone and a change can be tested before it goes live. A release’s copy expires after 7 days, and a test copy is deleted when the change is finished or after 7 days without use. They stay on the same Fly and Neon services, and only RALPH’s staff can sign in to them.

How long we keep it

  • Your sign-in record: until you ask us to delete it. When an organisation is deleted, the sign-in record of anyone whose only access was to it is deleted too, unless they still have access elsewhere or a billing relationship with us. Your Email sign-in details are kept as described in “Signing in with Email”.
  • Details of the person an organisation is set up for: until the organisation is set up for them.
  • Invitations, and access keys: until the organisation is deleted, including, once withdrawn or revoked, the record of when that happened.
  • Sessions: up to 30 days, as described above, then deleted within a day.
  • Preferences on your device: until you sign out or clear your browser’s data for RALPH.
  • Unsent drafts on your device: 24 hours, deleted the next time the app is open after that, or when you sign out.
  • Copies of replies to adding you: until the sign-in record of the person who added you is deleted.
  • Connected apps: deleted within a day of the grant expiring, going unused or being ended. When a connection stops working because your access to the organisation ended, its record is kept until the app’s last credential expires, at most 30 days, then deleted within a day.
  • Records of emails and texts: until the organisation is deleted, or indefinitely for RALPH’s own sign-in messages; a message’s link or code only until it is sent or given up. Resend and Twilio keep their copies as described in “Emails and texts from RALPH”.
  • A number that replied STOP: until that number replies START.
  • Files an organisation uploads: a spreadsheet imported into RALPH, until 30 days after its import is committed, discarded or fails. A photo of a tech-log page is kept while the organisation keeps the page in RALPH; one that made no page is deleted once its upload fails or is discarded. A tech-log page is part of an aircraft’s records, which the organisation must keep, so a person’s request to be erased doesn’t delete the pages they appear on. Every file is deleted when the organisation is deleted.
  • What we keep to improve RALPH: until it is turned off for it, as described in “Improving RALPH”, and at most until the organisation is deleted.
  • Feedback you send us: in Linear, for as long as we need it to act on it.
  • Billing and setup records: while the billing account exists, then as long as our legal, accounting and tax obligations or a dispute require.
  • Security record of changes: for as long as RALPH runs, as described above.
  • RALPH’s logs: about 7 days, held by Fly in the United States; records of what staff do stay only with the staff member who acted.
  • Counts and timings that identify no one: about 15 days.
  • Website data: as stated in “Our website”.

Your rights

Under UK and EU data protection law you have the right to:

  • ask for a copy of the personal data we hold about you;
  • have it corrected if it’s wrong;
  • have it deleted;
  • restrict or object to how we use it, including anything we do on the basis of our legitimate interests;
  • receive it in a portable format;
  • withdraw your consent at any time, where we rely on it, without affecting what we did before.

To use any of these rights, email hey@ralphops.ai. We will reply within one month. For your organisation’s records, contact your organisation, and we will help them.

You can also complain to the UK Information Commissioner’s Office at ico.org.uk, or to the data protection authority where you live or work in the EU. We’d appreciate the chance to put things right first.

Changes to this notice

When we change this notice, we’ll update the date at the top. If a change affects how we use data we already hold, we’ll tell you before it takes effect.