Effective Date: August 4, 2026
This Privacy Policy explains how IE Uladzislau Luchkouski ("Developer," "we," "us," or "our") handles information when you use the Antigravity application on iOS or Android (the "App").
Antigravity connects a mobile device to a desktop development environment and related AI tooling. The App does not require a name, email address, or other traditional sign-in information. It uses an anonymous account and installation identifiers to provide its services. Those identifiers can still be personal data under applicable law.
1. Information We Handle
Anonymous account and installation identifiers
The App creates an anonymous Supabase authentication identifier and a random, stable installation identifier. We use them to pair the App with your desktop, restore eligible pairing and chat state, enforce usage limits, associate subscription entitlements, and protect access to your data.
The installation identifier is stored using platform-protected storage. On iOS, it may be synchronized through iCloud Keychain. On Android, it is stored in encrypted local preferences and may be restored through Google Block Store.
Chat, development, and command content
When you use Antigravity, the App may transmit and store content needed to perform your request, including:
- prompts, chat messages, AI responses, conversation history, reasoning, and status output;
- terminal input and output;
- file paths, file excerpts, edits, diffs, Git information, selected workspace or session identifiers, and other development context you choose to use; and
- custom prompts, instructions, or configuration you submit through the App.
This content travels through Supabase infrastructure so it can be synchronized with the connected desktop bridge. It may also be processed by the desktop development tool or AI service you choose to connect. Do not submit secrets or personal data that are not needed for your request.
Connection and operational data
We process pairing records, connection and presence state, heartbeat timestamps, selected project or chat state, message counts, free-tier usage, notification preferences, and technical request or error information needed to operate, secure, and troubleshoot the service.
Voice input
Voice input is optional and requires microphone permission. The App asks the operating system's speech-recognition service to turn speech into text. On-device recognition is preferred when available, but Apple or Android speech services may process audio remotely depending on the device, language, operating-system settings, and installed recognition service.
The App does not permanently store raw microphone audio on our servers. The resulting transcript becomes chat or command content if you choose to submit it.
Camera and QR pairing
Camera access is optional and is used to scan a desktop pairing QR code. QR frames are processed on the device using platform camera and barcode-recognition technology. The App does not upload or store camera frames for pairing. On Android, Google ML Kit does not receive the input QR image for this processing, but its SDK may collect application, device, installation, performance, and diagnostic metrics as described by Google.
Analytics, attribution, and diagnostics
In production builds, we use Firebase Analytics to understand App launches, feature interactions, onboarding and paywall flows, connection outcomes, and similar product usage. Analytics may include an anonymous account identifier, App version, platform, device or app-instance identifiers, language or region, install-referrer or campaign attribution, and event parameters describing the interaction.
We do not use Firebase Analytics to serve advertising or build an advertising profile. The Android App disables advertising-ID collection and ad-personalization signals. The App does not request Apple's advertising identifier for analytics. We may also receive crash reports and technical diagnostics through Firebase services where those services are enabled.
Feedback
If you submit written feedback, we store the feedback text, anonymous account identifier, App version, source screen, and submission time in Firebase Firestore. Sending feedback is optional.
Purchases and subscriptions
Purchases are processed by Apple App Store or Google Play, depending on your platform, and may be managed through RevenueCat. We may receive your anonymous App account identifier, product and transaction identifiers, purchase or entitlement status, expiration information, and limited diagnostic information needed to provide and restore paid features. We do not receive your complete payment-card number or bank-account credentials.
Push notifications
When push notifications are available and you enable them, we process a platform push registration identifier, installation and anonymous account identifiers, notification preferences, platform, and delivery environment so we can send the notifications you requested. You can disable notification permission in system settings and notification categories in the App.
2. How We Use Information
We use the information described above to:
- authenticate the App anonymously and connect it to your desktop environment;
- synchronize chats, commands, files, sessions, and tool output;
- provide speech input, QR pairing, notifications, purchases, and other requested features;
- restore eligible pairing, history, and entitlements;
- apply free-tier limits and prevent abuse;
- understand feature usage and attribution; and
- secure, maintain, diagnose, and improve the App.
3. When Information Is Disclosed
We do not sell or rent personal data, and we do not use it for third-party advertising. We disclose information only as needed to operate the App, respond to your directions, comply with law, or protect the App and its users. Relevant recipients can include:
- Supabase, for anonymous authentication, database storage, realtime synchronization, and server functions;
- Google and Firebase, for Android platform services, analytics, attribution, Firestore feedback, ML Kit diagnostics, optional notification delivery, and related infrastructure;
- Apple, for iOS platform services, optional speech recognition and notification delivery, iCloud Keychain synchronization, attribution, and App Store purchases;
- RevenueCat, where configured, for subscription offerings and entitlement management; and
- your connected desktop bridge and the development or AI tools you direct the App to use.
These providers process information under their own terms and privacy policies. Information may be processed in countries other than the one where you live.
4. Storage, Retention, and Security
Network communication uses encrypted transport such as HTTPS/TLS or secure realtime connections. We also use platform-protected storage and access controls intended to restrict data to the relevant anonymous account and paired bridge. No method of transmission or storage is completely secure.
Chat and operational records are retained for as long as needed to provide history, pairing, synchronization, security, and support, unless you delete them or request deletion. Feedback and diagnostics are retained for support and product-improvement needs. Purchase records are also retained by the applicable store and billing provider under their policies. Provider backups and security logs may persist for a limited period after deletion.
Because the installation identifier can use iCloud Keychain or Google Block Store, uninstalling the App may not remove that identifier from platform backup or synchronization systems.
5. Your Choices and Requests
You can:
- clear chat history or delete eligible conversations using controls available in the App;
- disconnect a paired desktop from the App;
- decline or revoke microphone, camera, and notification permissions in iOS or Android settings;
- disable notification categories in the App where available;
- choose not to submit feedback or use optional voice and camera features; and
- request access to or deletion of information associated with your anonymous account or installation by contacting us.
When contacting support about a data request, include enough App or pairing context for us to locate the relevant anonymous record. Do not send passwords, API keys, or other secrets. We may need to verify that the request relates to your installation or paired environment before acting on it.
Some locally stored data can also be removed by clearing the App's storage. Platform-synchronized identifiers and records held by Apple, Google, a purchase provider, your connected tool, or another service may require separate controls or requests to that provider.
6. Contact
For questions, privacy requests, or data deletion requests, contact us:
Support: support@luch.dev
Developer: IE Uladzislau Luchkouski
7. Changes to This Policy
We may update this Privacy Policy as the App or its service providers change. We will update the Effective Date above and provide any additional notice required by law.