Privacy Policy

dosd stores health-adjacent personal data, so this policy is written to be actually readable. Short version: your data is yours, it's only used to run the app for you, and you can export or delete all of it yourself.

What we store

• Account: name, email, password hash (or OAuth identity), sessions.
• Your entries: goals, recipes, protocols, schedules and check-offs, inventory, orders you record, health scores and notes, settings.
• Operational data: AI usage metering and standard server logs (kept short-term for abuse prevention and debugging).

We don't run ads, don't use tracking cookies, and don't sell or share your data. Cookies are limited to what login requires.

Where it lives

Data is stored in a managed Postgres database (Neon) and served via Vercel, encrypted in transit and at rest. Backups follow the database provider's point-in-time recovery.

AI processing

When you use an AI feature (recipe extraction, suggestions, stack analysis, help chat), the relevant content — e.g. your ingredient list and doses — is sent to the AI provider (currently Google Gemini) without your identity: no name, no email, no account id. AI features are optional; nothing is sent unless you invoke them.

Sharing between users

Only recipes you explicitly set to public are visible to others, limited to the recipe definition and your display name. Inventory, schedules, consumption history and health scores are never shared.

Your rights

Settings → Your data gives you both: Export my data (one JSON file with everything you own) and Delete account (immediate, permanent removal of your account and every row you own). No support ticket needed. For anything else: hello@dosd.app.

Changes

Material changes to this policy will be announced in the app before they take effect.