Laberty Privacy Policy
Version: 2026-10-13
This describes what Laberty collects when you use the hosted service at laberty.app, why, and who else ever sees it. It does not cover the Founder License (buying the source code to self-host) — if you run your own copy, this policy doesn't apply to it; your own deployment's data never reaches us at all, because we have no access to your copy, your database or your keys.
"We", "us" means the operator of Laberty at laberty.app. "You" means the person using it; "your workspace" means your household or organization's account.
What we collect, and why
To sign you in. Laberty has no passwords. We collect the email address you sign in with, to send a one-time sign-in link, and/or a passkey your device creates, which we never see the private half of. We keep your email, display name and role so the right person gets the right access.
What you type in to use the product. Household names, addresses, occasion dates, people's names, food and grocery items, notes, printer and label-stock setup, and anything you say to the assistant. This is the data that makes Laberty work; it lives in your workspace's own rows in our database and nowhere else.
Photos, for one request only. If you take a photo to identify a grocery product Laberty couldn't otherwise recognize, that photo is sent once to the AI provider handling the request (see below) and is not saved anywhere by Laberty — not to a database, not to file storage. It exists for the length of that one request.
Voice, for one request only. If your workspace has voice turned on: what you say is sent away to be turned into text, and a reply's text is sent away to be spoken. Neither the audio nor the recording is kept, by Laberty or in the conversation history.
Payment information. Card numbers and billing details go straight to Stripe; we never see or store them. We keep the plan you're on, your subscription status, and enough of what Stripe tells us (customer and subscription IDs, renewal dates) to run billing.
Activity logs. Workspace admins can see a log of who changed what in their own workspace — this is for your own household or organization's use, not something we monitor.
Who else sees it, and why
Nobody outside Laberty sees your data unless one of the features below is turned on and needs it to do its one job. We do not sell your data, and we do not let any of these providers train their models on it — the same commitment already made on our pricing page.
| Who | What they get | When |
|---|---|---|
| Cloudflare | Everything, as our hosting, database and network provider | Always — this is where Laberty runs |
| Resend | Your email address, to deliver sign-in links, receipts and alerts | Always |
| Stripe | Your email and whatever you enter at checkout | Only if you're on a paid plan or buy an add-on |
| Anthropic and/or OpenAI | The text or photo you send the assistant, food lookup, or a photo you're identifying, or the text you paste into address lookup when it needs help finding the address in it | Only when your workspace's AI features are in use |
| ElevenLabs | Reply text (to speak it) and your voice recording (to transcribe it) | Only if voice is turned on for your workspace |
| Coordinates or a Plus Code, to turn into a formatted address | Only when address lookup is used and a Google Maps key has been set up (yours or the deployment's) — with no key, Google is never contacted | |
| OpenStreetMap (Nominatim) | The coordinates of a map pin, or a place name or address line from what you pasted, to find the nearest street address. Not your name or account | Only when address lookup is used and the paste is a map pin or a place name rather than an address already spelled out |
| upcdatabase.org | A product barcode | Only during a food-label lookup |
| GitHub | The GitHub username you give us | Only if you buy a Founder License, to invite that username to the private repository |
Each of these is bound by its own provider's terms, not ours — most relevantly, the AI providers' API terms, which is what "no training on your data" actually rests on.
Workspace isolation
Every family or organization on Laberty is its own workspace. Every query for your data is scoped to your workspace; other workspaces' admins cannot see it, and neither can we, except the one person who runs this deployment (the domain admin), who can see workspace-level settings and billing but not for the purpose of reading your labels.
How long we keep it, and getting your data out or deleted
We keep your data for as long as your workspace exists. Cancelling a paid plan drops you to Free; nothing is deleted.
Taking a copy (export). Any full admin of a workspace can download everything the workspace owns from Admin → Your data, whenever they like: as one JSON file, and as CSV spreadsheets of households, people and occasions. It covers your households and people, occasions, notes, food and grocery data, appointments, printers and label stock, settings, the activity log and the people who can sign in (their names, roles and email addresses). It never contains passwords or sign-in secrets, passkeys, authenticator secrets, recovery codes, API key values, session tokens or card details. If a workspace is too big to export from the app, the export says so and stops rather than handing you an incomplete file; contact us and we will produce it by hand.
Deleting your workspace. Any full admin can also delete the workspace from Admin → Your data. It takes several deliberate steps: type the workspace name, then open the one-time link we email to you (and enter your authenticator code if you use one). At that point any paid subscription is cancelled first (if that cannot be done, nothing is deleted), the workspace is suspended immediately, and a 7-day grace period starts. The email we send you contains a link that cancels the deletion at any time during those 7 days, and the workspace comes back exactly as it was (a cancelled subscription is not restarted). When the 7 days end, everything the workspace owns is permanently deleted: all households, people, occasions, notes, food and grocery data, appointments, printers, label stock, devices, print history, settings, the activity log, and every person's sign-in, passkeys, authenticator setup, recovery codes and API keys. The one workspace that an installation itself is run from cannot be deleted from inside the app.
What we keep after a deletion, and why. Our payment processor, Stripe, must keep its own billing records, and we keep our record of which plan, add-on or action pack a payment was for, for accounting; neither holds anything you entered into Laberty. We also keep one minimal line saying that the workspace existed and was deleted: its name, the dates, the Stripe customer reference and a count of how many records of each kind were removed, but none of the content. Deleted data can remain in Laberty's database backups for up to 30 days afterward (Cloudflare D1's point-in-time recovery window), after which it ages out on its own; we do not restore a deleted workspace from a backup.
Removing one person. An admin can remove a single person from the workspace under Admin → Users, which deletes that person's sign-in, passkeys and recovery codes. Everything else in the workspace stays.
If you cannot use the buttons (for example you lost access to your account), contact us through laberty.app/help/contact and we will help you export or delete by hand after confirming who you are.
Children
Laberty is a household and organizational tool, not a service directed at children. We don't knowingly collect information directly from a child using the service on their own. A child's name or birthday entered by a parent or admin as part of managing their own household is treated the same as any other data in that workspace.
Security
Sign-in is passwordless (a one-time emailed link or a passkey); we never hold a password to leak. All traffic to laberty.app is encrypted in transit. Access to your workspace's data is checked on every request against your role and, where the account has one, two-factor confirmation. No system is perfect — see the Terms of Service for what we can and can't promise about that.
Changes to this policy
We may update this policy. The version and date at the top will change when we do. We do not currently maintain a per-account history of which version you agreed to; if that becomes important (for example, for a specific regulatory disclosure) we will add it, the same way the Founder License already tracks the terms version each buyer agreed to.
Contact
Questions about this policy, or a request about your data that the buttons under Admin → Your data do not cover: laberty.app/help/contact.
Download this policy (Markdown) · Contact support