Privacy Policy

Clear rules for customer intelligence data.

Jovis AI helps customer-facing teams ask questions across CRM, support, product data, documents, and internal systems. This policy explains what we collect, how we use it, and the controls available to customers.

Last updated: May 31, 2026. This policy applies to the Jovis AI hosted service at jovis.ai and related product experiences.

1. Scope

This Privacy Policy covers Jovis AI, an AI analyst workspace for customer-facing teams. It applies when you visit our site, sign in, create or join a workspace, connect third-party systems, upload or index documents, chat with agents, or use related support channels.

If your organization uses Jovis, your organization controls the customer content it brings into the product. We process that content to provide the service under our agreement with your organization.

2. Data we collect

Account and workspace information

We collect information needed to create and secure accounts, such as work email address, authentication events, workspace membership, role, invitations, preferences, and basic usage metadata.

Connector and integration data

Jovis can connect to systems such as CRM tools, support desks, databases, document sources, code or ticketing systems, email, and internal APIs. Depending on your configuration, we may process connector names, metadata, schemas, records, tickets, messages, documents, query results, OAuth tokens, API keys, or other credentials needed to perform authorized workflows.

Chats, prompts, files, and generated output

We process the questions you ask, agent plans, retrieved context, citations, uploaded or connected documents, and generated responses so the product can answer questions and keep useful workspace history.

Technical and security data

We collect logs, device and browser details, IP address, request metadata, error reports, audit events, and similar operational data to keep the service reliable and secure. We may use cookies, local storage, or similar technologies for authentication, preferences, and product operation.

3. How we use data

  • Provide the product: authenticate users, manage workspaces, run connectors, retrieve context, answer questions, and show chat or document history.
  • Protect tenant boundaries: enforce workspace membership, role-based controls, audit privileged actions, and prevent unauthorized cross-workspace access.
  • Improve reliability: debug errors, monitor performance, prevent abuse, and maintain integrations.
  • Support customers: respond to requests, investigate reported issues, and communicate product or security updates.
  • Meet legal obligations: comply with applicable law, enforce agreements, and protect rights, safety, and service integrity.

We do not sell customer content. We do not use customer content for unrelated advertising.

4. How data is shared

We share data only as needed to operate Jovis, comply with law, or follow your organization's instructions.

  • Connected services: Jovis sends requests to the systems your workspace connects, using the credentials and permissions configured by your organization.
  • AI model providers: Jovis may send prompts, retrieved context, and related metadata to the language model provider selected or configured for your workspace.
  • Infrastructure and support vendors: We use service providers for hosting, storage, logging, email delivery, security, analytics, and customer support.
  • Legal and safety: We may disclose information when required by law or to protect Jovis, customers, users, or the public.
  • Business transfers: Information may transfer as part of a merger, acquisition, financing, restructuring, or sale of assets, subject to appropriate protections.

5. Security

Jovis is designed around workspace isolation, authenticated access, role-based permissions, and read-only connector behavior by default. We use technical and organizational safeguards intended to protect account data, credentials, connected content, and generated output.

No service can guarantee perfect security. Customers should configure connectors with least-privilege accounts, remove unused integrations, review workspace membership, and promptly report suspected misuse.

6. Retention

We retain personal data and customer content for as long as needed to provide Jovis, meet legal obligations, resolve disputes, enforce agreements, and maintain security. Retention periods may vary based on workspace settings, connected systems, plan, backup schedules, and legal requirements.

When your organization deletes content, disconnects a connector, or closes an account, we delete or de-identify associated data according to applicable agreements and operational requirements.

7. Your choices and controls

  • Workspace owners and admins can manage members, roles, connectors, documents, providers, and agents.
  • You can request access, correction, export, or deletion of personal information, subject to verification and applicable law.
  • Your organization may control certain requests if you use Jovis through an employer or other customer account.
  • You can control browser cookies and local storage through your browser, though some settings may affect sign-in or product functionality.

8. Children

Jovis is built for business use and is not directed to children. We do not knowingly collect personal information from children under 13.

9. Changes to this policy

We may update this policy as Jovis, our practices, or legal requirements change. The updated version will be posted on this page with a new effective date. Material changes may also be communicated through the product or by email.

Contact

For privacy questions or requests, contact privacy@jovis.ai.