SaltyBytes Privacy Policy

Last updated: July 6, 2026

SaltyBytes (“we”, “our”) is a recipe app operated by Julian Dice. This policy describes what data the SaltyBytes app and service handle, why, and the choices you have. The short version: we collect the minimum needed to run your account and your recipe collection, we don't sell data, and the app contains no ads and no third-party analytics or advertising SDKs.

What we collect

Account data. When you sign up we collect your email address, a username, and a password (stored only as a salted hash). Your email is used to verify your account and for essential service messages — never marketing lists you didn't ask for.

Your content. Recipes you import, save, fork, or edit; photos, PDFs, text, links, and video links you submit for import; and the recipe images generated or fetched for your collection. Uploaded files and images are stored with our hosting provider (Amazon Web Services, US regions).

Family dietary profiles. If you choose to add family members' dietary information (allergies, intolerances, preferences), we store what you enter and use it for exactly one purpose: checking recipes and search results for safety flags. This can include health-related information — add only what you're comfortable storing, and you can edit or remove profiles at any time.

Voice input. If you use voice features (dictating a recipe, hands-free cooking mode), audio is processed to transcribe your words and fulfill the request. We keep the resulting text (for example, an imported recipe); we do not keep a library of your audio recordings.

Operational logs. We keep first-party logs of how features behave (for example: whether an import succeeded, how a search run performed, and AI usage for cost accounting) to operate, debug, and improve the service. The app itself contains no third-party analytics, tracking, or advertising SDKs.

How AI processing works

SaltyBytes features like recipe extraction, agent search, allergen analysis, and dietary interviews send the relevant content (a page you asked to import, a photo of a cookbook page, your search request) to large-language-model providers acting as our processors — currently Anthropic, OpenAI, and Google — through their commercial APIs, which do not grant them the right to train their models on your data. Content is sent only to fulfill your request.

When you ask SaltyBytes to import or preview a URL, our servers (and our web-fetching subprocessor, Firecrawl) fetch that page on your behalf.

Public recipe pages

When a recipe is extracted from a public web page, the cleaned-up extraction may be viewable at a saltybytes.ai link so it can be shared. These pages contain only content extracted from the public source (with attribution and a link back) — never your account details, notes, or personal edits.

Sharing

We do not sell your data and we do not share it with advertisers. Data is shared only with the subprocessors that make the service work — Amazon Web Services (hosting, storage, email), Anthropic, OpenAI, and Google (AI processing), and Firecrawl (web fetching) — and when the law requires it.

If you connect SaltyBytes to an AI assistant (for example, adding the SaltyBytes connector in Claude or ChatGPT), you authorize that assistant to access your recipes through a scoped OAuth grant. What the assistant's operator does with data you surface there is governed by their privacy policy; you can revoke the connection at any time.

Retention and deletion

Your content stays in your account until you delete it. Deleting a recipe removes it from your collection. To delete your account and all associated data, email [email protected] from your account email — deletion is completed within 30 days. (In-app account deletion is coming; until then, email is the path.)

Children

SaltyBytes is not directed at children under 13, and we do not knowingly collect data from them.

Changes

We'll update this document when practices change and note the date at the top. Meaningful changes will be called out in release notes.

Contact

Questions or requests: [email protected]