Legal
Privacy Policy
Last updated: 11 November 2026
Bytos is an open-source VS Code extension and this website is its home. This page explains what the website, the optional Bytos Account, and the Bytos API process, why we process it, and how to remove it. The extension sends model requests only to the provider you configure. If you explicitly select a Bytos-hosted provider, requests go to the Bytos API.
1. Data we process
You can use the website and the extension without an account. The Bytos Account is optional. If you create one, we process your email address, a Supabase Auth record, the profile fields you enter (first name, last name, optional username), and account/session metadata. Your password is hashed by Supabase and never reaches us. Google or GitHub process your sign-in only when you choose that provider.
The extension processes the files, tasks, prompts, and provider credentials you give it so it can perform the work you request. Provider API keys are stored in the editor's secret storage. Model requests go directly to the provider you select; we do not receive them unless you explicitly select a Bytos-hosted provider. Our host keeps standard request logs (IP address, user agent, URL, time) for security. Analytics, when enabled, is cookieless and aggregated. We never sell data or run ad trackers.
2. Cookies and local storage
No advertising cookies are set. Browser storage is used only for:
| Name | Purpose | Lifetime |
|---|---|---|
bytos.auth | Keeps you signed in (Supabase Auth). | Until sign-out or expiry |
bytos.lang | Remembers your language. | Until you clear it |
bytos.extension.handoff | PKCE hand-off for VS Code sign-in. | 10 minutes |
bytos.404.best | Best score in the 404 game. | Until you clear it |
3. Service providers
We share the minimum with Supabase (authentication and profiles), Google or GitHub (only if you choose OAuth), Cloudflare (hosting, security, and optional cookieless analytics), the Bytos API (account, usage, and remote-configuration requests when you are signed in), GitHub Releases (release downloads), and the model or MCP providers you configure. Those providers process data under their own terms and privacy policies.
4. Retention and security
Account and profile data stay while your account exists. When you delete your account, the Supabase Auth user, profile row, active sessions, and refresh tokens are deleted immediately. Backup copies may persist for a limited period under the hosting provider's retention policy; backups are not used to restore deleted accounts. Server logs rotate under the hosting provider's retention policy. Sign-in hand-off tokens expire within 10 minutes. Profile rows use row-level security, and the website never stores passwords or logs tokens.
Supabase issues short-lived access tokens and rotating refresh tokens. Access tokens can remain technically valid until they expire even after an account is deleted, so account deletion also removes the auth user that every Bytos API request is checked against.
5. Your rights
You can access, correct, export or delete your data at any time. Signed-in users can edit their profile and permanently delete their account on the account page. Account deletion requires your email address, the word DELETE, and a recent reauthentication. Contact us for anything else.
6. Children and changes
Bytos is a developer tool and is not directed at children under 16. If this policy changes materially we update the date above.
7. Contact
Controller: the Bytos project. Privacy and deletion requests: [email protected]. The current legal entity and registered address are available from that contact. Security reports: GitHub Security Advisories.
This policy describes the current implementation and is not a claim of certification or of GDPR compliance.