Trust and privacy
Privacy Notice
This notice explains what DontStay processes when you visit our website, sign in, pair a device, or use the service. Our product is designed to keep account identity separate from device trust and local agent permissions.
Last updated: 23 August 2026
Who operates DontStay
DontStay is the service described at this website. For privacy questions, access requests, or deletion requests, contact alpha@dontstay.ai.
Data we process
Depending on the features you use, we may process:
- account identity data supplied by Google, GitHub, or Apple, such as provider account ID, name, email address, profile image, and sign-in timestamps;
- device and connection metadata, including a device label, operating system, app version, pairing state, and security events;
- service activity you choose to sync, such as project and run identifiers, task status, approvals, and result metadata;
- support messages and feedback you send to us; and
- technical logs such as IP address, browser or app type, request time, errors, and abuse-prevention signals.
Google sign-in
Google sign-in does not give DontStay access to Gmail messages, Google Drive, Google Calendar, or your Google password. We request only basic identity scopes needed to authenticate you: OpenID, email, and profile.
A successful login identifies an account. It does not grant control of a Mac, repository, coding agent, group, or worker. Those permissions require a separate cryptographic device-enrollment and authorization flow.
How we use data
We use data to authenticate accounts, maintain sessions, pair and secure devices, provide the features you request, prevent abuse, diagnose failures, answer support requests, comply with law, and improve reliability. We do not sell personal data or use account identity data for third-party advertising.
Service providers
We may use infrastructure and authentication providers such as Supabase, Railway, Google, GitHub, and Apple. If you ask DontStay to send a task to a selected AI or coding provider, the content you submit is also governed by that provider’s terms and privacy notice. Providers receive only the data needed for their role.
Local-first boundaries
DontStay is designed so that coding-provider credentials and local workspace access remain on devices you control. Authentication data and the minimum metadata required for account, collaboration, security, and synchronization may be processed by hosted services. We document material changes to these boundaries before enabling them.
Retention and security
We retain account and service data while your account is active and as reasonably necessary for security, backups, dispute resolution, and legal obligations. Retention periods vary by data type. We apply access controls, encrypted transport, secret-management practices, logging minimization, and separate account and device authorization boundaries. No service can guarantee absolute security.
Your choices and rights
You can sign out, disconnect supported identity providers, or request access, correction, export, or deletion of your personal data. Until an in-product deletion control is available, email alpha@dontstay.ai from the address associated with your account. We may need to verify the request and may retain limited records when required by law or security needs.
You can also revoke DontStay access from your Google, GitHub, or Apple account settings. Revoking a provider does not automatically delete the DontStay account.
Cookies and sessions
We use session cookies or equivalent secure storage to keep you signed in, protect login flows, and prevent abuse. We do not require advertising cookies for authentication. Browser and app controls can remove local session data, but doing so may sign you out.
Children and changes
DontStay is not directed to children under 16, and we do not knowingly collect their personal data.
We may update this notice as the service evolves. We will update the date above and provide additional notice when a change materially affects how personal data is used.