Sartrix
← Back to Sartrix

Cookie Policy

Version information loading…

Sartrix keeps things simple: only strictly necessary technologies, no trackers, no consent banner needed.

1. Overview

This Cookie Policy describes the cookies and similar technologies used by Sartrix. The short version: we use only strictly necessary technologies — nothing for analytics, advertising, or cross-site tracking. Because no optional cookies exist, no cookie consent banner is required or shown.

2. What We Actually Use

Sartrix relies on the following technologies, all strictly necessary:

  • Sign-in token (local storage) — keeps you signed in on this device. Stored in your browser's local storage, sent only to our own API, and removed when you log out.
  • Draft state (local storage) — remembers your unsent Studio draft (selected tool, prompt) so you don't lose work between visits. Never leaves your device.
  • Social sign-in security cookie — a short-lived cookie set only during a Google/Apple/Facebook/Discord sign-in to protect against cross-site request forgery. It expires within minutes and holds no profile data.

3. What We Do NOT Use

  • No analytics cookies (no Google Analytics or similar).
  • No advertising or retargeting cookies.
  • No social media pixels or cross-site trackers.
  • No device fingerprinting.

4. Third-Party Pages

When you pay, you are redirected to Stripe's checkout pages on stripe.com, and when you use social sign-in you visit the provider's own pages (Google, Apple, Facebook, Discord). Those sites set their own cookies under their own policies — we do not control them, and they are not set on sartrix.net.

5. Managing These Technologies

Because everything we use is essential, there is nothing to opt out of while continuing to use the Service. You can clear your browser's local storage and cookies at any time — doing so signs you out and clears saved drafts. The "Cookie Settings" link in the footer summarizes this policy in-app.

6. Changes to This Policy

If we ever introduce optional cookies (for example, analytics), we will update this policy, bump its version, and — where legally required — introduce a consent mechanism that asks for your permission before any optional cookie is set.

7. Contact

Questions about this policy can be sent to our support email (see the Terms of Service, Section 1) or via the feedback form in the app.