Privacy Policy

Last updated: October 22, 2026
Effective: October 26, 2026

1. Scope

This Privacy Policy explains how Volterra Intelligence (“VolterraIQ,” “we,” “us,” or “our”) collects, uses, discloses, and protects personal information in connection with the VolterraIQ websites, applications, beta program, dashboards, reports, support, and related services (collectively, the “Service”).

Volterra Intelligence operates the Service under the VolterraIQ operating name. The Service is intended for business use by adults and is not intended for personal, family, or household use.

This Policy does not govern information processed independently by third parties under their own policies.

2. Information you provide

Depending on your use of the Service, we may collect:

  • account and profile information, such as name, business email address, profile image, user identifier, and authentication information;
  • organization information, such as organization name, workspace identifiers, membership, and technical role;
  • beta-access and support information, such as invitation status, eligibility, communications, questions, and support requests;
  • report and workflow inputs, such as site names, addresses, coordinates, report titles, selected locations, filters, and other content submitted to create, save, or evaluate an output;
  • feedback, comments, attachments, screenshots, and related metadata submitted through an enabled feedback or support channel;
  • billing and transaction information when paid features are enabled, excluding full payment-card details collected directly by our payment provider; and
  • other information you choose to provide.

3. Information collected automatically

When you use the Service, we and our service providers may process:

  • authentication, session, security, and organization-membership information;
  • device, browser, IP address, approximate location derived from IP address, operating system, language, and similar technical information;
  • request and operational metadata, such as date and time, requested path, status code, timing, error information, and security events;
  • usage information, such as pages or features accessed, workflow state, report-generation events, and interactions needed to operate, secure, troubleshoot, or improve the Service;
  • browser storage, cookies, or similar technologies used for authentication, security, preferences, support, feedback, or other enabled functionality;
  • map, tile, geocoding, and address-resolution requests when location features are used; and
  • provider-generated identifiers or diagnostics associated with enabled identity, infrastructure, communications, feedback, payment, mapping, or support services.

The specific technologies and providers may change as the beta evolves.

4. How we use information

We may use personal information to:

  • authenticate users and maintain secure sessions;
  • provision and enforce beta eligibility, organization membership, subscription, entitlement, and usage controls;
  • operate accounts, workspaces, reports, exports, maps, notifications, feedback, support, and other authorized features;
  • generate, save, display, and deliver requested intelligence outputs;
  • process payments and administer paid features when enabled;
  • communicate about access, security, reports, support, policy updates, and Service changes;
  • investigate errors, maintain availability, prevent misuse, and protect users, the Service, and third parties;
  • evaluate and improve the beta, data quality, usability, and product performance;
  • enforce agreements and establish, exercise, or defend legal claims; and
  • comply with law and valid legal process.

Where applicable law requires a legal basis, processing may be necessary to provide the Service or perform a contract, comply with legal obligations, protect legitimate business and security interests, or carry out activities for which consent is requested. Authentication or beta onboarding is not blanket consent for unrelated processing.

5. Beta access and organization information

Current beta access is centrally administered and invitation-only. VolterraIQ or an authorized representative—not a customer organization administrator—controls beta provisioning and access requests unless we expressly enable a different model.

The underlying identity system may use technical roles such as admin or member. Those role names do not necessarily mean that a user may independently invite, suspend, remove, or administer other beta users.

Authorized users may be able to view limited organization membership information required for access and workspace operation.

6. Reports and organization sharing

New reports are private to their owner unless the user explicitly selects an enabled organization-sharing option. When a report is organization-shared, it may be viewed by permitted members of that organization and is not accessible to nonmembers.

The current beta does not provide public links, guest access, or external in-product collaboration. An authorized exported PDF may be circulated outside the product for legitimate client, sales, diligence, or other internal business purposes, subject to the Terms of Service. Circulating that PDF does not create in-product access for its recipient.

7. Cookies and similar technologies

We and our service providers may use cookies, local storage, session technologies, pixels, SDKs, or similar technologies to authenticate users, secure the Service, remember preferences, operate support or feedback features, process payments, and understand or improve Service performance.

