Cookie Policy
Operational launch draft — subject to legal review before publication
Effective date: September 3, 2026
Last updated: September 3, 2026
This Cookie Policy explains how TOEVERYTHING PTE. LTD. ("TOEVERYTHING," "AFFiNE," "we," "us," or "our") uses cookies and similar technologies when you visit https://affine.pro and its related pages (the "Website"). It should be read with our Privacy Policy.
1. What these technologies are
Cookies are small text records stored by a browser. We also use browser local storage, session storage, pixels, tags, and comparable identifiers. First-party technologies are set from an AFFiNE domain. Third-party technologies are controlled by another provider and may allow that provider to recognize a browser across websites or services, subject to its own terms and settings.
2. How consent works
Strictly necessary storage is active because the Website cannot reliably remember security, privacy, or requested interface choices without it. Analytics and Marketing technologies are disabled by default and are loaded only after the relevant consent, except where applicable law permits otherwise.
The consent banner lets you accept all optional categories, reject non-essential technologies, or choose categories. You can reopen the manager through Manage preferences in the Website footer. Rejecting optional technologies does not prevent ordinary access to the Website, although measurement or personalized campaign functions may be unavailable.
3. Current first-party inventory
The table below describes first-party browser storage intentionally used by the current Website code. Actual values do not contain payment-card details.
| Name | Storage and category | Purpose | Typical duration |
|---|---|---|---|
affine_consent | Cookie — Necessary | Records the consent categories you selected so the banner and vendor gates can honor that choice. | 365 days |
affine.last-locale | Local storage — Necessary preference | Remembers a language you explicitly selected. It does not trigger an automatic language redirect. | Until removed in browser settings |
vueuse-color-scheme | Local storage — Necessary preference | Remembers or applies the Website color preference. | Until removed in browser settings |
mobile-sticky-cta-dismissed | Session storage — Necessary interface state | Remembers that a mobile call-to-action was dismissed for the current browser session. | Until the browser session ends |
affine_attribution | Cookie and local storage — Analytics | Preserves first- and last-touch campaign parameters, referrer domain, and landing path. It is created only after Analytics consent and is cleared when Analytics consent is withdrawn. | 90 days |
dub_id | Cookie — Marketing | Identifies a consented Dub affiliate click so an eligible Web Stripe purchase may be attributed. On AFFiNE production hosts it is scoped to .affine.pro; local and preview hosts use a host-only cookie. | 90 days |
dub_partner_data | Cookie — Marketing | May be set by Dub for partner attribution data when its click response includes partner information, even though AFFiNE does not enable direct discounts or partner promotion codes in Phase 1. On production it follows the configured .affine.pro scope; local and preview hosts remain host-only. | Configured by Dub; subject to Dub's current cookie settings |
_fprom* | Cookie — Marketing | Legacy FirstPromoter affiliate attribution when FirstPromoter is the selected provider. | Provider-controlled; cleared on Marketing withdrawal where accessible |
The Website enables exactly one affiliate provider at a time: FirstPromoter or Dub, or neither. It does not intentionally run both for the same visit. The consent code attempts to delete host-only and .affine.pro copies of both Dub cookies on rejection or withdrawal.
4. Analytics providers
Analytics technologies help us understand traffic, product-interest patterns, and Website performance. They run only after Analytics consent.
| Provider | Current use | Example browser identifiers cleared or controlled by the Website |
|---|---|---|
| PostHog | Event and product analytics. Autocapture and session recording are disabled in the current Website setup; the client starts opted out and is enabled only after consent. | ph_*, mp_*, and PostHog local storage or cookie identity |
| Google Analytics through Google Tag Manager | Page and campaign measurement. | _ga*, _gid |
| Microsoft Clarity | Usage measurement and session replay with form inputs and designated sensitive fields masked. | _clck*, _clsk*, CLID, MUID |
Provider scripts may create additional identifiers or change their names. Their own retention settings and policies may also apply.
5. Advertising and affiliate providers
Marketing technologies help measure advertising and affiliate referrals. They run only after Marketing consent.
| Provider | Current use | Example identifiers |
|---|---|---|
| Google Ads through Google Tag Manager | Advertising conversion and campaign measurement. | _gcl_* |
| DoubleClick | Google advertising measurement where enabled through the tag configuration. | IDE |
| Meta Pixel through Google Tag Manager | Advertising conversion and campaign measurement. | _fbp, _fbc, fr |
| Dub | Affiliate click attribution through refer.affine.pro; eligible purchases are reconciled with Web Stripe records. | dub_id, and dub_partner_data when returned by Dub |
| FirstPromoter | Legacy affiliate attribution when it is the selected provider instead of Dub. | _fprom* |
Google Tag Manager is a tag delivery mechanism. Which Google Analytics, Google Ads, DoubleClick, or Meta tags actually run also depends on our container configuration and the consent signals sent to those tags.
6. Attribution and cross-domain use
AFFiNE's Website and web application use related hosts under affine.pro. Where consent is granted, a parent-domain cookie may be used so a referral or analytics identifier can survive navigation from the marketing Website to the Web Stripe checkout flow. Browser settings, ad blockers, cookie deletion, private browsing, or changing devices may prevent this attribution.
The affine_attribution record stores campaign parameters and referrer domain, not the full referring URL or payment details. The Website transmits analytics attribution to PostHog and the data layer only after Analytics consent. Dub attribution is separately controlled by Marketing consent.
7. Withdrawing consent and deletion limits
You may withdraw optional consent at any time through Manage preferences. Withdrawal prevents future optional loading and our code attempts to remove known first-party or parent-domain identifiers for the withdrawn category. For Dub, this includes both host-only and .affine.pro copies of dub_id and defensive cleanup of dub_partner_data.
Withdrawal does not retroactively delete information already transmitted with prior consent. It also may not remove every identifier held in third-party storage or on another provider's domain, and browser restrictions can prevent a deletion attempt. You may need to clear site data in your browser or use the provider's own privacy controls. Removing a script element does not undo code that already ran; reloading the page after changing preferences gives the browser the cleanest new state.
8. Browser controls
Most browsers let you review, block, or delete cookies and site storage. Blocking all storage may prevent preference or consent records from working. Browser documentation explains the controls available in that browser.
9. Updates to this policy
We may update this Cookie Policy when our technology, providers, legal obligations, or practices change. The effective and last-updated dates above identify the current version. Material changes may also be communicated through the Website or consent manager where appropriate.
10. Contact
Questions about this Cookie Policy may be sent to contact@toeverything.info.
TOEVERYTHING PTE. LTD.
2 Havelock Rd
Singapore 059763
Singapore