Dinner Minutes — Privacy Policy
Effective 2026-09-10 · v1.0
The short version, in plain words
Think of Dinner Minutes as a notebook that lives in your pocket.
The notebook stays with you. Your companies, the people at your table, your agendas, your receipt photos, what you said in your recap, and the finished PDFs are saved on your phone. Not on our computers. If we shut down tomorrow, your records would still be on your phone and in your email.
We borrow things; we don't keep them. To turn one dinner into two documents, your phone hands our server the pieces it needs. The server makes the PDFs, emails them to you, and throws its copy away the moment your phone says "got it." If your phone never says that, the copy deletes itself within about an hour anyway.
Two different AI companies help, and neither keeps your stuff. One reads your receipt and one writes up your notes — both are Claude, made by Anthropic. A third turns your talking into text, and that one is Whisper, made by OpenAI. Each gets only the piece it needs. Neither is allowed to use your information to train their models.
We do keep a few boring things. Your email address so you can sign in. Whether you paid. That you promised you're keeping records for your own company. That's about it.
What we couldn't hand over. If someone demanded every customer's meeting records, we couldn't produce any, because we don't have any. That is a design choice, not a promise.
Everything below says the same thing with exact detail.
1. What stays on your device and never reaches us
These live in your browser's own database (IndexedDB) on the device where you use Dinner Minutes. They are not uploaded to us, not backed up by us, and not readable by us:
- Your entities: legal name, state of formation, what the company does, the people and their roles, each roster, who signs, and each signer's drawn signature image.
- Each entity's standing agenda, and each meeting's agenda.
- Every meeting: date, who was present, place, times, amounts.
- Receipt photographs.
- Recap audio recordings.
- Recap transcripts.
- Drafted and approved minutes.
- The finished PDFs.
- Your app settings.
If you clear your browser data, uninstall the app, or lose the device, we cannot restore any of it. Your emailed PDFs are the backup — which is why every compiled meeting is emailed to you.
2. What your device sends us, and how briefly we hold it
Producing your two records is the only thing that needs our server. When you approve a meeting, your device sends in a single request: the entity snapshots for the entities that met (including signature images, so they can be drawn onto the PDF), who was present, the place, times and amounts, the itemised list, both receipt images, and the approved minutes drafts.
Our server renders the two PDFs, emails them to you, and retains the files only long enough for your device to confirm receipt or request them again. They are deleted as soon as your device acknowledges delivery, and in every case within one hour, enforced by a sweep of the job directory. They are copied nowhere else. There is no customer database of meeting records for them to be copied into.
3. What we send to AI providers, and exactly what each receives
We use two AI providers. They are separate companies and they receive different things.
Anthropic (Claude) receives:
| When | What is sent |
|---|---|
| You photograph a receipt | The receipt image only — no entity name, no account identifier |
| You approve a recap for drafting | The entity's legal name, its one-sentence description, the agenda, the names of any other entities that met the same night, and the recap transcript |
| You use the spoken setup interview | Your answers about your company and its people |
| You run the agenda tune-up | The entity name and description, the standing agenda, items left open at the last meeting, and the headings of recently discussed topics — not the body of any minutes, no amounts, no dates |
OpenAI (Whisper) receives:
| When | What is sent |
|---|---|
| You record a recap, or speak your setup answers | The audio recording, plus a short hint that the speaker is a business owner discussing an LLC, which improves transcription accuracy |
The audio goes to OpenAI, not to Anthropic. We spell that out because it is reasonable to assume a single AI company handles everything.
Both are used through their commercial APIs under terms that do not permit training on submitted content. Neither receives your account identifier, your email address, or your billing details.
Other processors, each bound to use data only to provide their service to us:
- Clerk — sign-in; holds the account facts listed in §4.
- Stripe — payments; holds billing details. We never see or store full card numbers.
- Resend — email delivery; receives your email address and the two PDFs in order to deliver them.
- Render — application hosting, including the short-lived compile job in §2.
- Cloudflare — website hosting and network security.
We disclose personal information when required by law or to protect rights and safety, and we will tell you about a legal demand for your data unless prohibited. Because we keep no meeting content after delivery, there is usually nothing to produce.
4. What we keep, deliberately
Held against your account for as long as the account exists:
- Your email address, and your name if you gave one.
- How many free meetings you were granted and how many meetings you have compiled — a count, not the meetings.
- Your Stripe customer identifier, whether a card is on file, and whether a payment failed.
- The time you accepted the Terms and this Policy.
- If you redeemed a code: which code and when, so it cannot be reused.
- If you enable notifications: that device's push subscription, and any scheduled reminder wording (see §5).
Attestations. When you add an entity you attest that you are authorised to keep its records and are preparing them for your own entity. We keep that attestation text, your account identifier, and the timestamp permanently. It is our record that the Service was used as intended.
Technical logs. Standard server logs — timestamps, request paths, error messages. They do not contain the contents of your meetings.
Retention
| Data | Retention |
|---|---|
| Receipt photos, recordings, transcripts, agendas, generated PDFs | Deleted as soon as your device confirms receipt; within about one hour regardless |
| Emailed PDFs | Delivered to your inbox, which is the archive; we keep no copy after delivery |
| Attestations | Permanently |
| Account information | While your account is open; deleted within 30 days of closure except where law requires longer |
| Billing records | As long as law and our payment processor require, typically 7 years |
| Redemption-code record | Life of the account |
| Push subscription and scheduled reminder text | Until you disable notifications, the reminder fires, or the account closes |
5. How the device-side design actually works
This is not a policy promise laid over an ordinary cloud app; it is how the app is built.
- Local database. Records are written to IndexedDB on your device through the Dexie library and read back directly by the screens. There is no sync service and no account-scoped copy on our side.
- Stateless endpoints. Our routes take an input, return an output, and keep nothing. The single exception is the compile job in §2, which exists only so the files survive the seconds between rendering and your device confirming receipt.
- Reminders are local. The recap reminder is a timer running inside the app on your device, fired from your device's own clock. Nothing about it is sent anywhere.
- Badges are computed on your device. The count on the app icon is worked out on the phone from local data. If you enable notifications so a reminder can reach you while the app is closed, your device composes the wording itself and our server acts only as a relay: it is given a time and a short generic line such as "A quarter closes soon" — never an entity name, an amount, or a meeting date.
- Deletion is real. Deleting your account removes your sign-in, your billing profile, and the local database. There is no server-side copy of your records to delete, because none was made.
6. What we do not do
We do not sell personal information. We do not share it for advertising. We do not use your meeting content to train AI models, and our providers are not permitted to either. We hold no database of customers' tax records.
7. Your choices and rights
- Access and export. Everything the Service produces is delivered to you by email and stored on your device. Your entities and meetings are editable in the app.
- Correction. Entities can be edited at any time from the entity screen; meetings can be corrected before you approve them.
- Deletion. Delete your account from Settings. That removes the account data in §4 and the local database. Attestations and billing records are retained as stated above.
- State and national privacy rights. Residents of California and other states with privacy laws, and users subject to comparable laws elsewhere, may have rights to know, access, correct, delete, port, or opt out of sale or sharing. We do not sell or share personal information. Write to [email protected]; we will verify and respond within the time the law allows.
8. Children
The Service is for adults acting for their own business entities. It is not directed to anyone under 18; you confirm you are 18 or older when you sign up. We do not knowingly collect information from children. If we learn an account belongs to someone under 18, we close it and delete its data.
9. Where data is processed
Dinner Minutes is operated from the United States and our providers process data in the United States. If you use the Service from elsewhere, your information is processed in the United States.
10. Security
Traffic is encrypted in transit and access to production systems is limited. No system is perfectly secure, so the protection that matters most here is structural: for the overwhelming majority of what you put into Dinner Minutes, there is nothing on our servers to breach.
11. Changes
If we change this policy we will update the date above, and for a material change tell you in the app or by email before it takes effect.
12. Contact
Dinner Minutes · Empire Oaks Estate LLC · [email protected]