Data processing addendum
How we look after your team's records for you.
For businesses that keep their workers' records in CleanCleaver. Effective October 8, 2026.
Last updated
1. Who and what
Who is this between, and what does it cover?
This addendum is between the business that uses CleanCleaver ("the customer") and Praiseworthy Apps LLC (9241 January Dr, Las Vegas, NV 89134). It is part of the terms of service. Where they differ about personal data, this addendum wins.
It covers the personal data the customer keeps in CleanCleaver about its own work and people (its "records"). For those records the customer is the controller and we are its processor (and, under US state laws, its service provider). For our own accounts, billing, emails and website we are a controller; the privacy policy covers that.
Annex 1
What we process for you
| Details | |
|---|---|
| Subject and purpose | Keeping the customer's food-safety records: checks, temperature readings, fixes, cleaning, people and roles, permits, reports, daily health check-ins, photos, and the inspection binder; reminders to its people; reading paper logs and photos when the customer uses those steps. |
| People | The customer's owners, managers, workers and volunteers; in home mode, household members the adult adds. |
| Data | Your account and business, The records your business keeps, Daily health check-ins, Photos and files, The record of changes, Sign-in, Home mode, Questions to Ask, Reminders to your phone or browser, Your settings. |
| Sensitive data | Daily health check-in answers (yes or no to the Food Code's illness questions). Shown only to the worker; managers see only the result; never sent to an AI model, a notification or an export. |
| How long | While the customer's account is open; then as section 9 says. |
2 to 6. What we promise
How we handle your records
- Only on your instructions. We process the records only to run CleanCleaver for you, as the terms, this addendum and your settings say, unless the law makes us do otherwise (then we tell you first, where the law allows).
- People bound to confidence. Only our staff who need to, on a reviewed access list, can see your records, and they are bound to keep them confidential.
- Security. We keep the measures in Annex 2 and may improve them; we will not make them weaker.
- Help with your duties. We help you answer your people's requests, assess risk and talk to authorities. If one of your workers asks us directly, we pass it on to you within 5 days and do not answer it ourselves.
- Not ours to sell. We do not sell or share your records, use them for our own purposes outside running the service, or combine them with other data, except as the law allows a service provider (for example, to keep the service secure).
7. Subprocessors (Annex 3)
Who else processes your records
You authorize the subprocessors below. Each one has a written contract with data protection terms at least as strong as these. We tell you 30 days before a new one starts (on the subprocessor page and by email); you can object, and if we cannot fix the objection you can end the service and be refunded for the unused time. We stay responsible for our subprocessors.
| Company | What it does | What it gets | Where | Kind |
|---|---|---|---|---|
| Fly.io Fly.io, Inc. | Hosts the app, the API, the Postgres database, the photo volume, snapshots and logs. | Everything we store to run the service. | United States. | Subprocessor |
| Tigris (object storage, through Fly.io) Tigris Data | Not in use today: photos and uploaded files are kept on our Fly.io servers. If we turn it on, it keeps them in private storage. | Every photo and uploaded file (paper-log and setup scans, place, equipment and permit photos, report PDFs), as private objects. | Not in use today. | Subprocessor |
| Postmark AC PM LLC (an ActiveCampaign company) | Sends sign-in codes, trial and billing notices, deletion notices, review and checklist emails. | Email address, the message text. | United States. | Subprocessor |
| Stripe Stripe, Inc. | Card payments, subscriptions, the billing portal. | Billing name, email, business name, card (typed on Stripe's pages only), plan and invoices. | United States. | Subprocessor |
| Anthropic (Claude API) Anthropic, PBC | Ask answers and backup picks, the auto-answer drafts, reading paper-log and set-up photos (with Gemini's reading), the AI RoomCheck second look, and the team site's one-line summaries of support conversations (the feedback loop). | Ask questions with emails, phone numbers and known names removed; photos of paper logs, kitchens and receipts; room photos (AI RoomCheck, off by default); support conversations (app, email, chat) as customer/us lines with emails, phone numbers, card numbers and known names blanked, never a thread in which any message trips the health keyword heuristic. Never a health check-in answer. | United States. | Subprocessor |
| Google (Gemini API) Google LLC | Reads paper-log, set-up and food photos; translates voice words in languages other than English and Spanish; AI RoomCheck first pass. | The photo or the words sent. | United States (Google's global infrastructure). | Subprocessor |
| Google (Firebase Authentication) Google LLC | "Continue with Google" sign-in only. | Email, name and Google account id in the sign-in token. | United States. | Subprocessor |
| Expo (push relay for the phone app) 650 Industries, Inc. (Expo) | Delivers phone reminders to Apple (APNs) and Google (FCM). | The phone's push token and the reminder text (no health detail). | United States. | Subprocessor |
| Apple (APNs, iPhone reminders) Apple Inc. | Delivers phone reminders to iPhones straight from our server (no Expo relay). | The iPhone's push token and the reminder text (no health detail). | United States. | Subprocessor |
| Google (Firebase Cloud Messaging, Android reminders) Google LLC | Delivers phone reminders to Android phones straight from our server (no Expo relay). | The Android phone's push token and the reminder text (no health detail). | United States (Google's global infrastructure). | Subprocessor |
| Crisp (website chat) Crisp IM SAS (France) | The website chat button, only after a visitor presses it. | What a visitor types and any email they give. | European Union (per Crisp's privacy page). | Subprocessor |
8. Breaches
If something goes wrong
If we become aware of a breach of your records, we tell you without undue delay and within 48 hours, with what we know: what happened, the people and records involved, the likely effects and what we are doing. We keep you posted as we learn more, and give you what you need to tell your people and any authority. Our incident register tracks each legal clock (in Europe and the UK, 72 hours for you to tell the authority; each US state's own rules) so nothing is missed.
9. At the end
Getting your records back, and deleting them
At any time the owner can download everything the business has stored, as one file. When the owner deletes the business, we wait 7 days (the owner can cancel), then erase every record, person and photo, and keep one line that the business existed and was deleted. Backups hold deleted data for up to 5 days. We keep nothing else unless the law makes us, and then only for that.
10. Audits
How you can check
Once a year, on request, we answer your written security questions and share our security documents and our evidence pack (the list of our controls and the evidence for each). We have no outside security audit report yet and do not claim one. An on-site or third-party audit is possible after a breach, or when an authority asks, on reasonable notice and at your cost.
11. Transfers
Records from Europe or the UK
Your records are kept in the United States. Where European or UK law applies, the Standard Contractual Clauses (Module 2, controller to processor) and the UK Addendum are part of this addendum, with Annex 1 as their description of the transfer and Annex 2 as their security measures.
- In transit: HTTPS only (force_https), HSTS; TLS 1.3 measured on public hosts; see the security page.
- At rest: the database and files sit on Fly.io volumes protected at rest by the host, snapshots included; see the security page.
- Access: per-business walls; roles; staff areas need a verified sign-in on an allow-list; quarterly access review.
- Secrets hashed: sign-in codes (HMAC-SHA-256), sessions (SHA-256), tablet PINs (salted hash).
- Health check-in answers never shown to managers, exported, sent to AI, notifications or analytics.
- Append-only audit trail of changes and sign-ins.
- Daily snapshots kept 5 days; restore rehearsed (docs/security/backup-and-restore.md).
Your binder is ready when the inspector is.
Pick your place. Start with one shift.
Start your 25 days free See it work
25 days free. Cancel anytime.
Questions? Call or text (415) 640-1667