Privacy
Notice

Effective 28 September 2026.

What we collect

• Account details you enter at sign-up: name, email, optional company name, number of seats, the AI tools you plan to use, an optional use-case note, and your acceptance of the terms.
• Billing references: Stripe processes your payment. We keep the Stripe customer and subscription references and payment status needed to confirm your plan. We never receive or store full card numbers.
• Keys and devices: your SGT key and your account access token are stored only as one-way hashes. When the software activates, it sends a random device identifier, which we store only as a hash to enforce the one-device-per-seat limit.
• Hosted retrieval requests: when SGT Fleet looks up task procedures, it sends the short task description and the role name. We use them to answer the request. They are not written to our database or access logs; usage counting for the five-hour window is held in server memory only and is lost when the server restarts.
• Education requests: if you apply for education access, your name, email and stated role, and the review outcome.
• Sign in with Google: if you choose it, Google tells us your name, your email address and that Google has verified it. We do not receive your Google password or access to your Google account.
• Update emails: when you sign up you receive occasional SGT Fleet update emails unless you tick "No thanks". We keep whether you are subscribed, and a record of emails we sent you. Every email has an unsubscribe link; unsubscribing takes effect immediately.
• Support requests: messages you send through the support form and our replies.
• Technical data: our web server keeps short rolling access logs (IP address, time, requested page, browser identifier) for security and troubleshooting, and IP addresses are used briefly in memory for rate limiting.

What we do not collect

• Your source code, project files or model outputs. SGT Fleet runs on your computer.
• Credentials for Codex, Claude Code, Ollama, DeepSeek or JEV. They stay on your computer and are never sent to SGT.

Essential browser storage

Some SGT Fleet features rely on browser storage to work. The items below are feature-specific rather than site-wide, and they serve onboarding continuity and sign-in security.

Starting onboarding stores an onboarding ID and an access token in browser sessionStorage. The success page reads that stored ID and token so it can continue the flow.

Signing in to the account area sets an authentication cookie with a one-hour Max-Age.

Starting Google sign-in sets a temporary OAuth-state cookie with a 15-minute Max-Age, used to complete that sign-in.

Administrator sign-in sets a separate sign-in cookie with a 30-day Max-Age.

Why we use it

To provide the service you subscribed to (contract), to bill and keep required business records (legal obligation), and to keep the service secure and within fair-use limits (legitimate interest). We send SGT Fleet update emails based on your sign-up and your right to decline or unsubscribe at any time (legitimate interest and, where required, consent). We do not sell personal data and do not share it for anyone else's advertising.

Who receives it

Stripe, Inc. (payments) and our hosting provider (servers located in Germany). Data may be processed in the United States, where DreamSleepAI, Inc. is incorporated. We may disclose data if the law requires it.

How long we keep it

Account and billing records are kept while your account is active and afterwards as long as tax and accounting law requires. Revoked keys are kept as hashes to prevent reuse. Web access logs rotate automatically and are overwritten.

Your choices and rights

You can cancel your subscription at any time from the billing portal. Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict processing, and to complain to your data-protection authority. To make a request, contact DreamSleepAI, Inc. through dreamsleepai.com ↗; we will verify that the request comes from the account owner before acting on it.

Changes

We will post any change to this notice on this page and update the effective date. See also the Terms of Service.