Cookie Policy

Dint+ Inc. uses cookies, local and session storage, browser databases, SDKs, and similar technologies for the functions described here. Essential storage supports features you request. Optional website analytics and Crisp chat are off until you choose them. Use Cookie preferences at any time to reject optional tools or change your choices.

dint_auth_session: first-party HttpOnly authentication cookie, used for signed-in access; expires with the refresh session, with a maximum of seven days. Signing out clears it. Security and password-recovery cookies support the corresponding requested flow. dint_legal_agreement is a first-party HttpOnly cookie lasting up to one day after an explicit pre-account agreement, used to associate that agreement with signup or guest checkout.

dint.theme and the legacy dint-theme-mode: first-party local storage for the selected display mode, retained until cleared or replaced. Feature-specific local or session storage holds drafts, installation or device state, booking selections, and messaging state; browser databases can store encrypted messaging keys and local message state. Clear these in browser settings, recognizing that this can remove drafts or affect access to messages.

dint.cookie-preferences.v1: first-party local storage recording optional-tool choices and the choice date for up to 180 days. It is used only to apply those preferences. Essential security tools include Cloudflare Turnstile where configured for protected authentication actions. Stripe scripts and embedded payment controls load for requested payment setup and processing; their storage and fraud controls depend on the processor and flow.

dint.website-analytics.session.v1: first-party session storage with a random analytics session identifier and referrer category; 30-minute inactivity window, ending when session storage is cleared. dint.website-analytics.queue.v1: session storage of pending analytics events, retried for up to 24 hours. Both require analytics consent and are cleared on withdrawal. Video-view analytics use dint.anonymousViewerId in local storage after analytics consent, retained until cleared; withdrawing analytics clears that identifier.

Website product-event adapters can send to an already configured Google Analytics or Plausible integration only after analytics consent. Their presence as adapters does not mean either vendor is currently installed. No marketing-pixel loader was identified in this website. Do Not Track or Global Privacy Control disables optional analytics even if a prior choice allowed it.

Crisp’s chat SDK loads only after you enable support chat. It can use session identifiers and conversation storage to operate the widget. The provider determines its own storage lifetimes; this website does not set a fixed duration for those identifiers. Rejecting chat keeps its SDK from loading. Withdrawing chat permission reloads the page to stop the previously loaded SDK. To remove existing vendor storage, use browser site-data controls; consent withdrawal alone does not erase a prior support conversation. Email support remains available.

dint.referral_attribution is a first-party cookie storing the supplied referral attribution token for up to 14 days. It supports remembering and applying an invitation across signup; it does not establish campaign eligibility. Optional attribution storage requires analytics consent. Without that choice, you can use the invitation or referral code explicitly through the supported flow.

Accept optional, Reject optional, and Save choices are available in Cookie preferences. You can change choices at any time; rejecting optional tools does not prevent core sign-in or transactions. If browser storage is unavailable, optional tools default off on the next page load. Browser settings can clear or block cookies and other storage, but blocking essential storage can affect requested services.

Web cookie preferences apply to this browser. Native iOS and Android permissions and SDK settings are separate; use the app and operating-system controls for location, contacts, calendar, microphone, camera, photos, and notifications. Contact Privacy requests for account-level rights or questions about native app processing.

The version, last updated date, effective date, and change summary appear with this document. Material changes require appropriate notice and renewed agreement where required before the affected activity continues. A new notice is not retroactive permission for a different use of your information. Contact Dint+ Inc. through the linked contact and request pages.