BigDevSoon

Cookie policy

Updated

BigDevSoon uses cookies and browser storage to keep you signed in, save your work and remember privacy choices across bigdevsoon.me and app.bigdevsoon.me. You can use the service with all optional tracking switched off.

Storage used for features you request

Privacy preferences
A first-party cookie named bds_privacy remembers the notice version, your choices, their expiry and a receipt identifier across the public site and app. A saved choice lasts up to 180 days, or until you replace it or clear site data. The browser may temporarily keep a pending choice in session storage so it can finish saving it. The server can keep a separate receipt with a random identifier, the previous receipt reference when available, the categories, notice version and time. Receipts are scheduled for deletion after 365 days.
Account, authentication and payments
Supabase uses browser storage to maintain a signed-in session. The app also uses cookies for the GitHub sign-in and linked-account flow. Stripe may use its own cookies or device identifiers for checkout, secure payment and fraud prevention when you use billing features. Signing out ends your app session. A provider’s security or payment identifiers may have their own expiry.
Member invitation
If you choose Apply invitation, the app keeps the invite code in the current tab’s session storage through the GitHub sign-in redirect. After registration the app clears the code and can credit BigTokens to the inviting member. You can continue without applying an invitation. The separate affiliate program has a 90-day referral window. BigDevSoon does not use an external affiliate tracker for that program.
Work and display settings
The editor and public CV demo can use local storage to keep drafts and preferences between visits. The site also remembers choices such as dismissing a promotion. Session storage lasts for the tab session. Persistent local data can remain until you clear it, reset the feature or your browser removes it. Clearing site data can erase unsynced work.

Optional tracking on public marketing pages

Each category is off until you allow it. Your choices are independent, so you can allow traffic measurement while declining recordings and advertising. The app workspace, CV tools and these legal pages do not load the advertising or session-replay scripts.

Analytics · Umami
Umami measures which public pages people visit and which browsers, devices or referrers they use. Its analytics runs without setting a tracking cookie. We still ask for your permission before loading it. Umami analytics FAQ
Session replay · Microsoft Clarity
Clarity can record clicks, scrolling and page interactions to help us see where navigation breaks down. Its first-party cookies include _clck for a browser identifier (typically one year) and _clsk to group page views into a recording (typically one day). Microsoft may also use its own cookies. Microsoft’s Clarity cookie list
Marketing · Meta Pixel
Meta receives a public page-view event, browser and connection information, and advertising identifiers to measure our campaigns. Its tools can use _fbp and, where available, _fbc to recognize visits or connect them to an ad click. These cookies typically last three months. Meta may match data with a Facebook or Instagram account. Meta’s cookie policy

Changing your mind

Open Cookie settings, reject optional tracking or save the categories you want. Switching a category off stops future collection by that integration here. You may also clear site data in your browser, manage third-party cookies or enable Global Privacy Control, which we treat as an advertising opt-out. Repeat your choice if you use another browser or device. To request deletion of personal data already collected, contact the controller under our privacy policy.