At a glance
- Essential first — We use cookies and browser storage mainly to sign you in, protect your account, remember settings, and keep the app usable.
- No ad tracking cookies — We do not currently use third-party behavioral-advertising cookies, retargeting pixels, or data-broker tracking on DinDin.
- No session recording — We do not record your screen or session, and we do not automatically capture what you click or type. Our analytics provider stores nothing in your browser.
- 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 store, and why
- Essential session cookies
- Keep you signed in, route you to the right account area, protect authenticated pages, support logout, and maintain account security.
- Member session and admin session cookies. Required for signed-in use.
- Preference storage
- Remember choices that make the app feel consistent between visits.
- Theme preference, UI mode, collapsed sections, drawer state, and guided tour state. Can 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.
- Pending state patches, selected week context, recipe insert handoff, ready-list drawer state, and return-to-page state. Used 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.
- Temporary OAuth state, login return paths, one-time flow state, and reload protection markers. Temporary 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.
- Basic product events, API operation logs, error details, and sync diagnostics. Used 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.
- Stripe-hosted checkout or portal cookies; Google authorization cookies on Google pages. Controlled by the third-party provider when you use that flow.
- Measurement
- Count page views and named events on the public DinDin pages so we can see which pages lead to an account.
- None. The analytics provider is configured to keep its identifier in memory only, so it writes no cookie and no local or session storage — closing the tab ends it. Page-performance measurement is likewise cookieless. Nothing to clear. There is no session recording and no automatic capture of clicks, typing or scrolling.
Why we use browser storage at all
- 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.
Measurement, and no session recording
Our analytics provider is configured to keep its identifier in memory only, so it writes no cookie and no local or session storage — closing the tab ends it. Page-performance measurement is likewise cookieless.
We do not record your screen or your session, and we do not automatically capture what you click or type. There is nothing here for you to clear.
Advertising
DinDin does not currently use third-party behavioral-advertising cookies, retargeting pixels, or data-broker tracking. If that ever changes we will update this page before the technology is added.
Third-party pages
When you use Stripe checkout or the billing portal, or sign in with Google, or authorize Google Calendar, those providers may set their own cookies under their own policies. Those are their pages, and their controls apply.
Your controls
- 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.
Changes to this policy
We may update this policy as the service changes. The date at the top tells you when it was last revised.
Questions can be submitted through DinDin's Contact page.