This policy describes how Anastig collects, uses, and protects information about account holders, the workspaces they create, and visitors to the public site.
1. What we collect
- Account data: email, name, hashed password, MFA status, organization name, country, industry, intended use, role, language preference.
- Workspace data: projects, images, labels, models, exports, members, audit events.
- Technical data: user agent summary, coarse IP-derived country, request timestamps, error fingerprints, browser device class.
- Usage data: which features you use, throttle counters, security events (failed logins, throttle hits, account changes).
- API credentials: for API keys you create, we store only a non-reversible hash and a short non-secret prefix (never the secret itself). You are responsible for keeping the secret confidential.
- Operational diagnostic events: to keep the service reliable we record redacted diagnostic events — a hashed user identifier, organization/project identifiers, a support reference, and redacted error details. Secrets, tokens, cookies, and raw filenames are stripped before storage; these are retained up to 90 days for incident response.
- Consent records: the version of the Terms, Privacy Policy, and Acceptable Use Policy you accepted, and when.
We do not knowingly collect precise GPS, payment-card numbers, government IDs, biometric identifiers, or special-category personal data. The contact form is optional.
2. Email verification
We send a confirmation email to every new account from [email protected]. The link contains a single-use verification token. Only the cryptographic hash of the token is stored. The link expires 60 minutes after we issue it.
3. Cookies and analytics
We use a first-party, HTTP-only session cookie for authentication and CSRF protection. We do not use third-party advertising cookies and do not set non-essential cookies.
We use Cloudflare Web Analytics, a privacy-preserving, cookieless measurement tool that runs on all pages to count aggregate page views and performance. It does not set cookies, does not use cross-site identifiers, and does not fingerprint you. Any other non-essential product analytics remain off unless you opt in.
4. Service providers we rely on
- Cloudflare — content delivery, DNS, TLS termination, web application firewall (WAF), and privacy-preserving web analytics. Cloudflare processes connection metadata (IP address, request headers, URL) to deliver and protect the service.
- Resend — sends transactional email from
[email protected]. - Zoho — inbound corporate mail for
[email protected]and[email protected]. - Object storage — your chosen S3-compatible bucket or our managed bucket for image and export storage.
We share the minimum data each provider needs to function. We do not sell personal information.
5. AI processing of your content
When you use server-assisted features (for example Vision Lab inference or auto-labeling), the images, video frames, and labels you submit are sent to our isolated GPU worker to run computer-vision models, and the results are returned to you. This processing happens only when you invoke such a feature. We do not use your workspace content to train models for other customers. Temporary processing artifacts (staged upload chunks, in-flight worker jobs) are ephemeral and removed after the job completes. Demo / local-only features run in your browser and are stored in your browser's session storage, not on our servers.
6. How long we keep it
- Active account data is kept while your account is active.
- Security event logs are retained for up to 24 months for incident response and audit.
- Email verification and password-reset tokens are deleted after use or 60 minutes.
- If you delete your account, we plan to keep the account in a frozen, isolated state for a 30-day recovery window, followed by up to 90 days of internal retention for legal/security purposes, before anonymization or deletion. Deactivation / deletion / recovery flows are partially implemented and will be completed in a follow-up release.
7. Your rights
You can access, correct, or delete your account data by writing to [email protected]. For data-protection-specific requests (export, restriction, objection), the same address routes to a human reviewer.
8. Security
Transport is encrypted (HTTPS). Passwords are hashed by Django's configured hasher. MFA secrets are encrypted at rest. Verification and reset tokens are stored as SHA-256 hashes only. Sensitive administrative actions are gated, audited, and require a reason string of record.
9. International transfers
We may process data outside your country to deliver the service. Where required, we rely on standard contractual clauses or equivalent safeguards. Operational draft pending legal review.
10. Changes
We will publish updates here with a new version date. Material changes will be highlighted in the app and emailed to active accounts before they take effect.
11. Contact
Privacy questions: [email protected]. Technical / product: [email protected].