Cookie Policy

Effective and last updated: November 2, 2026

This policy describes cookies and similar storage used by the Daye Health Transport website and apps. Read it together with our Privacy Policy.

1. What we use

Daye does use a necessary website sign-in cookie. We also use browser storage for sign-in, family invitations, and push-device settings. We do not currently add advertising pixels or a separate website analytics tool to Daye’s pages. A service feature can still use third-party storage or technical identifiers without being an advertising feature.

Daye sign-in cookie: access_token

Authenticates your website session and lets protected pages recognize your account. It is HttpOnly, uses SameSite=Lax, and is marked Secure in production.

Duration: Up to 12 hours. Logging out clears the cookie and revokes the Daye session.

Apple/Google/Firebase sign-in storage

Supports the provider sign-in you choose. Firebase may use IndexedDB, local storage, or other browser storage to maintain its authentication state separately from the Daye session.

Duration: Managed by the provider and browser; it can persist until sign-out, storage clearing, or provider expiration.

Push-device setting: daye_push_device_<account ID>

Remembers the non-secret Daye device-registration ID for the signed-in account so that you can manage push on this device. It is not an advertising identifier or the push token itself.

Duration: Local storage persists until removed by the app or cleared by you. Revoked registrations are no longer used for future Daye sends.

Family invitation: daye.pendingFamilyInvite

Keeps an invitation available in the same tab while you sign in or create an account, so you do not need to reopen the email.

Duration: Session storage normally ends when the tab closes. The app also rejects saved invitations after 7 days and clears them after successful acceptance.

A developer can explicitly enable a local animation-debug preference named daye:debug:reveal. It remains until cleared and is not a visitor analytics or advertising system.

2. Third-party services

If you use Apple or Google sign-in, display a Google map, or visit Stripe checkout, the relevant provider may use its own cookies, storage, and service identifiers. The exact names and lifetimes depend on the provider, your browser, and your existing provider-account settings. Hosting and security providers may also use technical controls to deliver and protect their services.

3. Your controls

Sign out to end your Daye session. Close the invitation tab or clear site data to remove locally saved invitation information.
Use your browser’s privacy settings to inspect, block, or remove cookies and site storage, including third-party cookies. Blocking necessary storage can prevent sign-in, invitations, maps, or other features from working correctly.
Manage push registrations in your dashboard and notification permission in your browser or phone settings. Clearing a browser’s site data is not a substitute for revoking a device registration from your account.
Manage Apple, Google, and Stripe choices with those providers. We do not offer an advertising-cookie or analytics-cookie toggle because we have not implemented those optional tools on Daye’s website.

4. Mobile app storage

The mobile apps also use app storage and operating-system services, which are different from website cookies. These can include provider sign-in state, installation identifiers, push settings, and protected active-trip credentials and queued driver locations. Clearing browser cookies does not necessarily remove mobile-app data. See the Privacy Policy and account-deletion information.

5. Changes and questions

If we introduce optional analytics or advertising technologies, we will update these disclosures and provide any choices or consent controls required before their use. The current policy does not treat using the site as permission for future optional tracking.

For questions, contact dayehealthtransport@yahoo.com.