Effective date: August 23, 2026
BeFree is a brain dump app: you talk or type, and BeFree organises what you share into tasks, calendar events, reminders, grocery items, and notes.
This policy describes what BeFree collects, why, and what choices you have. It is written to be read, not skimmed past. If anything is unclear, email us at support@heybefree.app.
Account information. When you sign in, we create an account identifier and store the email, Apple Sign-In, or Google Sign-In identifier you used.
Your content. We store the content you create — tasks, events, reminders, grocery items, lists, notes, projects, tags, and the original brain-dump text. This is the data you'd lose if your phone fell in the ocean, and it's what BeFree exists to keep safe across devices.
Voice audio is not stored by BeFree. On Apple devices, speech-to-text is handled by Apple's built-in speech recognition; depending on your device and language, Apple may process the audio on its servers to produce the transcript. If you use BeFree in a web browser, speech-to-text is provided by your browser's own speech engine and may be processed by the browser vendor's servers. In every case, BeFree never receives or stores your raw audio — we receive only the resulting text, and only when you submit a capture.
Personalisation. BeFree derives lightweight usage patterns from how you use the app, and remembers personal facts you explicitly volunteer during a capture (for example, “I don't drive”) so sorting fits your life. The in-app About you screen — ask BeFree “what do you know about me” — lists every stored fact in your own words, and lets you delete any one of them or clear them all.
Calendar and Reminders. If you grant access, BeFree reads from your selected Apple Calendar and Apple Reminders to surface events and reminders in the app. Reading is the default. If you turn on Two-way sync in You → Connections, BeFree also writes events and reminders you create in BeFree back to a calendar/list you choose; it only ever changes items it created in BeFree and never modifies events or reminders you made elsewhere. Reading and two-way sync run through Apple's EventKit on your device. Events imported from your Apple Calendar are stored in your BeFree account on our servers — the same as items you create in BeFree — so they appear across your devices and work with BeFree's search and AI features; this includes generating embeddings from the event text (see AI processing below). Your Apple Reminders mirror stays on your device and is not sent to our servers. Turning the sync off stops further writes. Two-way sync is off until you enable it, and is enabled separately on each device.
Google Calendar. (This connection is rolling out and may not yet be available in your version of BeFree; on iPhone, Google calendars you've added in iOS Settings already appear through Apple Calendar, covered above.) If you connect a Google account in You → Connections, BeFree requests calendar read + write access via Google OAuth 2.0. Read access lets BeFree show your Google events alongside what you capture; write access lets BeFree push events you create in BeFree back to your Google calendar. OAuth tokens are stored in your device's Keychain. When an access token expires, the refresh token is sent over TLS to BeFree's private Supabase Edge Function solely to exchange it with Google; BeFree stores only a one-way token hash server-side and does not persist the raw token. You can disconnect at any time in You → Connections; disconnecting clears every token and removes the Google-imported events from your BeFree views.
Google API Services User Data Policy — Limited Use disclosure. BeFree's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. When you connect Google Calendar, BeFree reads your events (title, description, location, start/end times, and identifiers) and writes events you create in BeFree back to a calendar you choose. That data is used only to provide the user-facing features you turn on: (a) a unified calendar view with two-way sync; (b) AI organisation of what you capture — when you record a brain dump, BeFree gives the language model your upcoming events (event title and start/end times only — descriptions and locations are not sent to the language model) so it can answer “what's on my schedule,” let you reference an event by voice, and avoid duplicates; and (c) in-app search, for which BeFree generates a numerical embedding of each event's text (title, description, and location). To deliver these features, BeFree shares event data with its processors — Anthropic (Claude; receives event title + times), Voyage AI (receives event title + description + location to build the search embedding), Supabase (stores your events in your own row of our database), and PowerSync (syncs your own data to your devices) — each solely to provide the features above. Specifically: (1) we use Google user data only to provide those features; (2) we do not transfer it to third parties except to the processors named here to provide the features, for security purposes, or to comply with applicable law; (3) we do not use it to serve advertisements, and we do not sell it; and (4) we do not allow humans to read it unless we have your affirmative agreement, doing so is necessary for security purposes (such as investigating abuse), or to comply with applicable law. Anthropic is contractually prohibited from using your content to train its models; the context sent to Anthropic is assembled fresh for each request and is not retained by BeFree beyond anonymous usage counters. The Voyage embedding is stored as a numerical vector (not the original event text) and is deleted when you delete the event or your account; BeFree has enabled its organization-level training opt-out with Voyage, so text sent to Voyage is excluded from model training and deleted by Voyage after processing. Disconnecting Google Calendar in You → Connections stops all future syncing and removes the imported events (including their embeddings).
Photos and Camera. If you attach a photo to a note, BeFree first resizes and re-encodes the image on your device — a step that also removes embedded metadata such as GPS coordinates, camera model, and device serial — and then uploads the resulting image to encrypted object storage so it can sync across your devices. The image is associated with your account and served to the app via short-lived signed URLs. Deleting a note hides it from the app immediately; the stored image is purged when you delete the attachment from the note or delete your account. If you take a photo with the in-app camera, the captured image is treated identically. We do not access your photo library or camera at any other time.
Microphone. On Apple devices, BeFree captures your voice using Apple's built-in speech recognition; depending on your device and language, Apple may process the audio on its servers to produce the transcript. In a web browser, your browser's own speech engine produces the transcript. BeFree itself never uploads or stores your raw audio. Only the resulting transcript text is sent to our servers, and only if you submit the capture.
Location. BeFree does not collect device location in this release. If a future feature needs it, we will update this policy first.
Purchases. If you subscribe to Pro, our subscription processor handles purchase and entitlement details so BeFree can unlock paid features.
Crash reports. When BeFree crashes or hits an error, we receive a crash report. This happens for everyone and is not optional — without it we cannot tell that the app is broken for you. A crash report contains the technical details of the failure (what code failed, the app version, the device model and OS version) and a pseudonymous installation identifier. It never contains your thoughts, your captures, or any content you have written, and while diagnostics are off it is not linked to your account identifier. Crash reports are processed by our diagnostics provider.
Product-usage analytics. Analytics are off by default and optional. During onboarding, BeFree offers a "Help improve BeFree" switch, and you can change your choice at any time in the app's privacy settings. When it is on, we collect pseudonymous product-usage analytics linked to your account identifier — not to your name or email — and your account identifier is also attached to crash reports so we can tell whether a crash affected you specifically. When it is off (the default), no analytics are sent.
Basic usage records. Separately from optional analytics, BeFree keeps a small usage log on its own servers, limited to a fixed, named list of events: that the app was opened, onboarding milestones, capture milestones (a capture started, filed, or edited), an item being completed, resurfaced, or consciously let go, and views or dismissals of the upgrade screen. Each record contains your account identifier, which named event happened, when, and at most one broad category from a fixed list (for example, that a capture came from voice rather than typing). It never contains your content or free text, and no device or location details; it is never shared with a third party or used for advertising. These records are deleted when you delete your account and, in any case, after 400 days.
Website analytics. Our marketing website at heybefree.app measures aggregate traffic using Vercel Web Analytics, provided by the same company that hosts the site. It sets no cookies and stores nothing on your device. It records which page was viewed, the site that referred you, an approximate location (country, region, city) derived from your IP address, your device type, browser, and operating system, and the time of the visit. Your IP address itself is not stored, and the temporary identifier used to count a visit is discarded after 24 hours. The result is aggregate only — it cannot identify you, it is never linked to your BeFree account, it is not used for advertising, and it is not combined with any other data. If you would rather not be counted at all, any content blocker or your browser's “Do Not Track” setting will stop it, and you can email us at support@heybefree.app to object — there is nothing to opt out of inside the BeFree app, because this runs on the marketing website only. It is separate from the optional “Help improve BeFree” setting described above, which continues to govern the app's crash reporting and product analytics.
We do not sell your data, and we do not track you across other companies' apps or websites.
BeFree uses AI to turn your brain dumps into structured items.
BeFree relies on a small set of service providers to operate the app:
For the current list of named providers, see our Subprocessors page. We update that list when we change a provider, so you can always see exactly who processes BeFree data.
These providers process data only to deliver the app functionality you've used. We do not sell personal data.
BeFree uses encrypted network connections and database-level access controls so each account can access only its own data. Authorized BeFree personnel can access stored data when necessary to operate, secure, or support the service — for example, to investigate a bug you've reported or respond to a security incident — and never for any other purpose. We design around least-necessary processing — no provider sees more than they need to do their job. No system is perfect, and we recommend keeping your device's OS up to date.
You can:
For step-by-step instructions, see our Data Deletion guide.
Earlier versions of BeFree let you start without signing in (“Skip — try without an account”). If you used that option, your account exists only as an opaque identifier generated by your device. We do not collect your email, name, Apple ID, or any other information that could let us recognise you across requests. Current versions require signing in with Apple, Google, or email before use.
Because there is no information we can use to verify that a data-access, correction, or portability request is coming from the account’s owner, we cannot fulfil those requests for an anonymous account by email. The in-app Delete Account flow (see our Data Deletion guide) is the self-service equivalent of these rights — it permanently removes all of your data from inside the app, and it does not require us to identify you.
If you later sign in with Apple or email, your existing anonymous data is linked to the new identifier and you can exercise all of your rights by emailing support@heybefree.app.
BeFree also runs in a browser at app.heybefree.app and as a Mac app, and an Android version is in pre-release testing. All of them use the same account, the same servers, and the same rights described in this policy. The differences worth naming: in a browser, microphone and speech-to-text are provided by your browser (see Voice audio above) and permissions are managed through your browser's site settings rather than iOS Settings; our web host processes standard request information such as IP address and browser type to serve the site.
We keep your account data while your account is active. When you delete your account, we remove it from production systems within 30 days. Some provider logs or short-window backups may persist for security, fraud prevention, or operational reasons, but those copies are isolated from the live product.
BeFree is not directed to children under 13. If you believe a child has provided personal information to BeFree, contact us and we will remove it.
We may update this policy as BeFree changes. The effective date at the top shows when. We will notify you in-app for material changes.
Email: support@heybefree.app