Privacy Policy

1. Who we are and what this policy covers

This policy explains what personal information Data Visions collects, why, who we share it with, and the choices you have. “Data Visions”, “we” and “us” mean Data Visions Inc., 2002 Stone Canyon Drive, St. George, Utah 84790, USA.

It covers:

• The website at datavisions.ai.
• The Data Visions platform: the web app at app.datavisions.ai, its API at api.datavisions.ai, and our desktop and mobile apps.
• The connector for AI assistants, which lets an assistant such as Claude work in your Data Visions workspace when you sign in and allow it.

Most information in the platform belongs to the business that subscribes to it (our customer), not to us. Section 6 explains how that works. If your employer gave you a Data Visions account, your employer's own privacy notice also applies.

2. Information we collect

We collect what you or your organization give us, and a small amount of activity and device information as you use the service.

The website datavisions.ai does not use analytics or advertising cookies, and its forms do not currently send us anything. Payments are handled by Stripe. When your organization adds a card or bank account, you enter it on Stripe's page and Stripe keeps it; we never see or store full card or bank numbers, only a label such as the card brand and last four digits.

3. How we use information

We use information to run the service your organization subscribed to, keep it secure, and support it. We do not sell personal information or use it for advertising.

• Provide the service: sign you in, show you your workspace, run the apps and AI features you use, and send the emails and notifications your workspace sets up.
• Keep it secure: enforce two-factor sign-in, lock accounts after repeated failed attempts, detect misuse, scan uploaded files for viruses, and keep an audit log your administrator can review.
• Support you: answer support cases, including any screen recording you send us.
• Bill your organization: count active users and AI use per workspace.
• Improve the service: see which screens are slow and which features are used, from activity counts rather than the content of your records.
• Meet legal obligations: respond to lawful requests and enforce our terms.

4. AI features inside Data Visions

When you use an AI feature, the part of your request and workspace data that feature needs is sent to an AI model provider to produce the answer. We do not use your workspace content or AI conversations to train AI models, and our providers' business terms do not allow them to either.

• Providers: Anthropic (Claude), Google (Gemini, through Google Cloud Vertex AI), OpenAI and xAI. Your workspace administrator chooses which models its features use.
• Your organization's own keys: a workspace can use its own AI provider account. Its AI then runs only on that account, under the workspace's agreement with that provider.
• Region: a workspace can choose to keep Google AI processing in the US or the EU.
• What we keep: each AI conversation inside Data Visions (your question, the answer and the steps taken) is stored in your workspace's records so you and your administrator can review it. Section 9 says for how long.
• Screen recordings you send to support are transcribed and summarized by Google Gemini on our own Google Cloud account. It is told to hide passwords it sees.

5. Connecting an AI assistant such as Claude

The Data Visions connector lets an AI assistant you use, such as Claude, read and work with your Data Visions workspace as you, with no more access than you have yourself.

How you connect. You add the connector in your assistant and sign in on a Data Visions page, with two-factor if your workspace requires it. The assistant never sees your password. A consent screen lists what the connection may do before you allow it.

What the assistant can see and do.

• Only the one workspace you are working in. If you belong to several, it can move between them only when you ask it to.
• Only what your role allows: the same apps, records and actions you have in Data Visions.
• Changes to records only if your workspace allows them, you agreed to them on the consent screen, and your role permits them. Workspace administrators can also have it build and deploy apps into their own workspace.

Administrator controls. Your workspace administrator can turn connected assistants off, allow reading only (the default), or allow reading and changes. A change takes effect on the assistant's next action.

Ending a connection. You can disconnect in your assistant, or ask your administrator to revoke it. A revoked connection stops working at once. Any connection also expires after 30 days without use, or 90 days after you made it.

What Data Visions records. For every action the assistant takes, we log which action it was, when, whether it succeeded, and identifying details such as the app or report name. We do not log the contents of files or the values you searched for, and we do not keep a copy of the data returned to the assistant.

What the assistant's provider receives. The information the assistant reads from Data Visions is sent to that assistant and is handled under its provider's privacy policy, for Claude, Anthropic's Privacy Policy. Connect only assistants your organization allows.

6. Your organization's data

The organization that subscribes to Data Visions controls the information in its workspace, and we process it on that organization's behalf and under its instructions.

• Each workspace is separate. Every organization's records sit in a database of their own, and its files in storage of their own.
• Your administrator decides who has accounts, what each role can see, which apps and AI features are on, and how long to keep records. Requests about workspace content usually go to your administrator first (Section 10).
• Our staff stay out unless allowed. Each workspace sets whether Data Visions support staff may enter it: never, only when an administrator approves, or always. Support access is time-limited, administrators can end it at any time, and everything support staff do appears in the workspace's audit log. Emergency access needs a written reason, notifies the workspace's administrators at once, and ends after 4 hours; it is not possible when the setting is “never”.
• Apps from other publishers. If your organization installs an app built by another company through the Data Visions marketplace, that app runs inside your workspace with only the permissions your organization grants it.

7. How we share information

We share personal information only with the service providers that run Data Visions for us, and as described below. We do not sell it or share it for advertising.

We also share information:

• Within your organization, according to the roles your administrator sets.
• With assistants and apps you connect, as described in Section 5.
• For legal reasons, when required by law, or to protect people, our users or our service.
• In a business transfer, such as a merger or sale, under this policy's protections.

8. Security

We protect information with encryption, separation between organizations, and limits on who can reach it, though no system is perfectly secure.

• Data is encrypted in transit and at rest. Passwords are stored only as one-way hashes; two-factor secrets and AI provider keys are additionally encrypted.
• Each organization's records sit in their own database, and every request is checked against the signed-in person's organization and role.
• Workspaces can require two-factor sign-in, and accounts lock after repeated failed attempts.
• Uploaded files are scanned for viruses on our own servers.
• Sign-ins, administrator changes, support access and connected-assistant actions are recorded in an audit log.

If we learn of a breach affecting your information, we will notify your organization, and you where the law requires, without undue delay.

9. How long we keep information

We keep workspace information while your organization subscribes, and delete it when the organization leaves, after the backup periods below.

When an organization ends its subscription, its workspace is switched off for 30 days, so it can change its mind or ask for an export, and then deleted. Copies in backups expire on the schedule above.

10. Your choices and rights

You can ask to see, correct, export or delete your personal information, and we will not treat you differently for asking.

• In the app: update your name and password, set up two-factor, delete your own recordings and chat messages, and disconnect AI assistants.
• Through your administrator: for records in your organization's workspace, start with your administrator, who controls that information. We help them answer you.
• From us directly: write to support@datavisions.ai. We will confirm who you are and reply within 30 days, or sooner where the law requires.

Depending on where you live (for example California and other US states, the UK or the EU), you may also have the right to object to or restrict some uses, to move your information to another service, and to complain to your data protection authority. We do not sell or share personal information for targeted advertising, so there is nothing to opt out of there.

11. Other things to know

Children. Data Visions is a business service and is not meant for anyone under 18. We do not knowingly collect children's information.

Where information is stored. Our servers are in the United States (Google Cloud, Iowa region). If you use Data Visions from outside the US, your information is transferred there, protected by the European Commission's Standard Contractual Clauses (and the UK Addendum to them) where the law requires.

Changes to this policy. We will post updates here with a new date, and tell workspace administrators in advance of any significant change.

Contact. Data Visions Inc., 2002 Stone Canyon Drive, St. George, Utah 84790, USA, support@datavisions.ai.