Terms of Service

Last revised: 8 September 2026. Status: proposed service terms. Legal review: not yet recorded. This version has no effective date.

These terms are a review copy, not an agreement created merely by viewing this page. Before use as binding terms, the DataVisitors operator must confirm its legal name, business address, jurisdiction, and the acceptance process.

“DataVisitors” means the service and, when an agreement takes effect, the operator named in that agreement. “Customer” means the individual or organization that enters the agreement. An authorized organization representative must have authority to accept it.

DataVisitors provides web and product analytics, with features that can include goals, funnels, retention, revenue reporting, heatmaps, individual views, alerts, and team reports.

The selected plan, enabled features, integration, and configuration determine what is available. Public examples demonstrate workflows and do not promise a particular business result. The feature pages and manual explain the product's supported behavior.

You must have legal capacity to enter the applicable agreement. You must provide accurate account information and maintain an email address that can receive account notices.

If you act for an organization, use the service only within your authority. The organization controls access granted through its memberships and roles. Resolve ownership and administrator responsibilities before the last owner leaves.

Keep passwords, API keys, signing secrets, and connected-application credentials confidential. Grant each person or integration only the access it needs. Review access when a person leaves or an integration is no longer needed.

Notify the DataVisitors contact promptly if you reasonably suspect unauthorized access. Use available revocation controls where appropriate. You are responsible for activity you authorize; these terms do not remove DataVisitors's own responsibilities for service security.

You retain your rights in the data you submit. You authorize DataVisitors to process that data only as needed to provide, secure, and support the agreed service and follow lawful instructions.

You must have the rights and lawful basis needed to collect and submit the data. Provide appropriate notices and obtain consent where required. Configure privacy settings, identifiers, event properties, and optional collection features accordingly.

Do not submit passwords, complete payment-card numbers, authentication secrets, or unnecessary sensitive personal data as analytics. Privacy filtering helps reduce accidental collection but does not replace your review of an integration.

The Data Processing Agreement, once completed and incorporated into an agreement, governs customer personal data processed on your behalf.

You must not use the service to:

• Break applicable law or infringe another person's rights.
• Collect data from a website, application, or account you do not control or have permission to instrument.
• Conduct covert surveillance or bypass required privacy choices.
• Access another customer's data or attempt to defeat authentication, authorization, or usage controls.
• Distribute malicious software, abuse delivery channels, or disrupt the service.
• Submit fabricated activity to manipulate another party's reports or consume its allowance.
• Use automated access outside the supported interfaces or agreed limits.

Security research must stay within an explicitly authorized scope. Report a suspected vulnerability privately through Contact, without accessing or disclosing other customers' data.

The current order or checkout offer must state the price, currency, billing interval, included allowance, and material feature limits. A public example or an older price announcement does not replace that offer.

Accepted analytics events contribute to event usage. Project, seat, retention, and feature limits can also apply. Check the organization's plan and usage information before increasing collection or adding members.

The service can enforce technical limits to protect capacity and the agreed allowance. A grace mechanism does not create an unlimited plan or authorize an unannounced charge. Any paid overage, plan change, or automatic renewal must follow the terms disclosed in the accepted offer.

Where recurring billing is offered, review the amount, renewal frequency, payment method, and cancellation method before accepting. Payment processing can use a separate provider and its applicable terms.

Taxes, annual discounts, trial conditions, refunds, and payment grace periods must appear in the current offer where relevant. This review copy does not create a free trial, a fixed discount, or a blanket no-refund rule.

A material price or subscription change requires the notice and agreement required by the applicable contract and law. It does not take effect merely because someone edits this page.

Subscription cancellation and account closure are different actions. Cancellation changes future paid service according to the accepted offer. Account closure removes access and starts the relevant account-data workflow.

Before closing an account, export information you need and resolve organization ownership. Closing one member's account does not cancel every organization subscription or delete every organization's analytics.

The accepted offer must state when cancellation takes effect and whether any refund applies. Mandatory consumer rights remain available where the law gives them. Privacy exports, deletion controls, and account closure do not depend on payment status.

You decide who receives public share links, exports, webhook deliveries, and access through connected applications. Review those destinations before enabling them. A recipient can retain a copy after you revoke future access.

Third-party systems have their own availability, security, and terms. DataVisitors does not control a destination you configure or an independent provider you choose. Read the relevant provider terms and restrict the information you send.

The service can require maintenance, security updates, and changes to integrations. DataVisitors can restrict harmful activity or suspend affected access where reasonably necessary for security, legal obligations, or a material breach.

Where feasible and lawful, the operator should explain the restriction and provide a reasonable way to resolve it. Urgent protection of other customers or the service can require immediate action.

Contact [[email protected]](mailto:[email protected]) for assistance. A support response time, uptime commitment, or service credit exists only if a separate accepted agreement states it.

Reports depend on the events received, collection settings, consent, filters, integrations, and data retention. Blocked requests, missing instrumentation, imported history, and disconnected devices can affect completeness.

Analytics and automated findings support your judgment. They do not guarantee revenue, conversion improvements, or error-free business decisions. Revenue reports are not a substitute for accounting records or professional advice.

DataVisitors and its licensors retain rights in the service software, documentation, branding, and other materials they provide. Access to the hosted service does not transfer ownership of those materials.

Your rights in customer data remain yours. Separate SDKs, libraries, or downloaded packages can have their own licenses. These terms do not replace those licenses or create a right to redistribute proprietary software.

Feedback does not require you to disclose confidential information. Any permission to use a customer's name, logo, quote, or results in marketing requires separate authorization.

Each party should protect non-public information received from the other for the service relationship. Access should remain limited to people who need it and who have an appropriate confidentiality duty.

Information already public, independently developed, or lawfully received without restriction is outside this confidentiality commitment. A party can disclose information when law requires it, subject to lawful notice and reasonable limits on the disclosure.

Each party remains responsible for its obligations under the accepted agreement and applicable law. No clause removes a liability or remedy that the law does not permit the parties to exclude.

Any negotiated liability limit, warranty exclusion, indemnity, or service remedy must appear in the completed agreement. This review copy does not invent a financial liability cap or require customers to waive statutory rights.

The operator must identify the governing law and any agreed court jurisdiction before these terms take effect. No mandatory arbitration clause or class-action waiver is included in this review copy.

Contact the other party first to explain a service dispute and seek a practical resolution. This does not prevent either party from using a remedy or meeting a deadline under applicable law.

Where completed documents conflict, the accepted order governs its commercial particulars. The Data Processing Agreement governs its personal-data processing subject matter. Mandatory law takes precedence over inconsistent contract terms.

Keep the account and organization contact details current. Send formal service questions to [[email protected]](mailto:[email protected]) until the completed agreement specifies another contact.

A revised version must show its revision date. Material contractual changes require appropriate notice and an acceptance process where required. Read the Privacy Policy, Cookie Policy, and pricing guidance before choosing the service.