1. Who we are
KJR Novelty & Concessions, LLC runs HACCP Plan Builder and is responsible for the personal information described here. [Lawyer: add data protection contact if required.]
2. What we collect
- Account details: your name, email address, organization name and a salted hash of your password (we never store the password itself).
- Content you enter: questionnaire answers, facility and product details, evidence files you upload and the documents generated from them.
- Billing records: what you purchased and when. Card details are entered on our payment provider's page and are not stored by us.
- Security and audit records: a log of important actions (sign-in, document generation, downloads, uploads) with the time, your IP address and browser type.
- Service email: confirmation and password-reset messages. We do not send marketing email through the service. [Lawyer: confirm before any marketing is added.]
3. How we use it
- To provide the service: build your plans, produce your documents, keep your account secure.
- To take payment and keep records of purchases.
- To detect abuse and investigate security problems, using the audit and rate-limit records.
- To answer your questions when you contact us.
4. How we protect it, and what is NOT encrypted
Only some data is encrypted. This list is exact: nothing else is encrypted by the service itself (the database and the disk are not separately encrypted unless the hosting provider does so, which we do not control). [Lawyer and engineer: re-confirm before launch.]
Encrypted before it is stored (AES-256-GCM; the key is kept in the server configuration, not in the database, and database backups hold only the encrypted form):
- The content of each plan: your questionnaire answers, your decisions, the evidence links and any AI suggestions.
- The saved snapshot of a plan taken each time you generate documents (revision snapshots).
- The contents of the evidence files you upload.
- The contents of the PDF, Word and Excel documents the service generates.
4a. Stored as readable text (not encrypted)
These items are kept as ordinary text in the database, so anyone with access to the database or a database backup could read them:
- Your name, your email address and your organization name. Your password is stored only as a salted hash.
- The record that you accepted the terms of use and privacy policy when you created the account: the time and the version of each document.
- Plan titles, plan status, the product category and progress / readiness labels shown in lists.
- Facility records: name, address lines, city, state, ZIP code and notes.
- Product names.
- Evidence records: the title and description you typed, the original file name, the evidence type, size, file type and checksum (not the file itself).
- The note you can add to a plan revision, and each revision's number, date and readiness label.
- Generated-document records: a generic file name (for example haccp-plan-rev3.pdf), size, checksum and date (not the document itself).
- Purchase and subscription records: what was bought, the amount, the date and the payment provider's reference numbers.
- Payment-provider event records, exactly as the provider sent them, which can include a billing name and email address.
- AI-usage records: which feature ran, the model, the token counts and the time (never the text that was sent).
- The activity log: the time, the type of action (sign-in, upload, download, document generation and so on), opaque ids, the IP address and the browser type.
4b. Other protections
Sign-in uses a secure, HTTP-only cookie. The application keeps the data of each organization separate from the data of every other organization. Uploaded files are checked before they are stored. No system is perfectly secure. [Lawyer: breach notification wording.]
5. Who we share it with
We share information only with providers that help us run the service:
- Our payment provider [Paddle or Stripe: whichever is live at launch], to process payments.
- Our email delivery provider [name], to send confirmation and reset messages.
- Our hosting provider [name], where the service and its backups run.
- Anthropic, only when you use an optional AI suggestion. The request contains the product and process details needed for that suggestion. The code that builds these requests leaves out business name, contact, address, licence and team details. The service works fully without AI. [Lawyer and engineer: re-confirm before launch.]
6. Cookies
We use one essential cookie to keep you signed in. We do not use advertising or analytics cookies at present. [Lawyer: confirm if that changes.]
7. How long we keep it
We keep your account and plans until you delete the account. [RETENTION PERIODS for the activity log, billing records and backups, as decided with a lawyer.] Deleting the account is described in section 8.
8. Your choices and rights: download and deletion
The owner of an organization can, on the Account page, (a) download all of the data of the organization as a file and (b) delete the account. Download gives you the plans with your answers in readable form, your facilities, products, evidence and document records, purchases and the activity log. It does not include password hashes or the uploaded and generated files themselves (download those from each plan). Only the owner can do either.
To delete, the owner types the organization name and re-enters their password. An active subscription must be cancelled first, because deleting the account does not stop billing at the payment provider; subscriptions cannot be cancelled from the app yet, so contact us to cancel one.
Deleting the account removes:
- The organization and every user in it (all members lose access immediately).
- All plans, plan revisions, facilities and products.
- All evidence files and generated documents. The stored files are deleted first.
- All purchase, subscription and expert-review records held in the app.
- The IP address, browser type and details of every activity-log entry of the organization.
- The content of the payment-provider event records that mention your organization.
8a. What remains after deletion
Some records stay, for the reasons given:
- An anonymised activity log: each entry keeps only its time, its action type and opaque ids. The IP address, browser type and details are removed. The log cannot be edited or deleted, by design, so that history cannot be rewritten.
- One "account deleted" entry with counts of what was removed and, for accounting, the payment references, amounts, currencies and dates of your purchases. It holds no name, email address or organization name.
- The payment-provider event records keep their type, provider reference and timestamps (their content is removed), so that payments can be reconciled.
- Our payment provider keeps its own records of your payments for as long as the law requires it to. We cannot delete those.
- Backups made before the deletion still contain your data until they are removed on the backup schedule. They are not edited. By default the newest 14 daily backups are kept, so your data is gone from backups once they have all been replaced.
- Security records that are not tied to an organization, for example failed sign-in attempts for an address that has no account. They hold a hashed identifier, the IP address and the browser type.
8b. Other requests
[Lawyer: access, correction and objection rights that apply in the places you serve.] To correct your name, email address or organization name, or for anything else, use the contact page.
9. Changes and contact
[How changes to this policy are announced.] Questions: see the contact page.