Privacy Policy
Your account. Your choices.
How OpenVegas handles account information, terminal requests and optional analytics.
Who this covers
This policy covers OpenVegas at openvegas.ai, app.openvegas.ai and its terminal integrations. Updated October 31, 2026. For privacy questions or requests, email [email protected].
Google sign-in and account information
- Google sign-in provides your Google account identifier, email address, name and profile picture when available. We use this information to create or identify your OpenVegas account and maintain sign-in.
- We do not request access to your Gmail, Drive, contacts or calendar. Google profile information is not sold or licensed as a research dataset or used to train a general-purpose AI model.
- Supabase processes authentication and stores account records. Session credentials connect your browser or approved terminal to that account. Keep connection codes and credentials private.
Your terminal conversation
- In host billing mode, the coding host manages its own inference. OpenVegas is not a shared conversation-memory service.
- When you choose supported $V-funded inference, the host sends the context needed for that request through OpenVegas to the selected AI provider. This can include messages, code, attachments and tool results.
- The native billing adapter processes that content to forward the response; its accounting records retain identifiers, token counts, costs and transaction state, not a replayable conversation. Your coding host retains its own session history. Provider retention is governed by the provider's terms and settings.
- Other explicitly used chat or research features may store their own records. This native-adapter statement is not a promise that every OpenVegas feature or historical backup is content-free.
Payments, games and operations
- We retain wallet transactions, game actions and outcomes, agent budgets, payment references and authorization records to operate the service, reconcile balances, prevent abuse and resolve disputes.
- Stripe processes payment details. OpenVegas uses payment references and limited billing information; raw card credentials are not given to coding agents.
- Hosting, database and security providers process operational information such as request timing, error categories and network identifiers. Google Fonts may receive normal network request information when fonts load.
- Research or data-partnership delivery requires separate purpose-specific rights and review. Connecting your terminal does not by itself authorize sale of private conversations or code.
Optional analytics
PostHog analytics and masked browser replay have separate controls and are off until you choose them. Replay excludes sensitive pages and masks inputs and private text. It does not record your terminal screen. Separate product analytics can collect fixed feature/action counts with a temporary random identifier, not prompts or code. Use the page's analytics controls to withdraw optional consent. Essential authentication and security records are separate.
Retention, sharing and your choices
- We retain records for the account or service purpose, security, reconciliation and applicable legal obligations. Deletion may not immediately remove required transaction records or backup copies.
- Information is processed by service providers to deliver these functions and may be disclosed when legally required or necessary to protect accounts and the service. Provider processing may occur outside your country.
- Contact us to request access, correction or deletion, subject to identity verification and applicable law. Revoke Google access in your Google Account's third-party connections; this does not itself delete your OpenVegas account or past transaction records.
- Use the terminal logout control to revoke its connection. Do not include passwords, API keys or payment details in a support email.
- Material changes will be dated here. New uses of Google data require appropriate notice and consent. OpenVegas is not intended for children.