Legal

Terms of service

What you can expect from us, what we expect from you, and what happens at the edges: plan limits, termination, liability.

In plain language, before the legal text

· You use Metricward to collect analytics on your own sites and products.
· Go over your plan's limits and we slow ingestion down, we do not delete anything.
· We do not promise a specific uptime percentage in this document.
· You own the data your projects collect. We are a processor, not an owner.
· Either side can end this. Your account stays exportable for a while afterwards.
· Swedish law governs this agreement.

The service

Metricward is an EU-hosted web and product analytics service. You create projects, install a tracking snippet or send events from your own servers, and Metricward stores and reports on the resulting data under the settings you choose for that project, collection mode, consent mode, retention, masking. What is built today and what is still on the roadmap is stated on the pricing page rather than only here, because that is where the claim actually gets tested against a plan.

Acceptable use

You agree not to, using Metricward:

·Collect data about a visitor without the legal basis your own use of that data requires. You are the controller of what your projects collect, and that responsibility does not transfer to us.
·Put special-category personal data, such as health information or a national identity number, into an event property. Properties are stored as you send them, and putting sensitive data there is a risk you create for yourself.
·Attempt to access, scan or probe another organisation's project or data.
·Attempt to bypass a rate limit, a quota, or an authentication or authorisation control.
·Run automated vulnerability scanners against production without arranging it with us first, see the reporting terms on the security page.
·Resell or sublicense access to the service without a separate written agreement.
·Use the free plan, or multiple free accounts, to circumvent the limits of a paid plan.

A material breach of this section can result in suspension or termination. We will tell you why, except where telling you would itself be unsafe, for example an active attempt to read another tenant's data.

Plan limits, and what happens if you exceed them

Each plan has a monthly event allowance, a project count, a retention window and a team size, listed on the pricing page. Bot-flagged and rejected events never count against your allowance. Going over your allowance does not delete anything and does not cut your data off mid-month: there is a 10% grace above your limit before ingestion starts pausing, and the dashboard keeps working throughout. Downgrading a plan never deletes data that is already collected, it stops collection above the new allowance and hides reports the new plan does not include.

Card billing is not wired into the product yet, so on a paid plan today there is currently no automatic way to charge an overage at all, a state we would rather state plainly than let a customer discover by accident. When billing is live, the first overage month on a paid plan is forgiven with a notice rather than a charge, and every month after that is billed in whole packs of 100,000 events, so the invoice is arithmetic you can do yourself.

Uptime

This document does not promise a specific uptime percentage or a service credit schedule. There is no SLA number here, and inventing one to look reassuring would be worse than leaving the section short. If a contractual SLA is a requirement for your organisation, ask, it is a negotiated Enterprise term, not a default that applies to every account.

Your data

You own the data your projects collect: your events, sessions, properties, reports and dashboards. We process it as your instructions describe, through your project settings, and for no other purpose, we do not sell it, and we do not use it to train anything outside your own account. The roles, the commitments and the mechanism behind each one are set out in full on the processor terms page. CSV export of your raw events and every report is available at any time from inside the product on every plan, free included. JSON and Parquet export are specified and not built yet.

Termination

You can close your account at any time. We can suspend or terminate an account for a material breach of the acceptable use section, for non-payment once billing is live, or where we are required to by law. On termination, however it happens, your account moves to read-only for 30 days rather than being deleted immediately, matching the same window used for a full project deletion, and you can export everything during that window. After it, your data is deleted according to your project's retention setting, and that deletion produces a receipt the same way any other deletion does.

Limitation of liability

To the extent Swedish law allows it, our total liability arising from these terms or your use of the service is limited to the amount you paid us in the 12 months before the claim arose, and neither side is liable to the other for indirect, incidental or consequential loss, including lost profits or lost data. Nothing here limits liability where the law does not permit it to be limited, for example for gross negligence, wilful misconduct, or a party's own confidentiality and data protection obligations.

Governing law

These terms are governed by the laws of Sweden, without regard to its conflict-of-law rules. Any dispute that cannot be resolved directly is subject to the exclusive jurisdiction of the Swedish courts.

This is a template. It has not been reviewed by a lawyer.

It describes the service and its limits honestly, but it is not a substitute for legal advice, for you or for us, and it should not be treated as a finished contract until it has actually had one.

Related: processor terms, compliance, pricing.