# SOVECOOK Privacy Notice

Effective: August 31, 2026

Counsel review remains required before broad commercial launch.

Cook uses local device storage for local taste preferences and PWA operation. Signed-in features may store a Sove subject identifier, Palate Graph values, recipe ratings, registered allergens, meal logs, plan entitlement, and operational audit records in the Cook service database.

Stripe processes checkout, payment details, invoices, and subscription lifecycle events. Cook stores Stripe customer/subscription references and the resulting plan state, but it is not designed to receive or store a full payment-card number.

Sove Support may store a conversation, answer evidence, feedback, and a ticket capsule. Common email, phone, payment-number, and secret-key patterns are redacted before support text is stored. Automated redaction is a safeguard, not permission to submit secrets or medical records.

Aeviva information is used only through the consent-bound, revocable connection described in the application. Cook does not treat that connection as permission to diagnose or ingest unrelated Aeviva data.

Administrative access is checked server-side using the active Sove session. Security, billing, and support events may be retained as needed to operate the service, prevent abuse, resolve disputes, and preserve tamper-evident audit evidence.

Use Sove Support for account-specific privacy requests. Authentication may be required to prevent disclosure or deletion of another person's data.