Cooking Journal Privacy Policy
This page describes the privacy design implemented in the Cooking Journal release candidate. It must be reviewed and finalized with the business’s actual contact information, vendors, jurisdiction, and legal counsel before public launch.
Information you provide
Cooking Journal can store your email address, display name, cooking journal entries, personal recipes, favorites, feedback, and photographs you choose to upload. Passwords are stored only as one-way password hashes.
Account and security information
The service stores session records needed to keep you signed in and protect your account. Security logs may include request identifiers, request paths, response status codes, and timing information. The application does not intentionally record precise location in product analytics.
Billing
If you purchase a paid plan, payment collection is handled by Stripe. Cooking Journal stores billing identifiers and subscription status needed to determine your access level. Cooking Journal is designed not to store full payment-card numbers.
Cooking photos
Journal photographs are private to the authenticated account. Images are reprocessed before storage, including removal of EXIF metadata during normal upload processing. Production deployments can store private images in S3-compatible object storage and serve them only through authenticated application routes.
Optional product analytics
First-party product analytics are disabled by default. If enabled, the release candidate records a restricted set of product events such as opening pricing, starting a cook, saving a cook, opening the meal builder, or submitting feedback. Event properties are deliberately limited.
How information is used
Information is used to operate the journal, recipes, subscriptions, account security, customer support, product improvement, and legal/security obligations.
Service providers
Production operation may use service providers for hosting, database storage, private object storage, email delivery, monitoring, and payments. The final policy must identify applicable providers and practices before launch.
Your controls
Signed-in users can export a JSON copy of account data from the Account screen and can request permanent account deletion from the same screen. Deletion removes Cooking Journal account data and private stored photos controlled by the application. Third-party records may be subject to their own legal retention requirements.
Retention
Account content is retained while the account remains active unless deleted by the user or as otherwise required for security, billing, legal, or operational reasons. Final production retention periods must be documented before launch.
Children
The release candidate is not designed for children under 13. Age eligibility and any additional regional requirements must be finalized before public launch.
Security
Cooking Journal uses HttpOnly browser sessions, CSRF protection, password hashing, private photo authorization, security headers, rate limiting, and production configuration checks. No internet service can guarantee absolute security.
Contact
Before launch, replace this section with the business’s verified privacy contact and mailing information.