Cookie Policy

Essential and security technologies

Dock uses technologies necessary to provide requested functionality or protect the Services, including login and sessions, authentication, CSRF protection, consent preferences, verification flows, authorized profile editing, checkout, billing, fraud and abuse prevention, rate limiting, account and API security, and service reliability.

Blocking these technologies in your browser may cause parts of Dock to stop working.

Preference technologies

Dock may use browser storage to remember non-essential interface and dashboard preferences such as sidebar state, display choices, dismissed notices, or temporary draft state. Where required, optional preferences follow Dock's consent controls.

Analytics technologies

Dock may use optional analytics technologies to understand product usage and performance, including route activity, device/browser categories, coarse country, referrer, campaign parameters, load timing, engagement, and aggregate product trends.

Where consent is required, Dock does not intentionally set or read optional analytics identifiers before the required choice is made. Dock may also use server logs, security telemetry, and limited cookie-less measurements where permitted for operation, security, debugging, reliability, or aggregate measurement.

Security and device context

Dock may use first-party cookies, protected identifiers, signed tokens, or similar technologies for account security, fraud prevention, abuse prevention, verification integrity, rate limiting, and enforcement of security restrictions.

A device or browser signal available for first-party security is not automatically available for a customer-facing detection result. That separate use must independently satisfy Dock's technical controls, applicable law, and applicable platform rules.

Dock may use session cookies, CSRF cookies, consent-preference cookies, optional analytics identifiers, first-party security or device-context cookies, verification-flow cookies, and local or session storage for dashboard state and temporary UI data.

Actual names and durations may change as the implementation changes. This Policy does not promise a particular cookie name, browser attribute, or lifetime unless Dock expressly identifies it as a fixed public commitment.

Dock relies on providers including Discord, Roblox, Stripe, Cloudflare, hosting, storage, monitoring, and other infrastructure services. Those providers may receive technical information such as IP address, user-agent, request metadata, payment metadata, or platform information as reasonably necessary for their role.

When you ask Dock to perform an integration with another platform, that platform's own technologies, terms, and privacy practices may also apply.

Where Dock provides a consent or preference center, it may allow you to accept or reject optional technologies and manage available categories.

Rejecting optional technologies does not disable lawful technologies required for authentication, security, fraud prevention, billing, authorization, or another necessary service purpose.

If you withdraw an optional choice, Dock will apply the new choice going forward and, where technically and legally required, stop using or remove the associated optional browser identifier. Dock does not intentionally recreate a rejected optional identifier through covert fingerprinting or similar workarounds.

You may also use browser controls to block or remove cookies, although doing so may prevent some Dock features from working. You can reopen Cookie Preferences where available.

Where applicable law requires Dock to recognize a supported browser-based universal opt-out or privacy preference signal, Dock will apply the signal to covered processing.

Such a signal does not disable authentication, security, fraud-prevention, billing, or service-operation technologies that remain lawful and necessary for their separate purpose.

Browser technologies may expire at the end of a session, after a fixed period, when replaced, or when cleared by the user or browser.

Related server-side records may follow different retention periods based on their documented operational, security, billing, consent, fraud-prevention, or legal purpose. Backups may retain related information until normal protected backup rotation completes.

Dock may update this Policy as its technologies or legal obligations change.

Privacy questions: [email protected]
Legal notices: [email protected]
Support: Dock support server