Privacy Policy

Last updated: 14 October 2026

Policy version 2026-10-14

Your privacy matters to us. This policy explains what personal information Orbrey collects, why we collect it, who we share it with, where it goes, how long we keep it and the choices you have. We have tried to say plainly what the product does.

The short version

What Orbrey keeps

  • Orbrey keeps what your household puts into it (calendar, tasks, lists, recipes, meals, groceries, pantry, rewards, notes and forwarded notices), your account details, and allergies and food preferences if you add them.
  • Everyone in a household can see what is in it, including allergies, the list of members and Family Inbox items. Child accounts can read it too (section 11).
  • Our database is in Singapore. Some providers we use work in the United States and elsewhere (section 5).
  • We do not sell your personal information. If you accept advertising cookies, Meta and Google receive identifiers (section 16).

Orbrey AI

  • Orbrey AI runs on models hosted by Cloudflare, on its network, with no fixed country (section 6). When you use Ask Orbrey it can send household details to the model, including members' names and allergies, and by default it asks before it changes anything.
  • Use Orbrey is off until you switch it on. Orbrey AI starts working for you only after you switch Use Orbrey on; saving another AI setting does not turn it on. It can send names and allergies to the model.
  • Turning Use Orbrey off for yourself does not stop another member of your household, who has it on, from asking Orbrey about household information that includes yours, such as allergies.
  • We do not train AI models on your household content, but we have not confirmed what Cloudflare, which runs the models, does with requests.

What runs without a choice

  • Error reports on orbrey.com run without a setting. In the mobile app they are on by default, with a switch to turn them off (section 9).
  • From the web app and the mobile app, an error report carries your account's ID and details about your browser or phone. From the mobile app it also carries the phone's time zone, language and region setting (section 9).
  • Sentry, which receives the reports, works out the country your IP address is in and keeps that. We saw this on the mobile app, and we expect the same for the web app and orbrey.com, which we have not checked (section 9).
  • It also checks Expo (our update and notification service) for updates and, on Android, uses Google ML Kit (a text-reading library). None of these has a switch.
  • Our hosting and service providers see your IP address as part of each request they handle.

Only if you agree

  • In the signed-in web and mobile apps, Product analytics stays off until you turn it on in Settings. The apps have no consent banner, and Advertising measurement and Error + crash reporting have separate settings. On orbrey.com, PostHog and advertising tags load only after you accept in Cookie choices (sections 9 and 10).
  • If you used either site before 7 October 2026 and did not enable analytics in the app or accept on the marketing site, an earlier version may have saved an identifier. It is not read or sent until the relevant setting or cookie choice is applied; turning analytics off or clearing site data removes it.
  • The web app sends no error reports until you allow them. If you do, a replay of the screen with the text hidden is recorded from shortly before an error until the session ends (at most 60 minutes). It does not hide the layout, the page address or the addresses of requests.
  • PostHog can also record sessions on the signed-in web app while Product analytics is on and on orbrey.com after you accept analytics. We have not confirmed that setting for the project that receives web events, and it hides form fields but not other text. Session replay is off in the mobile app.

Feedback and bug reports

  • The web app, the mobile app and orbrey.com have a feedback form for bugs, ideas, questions and praise. A message goes to PostHog only when you press Send, and it goes there whatever you chose about analytics (section 9).
  • Children cannot send feedback from the app, except through the report form on an error screen, which cannot tell whose sign-in it is and sends no account details (section 9).
  • A message carries your text, the kind of feedback, an optional rating in the apps, and your app version, device and screen. Your account and household IDs go only if you turn on Include my account details, and your email address only if you type one for a reply.
  • Obvious credentials are hidden, but free text can hold personal information, so please do not include any.
  • To have a message deleted, email privacy@orbrey.com and tell us the reply address you typed or the account you sent it from. A message with no reply email and no account cannot be traced to a person, so we cannot find it to delete it.

Children

  • Orbrey is made for adults to run a household. Children use it through a household member added without a login or a guardian-created child account: a parent or guardian can add children as members, and a guardian can create a child account in the mobile app.
  • A guardian who is a household admin can suspend or delete a child account (section 11, Parents and guardians).
  • Anyone who knows your household's Family Inbox address can send to it, child accounts can read Inbox items, and a household admin can turn forwarding off (section 2).

Deleting, and your choices

  • Deleting your account removes your sign-in and most of what you added. Some things stay (see what survives deletion) and some need an email to us.
  • You can change your choices in Settings, or email privacy@orbrey.com. The web export covers your household's recipes, events, tasks, lists, groceries and similar content, but not photos, Family Inbox or AI conversations, and the mobile app has none (section 13). In Australia you can also complain to the OAIC (section 14).
  • A few things about our providers are not yet confirmed. They are listed together under What we have not yet verified (section 4).

Words we use

  • Hash: a one-way scramble of a value. We can check a value against it but cannot turn it back into the original.
  • Pseudonymous: linked to a random ID instead of your name or email, which can still be traced to your account.
  • Traces: samples of how long things took, such as a page loading.
  • Sentry: a service we use to collect error reports (what went wrong, and where) so we can fix faults.
  • PostHog: a service we use for product analytics (which pages, screens and features are used) and to read the feedback you send us.
  • Session replay: a recording of what happened on a screen, played back like a video. Where we say the text is hidden, the words on the screen are not in it.
  • Cloudflare: the company whose network runs Orbrey AI, the Family Inbox email intake and some of our other services.
  • Controller: the organisation that decides why and how personal information is used.
  • Legitimate interests: a legal basis in UK and EU law for using information where we have a good reason that does not override your rights. You can object (section 15).
  • Member without a login: a person a household adds by name, such as a young child or a guest, who has no account of their own.
  • Child account: a sign-in that a parent or guardian creates in the mobile app for a child, which a guardian who is a household admin can suspend or delete (section 11).
  • Household admin and manager: an admin is a member with full control of a household, including erasing its content and asking to delete it (section 13). A manager is a member with extra control, for example over rewards. An admin or a manager can create a child account (section 11).
  • Family Inbox: the place where notices you paste, upload, share or forward are read (section 1).

1. Who we are and how to reach us

Orbrey ("Orbrey", "we", "us") makes a household organiser: a website at orbrey.com, a web app at app.orbrey.com, a mobile app, an AI assistant (Orbrey AI), and a Family Inbox that reads notices you paste, upload, share or forward to an email address we give your household. This policy covers all of them.

It applies to people who have an account. It also applies to the other people a household adds (members, guests, children, people invited to join, and people named in events and tasks), to people whose emails are forwarded into a household's Family Inbox, and to visitors to orbrey.com, including people who subscribe to our blog.

Orbrey is an Australian business. We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Where other laws apply to you, sections 15 (UK and EEA) and 16 (US) say what that means.

How to reach us

Orbrey and your household

Orbrey runs the service. What goes into a household, and who is in it, is decided by the people who use it. A household admin who adds someone else's information takes on some responsibilities, which are set out in section 13.

2. What we collect and how

We collect personal information in four ways: from you directly, automatically from your browser or phone, from services you sign in with or connect, and from emails and files sent to a household's Family Inbox. Some of it is information about other people in your household, which is why the household's own responsibilities matter (section 13).

Your account

  • Your email address and a password (we keep only a hash of it, never the password itself). If you sign in with Google or Apple, we receive the basic profile details they release, such as your name and email address.
  • A display name. On the web we start it as the part of your email before the @; you can change it. Optional two-factor sign-in (an authenticator app) if you turn it on, and a PIN for managing rewards if you are made a rewards manager (we keep only a hash of the PIN).
  • Short-lived records that make sign-in work: email verification tokens (kept as hashes) and a record of the sign-in methods linked to your account. Password-reset links are produced by Supabase's sign-in service.

Your profile and household

  • Household name, time zone and language, and an optional weather location. On the web app you pick a place by searching for a city and we store it with its map coordinates. On the mobile app you can type a place name, which is stored as text (the mobile app does not look up coordinates). We do not use your device's location services.
  • Microphone: neither app asks for microphone access. The web app has a voice-input option that is switched off; if it is ever switched on, we will update this policy first.
  • For each member: a nickname or display name, an optional email address (for members without a login), a colour, a profile photo, their role in the household, and preferences such as language, measurement units, date and time format, week start and theme.
  • In the mobile app you can add an optional birthday to your own profile (a date, with no time). The app shows it on your own profile and nothing else in Orbrey uses it, but it is held in your profile record, which other account holders in your household can read under our database rules. We do not ask for your age or date of birth to create an account, and we do not check age when you sign up.
  • Your notification settings and, on the mobile app, your phone's push token (section 4).

What your household puts in

Calendar events (title, description, location, attendees and reminders), tasks and routines, shared lists and notes, recipes with ingredients, ratings and cook history, meal plans, grocery lists, pantry items with expiry dates, rewards, gem wallets and their history, household updates, and notifications. The apps do not currently let you attach a file to an event, but attachments already on events are kept. We store this so the service can work and keep your devices in sync.

Allergies and food preferences (sensitive information)

A member can record allergies, foods to avoid and food preferences. Allergies are health information, which the Privacy Act treats as sensitive information and UK and EU law treat as a special category of data. We collect it only because someone in your household chooses to enter it. It is visible to the members of that household. If a member has their own login, only that member can change these fields. For a member without a login (such as a young child or a guest), a household admin can. Whoever enters another person's allergies should have that person's agreement or, for a child, be their guardian (section 13). We use it to flag recipes and plan meals, and Orbrey AI can use it as described in section 6.

People you add

  • Members without a login (sometimes called guests): a nickname, optional email address, colour, photo, allergies, foods to avoid and preferences.
  • People you invite: the email address you type, so we can send the invitation. The invitation names you, the household and up to four of its members, and it expires after 7 days.
  • Names you type into events and tasks, such as attendees and who something is assigned to.
  • Senders of emails forwarded to the Family Inbox: the display name from the email and, in a log that only household admins can read, the sender's email address.

Family Inbox

The Family Inbox accepts text you paste, files you upload or share from another app (PDF, JPEG, PNG, WEBP, HEIC, text and HTML), and emails forwarded to the address we give your household. We keep the original files, the text we pull from them, what Orbrey AI or our rules found in them (events, tasks and the passages they came from) and, for emails, the subject, the body and up to 10 attachments. The raw email message is read in memory and is not stored. Anyone who knows a household's Inbox address can send to it; there is no sender allow-list, and items from a first-time sender are marked as such. The address is made from up to the first 20 letters and digits of your household name (spaces and punctuation removed, and a trailing "Family" or "Household" dropped), a dot, and three random words, for example bennett.cedar-lamp-tiger@orbreymail.com. The name part is not secret, so the three words are what make the address hard to guess. Households that set up forwarding before 1 October 2026 may have an older address, for example one that starts with h- at inbox.orbrey.com, or one made of the household name and five digits. It works the same way. A household admin can turn forwarding off, or get a new address, in Settings, then Inbox.

Photos and files

Profile photos, recipe images, Family Inbox uploads, and attachments already on calendar events. A photo of a receipt is read and then discarded; we do not keep it (section 6). Profile photos in the web app are cropped and re-encoded in your browser before upload, which drops any location data embedded in the original, and receipt photos prepared in the mobile app have it removed before they are read. Photos and files you upload or share to the Family Inbox are stored as sent, including any location data embedded in them. Files are stored privately and opened through links that expire.

Orbrey AI

Your Ask Orbrey conversations, the instructions you give it, memories it learns, a log of what it used and did, your feedback on its suggestions, and your AI settings. Details are in section 6.

Payments

Your plan, billing status and the identifiers that link your household to Stripe or to the app store. We never receive your card number (section 8).

Device and usage information

  • Technical details your browser or phone sends with every request: IP address, browser or app version and operating system. Our hosting and service providers see these. We use IP addresses to protect the service, for example to limit repeated attempts, and keep them only briefly (section 12).
  • Error reports, usage analytics and performance measurements, if you allow them or where they run by default (section 9).
  • Feedback and bug reports you send us. The web app, the mobile app and orbrey.com have a feedback form that sends your message, the kind of feedback, an optional rating in the apps and your app or browser and device details to PostHog when you press Send. It adds your account and household IDs only if you turn that on, and an email address only if you type one (section 9).
  • Small items saved on your device, such as your sign-in, drafts and preferences (section 10).

