Privacy Policy

We collect the following categories of information when you use the Service:

• Account information. We store your email address and display name. How we receive them depends on how you sign in: from Google or Microsoft when you use social sign-in, from your employer's identity provider when your organisation uses single sign-on, or from you directly when you set a password. A password is stored only as a hashed credential; a passkey is stored only as a public key, which cannot be used to sign in as you anywhere else.
• Two-factor secrets. If you turn on two-factor authentication, we store your authenticator secret encrypted, and your recovery codes only as hashes — never in a form we can read back.
• Workspace data. We store the workspaces and membership information you create or are added to.
• Dashboard and tool data. We store dashboards, configurations, connected tools, and query results you create within the Service.
• Chat history. We store messages and conversation history within the Service to provide continuity across sessions.
• Files you upload. We store images and documents you attach to a chat or discussion, and the text we extract from them so the assistant can answer questions about them.

• To authenticate you and manage your account across sessions.
• To operate the Service, including storing and retrieving your dashboards, tools, and chat history.
• To display your name and email within your workspace.
• To send transactional email you request, such as sign-in verification codes.

Your account and application data is stored using Google Firebase (Firestore, Firebase Authentication, and Cloud Storage for files you upload) within the us-central1 region.

We do not sell, rent, or share your personal information with third parties for their marketing purposes. We share data only with infrastructure providers necessary to operate the Service (Google Cloud, Firebase, our transactional-email provider, the analytics and error-reporting providers in the next section, and the AI providers described below) and only to the extent required to provide it.

We measure how the Service performs and where it fails so we can fix it. Two providers receive this data, and neither is used for advertising.

• Google Analytics receives page timings (how long pages take to load and respond), counts of errors, and which features are used. It runs without cookies and without a consent banner, because we deny it every consent signal — it cannot track you across sites. When you are signed in, we attach your account's internal identifier, an opaque string that only we can link to you, so that we can count active users without a cookie. It never receives your name, email address, page titles, or anything you type.
• Rollbar receives details of errors that occur in your browser while using the Service: the error message, where in our code it happened, which page pattern you were on, and your account's internal identifier. It does not receive your IP address, your clicks or keystrokes, page titles, or the content of the page.

Embedded dashboards send nothing to either provider. A page opened through public access sends nothing to Rollbar, and sends Google Analytics three anonymous counts — that a public page was opened, that Sign in was pressed, and that a link into the Service was pressed. These counts carry no account identifier, even when you are signed in, and never the address or the title of the page.

Account and workspace data is retained for as long as your account is active. You can delete your account yourself from Settings. Deletion is not immediate: the account is suspended straight away and permanently purged after 30 days, and you can cancel and restore it at any point in that window. After the purge, your data cannot be recovered.

Content that belongs to a shared workspace rather than to you personally — a comment in a team workspace, for example — stays with that workspace when your account is deleted.

How Vistazo itself stores your chats and dashboards is described under Data Retention above. To answer a request, Vistazo sends an AI provider the text you type, the contents of files you attach, and, for a chat inside a dashboard, that dashboard's name, description, notes, widget titles, and current parameter values. Chart data is sent only when the assistant reads it to answer your question. We currently use:

• Anthropic (Claude) produces chat answers and prepares chart data. It keeps your content for up to 30 days, may access it in that time for safety and security, and then deletes it. Content its automated systems flag can be kept for up to two years.
• Fireworks AI reads images you attach, and steps in for chat answers and chart data when Anthropic is unavailable. It holds your content in memory only, for minutes at most, and does not write it to storage. It logs usage counts, not content.
• Google (Gemini) handles helper tasks such as naming a chat and summarising long ones, and steps in for image reading when Fireworks is unavailable. Google stores your content only for a limited period for abuse detection, and does not publish how long.

Under our current account settings, none of these providers uses your content to train its models. Vistazo does not control how a provider handles your content once it is sent. We may add or change providers, and we will update this section when we do. If you connect your own provider account (your own API key), that provider handles your content under its agreement with you, not under our account settings.

When you connect BigQuery or Google Sheets, you sign in with your Google account and allow Vistazo to reach that service on your behalf.

• BigQuery. Vistazo runs the queries you or your assistant ask for in your own Google Cloud projects, and reads their results.
• Google Sheets. Vistazo reads the spreadsheets you point it at by URL. It cannot list or search your files, and it never changes a sheet.

We use what we read only to build and refresh your dashboards and to answer your requests. Query results and sheet contents that a chart shows are stored as part of that dashboard and shown to the people it is shared with. When the assistant reads them to answer you, they are sent to the AI providers listed above, only to produce that answer. We never use Google user data to train AI models, never sell it, and never use it for advertising.

The access Google grants is encrypted and held on our servers, never in your browser. Disconnecting the source in Settings deletes it, and you can also revoke Vistazo's access from your Google Account at any time.

Vistazo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The Service is not directed to children under 13. By using the Service, you confirm that you are at least 13 years old. If you believe a child under 13 has provided us with personal information, contact us at legal@vistazo.ai and we will delete the associated data promptly.

You may access, correct, or delete your personal data at any time.

• Deletion — delete your account from Settings, subject to the 30-day window described under Data Retention.
• Data export — download a copy of your account data from Settings, including your dashboards and chat history.
• Correction — edit your profile and workspace data in the Service, or email legal@vistazo.ai for anything you cannot change yourself.

If you would rather we act on your behalf, or you can no longer sign in, email legal@vistazo.ai from your registered account email. We respond to all requests within 30 days of receipt.

We may update this policy from time to time. When we do, we will revise the "last updated" date at the top of this page. Continued use of the Service after changes constitutes acceptance of the revised policy.

Questions or concerns? Email us at legal@vistazo.ai.