Account, kitchen, and technical information
We receive the name and email address you provide when creating an account or joining a kitchen, authentication and session information, membership and role information, and account preferences. Authentication may include email verification, password recovery, and authenticator-based multi-factor authentication.
You provide kitchen records such as ingredients, item types and categories, purchase prices, images, stock movements and costs, recipes and preparation steps, production plans, shopping lists, and settings. Operational records may include the account that performed an action, its time, its source, and confirmation or synchronization status. Authorized members can see or change shared records according to their roles.
Our services and providers may process information needed for sign-in, security, delivery, troubleshooting, and abuse prevention, including IP addresses, device or browser details, request activity, errors, and delivery status. We also maintain usage and request identifiers needed to enforce limits and confirm or resume operations.
Contact and billing information
When you use the contact form, we receive your name, email address, topic, and message. Human-verification services can process technical and interaction information associated with that request.
For subscriptions, we process billing-related identifiers, subscription and payment status, billing contact details, and available invoice or receipt information. The app may display limited payment-method information, such as brand, last digits, and expiration. Full payment credentials are entered with Stripe; the app's billing detail view does not display a full card number or security code. The Owner can view tax identifiers, billing addresses and the verification status provided by Stripe in the billing view; changes are managed through the payment provider.
How we use information
We use information to authenticate accounts, provide and synchronize kitchen workspaces, calculate operational results, authorize actions, maintain audit and transaction history, manage subscriptions and usage limits, deliver requested notifications, respond to support requests, prevent abuse, and maintain the service.
Sharing a kitchen makes its permitted records available to authorized members. Removing a membership restricts future access, but records that member contributed may remain as part of the kitchen's operational history. Exporting or sharing records creates copies outside the workspace's access controls.
Optional AI processing
When an authorized member requests Cuisine AI generation, selected ingredient names, inventory identifiers, units, maximum quantities, measurement system, and preferred units are sent through our Google AI integration. The current generation input does not include your entire inventory, purchase prices, account email, or recipe images. Names or other text you enter can nevertheless contain personal or confidential information.
Google processes the request and generated response under the terms applicable to the configured AI service. Its Gemini API terms explain provider retention, review, and data uses, including differences between paid and unpaid services. Contact us before submitting confidential information if you need clarification about the configured service. Avoid including unnecessary personal or sensitive information in ingredient names.
The app records usage, reservations, request status, credit purchases, verified payment status and refund/dispute adjustments to manage the kitchen's shared allowance and balance, and can keep generated options on the device. A suggestion you choose to save becomes a kitchen recipe and is handled like other recipe content. Review AI output before using it, particularly allergens, food safety, quantities, and costs.
Optional POS Connect integration
POS Connect lets a kitchen authorize a supported point-of-sale provider. It is not exclusive to one provider; Clover is the integration currently available. When the kitchen Owner authorizes a connection, we process the merchant identifier, available merchant name, selected environment, connection and authorization status, and the account and dates associated with connection activity. We store the access and refresh credentials needed to read the authorized provider data in encrypted server-side credential storage; they are not displayed in the client or included as session tokens in the mobile return URL.
Authorized imports can include product identifiers, names, categories, SKU, price and activity status; order and line identifiers, quantities, amounts, status and dates; and available payment, tip and refund identifiers, amounts and status. We store synchronization checkpoints, event/retry status and safe error categories needed to update records and recover interrupted processing.
Associating a product with a kitchen recipe records the association and actor. Imported lines can retain recipe and subrecipe names, identifiers, yields, ingredient quantities and units captured on first import for historical interpretation and theoretical ingredient estimates. These snapshots are not replaced simply because a recipe or association is edited later.
POS Connect uses the authorized provider account and imported records to provide the kitchen’s connector, catalog, sales history and estimates. Available data and functions depend on the provider, permissions granted and supported integration. Each provider processes its own sign-in, authorization and merchant activity under its own terms and privacy policies. Review those policies in the provider’s service or published documentation before connecting; they are separate from this Privacy Policy. Starting authorization from mobile opens the browser and can return to the app; the browser may require a separate Cuisine Alchemy sign-in with the same Owner account.
Disconnecting removes the saved credentials used by this integration and stops further use of that connection, while imported history and recipe associations remain in the kitchen for authorized access. It does not cancel the POS subscription, uninstall an integration at the provider or erase records retained by that provider. Add-on expiration can pause further imports while preserving history. Kitchen/account deletion and applicable retention rules are separate from disconnecting.
Browser and mobile storage
The web app uses browser storage, including local databases and preferences, to retain workspace data, drafts, pending changes, and cached results. Essential authentication uses cookies or similar storage. A service worker can cache application resources for the installed web app and supported offline experiences.
The native mobile app also retains account sessions, preferences, kitchen caches, drafts, and pending operations in device-local storage. Its Files picker processes the files and images you choose, and export or print actions can create local or shared copies. These features do not require uploading all files on your device.
Normal sign-out can leave workspace records on the device. The web app offers sign-out with local data clearing and can keep the data when unsynchronized work prevents safe clearing. Browser storage controls or clearing mobile app data may erase pending work. Server-side account deletion cannot guarantee removal from other devices, downloaded files, system backups, or recipients' copies.
Optional website analytics and cookies
With your permission, the website uses Google Analytics to understand page usage and Microsoft Clarity for heatmaps, interaction analysis, and masked session recordings. These providers can process browser and device information, technical identifiers, and interaction activity. We do not send account names or email addresses as analytics identifiers.
Optional analytics are not loaded until you accept them in the cookie banner or Cookie preferences. Advertising consent remains disabled. Authentication, security, offline kitchen records, synchronization, and necessary preferences continue to work when you choose Only necessary.
Your choice is stored in this browser for up to 180 days. Use Cookie preferences in the website footer to change or withdraw it. Withdrawal stops analytics, clears accessible first-party analytics cookies, and may reload the page. This does not erase information already received by the providers or cookies controlled by third-party domains.
We mask page content for Clarity and exclude account, billing, settings, support, contact, authentication, recovery, and POS authorization routes from analytics initialization. URLs containing query parameters or fragments are excluded. Browser/device and interaction information can still be collected on permitted pages after consent. These website integrations do not add native mobile session recording.
See Google Privacy Policy and Microsoft Privacy Statement for provider processing.
Notifications and device permission
If you enable notification features, we process your channel preferences, time zone, summary schedule, quiet hours, and notification events. Push registration includes a device identifier, platform, push token, or browser subscription endpoint and associated delivery information. Email goes to your verified account email; push goes to registered devices.
Messages can contain kitchen-related information such as stock quantities in an email summary, process results, or synchronization issues. Push providers process delivery tokens and message content. Notification previews may be visible on a lock screen or shared device; you can manage previews through your device settings.
Manage optional alerts in Settings → Notifications. You can turn a type off, change its channels, or disable push on a device, and adjust device or browser permissions. These choices are personal. Essential account, security, billing, or legal messages are separate from optional kitchen alerts.
Optional device diagnostics for Support
When you choose Review diagnostic, the app prepares a dated troubleshooting snapshot. Choosing Share with Support sends the reviewed report, including account and known kitchen identifiers, platform and available version/build, connection observations, synchronization timestamps, pending/failed counts and a sanitized error category.
These diagnostic reports do not include recipe text, ingredient names, drafts, authentication tokens or raw error messages. Reviewing a report alone does not send it. Sharing requires a connection and is separate from cookie analytics consent; it does not automatically open a support case, synchronize the kitchen, repair records or confirm that an uncertain operation completed.
Service providers and other disclosures
We use Supabase for authentication and synchronized application data, including notification preferences and events; Stripe for checkout, kitchen-plan and add-on subscriptions, credit purchases, and payment-method management; the supported POS provider you authorize (currently Clover) for the optional POS Connect integration; Google AI for requested recipe generation; hCaptcha for human verification; Migadu for contact-message and configured SMTP email delivery; and Courier for configured kitchen-notification email routing and delivery-status processing.
When notification email is routed through Courier, it receives the recipient email address, message subject and body, and identifiers needed to deliver and track the request. Message content can include kitchen information described above. Courier and the configured email delivery provider process the message for delivery; we use returned request identifiers and delivery status to track completion and handle retries. This email integration does not route native or browser push through Courier.
Native push uses Expo's push service and the underlying Apple or Google delivery service. Browser push uses the delivery service associated with the browser or operating system, which can include Google, Mozilla, Apple, or Microsoft. Hosting and network services also process requests needed to deliver the website and app services.
Providers handle information needed for their functions under the applicable service arrangements. You can review the published policies of Supabase, Stripe, Clover, hCaptcha, Migadu, Courier, and Expo. Provider policies do not replace this explanation of Cuisine Alchemy's own processing.
We may disclose information when necessary to comply with law, respond to valid legal requests, protect the service and its users, or address fraud and security incidents. We also disclose information to recipients you select when using export, sharing, or printing features.
Exports, retention, and account deletion
Kitchen exports can include private team information and media. Browser exports can combine remote records with available local data and pending changes; native mobile exports include synchronized server records, so synchronize pending edits first. JSON and JSON Lines preserve the complete backup representation; tabular formats can omit media or truncate oversized cells. Current import tools restore supported Inventory items and Recipes only. Keep export files secure and review warnings before restoring data.
Smart Shopping CSV transfer is separate from a whole-kitchen backup. Its files can contain list and kitchen identifiers, ingredient names, quantities and units, purchase and receipt states, timestamps, and receipt references. Import processes the file you select and matches its rows to existing inventory items. It can create or update a shopping list, but does not add stock or recreate receipt transactions. Confirmed receipts already in the destination list are preserved; other imported received states are treated as purchased items awaiting a receipt. Downloading or sharing a CSV creates a copy outside workspace access controls.
We retain information while needed to operate accounts and kitchens, deliver and reconcile requests, maintain security and operational history, respond to support, or meet applicable obligations. Different records and providers may have different retention periods. Copies in provider backups or records needed for billing, security, or legal purposes can remain after application account deletion.
You can review account deletion in Account on the website; the mobile app links to that review. Deleting an Owner account removes its owned kitchen workspaces and associated application data and team access. Deleting a non-Owner account removes that account and its access while shared kitchen operational records remain. Account attribution can be removed from retained records, but personal details you or others entered into the record content may remain. Deletion does not retrieve previously exported or shared copies.
Your choices and privacy requests
You can update account details, manage team permissions when authorized, configure optional notifications, use permitted exports, and review account deletion in the app. Depending on applicable law, you may also have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent where consent is used. These rights can have legal limits and may require verification of your identity and authority over the records.
Use our contact page for privacy questions or requests. Explain the request without sending passwords, authenticator keys, or unnecessary sensitive information. If information was entered by another kitchen member, we may need to coordinate with the kitchen Owner while respecting the rights of the people concerned.
Security and international processing
We use access controls and technical safeguards intended to protect account and kitchen data, but no online service or device storage can guarantee absolute security. Protect shared devices, authenticator access, exported files, and notification previews.
Our providers may process information outside your country or territory. Applicable service arrangements and legal requirements govern those transfers; available privacy protections and provider retention rules can differ by location.
Children and policy changes
The service is intended for business users and is not directed to children. Do not include unnecessary personal information about children in kitchen records or AI requests.
We may update this policy when features, data practices, or legal requirements change. The date above identifies this version. We will provide notice of material changes through the service or another appropriate channel when required and obtain additional consent where applicable law requires it.