What we hold, and what we never do.
Written from what the software does. Every claim below is checkable in the product, in the connector code we share under NDA, or in your browser’s own tools.
This website
valistry.ai counts its visits with Mixpanel: the page, where the visit came from, the city, region and country worked out from your address, and the device. A cookie holds a random id, and your choice is kept in your browser’s storage. In Europe and the UK nothing is counted until you accept; elsewhere it is counted until you decline. Change your choice any time with Cookie settings at the foot of every page. Vercel, which serves the site, also counts page views, without cookies or any identifier. There is no advertising pixel and no session recording.
When you give your work email to book a demo, leave a question or have the check mailed to you, we keep it and the question, and Mixpanel joins it to your visits so we know who asked. Your browser keeps it too, so the next form here is already filled. If you email us from a link on this site, we hold that email and your reply as you would expect any company to.
The product
Signing in sets a session cookie so you stay signed in, and one cookie remembering which organization you are looking at. Two more last a year: valistry_region holds your data region and is set before you sign in, HTTP only and secure; v-tz holds your time zone, readable by the page. Your browser also remembers whether you folded the navigation and which theme you chose. All of it is necessary for the product to work, and none of it follows you to another site. When an error happens, or a screen is opened, we record that it did, with nothing that says who you are.
We read
- What ran, and when
- From coding tools and code hosts: sessions, commits, edits accepted, limits hit, and each pull request's times, size, reviews and checks; file paths only as codes
- On which model
- How much it cost
- The identifiers needed to attribute it
- Who holds each AI seat, from each vendor's seat list
- The AI apps in a directory you connect: names and counts, never a sign-in
- The people in a directory you connect: name, work email, team, title, manager, and whether the account is active
- Three vendor settings, as on or off: OpenAI data retention, Bedrock call logging, how each app signs in
- Documents you list: a name, an owner, a review date and a link
- If you install the browser extension: read in the browser, it sends each day's count of messages to five AI sites and of visits to known AI sites, by domain, per person as a code
- If you install the desktop agent: read on the computer, which of three AI apps is in front and the seconds since the last key or mouse input. It sends minutes per app, per day, per person as a code, and the team you name
We do not keep
- Prompts and replies
- Conversations and transcripts
- The contents of documents
- Source code
This is how the record is built, not a setting: it has no field for content, and a test fails the build if one is added.
Every GitHub read holds files and text in memory and drops them. Coding reads are off until an owner or admin turns them on for chosen repositories. A coding session's steps are then read on the developer's computer, and a pull request's changed lines become codes during the sync. The text is dropped; only counts and codes reach the record.
A person on a coding seat is stored as a hash. People from a directory you connect are stored with name and work email, and a key named after a person keeps that name. Employee usage is reported at team level by default.
Service providers
- SupabaseHosts the database and the sign-in.
- VercelServes the site and the application, and counts visits to this site without cookies. Its logs can hold organization ids, some email addresses and rated questions.
- Amazon Web Services (Bedrock)Runs the model behind Ask Valistry, in your organization's country. It is given your question and names from your ledger, never a result. For a question about Valistry itself, it is also given text from our own pages. It never gets prompts or replies from your AI vendors.
- ResendSends the product's own mail, from the United States. It is given an address and the message. Messages can hold your organization name, spend figures, and model and team names.
- StripeTakes payment for a paid plan. It is given the billing contact and the card, which it holds; we never see the card number, and it is given no ledger row.
- Amazon Web Services (relay)Runs the fixed-IP relay, in Mumbai, for a LiteLLM proxy behind a firewall. Usage records pass through it on the way to the ledger and are not stored there; it keeps the method, host, status and duration of each call for one month.
- GoogleSigns you in if you choose Google. It is given your identity at sign-in.
- SentryRecords an error in the product so we can fix it. It is given where the error happened, with personal fields, organization ids, addresses and key-shaped strings removed. In the United States; kept 30 days.
- MixpanelCounts which screens of the product are used, in the United States. It is given a screen's name, timing, deploy and region. IP collection is off. On this website it counts visits, as the first section says.
Credentials you give a connector are encrypted before they are stored, and the product shows only their last four characters.
Your controls and requests
Ask
What we hold about you, and to have it corrected or deleted. Write to hello@valistry.ai.
Disconnect
Disconnecting a source stops the reading.
Delete
Deleting an organization deletes its records.
Data location
You choose the region when you create an organization: the United States (AWS us-east-1, Virginia) or India (AWS ap-south-1, Mumbai). Its database and its records stay in that region.
Sign-in lookups, error reports, screen counts, mail and some administration data go through the United States from both regions. Personal fields are removed from error reports. Ask's model runs in the organization's country. The company is registered in India and the site is served from Vercel’s edge.
Retention and deletion
Your records stay while your organization exists. Deleting the organization removes them from the active product at once, and residual backup copies are deleted within thirty days. Disconnecting a source stops new ones arriving.
The decision ledger is never edited, by design, so a decision is never rewritten. Deleting the organization removes the ledger with everything else, except one row of the change log: who deleted it, its id and when.
Deleting the organization does not delete your customer record at Stripe. Mail, error reports and screen counts already sent stay with those providers until their own retention ends.
Your rights
Wherever you are, you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. We answer within thirty days.
Under the GDPR that covers access, rectification, erasure, restriction, portability and objection, and you may complain to your supervisory authority. Under the CCPA and CPRA it covers knowing, deleting, correcting and opting out.
The opt-out is short here: we do not sell or share personal information, under any definition of either word. There is no advertising and no data broker.
Your ledger exports as CSV and JSON from the product, so portability needs no request.
Children
Valistry is sold to companies and is not for anyone under 16. We do not knowingly collect their data, and we delete it if we find it.
Changes
The date at the top moves when this notice changes. A change that affects what we collect or who processes it is emailed to account owners before it takes effect.
Reaching us
A question, a correction or a deletion request: hello@valistry.ai. A person reads it.
VedicSync Pvt Ltd, Bangalore, India. We have not appointed a data protection officer; that address reaches the people who decide.
How that is enforced, connector by connector.
Access, logging and least privilege, with the evidence for each.