Cookie Policy

Last updated:: 2026-07-25
Effective:: 2026-04-22

This Cookie Policy explains how Atlas Task Manager uses cookies and similar technologies. It supplements our Privacy Policy.

1. What are cookies?

Cookies are small text files stored on your device when you visit a website. "Similar technologies" include local storage, session storage, and pixel tags. We use them to keep you signed in, protect your session, and - with your permission - measure product usage.

2. Categories we use

Strictly necessary: required to deliver the Service (authentication, CSRF protection, session balancing). Always on. Cannot be turned off in our interfaces without breaking the Service.
Functional / preferences: remember your theme, language, and layout choices.
Analytics: if you consent, we collect aggregated, de-identified product-usage metrics to improve the Service.
Marketing: we do not use marketing or advertising cookies on the Service today.

3. Cookies and storage we set

Name	Purpose	Duration	Party	Category
`atlas_session`	Authenticated session token.	Session / up to 30 days if "remember me" is used.	First-party	Strictly necessary
`atlas_csrf`	Cross-site request forgery protection.	Session	First-party	Strictly necessary
`atlas_theme`	Remembers light/dark theme preference.	1 year	First-party	Functional
`atlas_consent`	Stores your cookie-consent choices.	12 months	First-party	Strictly necessary
`_analytics_id`	Aggregated product analytics (only if you consent).	12 months	Third-party	Analytics

4. Trackers we use and how consent is handled

This section explains the specific analytics and reliability tools we use and the lawful basis for each. For visitors in the EU/EEA and other regions that require prior consent, non-essential scripts are not loaded until you opt in.

Web analytics (analytics): used to understand aggregated, de-identified product usage. These are consent-gated through a consent-mode mechanism: analytics and advertising storage are set to "denied" by default, and no analytics cookies are written until you opt in. In the EU/EEA the analytics scripts are not loaded at all until you have given consent. Lawful basis: consent (GDPR Art. 6(1)(a)).
Product analytics (analytics): used to measure how features are used so we can improve them. It is configured to opt-out by default and does not capture events until you have consented. Lawful basis: consent (GDPR Art. 6(1)(a)).
Error monitoring (reliability): used for reliability and security to detect and diagnose crashes and errors. It is loaded as a strictly necessary reliability tool, applies PII masking to the data it captures, and does not set analytics or advertising cookies. Lawful basis: legitimate interests in keeping the Service secure and available (GDPR Art. 6(1)(f)).

You can change your analytics choices at any time from the in-app Privacy settings or by clearing your consent cookie. Withdrawing consent stops future analytics collection but does not affect processing already carried out.

5. Managing cookies

You can manage cookies through your browser settings. Blocking strictly necessary cookies will break sign-in and core features. Where we set optional cookies, we display a consent prompt on first visit and you can revisit your choices from the in-app Privacy settings.

6. Do Not Track & Global Privacy Control

We honor the Global Privacy Control (GPC) signal as a valid opt-out of "sale" and "sharing" under CPRA. There is no consensus industry standard for Do Not Track (DNT); we treat DNT as an informational signal and rely on explicit consent in regions that require it.

7. Changes

We may update this policy when cookie usage changes. The "Last updated" date at the top will reflect the revision.

8. Contact

Questions? hello@wrxstack.com.

2. Categories we use

Strictly necessary: required to deliver the Service (authentication, CSRF protection, session balancing). Always on. Cannot be turned off in our interfaces without breaking the Service.
Functional / preferences: remember your theme, language, and layout choices.
Analytics: if you consent, we collect aggregated, de-identified product-usage metrics to improve the Service.
Marketing: we do not use marketing or advertising cookies on the Service today.

3. Cookies and storage we set

Name	Purpose	Duration	Party	Category
`atlas_session`	Authenticated session token.	Session / up to 30 days if "remember me" is used.	First-party	Strictly necessary
`atlas_csrf`	Cross-site request forgery protection.	Session	First-party	Strictly necessary
`atlas_theme`	Remembers light/dark theme preference.	1 year	First-party	Functional
`atlas_consent`	Stores your cookie-consent choices.	12 months	First-party	Strictly necessary
`_analytics_id`	Aggregated product analytics (only if you consent).	12 months	Third-party	Analytics

4. Trackers we use and how consent is handled

Web analytics (analytics): used to understand aggregated, de-identified product usage. These are consent-gated through a consent-mode mechanism: analytics and advertising storage are set to "denied" by default, and no analytics cookies are written until you opt in. In the EU/EEA the analytics scripts are not loaded at all until you have given consent. Lawful basis: consent (GDPR Art. 6(1)(a)).
Product analytics (analytics): used to measure how features are used so we can improve them. It is configured to opt-out by default and does not capture events until you have consented. Lawful basis: consent (GDPR Art. 6(1)(a)).
Error monitoring (reliability): used for reliability and security to detect and diagnose crashes and errors. It is loaded as a strictly necessary reliability tool, applies PII masking to the data it captures, and does not set analytics or advertising cookies. Lawful basis: legitimate interests in keeping the Service secure and available (GDPR Art. 6(1)(f)).