Available controls depend on the technology and applicable law. Disabling necessary browser or provider technologies may prevent portions of the Service from working.

If we introduce nonessential technologies that require consent or an opt-out under applicable law, we will provide the appropriate notice or control.

8. Service providers and disclosures

We may disclose personal information to service providers that perform functions for us, including:

  • identity, authentication, organization, and session management providers, including Clerk;
  • cloud hosting, databases, object storage, security, logging, monitoring, search, communications, and infrastructure providers;
  • feedback and support providers when those features are enabled;
  • map, tile, geocoding, and address-resolution providers when location features are used;
  • payment and billing providers, including Stripe if payment functionality is enabled;
  • professional advisers, auditors, and contractors subject to appropriate obligations; and
  • other providers necessary to operate an enabled Service feature.

Some providers engage their own subprocessors. A downstream provider is not automatically a direct VolterraIQ processor, and provider roles may differ by service and data flow.

We may also disclose information:

  • at your direction or with your permission;
  • to permitted members of your organization when you explicitly use an organization-sharing feature;
  • to comply with law, legal process, or valid government requests;
  • to protect rights, safety, security, and the integrity of the Service;
  • to investigate misuse or enforce agreements; and
  • as part of a merger, financing, reorganization, sale of assets, acquisition, bankruptcy, or similar transaction, subject to applicable law.

We do not sell personal information for money. We do not use personal information for cross-context behavioral advertising during the current beta.

9. Data retention and deletion

We retain personal information only for as long as reasonably necessary to provide and secure the Service, administer the beta or commercial relationship, maintain required business records, resolve disputes, enforce agreements, and comply with law.

Retention depends on the data type and purpose. Account, organization, report, feedback, support, billing, security, and operational records may follow different schedules. Dismissing a notification or hiding an interface item does not necessarily delete the underlying record.

When information is no longer reasonably required, we may delete, deidentify, or aggregate it, subject to legal obligations, security needs, backup cycles, dispute preservation, and applicable agreements. Deletion from active systems may not immediately remove information from protected backups.

10. Security

We use administrative, technical, and organizational safeguards designed to protect personal information, including authenticated access, organization-scoped authorization, access controls, and operational security practices.

No system is completely secure. You are responsible for protecting credentials and promptly reporting suspected unauthorized access.

11. Your choices and privacy rights

Depending on applicable law, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to object to or restrict certain processing; or to withdraw consent where processing depends on consent.

You may update certain profile or preference information through available Service controls. Other requests may require identity verification and coordination with your organization sponsor or a relevant identity provider.

Submit a request through the public Request Beta Access form, which remains available without application access, or through an enabled support or feedback channel in the Service. Product monitors and routes submissions from the public form during the beta. We will respond as required by applicable law. We may retain information when legally permitted or required.

12. International access and transfers

The Service is operated for a U.S.-focused business beta and may be hosted or supported from the United States and other locations where our providers operate.

If you access the Service from another country, personal information may be transferred to and processed in jurisdictions with different privacy laws. Where applicable law requires a transfer mechanism or additional safeguards, we and our providers will use an appropriate mechanism. Contact us using the methods below for information relevant to your access.

13. Children’s privacy

The Service is intended for business users who are at least 18 years old. It is not directed to children, and we do not knowingly collect personal information from children under 13.

If you believe a child has provided personal information through the Service, contact us using the methods below. We will investigate and take appropriate action, including deletion where required.

14. Third-party services and sources

The Service may link to or integrate with third-party websites, datasets, maps, identity tools, payment tools, or other services. Their independent collection and use of information is governed by their own policies.

When a provider processes personal information on our behalf, our contractual relationship with that provider governs that processing. When you interact independently with a third party, that third party may act under its own terms and privacy policy.

15. Changes to this Policy

We may update this Policy as the beta and Service evolve. We will post the revised Policy and update the date above. When required, we will provide additional notice or request consent.

16. Contact us

Privacy questions, requests, or concerns may be submitted through the public Request Beta Access form, which remains available without application access, or through an enabled support or feedback channel in the Service. Product monitors and routes submissions from the public form during the beta.