If you visit orbrey.com

  • Blog newsletter. If you subscribe we store your email address, an optional name, where you subscribed, any campaign tags and referrer, a PostHog visitor ID if you have accepted analytics (see section 10), your choice to receive blog email, a hash of your IP address and your browser's user-agent text. Subscribing is single opt-in: we send a welcome email straight away without asking you to confirm, so anyone can type any address into the form. If you didn't subscribe, ignore the email or use its unsubscribe link, or ask us to delete the record.
  • "Was this helpful?" votes on blog posts: the post, your vote, a hash of your IP address and your user-agent text.
  • Support page. The feedback form on the support page (orbrey.com/support) works like the feedback form in the apps, but visitors are signed out, so it has no account option, and it has no rating. It sends your message, the kind of feedback and basic details about your browser and the page you were on to PostHog when you press Send, with an email address only if you type one (section 9).
  • Pricing. Pages that show prices ask our database for the current price list; no personal information is sent, but your IP address and browser details reach our database host.

If you contact us

We keep what you send us, and our replies, so we can deal with your request. Privacy requests are logged with the email address they came from.

From other places

  • Sign-in providers (Google, Apple): the details above.
  • Calendars you connect: events from the calendar (section 7).
  • App stores and Stripe: whether a subscription is active, its plan and its dates.
  • Web pages you ask us to read: when you paste a recipe link, or look up a product's pack size, our servers fetch that page. For TikTok links we also ask TikTok for the public caption. Pictures from those pages can be shown in Orbrey by loading them straight from the original website, which then sees your IP address and browser details.
  • Other people in your household, who may add information about you.

3. Why we use it

We use personal information to run Orbrey and for the purposes below. We do not use your household content to build advertising profiles. The right column is for people in the UK and EEA (see section 15).

Why we use personal information, what that covers, and the UK and EEA legal basis
PurposeWhat it coversBasis for UK and EEA users
Run OrbreyAccounts, sign-in, households, syncing between devices, imports, the Family Inbox, rewards, file storage and support for the features you use.Contract (providing the service you asked for).
Service messagesVerification and password-reset emails, household invitations, approval requests, the weekly email digest, and push notifications you have allowed.Contract. The optional digest is also in our legitimate interests, and you can turn it off.
Orbrey AIAnswering Ask Orbrey, making suggestions, reading imports, receipts and Family Inbox notices, and running scheduled tasks.Our legitimate interests in providing the assistant you use. Use Orbrey is off until you switch it on. Orbrey AI starts working for you only after you switch Use Orbrey on; saving another AI setting does not turn it on. It can send members’ names and allergies, which are health information, to the model (section 6), and we have not asked for separate explicit consent for that.
PaymentsSubscriptions, billing records, tax and accounting.Contract; legal obligation.
Security and abuse preventionRate limits, bot checks, audit logs, spotting misuse and fixing security problems.Legitimate interests.
Error reports and performanceFinding and fixing crashes and slow screens.Consent on the web app, through the Error + crash reporting switch in Privacy preferences. Legitimate interests on the mobile app and on orbrey.com (the mobile app has a switch; you can also object by email).
Product analyticsSeeing which features are used and where people get stuck.Consent.
Advertising measurementMeasuring our own advertising on Meta and Google.Consent.
Blog newsletter and post votesSending a welcome email and, when we send them, blog updates to people who subscribe, counting helpful votes, and stopping abuse of the forms.Consent given by whoever completes the form: we do not check that the address belongs to them, so if it is yours and you did not subscribe, use the unsubscribe link or email us. Legitimate interests for votes and abuse protection.
Family Inbox messagesReading and filing the emails, files and text that someone sends or pastes to a household’s Family Inbox, including from people who are not Orbrey users.Contract with the household that set the Inbox up. Legitimate interests for senders outside the household.
Allergies and food preferencesFlagging recipes and planning meals.Explicit consent to record them and show them to your household: you choose to add them and can remove them at any time. When an admin enters another person’s allergies, we rely on the admin’s statement that they have that person’s agreement or are their guardian (section 13). Sending them to Orbrey AI is covered by the Orbrey AI row above, not by this consent.
Birthday and child age bandShowing the birthday you add to your own profile, and recording the age band a guardian picks when creating a child account.Consent: you, or the guardian, choose to enter it.
Feedback and bug reportsReading the messages you choose to send us, fixing what you report, replying if you typed an address, and deciding what to build.Legitimate interests in hearing from the people who use Orbrey and fixing what they report. You choose to send each message, and you can ask us to delete it.
Responding to youSupport emails, privacy requests and complaints.Legitimate interests; legal obligation for privacy requests.
Legal and safetyMeeting legal obligations, responding to lawful requests, protecting rights and resolving disputes.Legal obligation; legitimate interests.

The public marketing site has a Cookie choices banner for its non-essential tags. The signed-in web and mobile apps have no consent banner. Their Settings let you choose Product analytics, Advertising measurement and Error + crash reporting separately. On orbrey.com the banner is the only control, and you can reopen it from the footer (section 10).

Our legitimate interests are keeping Orbrey secure and working, and knowing whether it does. We weigh them against your rights, and we limit the impact by masking or scrubbing what the monitoring tools send, as far as section 9 describes, and by keeping IP addresses only briefly (section 12). You can object (see section 15).

4. Who we share it with

We do not sell or rent your personal information. We share it with the people and providers below, for the reasons given. Section 16 explains how US privacy laws treat advertising tags.

Other people in your household

Members of a household see that household's content, according to their role. That includes allergies and food preferences, Family Inbox items and the list of members. Child accounts can read household information too (section 11). If you are removed from a household or delete your account while other account holders remain, the content you added stays in the household. Other members of your household cannot read your Ask Orbrey conversations.

Service providers

These providers help us run Orbrey. We limit what each provider receives, but section 9 and the table below describe what they can see, including some content we could not filter out. Where a provider operates worldwide and we have not fixed a country, the table says so.

Service providers, what they do for Orbrey, what they can receive and where
ProviderWhat it does for usWhat it can receiveWhere
SupabaseDatabase, sign-in (including password-reset emails), file storage, and the server functions that run our back-end tasks.Everything in your account and household, including files.Database, sign-in and files: Singapore (ap-southeast-1). We have not pinned server functions to a region, so Supabase can run them elsewhere; they read and write the Singapore database.
VercelHosts the web app and orbrey.com.Technical request details such as IP address and browser type.Global edge network.
CloudflareRuns Orbrey AI and the Family Inbox email intake, the weather and address-suggestion service, the calendar-connection service and the connector for AI assistants. Also provides AI Gateway and Workers AI, the Turnstile bot check on sign-in pages, DNS lookups, and request logs for these services (section 9).The AI inputs in section 6, incoming Family Inbox emails, address text and, for a connected calendar, the server address you entered, your calendar login (decrypted in memory while a sync runs) and the events fetched, plus normal web request details.Global network; we have not fixed a country.
Google CloudScans Family Inbox attachments for malware.The attachment file itself.United States (us-central1).
Google PlacesAddress suggestions in the event location field.The text you type, a session token and, if your household has a weather location, its coordinates as a hint. Sent from our servers: not your identity or IP address.Not fixed by us.
Open-MeteoWeather forecasts and place search.Forecasts: your weather location rounded to about 1 km, sent from our servers. Place search in Settings: your browser contacts Open-Meteo directly, so it sees your IP address and what you type.Not fixed by us.
StripeWeb subscription payments.Your email and card details (entered on Stripe’s pages), plus our household and plan identifiers.Not fixed by us.
RevenueCatMobile subscriptions.Your household ID, the store, product and purchase status, and the country of your app-store account.Not fixed by us.
Apple and GoogleSign in with Apple and Google, app-store purchases and push delivery.Sign-in details; purchase details; and push messages.Not fixed by us.
Google ML Kit (Android)Reads text from receipts, scanned pages and photos on Android phones, on the phone itself.The text and the photo stay on the phone. The library has its own logging path to Google, which we have not checked, and no setting turns it off.Not fixed by us.
ExpoDelivers push notifications and app updates.Your push token and each notification’s title, text and link, which can include household content such as a name or a reward. On Android, update requests carry the app version, the platform, a random install ID and, after a crash, up to about 1,000 characters of the previous error message; we have not checked iOS. No setting turns update requests off.Not fixed by us.
ResendSends our email.Recipient address, subject and message. The weekly digest includes the household name, member names (or, for a member with no name, their email address), upcoming event titles, dinners, low-stock pantry items, rewards redeemed and task counts. A household invitation includes the inviter’s name, the household name and the names of up to four members.Resend is a company based in the United States. Its sending region has not been confirmed.
SentryError reports (section 9).Error details, the page or screen, browser or phone details (on the mobile app including its time zone, its language and region setting and an ID for this install), your account ID (web app and mobile app), the country Sentry works out from the IP address (seen on the mobile app, not checked on the web app or orbrey.com), and on the web app a replay of the screen with the text hidden (section 9).United States (we understand that our web and mobile projects both use the United States region).
PostHogProduct analytics, and reading the feedback you send us (section 9).Pages or screens viewed, events and, on the web app, clicks, tied to your account ID, with your household ID and member count (section 9). In the signed-in apps, only after you turn on Product analytics; on orbrey.com, only after you accept in Cookie choices. Separately, a feedback message when you press Send, whatever you chose about analytics (section 9).United States.
Meta and Google AdsAdvertising measurement, only after you accept marketing cookies (sections 9 and 10).Identifiers set by their tags, the pages you view and a sign-up event.Not fixed by us.

Services you connect

If you connect a calendar or an AI assistant, that service receives or sends information as you direct (section 7).

Our staff

Access to our administration tools is limited to staff who hold a platform-admin role or an admin role for a specific area, and only platform admins can make changes. Through them staff can look up households, accounts by email address and newsletter subscribers. The tools are designed to show identifiers, states, counts and dates, not household content such as event titles, Family Inbox text or Ask Orbrey conversations. Every request made through the tools is written to an audit log. Direct access to our database and its service keys sits outside these tools and can reach everything in the database.

Emails you send to privacy@orbrey.com and support@orbrey.com are held by the email provider that hosts those mailboxes. We have not named that provider in this policy, and what it keeps follows its own terms.

Legal requirements

We may disclose information if required to do so by law, court order or governmental authority, or to protect the rights and safety of Orbrey, its users or the public.

Business transfers

If Orbrey is involved in a merger, acquisition or asset sale, your information may be transferred as part of that transaction. We will give you notice before your information becomes subject to a different privacy policy.

What we have not yet verified

Where this policy says we have not confirmed something, it is because we could not check it from our own records or a provider's account. The list is accurate as of 7 October 2026, and we will update this policy when an item is confirmed. Each is also said where it matters.

  • What Cloudflare keeps from Orbrey AI requests, and for how long (section 6).
  • Whether a child account can start an Ask Orbrey chat (sections 6 and 11).
  • Whether the connector for AI assistants refuses every household that has a child account, a member without a login or an account of unknown type (section 7).
  • Sentry's retention (30 or 90 days, depending on our plan), whether the live web app sends Sentry page-load records, and whether Sentry works out a location for the web app's and orbrey.com's reports as it does for the mobile app's (section 9).
  • PostHog: the settings of the project that receives web events (retention, session recording, erasure), and the retention period of our PostHog plan (sections 9 and 12).
  • How long PostHog keeps feedback messages, and whether it can delete one sent without account details (section 9).
  • What the copy of Stripe's billing records in our database holds (section 8).
  • What Google's ML Kit library sends, and what Expo's update requests send on iOS (section 4).
  • Resend's sending region, and which provider hosts the privacy@ and support@ mailboxes (section 4).
  • The data processing terms and transfer safeguards that apply to each provider, and the country each one contracts from (sections 5 and 15).
  • How long our database provider keeps backups (section 12).

5. Sending information overseas

Yes, we are likely to disclose personal information to recipients overseas, because our database and several providers are outside Australia. For people in Australia, this is a cross-border disclosure under APP 8.

  • Singapore. Your account and household data are stored with Supabase in Singapore (ap-southeast-1). We have not pinned Supabase server functions to a region, so they can also process data briefly in other Supabase regions.
  • United States. Our PostHog project and, as we understand it, both of our Sentry projects use the United States region, so what they receive is processed there, and Family Inbox attachments are sent to Google Cloud in the United States for malware scanning. Resend, which sends our email, is a company based in the United States; its sending region has not been confirmed, so assume it may process email details there.
  • Other countries. Cloudflare, Vercel, Stripe, RevenueCat, Expo, Apple, Google, Meta and Open-Meteo run networks in more than one country, and we have not fixed where they process data. Orbrey AI runs on Cloudflare's global network.
  • Services you connect. If you connect an AI assistant such as Claude or ChatGPT, or a calendar service, that provider handles what it receives in its own locations.

