Privacy

Nothing leaves your device. Recipes and batches are written to your browser's local storage and stay there. Scovillo has no copy, and clearing your browser data deletes them permanently — there is nothing to restore them from.

Signing in syncs the following to Scovillo's servers:

• Recipes, their ingredients, process steps, and variations
• Recipe folders
• Batches, their steps, fermentation logs, and journal entries
• Your pantry, and any custom ingredients or step types you create
• Your settings — units, notification preferences, display name

Your account itself stores your email address and, if you set one, a handle and display name. Passwords are handled by our authentication provider and are never visible to Scovillo.

Data is stored on Supabase, and access is enforced per-row at the database level: a signed-in account can only read and write its own rows.

Sharing a recipe. Creating a share link makes that recipe readable by anyone holding the link — its name, ingredients, quantities, process steps, and notes, alongside the display name you chose. Nothing else from your account is exposed, and other recipes stay private.

Publishing to Explore. Marking a recipe public lists it for other Scovillo users to browse and fork. The same information is visible as with a share link.

Your pantry, batches, and fermentation logs are never shared by either action.

Step timers can send a push notification when they finish. If you allow that, your browser's push subscription is stored so the notification can be delivered — it identifies the browser, not you, and is removed when you revoke the permission.

If you turn on email notifications, timer alerts are also sent to your account email through our email provider. Scovillo does not send marketing email.

• No advertising, and no selling or sharing of your data with advertisers
• No third-party analytics or tracking scripts
• No reading of your recipes for any purpose other than showing them back to you

Export. Any recipe can be exported to a standard recipe file from its share dialog, readable by other recipe apps.

Deletion. Deleting a recipe or batch in the app removes it from your devices and our servers.

Deleting your account. At the bottom of Account there is a Delete Account button. It asks you to confirm and then to retype your email address, and the deletion happens immediately — every recipe, batch, pantry item, custom ingredient and setting goes with the account, along with the account itself. Nothing can be recovered through the app afterwards, so export anything you want to keep first — see backups, below, for the one exception. If you would rather not do it yourself, ask through the contact form and it will be done for you.

The database is copied to encrypted off-site storage once a day, so a failure at the hosting provider doesn't take everyone's recipes with it. Those copies are kept for up to 30 days and then deleted automatically.

So for a short window after you delete a recipe, a batch, or your whole account, a copy still exists inside a backup. It is not visible in the app, it is not used for anything other than restoring the entire database after a failure, and it ages out on its own. We do not restore individual accounts or recipes from backups — not for you, and not for anyone else asking about you.

If this policy changes in a way that affects what is collected or who can see it, the change will be noted here.

Questions, or a deletion request? Use the contact form.