Privacy Policy

Your Bath Log

SousVide may keep the following information in its app container:

• the cut, thickness, doneness target, temperatures, timing stages, notes, and completion state for a cook;
• cook cards, finished-cook photos, ratings, and short kitchen voice memos;
• favorite cuts, display and unit preferences, and saved draft-session state; and
• consumable-credit balances, credited transaction identifiers, and credit-journal entries.

Core cut selection, time-and-temperature reference, timers, and cookbook records work without creating an account. Local records remain on the device unless you use one of the network or export actions described below.

Camera, Photos, and Kitchen Voice Memos

SousVide requests access in the context of the feature you choose:

• Camera: to photograph a finished cook for a cook card or provide an ingredient image for Smart Thermal Read.
• Photos: to choose an image, save a cook-card image, or export cookbook material to your Photo Library.
• Microphone: to record a short voice memo for a cook card.

Cook-card photos and voice memos are stored locally. Voice memo audio is not part of a Smart Thermal Read request. An image selected for Smart Thermal Read leaves the device only after the separate consent and analysis action described next.

Smart Thermal Read and DeepSeek

Smart Thermal Read is optional. After you accept its data notice and start a read, SousVide sends DeepSeek the cooking description you entered and, when you chose one, a resized JPEG of the ingredient photo. The request also includes SousVide's bundled cut-and-doneness catalog so the service can return a structured match; it does not send your complete cookbook or voice memos.

DeepSeek may return a suggested cut, thickness, doneness, preparation steps, cautions, visible ingredient observations, and a confidence score. Treat the result as a cooking aid and verify food-safety requirements independently. If you decline or revoke Smart Thermal Read consent, manual cut selection, timers, and saved cook cards remain available.

DeepSeek processes the submitted description and image under its own service and privacy practices. Avoid submitting people, labels, account details, or other content that is not needed for the cooking read.

Attribution, ATT, and Adjust

SousVide does not display third-party ads inside the cooking planner. It uses Adjust to measure whether external promotions lead to app sessions, first visits, and credit-pack purchase events. iOS may show the App Tracking Transparency prompt after the app becomes active. Declining ATT does not disable cut selection, cook timers, cook cards, voice memos, purchases, or Smart Thermal Read; it limits access to the advertising identifier, while other measurement may remain available under platform rules.

Depending on device settings and service availability, Adjust and SousVide service infrastructure may process device or app identifiers, promotion-attribution fields, product-interaction events, and purchase-event metadata. The current purchase-event code supplies revenue and currency fields, and some call paths use the credited quantity. Those fields are measurement metadata, not a statement that SousVide receives payment-card details or independently verifies the amount Apple ultimately charged.

In user-facing terms, the release privacy manifest declares Device ID as tracking data used for analytics and app functionality and marks it as not linked to identity. The manifest also declares tracking and names measure.sousvide-app.pages.dev as a tracking domain. Manifest accuracy for the final binary is a separate technical review item.

Apple Purchases

Apple StoreKit handles credit-pack payment, billing, taxes, refunds, and App Store account records. SousVide receives verified transaction and product information needed to grant credits and prevent duplicate grants, and keeps the resulting balance and journal locally. SousVide does not receive your full payment-card details. Purchase and order events may also be measured through Adjust as described above.

SousVide Online Services

When an eligible online service path is active, SousVide may establish a device/session identity for configuration and activity delivery. Requests can include a generated device UUID, server-issued user or session identifier and token, app/package version, device model, OS version, language, region, time zone, and available Adjust attribution fields. This service identity is not a user-created SousVide account and is separate from the local cookbook.

Other network recipients are limited to the functions described here: DeepSeek for a Smart Thermal Read you request, Adjust for attribution, Apple for StoreKit and device services, and the public host used for legal or support pages.

Retention, Deletion, and Security

Cook sessions, cards, photos held by the app, voice memos, preferences, and credit records remain locally until you remove them with available controls, clear app data, or uninstall SousVide, subject to ordinary iOS backup behavior. Copies saved to Photos must be managed separately in Photos.

Information already sent to Apple, Adjust, DeepSeek, or SousVide service infrastructure is handled under the applicable provider or service rules. Removing local app data does not automatically delete records held independently by those recipients. SousVide relies on iOS sandboxing and device security for local storage, but no storage or transmission method can eliminate every risk.

Changes

This policy may change when SousVide changes its cooking workflow, permissions, AI feature, purchases, attribution, or online services. The effective date above identifies this version.

Contact

For privacy questions about SousVide, contact cooks@sousvide.app. Do not include payment details, private photos, or voice memos unless they are necessary for the support request.