If you are in the UK or EEA, this also means your information is transferred outside those regions. We have not yet confirmed which transfer mechanism (for example standard contractual clauses) covers each recipient; it is on the list under What we have not yet verified in section 4. You can ask us for the safeguards we have for these transfers at privacy@orbrey.com.

Section 4 lists which provider does what.

6. Orbrey AI

Orbrey AI is the set of features that use AI models: Ask Orbrey (the chat), suggestions (meal plans, ideas from your pantry and a weekly household review), imports and scans (pasted text, links, receipts), the Family Inbox reader and scheduled tasks.

Who runs the models

Every Orbrey AI feature runs on open-weight models hosted by Cloudflare Workers AI, reached through Cloudflare AI Gateway (currently IBM Granite, Google Gemma and OpenAI gpt-oss models). Cloudflare runs the models. Orbrey does not send your content to any other AI provider. If you connect an assistant such as ChatGPT or Claude yourself, that is a separate arrangement (section 7).

What is sent to the model

What each Orbrey AI feature sends to the AI model
FeatureWhat goes to the modelNotes
Ask OrbreyYour message (up to 2,000 characters), up to the last 8 turns of the conversation, your name or label, today's date and your time zone, your saved instructions and learned memories (up to 12 lines), and the household information it looks up to answer you: tasks, events, meals, groceries, pantry, recipes, lists, rewards and the list of members. That list includes members' names, allergies, foods to avoid and food preferences.It looks things up with your own permissions, so it sees what you can see. One answer can take several model calls, each resending the conversation.
Suggestions (meal plans, pantry ideas)Recipe titles, tags and cooking times (up to 60 of your most recently updated saved recipes), pantry item names, dates, your instructions and learned memories (up to 100 lines), and your reply to any clarifying question (up to 4,000 characters). For pantry ideas and custom meal plans it also sends the ingredient names in those recipes (up to 40 per recipe). Allergen screening runs before the request is built, and the request carries no member names or allergies.Suggestions are written by the AI model, not by fixed rules.
Weekly household reviewA summary of the household: how many tasks are overdue or done and how many routines there are; the titles of up to 5 tasks you add by hand again and again; the dates of unplanned dinners and how many meals, events and recipes there are; the usual busiest, shopping and planning days; up to 8 pantry items that are expiring; up to 10 grocery items you add by hand in most weeks; the household’s saved instructions (up to 20, not any one member’s personal instructions); the titles of scheduled tasks and earlier suggestions; and the names and roles of members who have Learn from our activity switched on.May run on Sunday evening in your household’s time zone. It runs only for a household where a household-wide Use Orbrey setting and a household-wide Learn from our activity setting are on, and whose plan has room for another scheduled task (the free plan has none). The apps read a household-wide Use Orbrey setting but do not currently let anyone switch it on (a member’s own switch is a separate setting), so we have not confirmed that it runs for any household. When it runs, a member’s own Use Orbrey switch does not keep their name out of it; only their own Learn from our activity switch does. It produces up to 3 suggestions a week for you to accept or ignore.
Imports and scansText you paste (up to 50,000 characters) or a link. For a receipt, a photo or PDF: in the mobile app the text is read on your phone first, and only the lines it finds are sent to Orbrey; no AI model reads them, and this works even if Use Orbrey is off. If that cannot run, the whole photo (up to 20 MB) or PDF (up to 15 MB) goes to a vision model. On the web the file is sent to the model.Recipe pages, event flyers and shopping-list photos are read on your phone in the mobile app. Nothing is added to your household until you review and confirm it, although the draft (the receipt lines, or the link, the first 10,000 characters of what you pasted and what we extracted) is kept as described under What Orbrey keeps. We do not keep the receipt image.
Family InboxThe notice text (up to 12,000 characters), the email subject, today’s date and time zone, and the first names of your household’s members. PDF and photo attachments go to a vision model when the text is not enough (an emailed notice sends at most 2 documents).If Orbrey AI is off, your allowance is used up, or the answer cannot be used, a rule-based reader (no AI) reads the notice instead. Attachments are also sent to Google Cloud for a malware scan first (section 4).
Scheduled tasksThe instructions you wrote, run later as if you had asked Ask Orbrey, with your permissions.A short summary of the result (up to about 200 characters) can appear in a push notification.

What Cloudflare keeps

We ask AI Gateway not to log the content of requests or answers. It still records which model was used, token counts, cost and speed. Cloudflare runs the models; the companies that built them (IBM, Google and OpenAI) do not receive your content from us. How Cloudflare handles requests inside Workers AI, including how long it keeps them, is covered by Cloudflare's own terms and privacy policy. We have not independently confirmed those terms, so assume Cloudflare may keep these requests under them.

