Skip to main content
AtlasOrc
Legal

CookiePolicy

Last updated June 1, 2026

1. Quick version

AtlasOrc uses cookies and similar browser storage to keep users signed in, deliver checkout and downloads, remember referral attribution, prevent abuse, respect cookie choices, and understand site usage. We do not use cross-site advertising trackers.

2. What this policy covers

A cookie is a small piece of data stored by your browser. This policy also covers similar technologies such as localStorage, in-memory session identifiers, third-party checkout scripts, and security widgets when they support the same kinds of browser-side functions.

3. Essential cookies and storage

  • Supabase auth cookies - cookies with names such as sb-*maintain login sessions, refresh authentication, and protect dashboard, library, and admin access. These are cleared or rotated through the authentication flow.
  • Checkout and delivery state - short-lived browser and server state supports purchase creation, Razorpay order handoff, success pages, receipts, and signed download links.
  • Cookie consent - atlasorc_cookie_consent inlocalStorage records whether you accepted or rejected analytics capture.
  • Referral attribution - aorc_ref is a first-party cookie set for up to 30 days when a prospective seller arrives through a referral link. It is cleared after seller onboarding consumes it.
  • Admin interface preferences - dashboard/admin UI preferences such as sidebar state may be stored locally on your device.

4. Security and payment-related cookies

  • Razorpay Checkoutmay set cookies or use browser storage when you pay for a product or authenticate a seller Pro subscription. Those controls are governed by Razorpay's own checkout and security practices.
  • Cloudflare Turnstile may set cookies or use browser signals on flows where CAPTCHA/bot checks are enabled, such as free-product claims or login protection.
  • Rate limits and security logs use server-side request identifiers and headers to reduce fraud, scraping, and abuse.

5. Analytics cookies

  • ph_* and related PostHog localStorage entries help us understand page views, clicks, submits, and product usage. PostHog is configured with pseudonymous identifiers, redacted sensitive query parameters, and no email/name properties.
  • If PostHog is configured, analytics may start before a visitor makes a banner choice. Choosing Reject opts the browser out of further PostHog capture. Choosing Accept confirms analytics capture.

6. Chat assistant storage

The support chat may generate a temporary in-memory session ID so follow-up questions in the same chat window make sense. Chat messages are sent to AtlasOrc's chat API and, where configured, to the upstream assistant provider.

7. What we do not use

  • No Google Ads, Meta Ads, TikTok pixels, or cross-site advertising cookies.
  • No third-party ad retargeting cookies.
  • No sale of cookie-derived personal data.

8. How to control cookies

You can accept or reject analytics using the cookie banner on the public site. You can also clear or block cookies in your browser settings. Blocking essential cookies may prevent login, seller dashboards, admin screens, checkout, library access, downloads, and referral attribution from working. Blocking analytics cookies does not affect core marketplace functionality.

9. Changes

We update this page when we materially add, remove, or change cookies, browser storage, analytics, payment, or security tools.

Questions about this policy? Email us and we'll reply within 48 hours.