Essential first
We use cookies and browser storage mainly to sign you in, protect your account, remember settings, and keep the app usable.
Cookie Policy
Small bits of browser memory, mostly for the app to work.
DinDin uses cookies, local storage, session storage, and similar browser technologies to keep accounts signed in, remember settings, preserve planning workflows, support payments, and troubleshoot the service. This page explains what those technologies do and how you can manage them.
Last updated: April 27, 2026
No ad tracking cookies
We do not currently use third-party advertising cookies, retargeting pixels, or data-broker tracking on Din Din.
Stripe may set its own cookies
When you use Stripe checkout or the billing portal, Stripe may use cookies and similar technologies under its own policies.
You control your browser
You can clear cookies and browser storage, but doing so may sign you out or reset local app preferences.
What We Use
Cookies and storage by purpose.
Some data is stored as cookies. Some is stored in your browser’s local storage or session storage. The names may change as the product evolves, so this policy describes categories and purposes.
Essential session cookies
Keep you signed in, route you to the right account area, protect authenticated pages, support logout, and maintain account security.
ExamplesMember session and admin session cookies.
ChoiceRequired for signed-in use.
Preference storage
Remember choices that make the app feel consistent between visits.
ExamplesTheme preference, UI mode, collapsed sections, drawer state, and guided tour state.
ChoiceCan be cleared in your browser, but preferences may reset.
Planning and app continuity storage
Keep the app responsive, preserve pending edits, help recover state, and move context between pages.
ExamplesPending state patches, selected week context, recipe insert handoff, ready-list drawer state, and return-to-page state.
ChoiceUsed for core product behavior.
Security and sign-in flow storage
Support login, verification, MFA, OAuth redirects, Google sign-in, calendar authorization, and safe return paths.
ExamplesTemporary OAuth state, login return paths, one-time flow state, and reload protection markers.
ChoiceTemporary and tied to security or sign-in flows.
Diagnostics and service logs
Help us understand whether the product is working, troubleshoot errors, and protect the service from abuse.
ExamplesBasic product events, API operation logs, error details, and sync diagnostics.
ChoiceUsed to operate and improve reliability.
Third-party service cookies
Support services you intentionally use, such as payment checkout, billing management, Google login, or Google Calendar consent.
ExamplesStripe-hosted checkout or portal cookies; Google authorization cookies on Google pages.
ChoiceControlled by the third-party provider when you use that flow.
Why It Exists
Storage supports the meal planning experience.
Without cookies and browser storage, signed-in SaaS apps become brittle: you get logged out, settings reset, pending edits disappear, and payment or OAuth flows can fail.
- Authenticate signed-in users and protect private account pages.
- Remember settings such as theme, display preferences, and onboarding state.
- Keep meal planning, recipe, calendar, grocery, pantry, and ready-list workflows responsive.
- Support checkout, subscription billing, invoices, and plan management through Stripe.
- Support login, OAuth, MFA, and calendar sync flows.
- Diagnose bugs, sync issues, failed imports, performance problems, and abuse.
Third Parties
Stripe, Google, and service providers may use their own storage.
When you leave DinDin for Stripe checkout, the Stripe billing portal, Google sign-in, or Google Calendar authorization, those providers may use cookies and similar technologies according to their own policies. We do not control those third-party cookies.
Payments and subscriptions
Stripe may use cookies, device identifiers, fraud-prevention signals, and payment-session data to process checkout, payment methods, invoices, billing portal sessions, renewals, and fraud prevention.
Authentication and integrations
Google or other authorization providers may use cookies during login, consent, and connected-calendar flows. These cookies are managed by those providers, especially when you interact with their hosted pages.
Controls
How to manage cookies and browser storage.
Browser controls
Most browsers let you delete cookies, block cookies, clear local storage, and clear site data. Blocking essential cookies may prevent login or break signed-in features.
In-app controls
Settings lets you update preferences, disconnect calendar sync, download account data, deactivate your account, and change security settings.
Logout
Logging out clears the active session cookie. Some local preferences may remain so the app can feel familiar next time.
Third-party controls
Stripe, Google, browser vendors, and device platforms provide their own controls for cookies and account authorization on their services.
Retention
Session cookies generally last until they expire, are replaced, or you log out. Local storage can remain until you clear browser site data, use account controls, or the app overwrites it. Server-side records connected to cookies or storage are handled according to the Privacy Policy.
Required Storage
Some cookies and storage are necessary for security, sign-in, paid account access, product settings, routing, and core app behavior. If you block or delete them, parts of DinDin may stop working, lose state, or require you to sign in again.
Changes
We may update the cookies, storage names, providers, or purposes as the product changes. If we add materially different tracking or advertising technologies, we will update this policy and provide any consent controls required by law.
Related
Cookies are one part of the data picture.
The Privacy Policy explains account and planning data more broadly. The Terms explain the rules for subscriptions, billing, AI tokens, and use of the service.