What Orbrey keeps

  • Conversations. Your messages and Orbrey's replies are kept until your household is deleted. Other members of your household cannot read them. There is no button for deleting a single conversation yet; email privacy@orbrey.com and we will delete it.
  • Records of AI tasks, the activity log you can see in Settings (a short written summary of what Orbrey proposed or did, which can mention household items), and your feedback on suggestions: 400 days. Usage and cost records for each model call (which feature and model, token counts, cost and outcome, with no message text) are kept until your household is deleted.
  • Proposals, suggestions and scheduled tasks. The changes Orbrey asked you to approve (with their details and Orbrey's summary), suggested scheduled tasks and your answers to clarifying questions have no automatic deletion: they are kept until your household is deleted. A scheduled task is kept until you delete it or your household is deleted.
  • Learned memories: until you delete them.
  • Instructions: you can retire an instruction, which stops Orbrey using it, but you cannot delete one in the app. A retired instruction is kept until your household is deleted; email privacy@orbrey.com to have one deleted.
  • Your AI consent history (when you switched things on or off, and the version label recorded with each change): kept for up to 7 years while the household exists, and deleted with a household that is deleted. Earlier AI consent records may show version 2026-07-22. New AI consent choices record the applicable notice version: 2026-10-14 for the general AI controls and 2026-10-15 for Personalise recommendations. A record's version identifies the disclosure shown when that choice was made.
  • Receipt scans (the retailer, date, total and lines found, never the image): 7 days. Import suggestions (the first 10,000 characters of what you pasted, and what we extracted from it): until you delete them or your household is deleted.

Training

We do not train or fine-tune AI models on your household content, and nothing in Orbrey builds a model from it. Orbrey has a Help improve Orbrey switch. It is off unless you turn it on, and it says it never applies to children. Nothing in Orbrey currently reads that setting. If that changes, we will update this policy first.

Personalised recommendations

Orbrey is preparing an optional feature that can choose and order next-best-action recommendations using relevant activity from your household. It is not active in the current app. If introduced, it will use activity for an individual only when that active adult member has switched on the separate Personalise recommendations setting. That choice is off by default and does not let a recommendation make changes to household information; the usual permissions and confirmation rules still apply. Child profiles are not eligible.

Your controls

  • Use Orbrey is the master switch for AI features, and it is set for each member. It is shown as off for each member. Orbrey AI starts working for you only after you switch Use Orbrey on; saving another AI setting does not turn it on. Turning it off stops Orbrey AI working for you. It does not stop another member of your household, who has it on, from asking Orbrey about household information that includes yours, such as allergies. In the web app it is under Settings, then Orbrey, then Privacy & data; the mobile app has the same controls under Orbrey in Settings. With it off, the AI features that need a model stop working for you, and the Family Inbox uses its rule-based reader.
  • Learn from our activity is on unless you turn it off. Turning it off stops Orbrey forming and using learned memories, and you choose whether to keep the existing ones (unused) or delete them.
  • Personalise recommendations is a separate, off-by-default choice for active adult members. It will be used only if the optional recommendation feature is introduced and enabled; it does not allow Orbrey to make changes to household information.
  • Instructions and memories. Instructions can be viewed, added and retired (not deleted, see What Orbrey keeps). Memories can be viewed, edited, retired and deleted, and everything Orbrey has learned can be deleted at once. Both apps can export them: on the web it is under Settings, then Orbrey, and on the mobile app it is Settings, then Orbrey, then Download my AI data. Memories are short plain-language statements, not written by an AI model. In meal planning, three or more explicit “See fewer like this” actions can add or reinforce a recipe preference for that member when “Learn from our activity” is enabled. That preference affects only meals planned for that member. A household admin can also add a memory in Settings. Orbrey does not file memories under allergy, dietary-restriction or medical categories, but the text of a memory or instruction is kept as typed, so keep allergy and medical details in the member's profile.
  • Permissions. For each kind of action (look things up, add, change, remove, rewards) a household admin sets whether Orbrey AI asks first, goes ahead automatically, or never does it, and each member can make their own setting stricter but not looser. The defaults are: looking things up is automatic; adding, changing and removing ask first; and rewards are never touched.

Automated decisions

Orbrey AI suggests, and by default nothing changes until a member confirms it. If a household admin sets an action type to automatic, Orbrey AI can make those changes without asking. None of these features makes a decision about you with a legal or similarly significant effect on its own.

It can be wrong

AI can get things wrong: dates, quantities, who a task belongs to, or whether a recipe suits someone with an allergy. Check what it proposes before you confirm it, and do not rely on it for allergy or medical decisions.

Children

A managed child account can read household information but cannot ask Orbrey AI to change anything. We have not checked whether a child account can start an Ask Orbrey chat. Nothing we found in our code blocks it by name, though a child account cannot switch Use Orbrey on, which may stop it, and what it could ask about is limited to what the child account can read, which includes members' names and allergies.

7. Connected calendars and apps

Calendars

Calendar connections are being rolled out and may not be available to you yet. Orbrey currently connects to CalDAV calendars (such as iCloud) and Google Calendar; it does not connect to Outlook or Slack. If you connect a calendar (a CalDAV calendar, with a server address, username and app password, or Google Calendar through Google's sign-in), Orbrey imports its events: the title, start and end, all-day flag, location and description, and, for CalDAV calendars, the time zone and repeat rule. We do not import the attendee list. The connection belongs to you and you choose which households see it. Managed child accounts cannot connect calendars.

Google will show that Orbrey asks to view and edit your calendars. Today Orbrey only reads from Google; it does not create, change or delete events there, and if that changes we would update this policy first.

  • Your calendar password or sign-in token is stored encrypted (AES-256-GCM). The key is held by our calendar-connection service, not in the database, so the database alone cannot read it.
  • Before connecting to a CalDAV server, our service looks up its host name through Cloudflare's DNS service.
  • Disconnecting deletes the stored credential, the imported events and the sync state, and ends any household sharing. We keep a short record that the connection existed and when it was disconnected, until you delete your account. We do not revoke the connection at the calendar provider. To remove Orbrey's access at Google, use your Google Account's third-party access page.

AI assistants (Claude, ChatGPT and others)

You can connect an AI assistant to Orbrey through our connector at mcp.orbrey.com, which runs on Cloudflare. On the consent page you choose which household and which areas (read or write) the assistant can use. Each connection covers one household. The assistant sends Orbrey the details of each request, for example "list this week's tasks", and Orbrey sends back the records or results. Orbrey does not receive the full conversation. The assistant's provider keeps its own copies under its own terms; manage or delete those in the assistant.

Adults only. Connected assistants are designed to be refused for a household that includes child accounts, members without a login (guests), or accounts whose type is unknown. This check uses stored account types. It does not verify anyone's age or scan free-text records for references to minors, and we have not read the connector's code to confirm it (see What we have not yet verified in section 4).

Grants expire after 180 days, or sooner if a grant has been used and is then left unused for 90 days. You can revoke one at any time in the web app under Settings, then Connected apps (we ask for extra verification if you have set up two-factor sign-in). We keep a record that a grant existed and was revoked for 7 years.

Links to other sites

In the mobile app, tapping an event's location opens Google Maps with that text. Other links go to the sites they name, which have their own policies.

8. Payments

  • On the web, subscriptions are paid through Stripe's hosted checkout and billing portal. You enter your email, and your card when one is needed, on Stripe's pages. We send Stripe an identifier for your household, your user ID and the plan you chose, and we receive back a Stripe customer ID, a subscription ID, the plan, its status and period, and whether it is a founding-member plan. A synchronised copy of Stripe's billing records for your household is also kept in our database in Singapore, and it can include your email address and billing details.
  • In the mobile app, you pay through the Apple or Google store. RevenueCat tells us your household ID, the store, the product, the purchase status, the expiry and the transaction IDs, and we keep the complete notification it sends. The app also sends us your platform, app version and the country of your app-store account so we can show the right purchase options.
  • We do not receive your card number in either case. A subscription belongs to the household, not to an individual's store account.

Deleting your account when you are the only account holder in a household deletes our billing records for it, and we ask Stripe to delete the customer record. Deleting a household on its own may currently fail (section 12); when it works it deletes our billing records but does not ask Stripe to delete the customer or cancel a web subscription, so cancel in the billing portal first. The synchronised copy of Stripe's records in our database follows Stripe's own records, and our household deletion does not itself remove it. Stripe, Apple and Google may keep their own transaction records under their own legal obligations, and we cannot delete those. If you bought through an app store, cancel in the store first, because we cannot cancel it for you.

9. Error reports, analytics and session replay

We use a few tools to find faults, measure performance and understand how Orbrey is used. Which run depends on where you are and what you choose. PostHog also receives the feedback you choose to send, which the section Feedback and bug reports below describes.

Which monitoring tools run on the web app, orbrey.com and the mobile app
ToolWeb apporbrey.comMobile app
Error reports (Sentry)Only when your signed-in account has Error + crash reporting enabled in Settings, then Account, then Privacy preferences.Always on. There is no setting on the site.On by default. Turn it off in Settings, then Data & privacy. It is the same choice as the web app’s Privacy preferences.
Product analytics (PostHog)Off until your signed-in account has Product analytics enabled in Settings, then Account, then Privacy preferences.Nothing is stored or sent until you accept in Cookie choices.Off until you turn it on. Never for child accounts. It is the same choice as the web app’s Privacy preferences.
Advertising measurementGoogle Ads only, after your signed-in account enables Advertising measurement in Privacy preferences.Meta Pixel and Google Ads, only after you accept.None.
Session replaySentry, around an error, if you allow error reporting: a replay with the text hidden, from shortly before it until the session ends (at most 60 minutes). PostHog recording: see below.None from Sentry. PostHog recording: see below.Off in the released app.
PerformancePage-speed measures with analytics; Sentry traces with error reporting.Sentry traces.Sentry traces and PostHog speed events with the matching switches.
Feedback and bug reports (PostHog)Only when you press Send in the feedback form. It does not depend on your analytics choice.Only when you press Send on the support page. It does not depend on your cookie choice.Only when you press Send in the feedback form. It does not depend on your analytics choice.

What happens while analytics is off

In the signed-in apps, PostHog analytics stays off until Product analytics is on in Settings. On orbrey.com, PostHog analytics and advertising tags wait for you to accept in Cookie choices. A message you send through a feedback form is separate: it goes to PostHog when you press Send. Other things do not wait for a choice:

  • Web app. No error reports or Product analytics events are sent until their corresponding Settings choices are on. The Cloudflare Turnstile bot check loads on the sign-in and sign-up pages, and our hosting providers see the usual request details, such as your IP address (section 4).
  • orbrey.com. Error reports and a sample of traces run with no setting (see below).
  • Mobile app. Crash reports are on by default. It checks Expo for updates and, on Android, uses Google's ML Kit to read text on the phone. Update checks and ML Kit requests have no switch (section 4). Analytics stays off until you turn it on.

Sending feedback is separate from all of this. A message you send through a feedback form goes to PostHog when you press Send, whatever you chose above, and no message is sent before then (see Feedback and bug reports below).

Your analytics, error-reporting and marketing choices are one record on your account. A choice you save in the web app's Privacy preferences also applies in the mobile app, and a choice you save in the mobile app applies to the web app when you next open Privacy preferences there. A change made on another device reaches the mobile app's analytics setting when the app next opens, but it can take up to about a week to reach its crash-report setting.

Error and crash reports (Sentry, United States)

  • What they contain. The error type, its message and where in the code it happened; the app or site version, your browser or phone model (the events we checked carried the model, not the name you gave your phone), operating system, and the page or screen. On the web app and orbrey.com the report also carries the full address of the page, including anything after a ? or #, and the page you came from; a short trail of recent activity (page changes, clicks, console messages and the addresses of recent requests to our servers, which can include search words, record IDs and, occasionally, file-link tokens); and, for the sample of page loads we trace, the addresses and timings of the requests the page made. The mobile app's reports carry more about the phone, listed in the next point. On the web app and the mobile app every report carries a random user ID, which is your account's ID and not your name or email. For failed data requests they include the error code, details and the IDs of the records involved, the web app also attaches the screen component stack, and database error messages can occasionally include a fragment of the record involved.
  • What the mobile app's reports add. The Sentry user record holds your account's ID only: no name and no email address. Labels for the environment, release, app version and build number, your phone's model and a performance tier, the operating system version, the network type, whether you were offline or signed in, and a band for your household's size. Details about the phone that Sentry's library adds: its manufacturer and model, screen size and density, memory and storage, battery level and whether it is charging, which way it is held, whether it is a simulator or has been rooted, when it was last started, its time zone, its language and region setting, an ID for this install of the app, and which of the permissions the app can ask for you have granted. A crash report also carries the stack trace, which is the path through our code that failed, and a short trail of what happened just before (up to 50 entries): the last screens you moved between, that you tapped something (not what it said), and the method, result and address of recent requests, with record IDs replaced and anything after a ? left out. Together these can link the reports from one phone to each other and to your account, so they are pseudonymous, not anonymous.
  • What we remove. On the web app and orbrey.com our code removes any IP address the Sentry library attaches to an error event, and on the web app your email and username as well. On the mobile app, text is passed through scrubbers that rewrite emails, tokens, links, long identifiers and similar before it is sent. They are heuristics and cannot recognise a first name or a recipe title, and crash reports created by the phone's native layer do not pass through them. Whatever the surface, the IP address you connect from is visible to Sentry as part of the request itself. Our Sentry account is set to remove IP addresses on Sentry's own servers, for both the web and the mobile project, and to scrub certain sensitive fields on arrival (for example email addresses, household names, prompts, invite codes and tokens). That is a second line of defence behind our own scrubbing, not a replacement for it.
  • Location and IP address. Neither app reads your device's location, but Sentry works out a rough location from the IP address a report arrives from. We saw this on the mobile app's reports, and we expect the same for the web app and orbrey.com, which we have not checked. Since 7 October 2026, storing IP addresses is switched off in our Sentry organisation and in both projects, and a rule removes the city and region, so Sentry keeps only the country. Reports received before that day may still hold the address, the city or the region until they expire.
  • Traces. A sample of how long things took, with the page or screen and timings. On the web app and orbrey.com a trace also lists the requests the page made, with their addresses. On the mobile app they are not sent for child accounts.
  • The mobile app is on by default. A crash can happen before you have signed in or seen a setting, so the switch (Settings, then Data & privacy, then Crash reports) starts on. If you turn it off we remember that on the phone even after you sign out. Sentry also records each time the app is opened (the app version, whether it ended in a crash, and possibly your account ID) so we can see how many people a crash affects. For a short moment at app start, before your choice is read, a report or an app-opened record can still be sent.
  • The web app loads this tool only if you allow it, and only on the live site. Once you allow it, Sentry may also receive a small record each time you load or change page, with no error in it, so we can count crashes per release; whether it does depends on how the live build was made, which we have not confirmed. Withdrawing stops sending, but cannot recall what was already sent.
  • orbrey.com sends error reports, and a sample of traces, with no setting. To object, email privacy@orbrey.com.
  • Bug reports (web app). A bug report from the web app goes to PostHog through the feedback form (see Feedback and bug reports below), and the form sends nothing to Sentry. Sentry sends a replay of the screen only around an error (see Session replay below).
  • Child accounts. On the mobile app, errors are still sent for a child account, and only traces are not. A child's report carries the child account's ID and the same phone details and ID for this install as an adult's (listed above), and Sentry works out the country from the IP address in the same way.
  • How long. Sentry deletes error reports when the retention period of our Sentry plan ends, which is 30 or 90 days depending on the plan. Deleting your account does not delete them sooner: they expire on their own (section 12).

Usage analytics (PostHog, United States)

  • Who you are to PostHog. A random user ID (your account's ID), plus a household ID with the number of members (a household created in the app is also labelled free once, and the label is not updated). No names or email addresses. Earlier versions of the apps also sent account emails and household names to PostHog. They no longer do in the mobile app from version 1.0.4 and in the web app from the release that comes with this policy; earlier versions did, and those earlier properties may still be held there. If you would like us to delete analytics data held about you, email privacy@orbrey.com. We can ask PostHog to delete it, except web analytics sent before 8 October 2026, which went to a different PostHog project that we cannot currently open.
  • Web app. Sign-up method, checkout started (plan), household created, member joined, meals planned (which day and meal slot), grocery lists made from a meal plan (how many items), pantry items added (how), members invited (and by which method), recipes cooked (servings), recipes imported (the source website and counts), paywall views, activity in Household updates (sharing, reacting, hiding and opening updates, with the kind of update but not its text), which AI app you approved or declined and how many areas, and page-speed measures. PostHog's automatic page views and click tracking also record the full page address, including anything after a ? or #, and the text of the button or link you click, which can include names you have entered (for example a task, recipe, list or family member shown on a button or link).
  • Before Product analytics is on. In the signed-in web app, the authenticated account's saved Product analytics setting is applied after sign-in. Until it is on, the app does not set a PostHog cookie or storage entry, send an event, or make a request to PostHog. The signed-in apps have no consent banner. On orbrey.com, PostHog waits for you to accept in Cookie choices. When you turn analytics off in the web app's Privacy preferences, it stops sending and removes the cookie and storage entries it had saved. Turning it off cannot recall what was already sent, including an event captured shortly before the change that had not yet left your device. If you used either site before 7 October 2026 and did not enable analytics in the app or accept on the marketing site, an earlier version may have saved an identifier. It is not read or sent until the relevant setting or cookie choice is applied; turning analytics off or clearing site data removes it. A feedback message is separate: it goes to PostHog only when you press Send (see Feedback and bug reports below).
  • orbrey.com. Page views (with the page address and its query), blog reading (post, category and tags), whether you read most of a post, helpful votes, clicks on our sign-up buttons, pricing views, and newsletter sign-up attempts (never the email).
  • IP address and location. Your IP address reaches PostHog as part of every request, on the web app, orbrey.com and the mobile app. On the mobile app, our PostHog project is set to discard it, the app tells PostHog not to look up a location from it, and the events we checked carried neither an IP address nor a location. On the web app and orbrey.com, PostHog's library is told not to record the address, and we have not confirmed PostHog's own setting for discarding it on the project that receives those events.
  • Mobile app. Only after you turn it on and only for accounts that are not child accounts: the screens you open (as page names, not content), speed measurements, household-updates activity and a few product events such as sign-up method, checkout started, household created and meal planned. Each event also carries the app version and build, the release and environment, your phone's model and device type, operating system, screen size and a performance tier, the network type, whether you are offline or signed in, and a band for your household's size. PostHog also keeps the same app, operating-system and device details on your analytics profile. These are linked to your account ID, so they are pseudonymous rather than anonymous. The app tells PostHog not to look up a location from the IP address. Turning analytics off, or using a child account, stops events at once and deletes unsent events from your phone; PostHog's stored ID is deleted the next time the app starts. Signing out replaces PostHog's stored ID with a new random one and deletes unsent events.
  • The feedback form. If you have allowed analytics, the web app, orbrey.com and the mobile app also count that the feedback form was opened and whether a message was sent. These counts carry no message text.
  • How long. We keep analytics events for the retention period of our PostHog plan, which we have not confirmed, and we do not delete them earlier on a schedule. Deleting your account does not yet delete your PostHog data automatically. To have it erased, email privacy@orbrey.com and we will ask PostHog to delete what we can reach (section 12 says what stays).

Feedback and bug reports (PostHog, United States)

  • What it is. The web app, the mobile app and orbrey.com each have a form for sending us a bug report, an idea, a question or some praise. In the web app and the mobile app you can also open it from an error screen. On orbrey.com it is the support page, where visitors are signed out, so it has no account option and no rating. The mobile app does not offer the form on a sign-in made for a child. The one exception is the report form on an error screen, which cannot tell whose sign-in it is: a report sent from there carries no account, household or email address, only any note typed into it and the app version, device and error name.
  • When it is sent. Your message is sent only when you press Send, and closing the form sends no message. If you have allowed analytics, we also count that the form was opened and whether a message was sent, never its content. A message goes to PostHog over HTTPS as a single event. It does not use PostHog's analytics library, and it does not depend on your analytics choice: you can send feedback after you decline analytics or cookies, and sending it does not turn analytics on.
  • What a message contains. Your text, with obvious credentials such as tokens replaced (see below); whether it is a bug, an idea, a question or praise; an optional rating from 1 to 5 (in the web and mobile apps; the orbrey.com form has none); which app it came from and where you opened the form; and the app version and build, platform and operating system version, device model (on a phone), language and region setting, and the screen you were on, with IDs and long codes removed. It also says whether the build is a test or live build. On the mobile app it also says whether the build came from a beta or a store release, and gives its release, commit and update identifiers. A message sent from an error screen also carries the type of the error (for example TypeError), never its message, and, where a crash report exists, Sentry's reference for it so we can match the two. Each message also records its length and how many pieces of text were replaced.
  • Only if you choose. Your account ID and household ID go with a message only if you turn on Include my account details, which is off unless you turn it on. Your email address goes with it only if you type one for a reply. The orbrey.com form has no account option.
  • What a message does not carry. Your name, the text of an error message, a screenshot or any file (the form cannot attach one).
  • Who you are to PostHog. Without the account switch, nothing links one message to another (an email address you type each time would): each message gets its own random one-off ID, made when you press Send, and PostHog creates no person record for it. With Include my account details on, a message carries your account ID, so we can see your messages together, and it is sent under that ID, the same one PostHog analytics uses. That creates a PostHog record for your account even if you declined analytics.
  • Location and IP address. A message tells PostHog not to look up a location from your IP address. Your IP address still reaches PostHog as part of the request, and our PostHog project is set to discard it.
  • What is stored on your device. The form stores nothing on your device. The one exception is the mobile app: if a message could not be sent (no connection or a temporary error), the app keeps the finished message, with obvious credentials already replaced, in a small queue on the phone, at most 20 messages, and sends it later. A queued message is kept until it is sent, and is removed if it is still unsent after 14 days, the next time the app opens. It is also removed if it carries your account ID and you sign out. If PostHog refuses a message, the app drops it from the queue.
  • Free text. What you type is free text. We replace obvious credentials, such as tokens and keys, before the message leaves your device. That catches accidents. We cannot recognise personal information in free text, so the form asks you not to include passwords, or financial or health details. Please do not put anyone else's personal information in a message.
  • What we do with it. Our team reads messages in PostHog to fix problems and decide what to build next. If you typed an email address, we may reply to it from support@orbrey.com, and we use the address only to answer that message. If the form cannot send your message, it offers to open an email to support@orbrey.com instead, with the same kind of app and device details underneath and never your account or household ID.
  • How long we keep it, and deleting it. We have not confirmed how long PostHog keeps events on our plan, so we do not state a period for feedback. To ask us to delete a message, email privacy@orbrey.com and tell us the reply address you typed or the account you sent it with, so we can find it. A message sent without account details has no person record in PostHog, so we may not be able to delete it ourselves and may have to ask PostHog, and we cannot say how long that takes. A message with no reply email and no account cannot be traced to a person, so we cannot find it to delete it. A message sent with account details is tied to your account's PostHog record (section 12 says what happens to that record when you delete your account).

Session replay

  • Mobile app: not running. PostHog screen replay is switched off in the released app and in test builds. It runs only in development and benchmark builds that are never given to customers. We have checked what a recording shows on one Android screen only, a sheet, on an emulator: it showed the layout, what was selected and the icons, and hid text, emoji, photos and initials. We have not checked an iPhone, a physical phone or any other screen. Before it is ever turned on for the released app it would need your analytics consent, it would never record a child account, and we would update this policy first.
  • Web app: Sentry, around an error. If you allow error reporting, your browser keeps the last minute or so of what happened on screen in memory. If an error occurs, Sentry sends that and then keeps recording until the session ends (after a period of inactivity, or at most 60 minutes). So a replay runs from shortly before the error until the session ends. All text is masked and images and media are blocked in your browser before anything is sent, but the layout of the screen, the page address and the addresses of requests are not masked. A session in which no error happens is never sent.
  • Web app and orbrey.com: PostHog. PostHog's browser library can also record sessions, and PostHog project settings can switch on screen recordings, heatmaps and surveys. Our setup masks form fields but not other text on screen. An earlier internal record shows session recording as switched off for our PostHog project, and we have not re-checked that setting for the project that receives web events. Nothing in our code asks for heatmaps or surveys. If we turn recording on, it would run only while Product analytics is on in the signed-in app or after you accept analytics in Cookie choices on orbrey.com, and we would update this policy first.

Advertising measurement

If you press Accept all on orbrey.com, Meta Pixel and the Google Ads tag load. Meta receives a page view on each page and an event when you view pricing. Google's tag reports your visit to Google Ads. In the signed-in web app, if your account has Advertising measurement enabled, the Google Ads tag reports one sign-up event when a newly created account first signs in. We do not send your name, email or other contact details to either, although these tags set their own cookies and receive your IP address, browser details and the pages involved, and settings inside Meta's and Google's own accounts can add to what they collect. Once you withdraw, they stop loading from the next page; what they already received stays with them.

Test and benchmark builds

Every build of the mobile app labels its events with its environment (development, preview, test, benchmark or production), so test traffic can be separated from real use. Benchmark builds are never given to customers.

Our server logs

Each request to our AI service writes one log line (a request ID, the kind of request, the result and how long it took) that is designed to carry no account IDs, message content or tokens. Our calendar-connection and other services write short log lines of their own that can include a connection ID and an error name, and are not meant to carry message content. Our Cloudflare Workers also have Cloudflare's own request logging switched on, which Cloudflare keeps under its own retention. If someone sends an email to a Family Inbox address that does not exist, we log the part of the address before the @ (not the sender) and the message size. Error logs can occasionally include a short fragment of a database error.

A monitoring job also posts short summaries of system faults (which job failed, counts and error text) to an alerting webhook that our team reads. They are not meant to carry household content, but the error text is free-form.

10. Cookies and similar technologies

Cookies are small files a website saves in your browser. We also use local storage and session storage in your browser, saved data in the mobile app, and identifiers inside software we use. We call them all "cookies and similar technologies". "Essential" items are the ones the service cannot work without or that remember a choice you asked us to remember; we ask before using anything else. Names are shown as written in our code; a trailing * means there are several. The Type column says where an item is kept and who sets it.

Web app (app.orbrey.com)

Cookies and similar technologies on the web app
Name or keyTypeWhat it is forHow longNeeds consent?
sb-<project>-auth-tokenLocal storage, set by usKeeps you signed in (also -code-verifier and -user).Until you sign out or clear site data.No (essential).
orbrey_consent_v1Local storage, set by usTemporary browser copy of your signed-in account’s analytics, advertising and error-reporting choices. The account record is authoritative; signing out or switching accounts clears this copy.Until you sign out, switch accounts, or clear site data.No (essential).
heimora.current_household_id.v1Local storage, set by usRemembers which household you were using.Until cleared.No (functional).
sidebar:stateCookie, set by usA cookie that remembers whether the sidebar is open.7 days.No (preference).
orbrey.appearance.v1, orbrey.theme.userHasSet.*, calendar:view-type, orbrey.calendar.*, mealPlannerView, grocery.filterMode, grocery.sidebarCollapsed, recipes.organizeBy.*, recipes.organizeView.*, recipe.servingsDesired.*, lists-page-sort-by, rewards_hide_redeemed, rewards_assignment_order:*, rewards_column_order:*, orbrey.degraded-read-banner.dismissedAtLocal storage, set by usPreferences and interface state: your theme and whether you have chosen one, your calendar, meal planner, grocery, recipe, list and rewards views, sorting and ordering, your serving choice for each recipe, and whether you dismissed a notice that data may be out of date. Some keys include your user, member, household or recipe ID.Until cleared.No (preference).
orbrey.checklist.*, orbrey.show_tour.*, orbrey.tour_completed.*, orbrey_seen_badges_v1:*Local storage, set by usYour progress through the tour and the setup checklist, and which badges you have seen. These keys include your user, household or member ID.Until cleared.No (preference).
orbrey_member_joined_v1:*Local storage, set by usRemembers that this browser has already counted you joining a household, so it is counted once. It is saved even if Product analytics is off; nothing is sent unless analytics is enabled.Until cleared.No (a local marker; it sends nothing).
orbrey.draft.v1:*, orbrey:qi-draft:*, task_timers_state_v2, family-inbox-aliases:*, orbrey.pantry-transfer-recovery.v1:*Local storage, set by usKeep what you were typing, running task timers, your Inbox forwarding address and pantry transfers so nothing is lost. These hold your content as plain text on that browser and are not cleared when you sign out, so clear site data on a shared computer.Until you save or clear them.No (functional).
orbrey.household_snapshot.v1:<your user ID>Local storage, set by usA copy of your households and, for the household you are in, its member list (names and nicknames, emails if added, roles, colours, photo file paths, allergies, foods to avoid and food preferences), so the app opens quickly. It is plain text on that browser.Until you sign out or sign in as someone else.No (functional).
orbrey.verify.email, orbrey.verify.userIdSession storage, set by usCarry your email and ID through email verification.Until you close the tab.No (essential).
orbrey.chunkReloadAt, app:lastNonSettingsPath, orbrey.onboarding.*Session storage, set by usStop reload loops after an update, return you from Settings, and track onboarding steps.Until you close the tab.No (functional).
sentryReplaySessionSession storage, set by SentryHeld by Sentry’s screen replay while error reporting is on.Until you close the tab.Yes (error reporting).
__Secure-orbrey_mcp_requested_scopes, orbrey_mcp_requested_scopes, __Secure-orbrey_mcp_client_idCookies on orbrey.com, set by our connector for AI assistantsCarry which AI app and permissions you are approving to the consent page.A few minutes.No (essential).
ph_*Local storage, session storage and a cookie that covers orbrey.com and its subdomains, set by PostHogPostHog analytics identifier.Cookie up to 365 days. The session-storage entries last until you close the tab. All are removed when Product analytics is turned off.Yes. In the signed-in web app, created only while Product analytics is on.
__ph_opt_in_out_*Local storage, set by PostHogRecords whether PostHog is enabled on this browser based on the signed-in account’s Product analytics setting.Until the account choice changes or you clear site data.No (records your choice).
Google Ads tag cookiesCookies, set by GoogleAdvertising measurement of sign-ups after the signed-in account enables it in Settings.Set by Google.Yes (marketing).
Cloudflare TurnstileSet by CloudflareA bot check on the sign-in and sign-up pages. Cloudflare may set its own storage.Set by Cloudflare.No (security).

Website (orbrey.com)

orbrey.com has no sign-in, so it sets no sign-in cookies. Our code uses local storage for Cookie choices and blog feedback; it does not set browser cookies.

Cookies and similar technologies on the marketing website
Name or keyTypeWhat it is forHow longNeeds consent?
orbrey_consent_v1Local storage, set by usRemembers your Accept all or Reject non-essential choice.Until you clear site data.No (essential).
orbrey:post-feedback:<post>Local storage, set by usRemembers that you have voted on a blog post, so the vote counts once per browser.Until cleared.No (functional).
ph_*Local storage, session storage and a cookie that covers orbrey.com and its subdomains, set by PostHogPostHog analytics identifier.Cookie up to 365 days. The session-storage entries last until you close the tab. All are removed when you withdraw analytics in Cookie choices.Yes. Not created until you accept analytics.
__ph_opt_in_out_*Local storage, set by PostHogRecords that you accepted analytics on this browser. Saved when you accept, and removed when you decline or withdraw. Nothing is stored for a visitor who has not accepted. Pressing Reject saves only our own record of your choice.Until you decline, withdraw or clear site data.No (records your choice).
Meta Pixel cookiesCookies, set by MetaAdvertising measurement.Set by Meta.Yes (marketing).
Google Ads tag cookiesCookies, set by GoogleAdvertising measurement.Set by Google.Yes (marketing).
ph_idA parameter in the link, not stored by the siteIf you have accepted analytics on orbrey.com, the link to the app can carry a random analytics ID in its address, so a visit can be linked to a later sign-up. If you have not accepted, the link has no ID. The signed-in app adopts that ID only while Product analytics is on; while it is off, the app holds the ID in page memory and neither sends nor stores it. The newsletter form stores the ID with your subscription. The app removes it from the address bar.In the link, in the app’s PostHog storage, and with a newsletter subscription until it is deleted.Yes: only if you accepted analytics on orbrey.com.

Mobile app

The app uses no cookies. It saves the following on your phone or uses these identifiers.

Data saved on the phone and identifiers used by the mobile app
Name or keyTypeWhat it is forHow longNeeds consent?
Sign-in sessionPhone storage, set by usKeeps you signed in.Until you sign out.No (essential).
orbrey.device-id.v1Phone storage, set by usA random ID for this install, so one phone has one push target. Not a hardware or advertising ID.Until you uninstall.No (needed for notifications you allow).
Push token (kept on our servers)Our serversDelivers notifications.Until it is replaced, rejected by the push service, or you delete your account. Signing out does not remove it, so notifications can keep arriving on that phone until another person signs in on it, you turn notifications off in your phone’s settings, or you delete your account.You are asked for notification permission.
orbrey.telemetry.errorReporting.v1, orbrey.telemetry.accountKind.v1Phone storage, set by usRemember a crash-report opt-out and whether the account is a child account.Until cleared.No (essential).
orbrey-query-cache, orbrey.offline_read.v1:*, orbrey-offline-write-failures.v1, queued offline changesPhone storage, set by usSave recent data (a cache of about 2 MB, and saved lists, groceries and pantry) and changes made offline so the app opens and works without a connection.Removed when you sign out.No (functional).
orbrey.household_snapshot.v1:<your user ID>Phone storage, set by usA copy of your households and the member list of the household you are in (names, emails if added, allergies, foods to avoid and preferences), so the app opens straight to Home without a connection.Removed when you sign out.No (functional).
orbrey.family-inbox.pending-share.v1Phone storage, set by usHolds up to 20 shared items, which can include attachments, until they upload.Until uploaded.No (functional).
orbrey.recipe.pending-share-import.v1, orbrey.family-inbox.share-dedupe.v2Phone storage, set by usThe first holds up to 20 recipe links or pieces of text you shared to Orbrey until they are imported. The second keeps fingerprints of recent shares, not their content, so one share is not handled twice.Until imported or 7 days; the fingerprints for a short time.No (functional).
Theme, pinned lists, recipe tabs, screen counts and a first-launch markerPhone storage, set by usRemember your settings.Until cleared.No (preference).
.posthog-rn.json, .posthog-rn-logs.jsonPhone storage, set by PostHogPostHog's ID and unsent events.Created only after you turn on analytics. Unsent events are deleted when you turn it off, sign out or use a child account; the stored ID is deleted or replaced the next time the app starts or you sign out.Yes.
A feedback message that could not be sentPhone storage, set by usIf a message could not be sent (no connection or a temporary error), the app keeps the finished message here, with obvious credentials already replaced and the details listed in section 9, at most 20 messages, and sends it later. A message that carries your account ID is deleted from here if you sign out.Until it is sent. Removed if it is still unsent after 14 days, the next time the app opens.No (you pressed Send).
Identifiers inside toolsIdentifiers kept by Sentry, RevenueCat and ExpoSentry uses your account ID and an ID for this install of the app; RevenueCat uses a random anonymous ID and then your household ID; Expo’s update requests carry a random install ID.Kept by those providers.Expo and RevenueCat have no switch; Sentry follows the crash-report switch. See sections 4, 8 and 9.

Changing your choices

  • Web app: there is no consent banner. After signing in, use Settings, then Account, then Privacy preferences to choose Product analytics, Advertising measurement and Error + crash reporting separately, then select Save. The choices are stored on your account and restored in the web app and mobile app after sign-in. Saving records the current policy version. You can withdraw the choices there at any time.
  • orbrey.com: the banner keeps your choice in your browser. To change it, use Cookie choices in the footer, which reopens the banner with the same two buttons, or clear orbrey.com's data in your browser and the banner will ask again. There is no separate switch for each purpose on the site. The public site and signed-in app use separate choice flows. The app's account setting does not replace the public site's Cookie choices. PostHog's identifier cookie is shared on orbrey.com only after analytics has been enabled for the relevant surface.
  • Mobile app: Settings, then Data & privacy. Your analytics, error-reporting and marketing choices there are the same record as in the web app's Privacy preferences, so a choice you save in one place applies in the other (section 9 says how long a change can take to reach the phone). Update checks and ML Kit requests have no switch.
  • Your browser can block cookies and storage, but blocking the essential ones stops sign-in from working. We do not currently detect Global Privacy Control signals, and we do not respond to Do Not Track signals; on orbrey.com the advertising tags load only after you accept marketing cookies. In the web and mobile apps, Google Ads measurement follows the Advertising measurement/Marketing setting on your signed-in account.

11. Children and family members

Orbrey is made for adults to run a household. Children use it through a household member added without a login or a guardian-created child account. We do not knowingly allow a child to set up an account on their own. Children's information reaches Orbrey in three ways, through an adult or, for a child account, from the child's own device.

Members without a login

An adult can add a household member who has no account, such as a young child or a guest. We store a nickname, an optional email address, a colour, a photo, allergies, foods to avoid and preferences, because the adult entered them, on behalf of the person and for the household. An adult can remove a member in the app. To have a member's information erased completely, email privacy@orbrey.com.

Child accounts (mobile app)

A guardian (a household admin or manager) can create a child account in the mobile app. This is what that involves.

  • What we collect. No real email address: Orbrey makes a sign-in address of its own, in the form child-<random id>@child.orbrey.com, and the guardian sets the password (kept as a hash). The guardian types a display name and picks an age band (under 13, 13 to 15, 16 to 17, or unknown). We do not ask for a date of birth. The age band is a label we record; nothing in Orbrey changes what a child account can do based on it.
  • Guardian consent. The guardian ticks a box saying they are the child's parent or legal guardian and agree to Orbrey creating the account and using the child's information to run it. We record two consents (account creation and data processing) with the guardian, the age band, a version label for the child-account controls (not this policy's version) and the time. That is a confirmation by the guardian. We do not check their identity beyond it and we store no identity documents.
  • What a child account can do. It sees reduced, child-oriented screens and can read household information, including allergies, the member list and Family Inbox items. It cannot add or change household content, and it cannot ask Orbrey AI to change anything.
  • What guardians control. A guardian who is a household admin can suspend, restore or delete the child account from the member's page in the mobile app. The service also has room for in-app feature switches, a layout for the child and approval requests, but no screen in the app uses them yet. Orbrey never blocks, limits or monitors another app or the device.
  • Monitoring tools. On the mobile app, a child account sends no usage analytics, no performance traces and no session replay, and PostHog's unsent events are deleted from the phone (its stored ID the next time the app starts). Crash reports are different: when the mobile app sends them (section 9), a child account's are still sent, with the child account's ID, the phone details and the ID for this install listed there, and the country Sentry works out from the IP address. The web app uses the signed-in account's saved privacy settings and does not show a consent banner. A child's phone can register for push notifications like any other member's.
  • How long. Each child account gets a retention date 365 days after it is created. After that date a daily job marks the child's membership as deleted, expires the guardian consent record and deletes the child's controls and approval requests. It does not delete the sign-in itself, or the expired consent record, which stay until a guardian deletes the child account. The membership record itself, with the child's name or nickname, photo and any allergies or food preferences entered for them, is only flagged as deleted: it stays until a guardian deletes the child account or the household is deleted.
  • Deleting a child's data. A guardian can choose Delete child account in the app. It permanently removes the child's sign-in, household membership and consent record straight away. A short log of what the guardian did (who, what and when) stays in the household until the household is deleted, and no longer points to the child. Anything the household holds that mentions the child, such as an event title, stays in the household until someone deletes it. Email privacy@orbrey.com if you want help removing anything else.

Parents and guardians

If you are a parent or guardian of a child with a child account, this is what Orbrey holds, who receives it and how you stay in control.

  • What Orbrey holds. The child's sign-in (the made-up address and the password you set, kept as a hash), the display name and age band you chose, the consent record, and what the household holds about the child: their name or nickname, photo, allergies and food preferences if anyone enters them, and anything added to the household that mentions them.
  • Who receives it. Our database provider holds all of it. When the mobile app sends crash reports (section 9), those from the child's phone go to Sentry with the child account's ID, the phone details and the ID for this install listed there, and the country Sentry works out from the IP address. The child's push token and the text of notifications sent to their phone go to Expo. The phone checks for app updates and, on Android, can use ML Kit for on-device text recognition (section 4). On the mobile app a child account sends no usage analytics, traces or session replay. On the web app, settings are tied to the signed-in account; there is no consent banner.
  • Looking at it. A parent or guardian in the household can see what the household holds about the child on the member's page, as any household member can (section 13). To see, correct or delete anything else we hold about the child, email privacy@orbrey.com.
  • Stopping further collection. A guardian who is a household admin can delete the child account in the mobile app, which removes its sign-in at once and ends collection from the child's device. The app has no finer switches for a child account's data yet.
  • Ask Orbrey. A child account cannot make Orbrey AI change anything. Section 6 says what we have and have not checked about a child account starting a chat.
  • Family Inbox. Anyone who knows your household's Inbox address can send to it, with no list of allowed senders, and a child account can read Inbox items, including ones from senders you do not know. A household admin can turn forwarding off, or get a new address, in the web app or the mobile app under Settings, then Inbox.

Children in what an adult adds

Households put children's names, photos, allergies, school events and school notices into Orbrey. That information is handled like any other household content, and the adult who adds it has the responsibilities in section 13.

What we do not do

The mobile app has no advertising software and does not ask for App Tracking Transparency permission. It includes crash-reporting and analytics tools (section 9); analytics is off until an adult turns it on and is never used for a child account. We do not use your household content to build advertising profiles. If you believe a child has created an account without a guardian, contact privacy@orbrey.com and we will delete the account and the information we hold in our own systems within 30 days, and ask the providers that offer a way to delete what they hold to do so. Section 12 lists the providers we do not ask, and what stays and for how long. The mobile app does not offer the feedback form on a sign-in made for a child. The one exception is the report form on an error screen, which cannot tell whose sign-in it is: a report sent from there carries no account, household or email address, only any note typed into it and the app version, device and error name (section 9).

12. How long we keep information

We keep personal information for as long as we need it for the reasons in this policy. Where this table says "until deleted", it stays until you or your household delete it, or the household or account is deleted.

How long Orbrey keeps different kinds of information
InformationHow longNotes
Your account, household and contentWhile your account or household exists.Deleted when you delete them (see below).
Items you delete (events, tasks, lists, recipes, rewards and similar)30 days in Recently Deleted, then removed.You can restore an item or delete it permanently sooner. An automatic job removes expired items daily. If you restore an item, the copy Orbrey saved when you deleted it stays on record, marked restored, until your household is deleted.
Ask Orbrey conversationsUntil your household is deleted.Email us to delete a single conversation. If a member is removed or deletes their account, their conversations stay in our database but nobody in the household can open them; email us to have them deleted.
AI task records, the activity log and feedback on suggestions400 days.Task records and feedback carry no message text. The activity log keeps a short written summary of what Orbrey proposed or did, which can mention household items.
Proposals, suggestions and scheduled tasksUntil your household is deleted. A scheduled task: until you delete it or your household is deleted.The changes Orbrey asked you to approve (with their details and Orbrey’s summary), suggested scheduled tasks and your answers to clarifying questions. No automatic deletion.
AI usage and cost recordsUntil your household is deleted.These carry no message text.
AI learned memoriesUntil you delete them.Memories count for less as they age, but are not removed automatically.
AI instructionsUntil your household is deleted. You can retire one, but not delete it in the app.A retired instruction stops being used and is kept. Email us to have one deleted.
Your AI consent historyUp to 7 years while your household exists. Deleted with a household that is deleted.A record of your switches and the version label recorded with each change. Earlier AI consent records may show 2026-07-22. New AI consent choices record the applicable notice version: 2026-10-14 for general AI controls and 2026-10-15 for Personalise recommendations. In a household that continues after you are removed or delete your account, the record stays with your member reference removed.
Receipt scan records7 days.The receipt image is not stored.
Import suggestionsUntil deleted, or until your household is deleted.Include up to 10,000 characters of what you pasted.
Family Inbox items, original files and the sender logUntil your household is deleted.Archiving an item hides it but does not remove it. Deleting a household on its own may currently fail; if it does, email privacy@orbrey.com and we will delete it for you. When it works it removes the records; the stored original files are removed only when an account deletion deletes the household. Email us to have them removed.
Your profile photo file, if your membership ends in a household that other account holders keepNo automatic deletion.The file stays in storage after your membership is removed. Email us to have it removed.
NotificationsRead notifications are deleted 90 days after you read them.Unread ones are kept until read.
Household updates90 days by default.Set per type of update.
Queued and sent emailThe message text is removed once sent. The record is deleted 30 days after sending, or 7 days if it could not be sent.Deleting a user also removes queued email to their address.
Email verification tokensValid for 24 hours, then deleted within a day.Kept only as hashes. Password-reset links are issued and expired by Supabase’s sign-in service, and their lifetime is set there.
IP-based rate-limit counters1 day.The newsletter form counts attempts by the email address typed, for up to a day.
InvitationsExpire after 7 days; kept until your household is deleted.Include the invitee’s email address.
Connected AI app grantsExpire after 180 days, or 90 days after last use.The record of a revoked grant is deleted after 7 years.
Connected calendarsUntil you disconnect.Disconnecting deletes the credential and imported events. A short record that the connection existed and when it ended stays until you delete your account.
Billing recordsWhile the household exists.See section 8.
Reward and gem activity logUp to 7 years, or until your household is deleted.The log of transfers and redemptions.
Gem balances, gem transactions and redemption recordsUntil your household is deleted.No automatic age limit.
Blog newsletter subscriptionsUntil you ask us to delete them.Unsubscribing stops the emails but keeps the record (email, IP hash and the rest in section 2).
Blog helpful votesNo automatic deletion.A hash of your IP address and your user-agent text. Email us to have a vote removed.
Privacy requests7 years after we close them.The record includes the email address the request came from.
Account deletion log7 years.Your user ID and whether each provider confirmed deletion.
Your cookie, analytics and error-report choices (signed in)Until your account is deleted.The audit-log entry for each change stays. Its user columns are emptied when you delete your account, but earlier values recorded inside an entry can still carry your user ID.
Audit recordsNo automatic deletion.Records such as who approved a household action stay so others can review their history. When an account is deleted, the columns that name it are emptied, but details recorded inside an entry can still carry its ID.
Child accountsUntil a guardian deletes the child account. At 365 days the membership is only flagged as deleted, not removed.Each child account gets a retention date 365 days after creation. At that date the membership is marked deleted and the controls and approval requests are deleted. The membership record itself (name or nickname, photo, allergies and food preferences), the sign-in and the expired consent record stay until a guardian deletes the child account, and a log of guardian actions stays until the household is deleted. See section 11.
Error reports30 or 90 days, depending on our Sentry plan.Sentry deletes them when the retention period of our plan ends. Deleting your account does not remove them sooner (see below).
Analytics eventsFor the retention period of our PostHog plan, which we have not confirmed.We do not delete them earlier on a schedule. Deleting your account does not yet delete them. Email privacy@orbrey.com to have them erased (see below).
Feedback and bug reportsWe have not confirmed how long PostHog keeps them.Held in PostHog until they are deleted or age out of it. Email privacy@orbrey.com to have one deleted, and tell us the reply address you typed or the account you sent it with. A message the mobile app could not send is kept on the phone until it is sent, and is removed if it is still unsent after 14 days, the next time the app opens.
BackupsUntil the provider’s backups expire.Deleted data can remain in backups kept by our database provider until they expire.

Legal holds

If a legal hold applies to a household or person, for example because of a legal proceeding, we pause scheduled deletion for it and account deletion is refused until the hold is lifted.

What deleting your account does

Deleting your account takes effect immediately and cannot be undone. On the web app, go to Settings, then Account, then Danger zone. On the mobile app, go to Profile, then Settings, then Account, then Delete my account. If you cannot sign in, see our account deletion page or email support@orbrey.com.

  • Households where you are the only account holder are deleted from our database, with the records in them. Family Inbox files and profile photos are removed from storage, but recipe photos and event attachments are not (see below). If you are an admin of a household with other account holders, deletion is blocked: give up your admin role (making another member admin first if there is no other admin) or remove the other account holders from the household.
  • If other account holders remain in a household, your membership is removed and the content you added stays there for them. Your Ask Orbrey conversations also stay in our database, but nobody in the household can open them; email us if you want them deleted. Your scheduled tasks and the instructions and memories set for you are deleted with your membership. Your profile photo file also stays in storage; email us if you want it removed.
  • We delete your sign-in and push subscriptions, and we ask Stripe (the customer record, for a household we delete) to delete what it holds about you. We do not yet delete your PostHog data automatically: PostHog keeps the analytics person record and events tied to your user ID until they are erased on request. To ask us to erase them, email privacy@orbrey.com. Web analytics sent before 8 October 2026 went to a different PostHog project that we cannot currently open, so we may not be able to erase those older events. We cannot confirm that each provider has removed everything it holds. If one of them fails, the rest of the deletion still happens and we record the outcome.
  • Resend, which sends our email, keeps a log of the emails it sent you for a limited period, and we do not delete it. Sentry reports are not deleted for one person on request. They expire automatically after the retention period of our Sentry plan, which is a limited period (section 9). Until then, a report that carries your user ID stays in Sentry after your account is gone.
  • We do not send deletion requests to RevenueCat, Expo, Cloudflare or Google, which keep what they hold under their own policies, and we do not revoke a Sign in with Apple link; you can remove Orbrey in your Apple ID settings.
  • We do not currently remove recipe photos and event attachments automatically when a household is deleted. If you want them removed, email privacy@orbrey.com.

A household admin can use the web app (Settings, then Account, then Danger zone) to ask to delete a household, or to erase its tasks, events, recipes, lists, meal plans, groceries, pantry, rewards and notifications while keeping the household and its members. Both ask the other registered members to approve by email, and an approval request expires after 24 hours. Erasing does not remove Family Inbox items, Ask Orbrey conversations, learned memories or items still in Recently Deleted. Deleting a household on its own may currently fail; if it does, email privacy@orbrey.com and we will delete it for you. When it works it removes its database records but not the stored Family Inbox files, profile photos, recipe photos or event attachments, and it does not ask Stripe to delete the customer or cancel a web subscription; email us to have those removed. These two actions are not in the mobile app.

What survives deletion, and why

  • Our account-deletion log and privacy-request records, for 7 years, as proof we honoured your choices. Orbrey AI consent history is kept for up to 7 years while its household exists, and is deleted with a household that is deleted.
  • Audit records, so a household can review its history. Their user columns are emptied when you delete your account, but earlier values recorded inside an entry, such as a consent change, can still carry your user ID.
  • What you added to a household that continues, and the household's copies of anything that mentions you.
  • Sentry reports, until they expire (section 9).
  • The analytics person record and events held by PostHog, until they are erased on request or age out of PostHog. Events the web app sent before 8 October 2026 are in a different project that we cannot currently open, so we may not be able to erase them on request.
  • PostHog's profile for your household (its ID and member count), which is not a person and is not removed with your user ID; events sent from a device before you signed in, which a request for your user ID may not reach; and any event sent just after a request, which can create a new record. Email privacy@orbrey.com to ask us to remove what we can.
  • Feedback messages you sent without turning on Include my account details. They are not linked to your account, so deleting your account does not find them. If you typed a reply email, email privacy@orbrey.com with that address and we can find the message and delete it. A message with no reply email and no account cannot be traced to a person, so we cannot find it to delete it.
  • Resend's log of the emails it sent you, for the period Resend keeps it.
  • Your profile photo file, when other account holders keep the household.
  • Copies in backups kept by our database provider until they expire, and records held by Stripe, Apple, Google, RevenueCat, Expo and our other providers under their own policies.
  • Recipe photos and event attachments (see above), and your Ask Orbrey conversations in a household that continues.

We delete or de-identify information when we no longer need it, except the items above that say No automatic deletion or that stay until a household is deleted or you ask us to delete them, which we do not yet delete on a schedule. Those are: Ask Orbrey conversations, AI proposals, suggestions, usage records and instructions, Family Inbox items and files, invitations (which hold the invitee's email address), blog newsletter records and helpful votes, audit records, reward and gem records, the files listed above, and what you send us by email. We do not delete an account because it is inactive. Files are deleted from storage in the cases above, and copies in backups age out as described in the table.

13. Your controls, and your household’s

Where to find your privacy controls in the web app and the mobile app
What you can doWeb appMobile app
Edit your profile and household detailsSettings, and your profile.Edit profile, and Settings. The optional birthday is edited here.
Export your dataSettings, then Account, then Export data: your household’s content as JSON, or CSV files in a zip. It covers your household’s content tables only. It leaves out files and photos, task completion records, recipe ratings and cook history, the reward and gem activity log, your profile, consent records, Family Inbox, AI conversations and billing.The household export is not in the app; email us. Your Orbrey AI data can be downloaded from Settings, then Orbrey.
Manage Orbrey AI and what it has learnedSettings, then Orbrey: switches, instructions and memories, export and delete.Settings, then Orbrey: switches, instructions and memories, download and delete.
Change cookie, analytics and crash-report choicesSettings, then Account, then Privacy preferences.Settings, then Data & privacy.
Send feedback, or ask us to delete a message you sentUse the feedback form. To have a message deleted, email privacy@orbrey.com with the reply address you typed or the account you sent it with.Use the feedback form. To have a message deleted, email privacy@orbrey.com with the reply address you typed or the account you sent it with.
Choose notificationsSettings, then Notifications: in-app, the weekly email digest, delivery hour and categories, with snooze.Settings, then Notifications: push, in-app and the weekly email digest. Your phone's notification permission is asked for when it is needed.
Disconnect a calendar or AI appIntegrations for calendars, and Settings, then Connected apps for AI apps.Settings, then Integrations for calendars. AI apps can be disconnected on the web app only.
Restore or permanently delete an itemRecently Deleted.Recently Deleted.
Delete your account, a household or its contentSettings, then Account, then Danger zone. Deleting a household on its own may fail; email privacy@orbrey.com and we will delete it for you.Profile, then Settings, then Account, then Delete my account (your account only; households and their content are deleted or erased on the web app).

You can also email privacy@orbrey.com to ask to see, correct, export, delete or limit the use of information we hold about you, or to ask any question about it. We reply within 30 days. We may ask you to write from the account's email address so we know it is you. If you are not an account holder but a household has added information about you, see below.

If you are not an Orbrey user

A household can hold information about you without you having an account: if you are a member without a login or a guest, were invited by email, are named in an event or task, or have written to a household's Family Inbox. Depending on how you came into it, that can include your name or nickname, your email address (on an invitation, or in the sender log that only that household's admins can read), allergies, foods to avoid and preferences, a photo, and the text of what you sent. It comes from the household that added it, and we hold it so that household can use Orbrey (section 3); how long we keep it is in section 12. To see it, correct it or have it deleted, email privacy@orbrey.com; you do not need to sign in, and we may ask which household added it. You can also ask that household's admin.

If you have written to a household's Family Inbox, we do not send you an automatic reply, so you are not told at the time that Orbrey reads what you send. This section is where you can find out. We keep your email address (in a log only the household's admins can read), your display name and what you sent, for as long as the household keeps them (section 12).

If you manage a household

Orbrey is a tool for your household, and what goes into it is up to you. If you are an admin or you add other people's information:

  • Add information about other people (members, children, guests, attendees, invitees) only where you are entitled to, and tell them what is recorded, especially allergies and photos. Get their agreement first or, for a child, be their guardian.
  • Forwarding a notice or email to the Family Inbox shares it, and the sender's name, with everyone in the household. The people who write to your Inbox address are not told that Orbrey reads it (we send no automatic reply), so tell them yourself, and forward only what you are comfortable sharing.
  • Invitations send an email to the address you type. Use an address the person gave you.
  • Removing a member ends their access, but content they added stays in the household.
  • If someone asks to correct or delete information about them, do it or ask us to.

14. If you are in Australia

This section covers the points the Australian Privacy Principles ask us to tell you about. Most of the detail is elsewhere in this policy.

  • What we collect and hold, and how: section 2.
  • Why we collect, hold, use and disclose it: section 3, with disclosures in section 4.
  • Overseas recipients: section 5. We are likely to disclose to recipients in Singapore, the United States and other countries.
  • Sensitive information: allergies are health information. We collect them because you or someone in your household chose to enter them. The agreement that counts is that of the person they are about or, for a child, their guardian: an admin who enters someone else's allergies tells us, by doing so, that they have that person's agreement or are their guardian.
  • If you do not give us information: without an email address and a password (or a Google or Apple sign-in) we cannot create your account, and Orbrey can only organise what a household adds. Allergies, a birthday, analytics, advertising measurement, the newsletter and (on the web app) error reports are optional.
  • How long we keep it and how we dispose of it: section 12.
  • Security: section 17.

Access and correction

You can see and edit most of your information in the app. For anything else, including information we derive, such as cook-log ratings and recommendations, email privacy@orbrey.com. We respond within 30 days. If we refuse a request we will tell you why in writing.

Anonymity and nicknames

You can ask us a general question, including about privacy, without giving your name, and you can use a nickname as your display name. To create an account we need an email address (or a Google or Apple sign-in), so we cannot offer an account without one.

Changes to the law

Australian privacy law is changing in stages, including new rules about decisions made by automated systems and about children's privacy. We will update this policy as they take effect.

Complaints

If you think we have mishandled your personal information, email privacy@orbrey.com. We will look into it and reply in writing within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

Direct marketing

We send a welcome email to people who subscribe to the blog on orbrey.com, and we may email blog updates to them; the welcome email has an unsubscribe link. In the mobile app, the Marketing switch (called Product emails in earlier versions) is off unless you turn it on, and we do not currently send product emails. That switch is the same saved choice as Advertising measurement in the web app's Privacy preferences: your choices there and in the mobile app are one record that follows your sign-in, and opening Privacy preferences on the web applies it to that browser. We advertise on third-party platforms and measure that advertising with the tags in section 9, only after you accept them. We do not use your household content for marketing.

How to stop messages:

  • Blog email: the unsubscribe link in the email.
  • The weekly digest: Settings, then Notifications, on the web app or the mobile app.
  • Product emails: the Marketing switch, in Settings, then Data & privacy in the mobile app.
  • Advertising tags: Cookie choices on orbrey.com, or Settings, then Account, then Privacy preferences on the web app.

15. If you are in the UK or European Economic Area

Orbrey is built for households in Australia. If you use it from the United Kingdom or the European Economic Area, UK GDPR or EU GDPR may apply to what we do, and this section says what that means. It adds to the rest of this policy.

  • Who is responsible. Orbrey, at the contact details in section 19, is the controller of the personal information described here.
  • Why and on what basis. The table in section 3 gives each purpose and its legal basis. Our legitimate interests are keeping Orbrey secure and working, and knowing whether it does. Where we rely on consent you can withdraw it at any time (section 10 shows where for cookies, analytics and error reports), and doing so does not affect what we did before. For Orbrey AI you can switch Use Orbrey off (section 6).
  • Special category data. Allergies are health information. We record them and show them to your household on your explicit consent, given when you or your household add them, and you can remove them whenever you wish. Sending them to Orbrey AI is covered by our legitimate interests in providing the assistant, not by that consent (section 3).
  • Who receives it. The providers and people in section 4.
  • Transfers outside the UK and EEA. Our database is in Singapore, and several providers process data in the United States and elsewhere (section 5). We have not yet confirmed which transfer mechanism covers each recipient. Ask privacy@orbrey.com for the safeguards we have for these transfers.
  • How long. Section 12.
  • Whether you have to give it. To create an account you need an email address and a password, or a Google or Apple sign-in. The content you add is what makes Orbrey work. Allergies, a birthday, analytics, advertising measurement, the newsletter and (on the web app) error reports are optional.
  • Children. A child account is created by a parent or guardian, who confirms they are the child's parent or legal guardian and agrees to the account. We do not check that confirmation beyond what they tell us (section 11). A parent or guardian can ask us, at the address in section 19, to use a child's rights for them.
  • AI and automated decisions. Section 6 describes what Orbrey AI does. It proposes, and by default a person confirms; none of it decides something about you with a legal or similarly significant effect on its own.

Your rights

You can ask us for access to your information, correction, erasure, restriction of how we use it, a portable copy, and you can object to processing based on our legitimate interests (including direct marketing). To use any of these, email privacy@orbrey.com. We reply within 30 days.

Complaints

You can complain to a data protection authority: the Information Commissioner's Office in the UK (ico.org.uk), or the authority in the EEA country where you live or work.

16. If you are in the United States

This section is for residents of US states with comprehensive privacy laws, such as California, to the extent those laws apply to us. It adds to the rest of this policy.

What we collected and disclosed in the last 12 months

Categories of personal information collected in the last 12 months and who received them
CategoryExamplesDisclosed toSold or shared?How long
IdentifiersEmail address, display name, account and household IDs, IP address, device install ID, push token.Supabase, Vercel, Cloudflare, Resend, Expo, Stripe (email, household and user IDs), RevenueCat (household ID), Sentry (account ID and, on the mobile app, an ID for this install), PostHog (account ID, and an email address if you type one in a feedback form), and Meta and Google only if you accept marketing cookies.Not sold. Shared for advertising only with Meta and Google, and only if you accept marketing cookies.Account details while your account exists. IP-based counters 1 day. Push tokens until replaced or your account is deleted. Section 12 has the rest.
Customer records and commercial informationPlan, billing status, purchase identifiers. No card numbers.Stripe, RevenueCat and the app stores.No.While the household exists (section 8).
Sensitive personal informationAccount sign-in details, allergies and food preferences (health information), and any precise location embedded in a photo or file you upload or share to the Family Inbox.Supabase; Cloudflare for Orbrey AI features that use them (section 6); Google Cloud for the malware scan of Family Inbox attachments (section 4).No.While your account or household exists. Inbox files until the household is deleted.
Internet and device activityPages and screens viewed, clicks, errors, speed measurements, browser or phone model and version, and on the mobile app the phone’s time zone, its language and region setting and an ID for this install.Sentry and PostHog; Meta and Google only if you accept marketing cookies on orbrey.com or, for Google, in the web app.Shared for advertising only through the Meta and Google tags, and only if you accept marketing cookies.Error reports 30 or 90 days, depending on our Sentry plan. Analytics: the retention period of our PostHog plan, which we have not confirmed.
Approximate locationA city you choose for weather, location text you type into events, and the country that Sentry works out from the IP address of an error report (seen on the mobile app, not checked on the web app or orbrey.com). We do not use device location.Google Places, Open-Meteo, Sentry.No.While the household exists. Deleted items stay 30 days in Recently Deleted. The country in an error report is kept as long as the report.
Messages you send usFeedback and bug reports: your text, the kind of feedback, an optional rating in the apps, app or browser and device details, the screen, and, only if you choose, your account and household IDs or a reply email address.PostHog.No.We have not confirmed how long PostHog keeps them (section 9). Email us to have one deleted (section 12).
Photos and filesProfile photos, recipe photos, Family Inbox files, and attachments already on events. Receipt photos are read and not kept.Supabase; Cloudflare and Google Cloud for the uses described in sections 6 and 4.No.Until the household is deleted. Some files are not removed automatically (section 12).
Age or birthdayAn optional birthday on a mobile profile, and the age band a guardian picks for a child account.Supabase.No.Birthday while your account exists. Age band with the child’s consent record, until a guardian deletes the child account.
InferencesOrbrey AI memories and suggestions about your household’s routines.Supabase; Cloudflare for Orbrey AI.No.Memories until you delete them. Suggestions and proposals until the household is deleted. AI task records 400 days.
Other contentHousehold content, forwarded notices (which can contain information about schools, children and activities).As above.No.While the household exists (section 12).

Where we disclosed information for a business purpose, it went to the service providers in section 4.

Sale and sharing

We do not sell personal information. When you press Accept all on orbrey.com, Meta and Google receive identifiers and the pages you view so we can measure our advertising. In the signed-in web app, the Advertising measurement setting can enable Google Ads conversion measurement. Under some state laws that is "sharing" for cross-context behavioural advertising, or "targeted advertising". On orbrey.com, you can decline by pressing Reject non-essential, which stops those tags from loading. In the signed-in apps, turn off Advertising measurement in Settings to stop app-side Google Ads measurement (section 10). We do not currently detect Global Privacy Control signals, and we do not respond to Do Not Track signals. The tags load only if you accept marketing cookies.

Your rights

Where we collected information from, and why, is in sections 2 and 3. You can ask to know and access what we hold, to know which providers received it (section 4 lists them), to delete it, to correct it, to get a portable copy, to opt out of sale, sharing and targeted advertising, and to limit the use of sensitive information. We use sensitive information to provide the features you use, including Orbrey AI features that can send allergies to the model (section 6), and not for advertising. You can limit that with the controls in section 13. We will not treat you differently for using these rights.

To use them, email privacy@orbrey.com or use the in-app controls in section 13. We reply within 30 days. We may ask you to write from your account's email address to confirm it is you, and an authorised agent can make a request for you with your written permission. If we decline, you can reply to ask us to reconsider, and you may also contact your state attorney general.

Children

Orbrey is made for adults to run a household. A guardian can create a child account, including for a child under 13, in the mobile app, and the guardian confirms by ticking a box that they are the child's parent or legal guardian. We do not verify that confirmation beyond what they tell us, and a guardian who wants the child account's information deleted can delete the account, but the app has no switch that stops collection while keeping the account. Section 11 says what we collect from a child account, who receives it, and how a guardian looks at it and deletes it.

17. Security and data breaches

What we do to protect your information:

  • Traffic to Orbrey uses HTTPS (TLS), with strict transport security on our sites.
  • Database rules are designed so that a signed-in person can read only the households they belong to (and, if invited, the name of the household that invited them), and so that our service keys do not reach your browser or phone. The exceptions are in sections 2 (people in the same household can read each other's profile record, which holds the optional birthday) and 4 (our staff and service keys can reach more).
  • Passwords and manager PINs are stored as hashes. You can turn on two-factor sign-in with an authenticator app, and sensitive actions such as revoking a connected AI app ask for it. If you change your email address, the change takes effect straight away and the new address is marked unverified until you open the confirmation link we send to it.
  • Calendar credentials are encrypted with a key kept outside the database. Email verification and newsletter unsubscribe tokens are stored only as hashes. Family Inbox addresses are matched by a digest, but addresses created since 30 September 2026 are also kept in readable form (the part before the @) so we can show them to your household again.
  • Uploaded files are stored privately and opened through links that expire: 5 minutes for Family Inbox originals and 1 hour for photos and attachments.
  • Supabase encrypts its database storage at rest.
  • Rate limits and bot checks protect sign-in and public forms, and the tools in section 9 are set up to limit what they send, for example by masking text in error replays and scrubbing text in mobile error reports.

No method of transmission or storage is completely secure. On a shared computer, sign out and clear site data: your sign-in and some drafts stay on the browser otherwise (section 10). If you think your account has been compromised, contact us immediately.

Data breaches

If we have an eligible data breach, meaning one likely to result in serious harm, we will tell the affected people and the OAIC as the Australian Notifiable Data Breaches scheme requires. Where UK or EU law applies, we will notify the regulator and people as that law requires.

18. Changes to this policy

We may update this policy. The date and version are at the top of this page. When we make material changes, we will change the date and version at the top of this page. The web and mobile apps do not show a consent banner; your saved choices remain available in Privacy preferences. Orbrey.com does not automatically reopen Cookie choices. If you keep using Orbrey after a change takes effect, the new policy applies to you.

What changed on 7 October 2026

We rewrote this policy to describe what Orbrey does today. In particular: it names the providers we use and where they work (sections 4 and 5); it says that Orbrey AI runs on models hosted by Cloudflare, where earlier versions named OpenAI (section 6); it describes error reports, analytics and session replay on the web app, orbrey.com and the mobile app, and when each waits for you (sections 9 and 10); it describes the feedback form, which sends a message to PostHog only when you press Send (section 9); it describes child accounts and what a parent or guardian can see and do (section 11); and it says what is kept after you delete an account (section 12).

19. Contact and complaints

Orbrey is the name we operate under. If you have questions or concerns about this policy or how your information is handled, email us:

To make a complaint, see section 14 (Australia), section 15 (UK and EEA) or section 16 (United States). Our Terms of Service govern your use of Orbrey.