xcode Cloud privacy
Updated 9 November 2026
Google sign-in
We use Google through Supabase Auth to identify your account. xcode Cloud requests your basic profile and email address. It does not request access to Gmail, Google Drive, contacts, or your Google password.
What is stored
When you enable cloud sync, your chat text and session metadata (title, project path, model, device name and timestamps) are uploaded to Supabase. Tool names and statuses are included. More detailed history can include bounded tool inputs and outputs, with known credential patterns redacted. Redaction is not a guarantee: do not put secrets in conversations that you sync. Private reasoning is excluded.
Who can read it
The application uses row-level security so signed-in users can access only their own account's records. It is not end-to-end encrypted. The service operator and infrastructure providers may access stored data in order to operate the service. Supabase stores the account and chat database; Vercel serves this website; Google provides sign-in.
Remote access
Remote control, when enabled, lets the same signed-in account send work to an explicitly allowed local session while xcode is running. Enabling cloud history alone does not grant remote execution. Do not share account access or authorization tokens.
Deletion and sign-out
You can delete uploaded chats in the history interface. This does not delete the local conversation on your computer. Signing out removes local cloud credentials but does not delete existing cloud records. To request account data deletion, contact the operator below. Infrastructure backups may retain data according to the providers' own retention policies.
Browser and local storage
The website stores the Supabase login session in browser storage. The CLI stores its cloud session in a private local file. You can sign out independently on each device. Operational logs may contain technical connection and error information.
Contact
Questions or deletion requests: thaneekaveeket51615@gmail.com.