1. Scope
This policy explains the cookies and similar browser technologies used by dApps.tools. A cookie is a small value stored and sent with web requests. localStorage and sessionStorage remain in the browser and are not cookies, but they are described here because they can remember information.
dApps.tools does not currently use advertising cookies or cross-site behavioural tracking. Vercel Web Analytics is optional and does not rely on a third-party cookie, but it still sends a limited page-view record after consent.
2. Technologies used
| Name or pattern | Type | Purpose and contents | Duration | Status |
|---|---|---|---|---|
sb-<project-ref>-auth-token and possible chunks |
first-party cookie, managed with Supabase | authenticates and secures an account; contains encoded session/token information | until expiry, revocation, sign-out or account deletion, according to the applicable session settings | essential when you request account access |
sidebar_state |
first-party cookie | remembers whether the sidebar is open | 7 days | functional |
theme |
localStorage |
remembers light/dark appearance | until you clear it or browser data | functional |
dapps-tools-currency |
localStorage |
remembers display currency | until you clear it or browser data | functional |
dapps-tools:privacy-consent |
localStorage |
stores consent version, analytics choice, decision time and expiry | 12 months | necessary to remember your privacy choice |
dapps-tools:privacy-choice-saved |
sessionStorage |
remembers that the choice confirmation was shown | current tab/session | functional |
tool-draft-<userId>-<locale>-<tool> |
localStorage |
stores the contents of a tool-submission draft; the key contains the user identifier | until submitted, cleared in the interface or deleted through browser controls | functional, initiated by the user |
| temporary administration keys | sessionStorage |
preserves an administrative workflow state | current session | administrators only |
Authentication cookie names may be split into multiple chunks when necessary. Their exact names and technical values may change with the authentication library. The values must not be shared.
3. Optional Web Analytics
If you select “Enable analytics,” dApps.tools loads Vercel Web Analytics on an allowlist of public pages. It may process a timestamp, sanitized URL path, referrer, approximate location, operating system, browser, device type and script version. Query strings and fragments are removed, sensitive-looking slugs and private routes are blocked, and no custom events are currently permitted.
Vercel says that Web Analytics uses no third-party cookie, creates a request-derived session hash and discards the session identifier after 24 hours. Aggregate reporting data is kept for the reporting window associated with the dApps.tools plan and may be retained longer by Vercel to support an upgrade. The absence of a third-party cookie does not make the technology invisible: dApps.tools discloses it and keeps it off until consent.
4. Your choices
On a first visit, you may select “Enable analytics” or “Continue without analytics.” Declining does not block ordinary site access. You can change the choice at any time using “Privacy choices” in the footer. Withdrawing consent stops future Analytics loading; it does not undo reports already lawfully produced.
In the current implementation, a Global Privacy Control or Do Not Track signal keeps Analytics off. The choice itself is stored locally for 12 months so the site can respect it.
Browser settings can delete or block cookies and local storage. Blocking an authentication cookie prevents account login; deleting a theme, currency or draft merely resets that preference or removes the draft. Browser controls do not by themselves delete information already stored in a dApps.tools account; use the account controls or contact the Privacy Officer for that purpose.
5. Third-party destinations
dApps.tools links to independent tools, including possible affiliate destinations. A third party may use its own cookies, pixels, wallet connection or storage only after you visit or interact with that third party. Those technologies are controlled by the destination and are governed by its policy, not this one.
6. Changes and contact
This policy will be updated if dApps.tools introduces a new category of storage or tracking. A new consent will be requested before a materially different optional purpose is activated where required by law.
Questions and privacy requests may be sent to:
dApps.tools
Responsable de la protection des renseignements personnels / Privacy Officer
support@dapps.tools