What braxby reads, and what it does with it.
Effective 25 August 2026 · Last updated 4 November 2026
braxby asks to read your calendar, and — if you choose to connect it — your inbox. That is a lot to ask on a first screen, so this page is written to be read rather than survived. The short version: we read a narrow slice, we keep the structured facts and not your messages, we never train models on you, and deleting your account deletes everything.
On this page
- Who we are
- What we read from your calendar
- What we read from your mail
- Google Limited Use
- Everything else we collect
- Why we process it
- We do not train models on you
- How long we keep it
- Deleting your account
- Who else touches it
- We do not sell your data
- How it is protected
- Your rights
- Children
- Where the data lives
- Changes to this policy
- Contact us
1Who we are
braxby is a personal events concierge operated by braxby LLC, a limited liability company organised in the Commonwealth of Massachusetts, United States. In this policy "braxby", "we" and "us" mean braxby LLC. "You" means the person using the service.
This policy covers the braxby service wherever you use it: the web app at
app.braxby.com, and the mobile app published as
braxby — Events Concierge on Google Play (package
com.braxby.app) and, once released there, on the Apple App Store.
For data-protection purposes braxby LLC is the controller of the personal information described here. You can reach us at concierge@braxby.com.
2What we read from your calendar
Your calendar is the primary signal braxby learns from. It is where the concerts you actually went to, the restaurants you actually booked and the trips you actually took are recorded.
The permissions we ask for
- Google —
calendar.eventsandcalendar.calendarlist.readonly. We deliberately do not request the broaderauth/calendarscope, which would grant read, write, share and delete across every calendar you can see. The narrower pair covers everything braxby actually does. - Microsoft —
Calendars.ReadWrite, the narrowest Microsoft Graph permission that supports both reading your agenda and adding an event you asked us to add. - Apple — Sign in with Apple grants no access to your calendar or mail; Apple publishes no such permission. iCloud Calendar is a separate, manual connection you make yourself with an app-specific password, and only if you choose to.
What we actually read
- The list of calendars on your account, so you can choose which ones braxby may look at.
- Events in a window around today — the first import reads roughly the past thirty days, and day-to-day braxby reads the month ahead. It does not trawl your entire calendar history.
- For each event: title, start and end time, location, description and the number of attendees.
What we write
Write access is used in exactly one situation: when you ask braxby to add something to your calendar. It never creates, edits or deletes an event on its own initiative.
You may sign in and connect no calendar at all. braxby is designed to work in that state — it will simply know less about you.
3What we read from your mail
This is the question people care most about, so it gets the most precise answer on this page.
We never read your whole inbox
Where mail access exists — through Microsoft's Mail.Read, an iCloud mailbox you
connected yourself, or a Gmail grant if you ever give one — braxby does not download or scan
your mailbox. It runs a narrow search and reads only what comes back:
- Messages from a known list of ticketing, travel and booking senders; or
- Messages matching event keywords — ticket, booking, reservation, confirmation, invitation, event, concert, flight, itinerary, e-ticket;
- Within a recent time window, and capped at 200 messages per scan.
Personal correspondence, work threads, newsletters, financial mail and everything else in your mailbox falls outside that search and is never retrieved.
What we keep from a matching message
The structured facts we keep are: the event title, its start and end time, its location, the type of event, a booking reference where one exists, a confidence score, and the provider's message identifier so the same message is not processed twice.
If you re-scan your mail, the previous extractions are replaced.
4Google Limited Use
Where braxby uses Google API Services, the following applies in full:
In practice that means data obtained from Google APIs is used only to provide and improve the user-facing features described on this page, is not transferred to anyone except as required to run the service (see who else touches it), with your consent, or for legal reasons, is never sold, and is never used for advertising. Humans do not read it except where you explicitly ask us to for support, where it is necessary for security, or where the law requires it.
5Everything else we collect
| What | Where it comes from | Why |
|---|---|---|
| Account details Name, email address, sign-in method | Google, Microsoft or Apple at sign-in, or an email address and password if you create an account that way | To create and secure your account. With Apple's Hide My Email, we only ever see a relay address. If you set a password we store it only as a salted hash — we never hold the password itself and cannot read it. |
| Access tokens | Your provider, when you grant access | To read the calendar and mail you authorised, and your Spotify listening if you connect it. Stored encrypted; revocable at any time. |
| Your messages to braxby | The concierge chat | To answer you, and to remember context across conversations. |
| Taste and behaviour What you open, save, dismiss, watch or add | Your use of the app | This is how braxby learns what you like. It is inferred from what you do, not from a questionnaire. |
| Location A home city, and your device's position only if you allow it | Your calendar events, your trips, a city you type, your phone's time zone, or — only if you allow it, and only while the app is open — your device's location | To know which city's events matter and what is near you. From a device fix we keep your home point (if you chose "Use my location") and the most recent point, which each new fix overwrites. We never collect location in the background and keep no history of where you have been. |
| Shared trips The people you invite and what they can do | You, when you invite someone to a trip; them, when they join or add to it | To let the people on a trip see or edit it. We keep the email address you invited (or a link token, if you sent a link yourself), their role, and who added each item to the plan. Members see the trip's plan and its chat, including your name, your role and what you write there, and braxby's replies to you in it; they never see your taste, your picks or your other trips. In a shared chat braxby answers from the trip alone: it does not draw on your taste, your calendar, your mail or anything it remembers about you, so nothing private reaches the other members. You can block a member, which hides what they write from you. Anyone with a view-only link can see that trip's plan until you turn the link off. |
| Spotify listening Top artists and genres | Only if you connect Spotify | To sharpen music recommendations. Entirely optional, and disconnectable. |
| Billing details | Only if you paid for braxby before it became free: Stripe on the web, or Apple or Google on the app stores | To keep the record of that payment. braxby is free for now and takes no payments. Card numbers went to the payment processor directly and never reached our servers — we hold a customer reference and the status of that past subscription, never your card details. |
| Product usage Which screens you open, what you tap, and anonymised session replays | Automatically, as you use the app | To find where the product confuses people. Replays are masked: we see the shape of your session, not its content. |
| Waitlist details Your email address, and a city if you gave one | The form on our website, if you joined the waitlist | To tell you when there is a place for you, and to decide which cities to open first. Joining the waitlist creates no account and connects nothing — we hold only what you typed into that form. |
| Technical logs IP address, request paths, errors, timestamps | Automatically, when you use the service | To keep the service up, debug failures and prevent abuse. |
| Push registrations | Your browser or device, if you enable notifications | To deliver the proactive messages that are the point of the product. |
| Support reports | You, when you use "Report a problem" or "Something off?" in the app | To investigate and fix what went wrong, and to reply to you. See below. |
| Things you share | You, when you share a find | To show the find to whoever you send the link to. A shared page is public to anyone with the link. It shows only the event's public details (title, date, venue, city, image and ticket link), plus your first name and a note only if you chose to include them — never braxby's message to you, your calendar or why it was suggested. We also keep a one-way hash of the network address the share was made from, so we can recognise someone referring themselves; it cannot be turned back into the address. |
| Referrals | A link someone shared with you, when you then sign up | To record who introduced whom, so a referral can be credited. We keep the link between the two accounts and when it happened, nothing else about either person. |
When you report a problem
If you send a report from inside the app, it contains your account email address, your device and the app build you are on, the message you wrote, and — unless you switch it off before sending — the last exchange in your conversation with braxby, so we can see what you saw. The report is emailed to our support mailbox and stored with your account. The copy stored with your account is deleted when your account is deleted; the copy in our mailbox is kept only as long as we need it to deal with your report, and deleted when it is no longer needed. Nothing is sent until you press send.
If you report one of braxby's replies as offensive or untrue, that reply is hidden in your conversation (you can still show it), and braxby stops using it as context for later answers. The reply itself is deleted with the rest of your conversation, and a copy stays with your report so we can review it. A person reads every such report, and we use them to improve how braxby answers.
If you report a message someone else wrote in a shared trip's chat, the report contains that message, who wrote it, the trip, your account and the reason you gave. It is emailed to our support mailbox and a person reads it. The person you reported is not told who reported them. A trip's organizer can remove a message from the chat; it then disappears for everyone on the trip and braxby stops using it, and we keep the original only so we can deal with any report about it. It is deleted with the account of the person who wrote it.
Cookies and analytics
We use PostHog to count how braxby is used: which pages and screens are opened, how fast they load, and where errors happen. That needs one identifier, kept in a cookie and in your browser's storage, so a visit to braxby.com and a sign-up in the app count as one person. We use it only for these statistics and to fix the product, never for advertising, and we do not share it with anyone else.
The app can also record a session replay: the screens you moved through and where you tapped, with every word on screen and everything you type hidden. If you are in the UK, replay is off until you say yes. The app asks once, and you can change your answer at any time in You → Settings, under "Let braxby record app sessions to fix problems" (the same switch turns replay off wherever you are). On braxby.com, visitors in the UK get no analytics cookie and nothing stored in the browser: each page view is counted on its own and forgotten when you leave, and no replay is recorded for anyone. We decide whether you are in the UK from your device's time zone, so we make no extra request to find out. If you would rather we did not count your visits at all, block cookies for braxby.com in your browser, or write to us and we will exclude your account.
The last 12 months, in California's categories
In the past 12 months we collected identifiers; account and commercial information (past payment status, where there was one); internet activity (product usage); location (precise only where you allowed it); inferences (your taste profile); and sensitive personal information as described in section 14. We disclosed each only to the service providers in section 10, for the business purposes in section 6. We sold or shared none.
6Why we process it
- To provide the service you asked for — detecting trips, building your taste model, finding events worth telling you about, and writing to you first.
- To keep it working and safe — debugging, rate limiting, fraud and abuse prevention.
- To keep records of payments made before braxby became free, where there were any.
- To comply with the law, where we are required to.
If you are in the UK or EEA: our legal basis is performance of our contract with you for the core service, your consent for optional connections such as Spotify, mail access and push notifications, and our legitimate interests in keeping the service secure and functioning, understanding how the product is used so we can improve it, and crediting referrals fairly. You can withdraw consent at any time by disconnecting the source or turning the notification off, and you can object to processing based on legitimate interests (see section 14). Where we rely on our contract with you, the processing is needed to provide the service; if you would rather it did not happen, the remedy is to disconnect that source or delete your account.
braxby profiles your taste to choose what to show you. It makes no decisions with legal or similarly significant effects on you.
7We do not train models on you
The "learning" braxby does is a private profile of your taste, held in your account and used only to choose what to show you. It is not pooled with other users, and it does not improve anyone's model but your own experience.
8How long we keep it
| Data | Kept for |
|---|---|
| Your account, taste profile, trips, extracted events, chat history | As long as your account exists. Deleting your account removes them immediately — see below. |
| Access tokens for connected accounts | Until you disconnect that source, or delete your account. Disconnecting deletes the token. |
| Extracted events from a mail scan | Replaced each time you re-scan — the previous extractions are deleted. |
| Something you asked braxby to forget | Removed immediately from everything braxby reads, shows or reasons over. The underlying record is cleared when your account is deleted. |
| Your event feed | Replaced each time it is rebuilt, and deleted with your account. |
| Cached model results | Minutes to 24 hours, then discarded automatically. |
| Support reports | The copy stored with your account is deleted when your account is deleted. |
| Things you share | A shared link stops showing the find seven days after the event (thirty days after you shared it, if the find has no date), or at once if you revoke it. The stored copy is deleted 90 days after the link stops working, and immediately if you delete your account. |
| Your device location | The most recent point is overwritten by the next one; the home point is kept until you change it. Both are deleted with your account. |
| Shared trip members and invites | As long as the trip exists. Removing someone, or deleting the trip or your account, removes their access. |
| Referral records | As long as both accounts exist; deleted when either account is deleted. |
| Waitlist details | Until you join, or until you remove yourself with the link in any email we send you. Removing yourself is one click and needs no account. |
| Technical logs | A short rolling window held by our hosting provider, then discarded. |
| Billing records | As long as US tax and accounting law requires us to keep them, independent of your account. |
| Encrypted database backups | Deleted data disappears from backups as our provider's rolling backup window passes. We do not restore a backup to recover deleted user data. |
9Deleting your account
You can delete your account yourself, from You → Settings in the app — nobody needs to approve it and there is no waiting period. If you can no longer sign in, you can request deletion by email instead: we send a confirmation link to the address on the account, and clicking it deletes everything immediately. See how to delete your account.
Deletion is immediate and it cascades. Every table that holds anything about you is keyed to your account with an on-delete cascade, so removing the account removes, in the same transaction: your profile, your provider tokens, your Spotify connection, your memory and taste model, events extracted from your mail, your detected trips, your conversation history, your discover feed, your armed watches, your calendar preferences and your onboarding records.
If you signed in with Apple, we call Apple's token-revocation endpoint before deleting, so the grant does not linger in your Apple Account with nothing behind it.
If you are on the waitlist rather than in the app, there is no account to delete — we hold only the email address and city you typed into the form. Use the removal link in any email we have sent you, or write to us, and the entry goes.
This is a hard delete, not a soft delete or a thirty-day grace period. We cannot undo it, and we cannot recover the account afterwards.
10Who else touches it
braxby is a small operation built on other people's infrastructure. These are the companies that process data on our behalf. We update this list when it changes.
| Provider | What it handles |
|---|---|
| Anthropic (Claude) | The concierge itself, and the extraction of events from calendar and mail text. Receives the text being processed and your messages to braxby. |
| OpenAI | Text embeddings only, so braxby can retrieve relevant memories. Receives short text, no account identifiers. |
| Supabase | Our database and authentication. Holds everything described on this page. |
| Render | Hosting for the application and the website, plus the cache and job queue. Processes requests and technical logs. |
| Stripe | Records of payments made on the web before braxby became free. Card details went to Stripe directly and were never held by us. |
| RevenueCat | The record of any purchase made inside the mobile apps before braxby became free: your account identifier and that purchase history. It does not receive your card details, your calendar, your mail or your messages. |
| Apple, Google (app store billing) | Any purchase made inside the iOS or Android app before braxby became free was taken by the store under its own privacy policy; we received only the resulting purchase status. |
| PostHog | Product analytics and session replay, so we can see where people get stuck. Replay masks all text and all form inputs — it records where you clicked and how long you paused, never the contents of your calendar, your mail or your conversation with braxby. In the UK it is off until you agree to it (see Cookies and analytics). |
| Resend | Sends transactional and digest email to your address. |
| Hostinger | Hosts our concierge@braxby.com mailbox. Support reports you send from the app, and anything you write to us or reply to, land there. |
| Ticketmaster, SeatGeek, Eventbrite, Skiddle, Resident Advisor, RunSignup | Event catalogues. They receive a city (or, for RunSignup, a postal code for that city), a date range and search terms derived from your interests — never your name, email or message content. |
| setlist.fm | Records of past concerts, used to show you shows you may have been to. Receives a city and a year, never your identity. |
| MusicBrainz | Public music metadata, used to recognise artists. Receives an artist name, never your identity. |
| OpenStreetMap (Nominatim) | Turns a place name into a city and coordinates — for example the home city you type, or a trip destination — and, when you set home from your location, turns that point into a city. Receives the place name or the point only, never your identity. |
| Mapbox | The maps on trip pages and the place suggestions as you type a city. Your browser or app asks Mapbox directly, sending what you type, or the point on the map or your location when you use it; never your name, email or calendar. |
| Serper (Google Search results) | Web search used to ground answers and find local listings. Receives a search query (a city, a category or an artist name), never your identity. |
| Brave Search | Fallback web search provider for the same purpose; receives the same kind of query. |
| Spotify | Only if you connect it. Returns your top artists and genres. |
| Google, Microsoft, Apple | Sign-in, and the calendar and mail you authorised. |
| Apple Push Notification service, Firebase Cloud Messaging | Delivery of push notifications, if you enable them. |
We may also disclose information if the law requires it, to enforce our Terms, or to protect the rights and safety of our users. If braxby is ever acquired or merged, your information may transfer as part of that — you will be told before it becomes subject to a different privacy policy.
11We do not sell your data
We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law. We run no advertising network, no tracking pixels for third-party advertisers, and no data brokerage. braxby is free for now. It earns affiliate commission when you buy a ticket through a link we showed you — which is disclosed in the Terms and costs you nothing extra.
Because we neither sell nor share personal information, there is nothing to opt out of. If your browser sends a Global Privacy Control signal, we treat it as a valid opt-out request anyway.
12Email we send you
There are three kinds, and they are governed differently.
- Account email always sends. Confirming your address, resetting your password, the link that deletes your account, and the note telling you the deletion is done. Each one completes something you asked us to do, so there is no opting out of them — and none of them ever carries marketing.
- Suggestions are yours to switch off. When braxby finds something worth telling you about, it may reach you by email as well as by notification. You control this per category and per channel in You → Settings, and you can switch email off entirely there or with the one-click unsubscribe link in any such message. We send at most one of these a week, with one exception: a ticket going on sale for something you asked us to watch, because that expires.
- Waitlist and announcements go only to people who joined the waitlist or agreed to hear from us, and every one carries an unsubscribe link.
We keep a suppression list. If you unsubscribe, or your provider tells us an address bounced or that you marked a message as spam, we stop sending to it and that decision is permanent — we do not clear it if you sign up again later.
We do not put tracking pixels in account email, and we do not use read receipts to profile you. Our email provider (Resend, listed in section 10) reports whether a message was delivered or bounced, which is what the suppression list is built from.
If you have told us to stop and something still arrives, reply to it or write to concierge@braxby.com and we will fix it.
13How it is protected
- Access tokens for every connected account — Google, Microsoft, Apple and Spotify — and any iCloud app-specific password are encrypted at rest by our server, on top of the database's own disk encryption.
- All traffic runs over TLS.
- Every user-owned table carries row-level security as defence in depth, and every query is scoped to your account.
- OAuth handoffs are signed and time-bounded, so a redirect cannot be forged or replayed.
- Text arriving from your mail or calendar is treated as untrusted input and neutralised before it reaches a model prompt.
No system is perfectly secure, and we will not claim otherwise. If we discover a breach affecting your personal information we will notify you and the relevant authorities as required by Massachusetts law and any other law that applies to you.
More detail, and how to report a security problem to us, is on our security page.
14Your rights
Wherever you live, you can access what we hold, correct it, delete it, and take it with you. Deletion is built into the app and takes effect immediately; for anything else, write to concierge@braxby.com. We will not treat you differently for exercising any of these.
To protect your account, we verify a request by having you make it from the app while signed in, or by confirming it from the email address on the account. An authorised agent must give us your signed permission, and we may ask you to confirm it directly. We respond within 30 days. If we need longer, up to 45 more days under US state law or two more months under UK/EU law, we'll tell you why within the first 30.
If you are in California
Under the CCPA as amended by the CPRA you have the right to know what we collect and why, to delete it, to correct it, to obtain a portable copy, and to opt out of sale or sharing — which is moot here, because we do neither. You may use an authorised agent to make a request, as described above.
The sensitive personal information we process is limited to the contents of calendar events and matching emails you authorised, your sign-in credentials, and your device's precise location if you allowed it. We use it only to provide the service, so there is no "limit the use" request to make.
If you are in another US state with a privacy law
Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana and others grant comparable rights of access, correction, deletion, portability and opt-out. We honour them for every user regardless of state, and you may appeal a refused request by replying to our response, and if we deny your appeal, you may contact your state Attorney General.
If you are in the UK or EEA
You additionally have the right to object to or restrict processing, and to lodge a complaint with your supervisory authority — the Information Commissioner's Office in the UK, or your national authority in the EEA. We would rather you told us first.
If you are in Canada
The Personal Information Protection and Electronic Documents Act gives you the right to see what we hold about you and to have it corrected, and you may withdraw consent to any use of it, subject to the notice we need to stop. You can complain to the Office of the Privacy Commissioner of Canada. In Quebec, our person in charge of the protection of personal information is braxby's founder, reachable at concierge@braxby.com, and you may also complain to the Commission d'accès à l'information.
If you are in Australia
We handle your information in line with the Australian Privacy Principles. You can ask to see it and to have it corrected, and complain to us first and then, if you are not satisfied, to the Office of the Australian Information Commissioner. Your information is held in the United States (section 16).
If you are in New Zealand
Under the Privacy Act 2020 you can ask for the information we hold and for it to be corrected; we answer within 20 working days. You can complain to the Privacy Commissioner. When someone invites you to a trip, we get your email address from them; the invitation says so and links here.
Decisions made by software
braxby uses software, including AI models, to read what you have connected and what you tell it, and to decide which events, places and messages to show you and when. Those choices affect only what braxby suggests to you. We make no decision about you by automated means that has a legal or similarly significant effect on you.
15Children
braxby is not directed to children. You must be 18 or over to use it, as set out in the Terms. We do not knowingly collect personal information from anyone under 18. If we learn that an account belongs to someone under 18, we will close it and delete what we hold. If you believe a child has given us information, write to us and we will delete it.
16Where the data lives
braxby is operated by a company in the United States. The application itself, and most of the services we use to run it — including the AI providers that power the concierge — run in the US. Your account data at rest is stored in the United States (Oregon) by our database provider, Supabase. If you use braxby from outside the US (including the UK, the EEA, Canada, Australia and New Zealand), your information is transferred to and held in the US as a normal part of running the service, and US law applies to it there. Where we transfer personal data out of the UK or EEA we rely on the European Commission's standard contractual clauses our providers offer (for UK data, together with the UK's International Data Transfer Addendum), or, where a provider is certified under it, the EU–US Data Privacy Framework and its UK extension. You can ask us for a copy of the relevant safeguards at concierge@braxby.com.
17Changes to this policy
If we change this policy we will update the date at the top of the page. If a change materially affects how we handle your information — a new category of data, a new purpose, a new sub-processor with real access — we will tell you in the app or by email before it takes effect, rather than quietly editing the page.
18Contact us
Questions, requests, or a paragraph on this page you think is wrong: concierge@braxby.com.
braxby LLC · Massachusetts, United States