Privacy policy

Customer data. When a customer sends prompts to Vindex, the customer decides what to send and why. For that data (prompt text, negative prompts, metadata, end-user ids, and the decisions, reviews and logs made from them) we are the customer's processor, and we handle it under our agreement with them, including our data processing agreement. If you use a platform that uses Vindex, that platform's privacy policy applies to you, and it is the right place to send questions and requests. We will help them answer.

Everything else. For account details, billing information, support conversations, security logs and visits to this website, we decide how the data is used, and this policy applies directly.

Data our customers send through the API

• The text of each prompt, and a negative prompt if one is sent.
• Optional metadata and an end-user id, if the customer chooses to send them. We ask customers to use pseudonymous ids rather than names or email addresses.
• What we produce from it: each check's scores, the decision, its explanation, tags, the policy version used, and the latency.
• What the customer's team does with it: review verdicts, rule runs and webhook deliveries.

Account data

• Your name, email address and workspace role, and the workspaces you belong to.
• If you sign in with Google, the name and email address Google shares with us. If you sign in by email, the address we send the link to.
• Policies, rules, webhook addresses and the other settings your team creates. Webhook secrets are stored for signing and never shown again.
• An audit log of changes made in the dashboard, including every reveal of a hidden prompt: who, which decision, and when.

Billing data

Card payments are handled by Stripe. We receive your Stripe customer id, plan, subscription status, invoice status and billing email. We never receive or store card numbers. We also count the decisions each workspace makes, to bill any overage.

Technical and security data

When you call the API, use the dashboard or visit this website, our hosting provider records request details such as time, IP address, browser or client, the API key prefix used and the response status. We use this to run, secure and debug the Service and to enforce rate limits.

When you contact us

If you email us, we keep your message and address so we can reply.

• Images or video. The API accepts text only, and nothing we store has a place for an image.
• Card numbers. Stripe collects them directly.
• Advertising or cross-site tracking data. We run no ad trackers.

• To screen prompts against the customer's policy and return, explain and log each decision. Prompt text is scored by our screening engine provider (see Sub-processors) at the moment of the check.
• To run what the customer set up: the review queue, rules, tags and webhooks.
• To create and secure accounts, sign you in, and send the emails the Service needs: sign-in links, invitations and notifications.
• To bill subscriptions and overage.
• To keep the Service secure and reliable, and to prevent and investigate abuse.
• To answer support requests. Our staff look at a customer's decisions only when that is needed to help them, to keep the Service secure, or to comply with the law.
• To understand how the Service is used, from aggregate numbers such as request counts and latency.
• To comply with legal obligations, such as keeping tax records.

We don't sell personal data, share it for advertising, or use customer prompts to train models.

Where European data protection law applies to data we control, we rely on:

• Contract: to provide the Service you signed up for, including your account and billing.
• Legitimate interests: to secure the Service, prevent abuse, answer questions and understand usage in aggregate. We balance these against your rights, and you can object.
• Legal obligation: to keep records the law requires, such as invoices.
• Consent, where the law requires it. You can withdraw it at any time.

For customer data, the customer is responsible for having a legal basis to send it to us.

This website sets no cookies of its own. We measure visits with Cloudflare Web Analytics, which counts page views without cookies and without following you across other sites.

The dashboard uses cookies that are strictly necessary: a session cookie that keeps you signed in, and short-lived cookies used during sign-in and setup. Cloudflare may also set strictly necessary cookies to protect the Service from attacks. We use no advertising or tracking cookies.

• Decisions, including prompt text and explanations, are kept for the customer's plan retention period: 7 days on Starter, 30 days on Growth and 1 year on Scale, or as agreed in an Enterprise contract. Then they are deleted.
• Prompts blocked by the minors check are kept for the same period, but their text is hidden everywhere in the dashboard and API. Only a workspace owner or admin can reveal one, and each reveal is written to the audit log.
• Account data is kept while the account is open. When a workspace is closed, its data is deleted within 30 days.
• Audit log entries, which record who did what and when but not prompt text, are kept after a workspace is deleted, for security and to show what happened.
• Billing records are kept for as long as tax and accounting law requires.
• Security logs are kept for a limited period and then deleted.

We use these sub-processors to run Vindex. Each is bound by a contract to protect the data and use it only to provide its service to us.

We email account owners before adding or replacing a sub-processor. We may also disclose data when the law requires it, to protect the rights and safety of people or the Service, or as part of a merger, acquisition or sale of assets, in which case this policy continues to apply to the data transferred.

Sqwark is based in the United States, and our sub-processors may process data in the United States and other countries. When we transfer personal data out of the EEA, the UK or Switzerland, we rely on the European Commission's Standard Contractual Clauses, with the UK Addendum and Swiss adjustments where they apply, or another lawful transfer mechanism.

Data is encrypted in transit and at rest. API keys are stored only as hashes. Webhooks are signed. Access inside a workspace follows roles, and access by our staff is limited to those who need it. Changes in the dashboard, and every reveal of a hidden prompt, are recorded in an audit log. No system is perfectly secure; if you find a weakness, please tell us at security@getvindex.com.

Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict how we use it, and to withdraw consent. To use any of these rights, email hello@getvindex.com. We will reply within the time the law allows, and may need to confirm who you are first.

If the data is customer data (for example, a prompt you typed into a platform that uses Vindex), please ask that platform. We will pass on any request we receive and help them respond.

Residents of California and other US states with privacy laws have similar rights. We don't sell personal information or share it for cross-context behavioural advertising, and we won't treat you differently for using your rights.

If you are in the EEA, the UK or Switzerland, you can also complain to your data protection authority. We'd appreciate the chance to help first.

The Service is for businesses and is not directed at anyone under 18. We don't knowingly collect personal data from children. Customer prompts can describe minors, because detecting and blocking that content is part of what Vindex does; that data is handled as customer data, under the protections described above.

If we make a material change, we will email account owners before it takes effect and update the date at the top of this page. Smaller changes, such as clarifications, are reflected in that date.

Sqwark Industries LLC, a Wyoming limited liability company, is responsible for this policy. Email hello@getvindex.com with any question about it or about your data.