Your copy of the DPA
Optional. Fills in your details below, ready to save as a PDF and sign for your records. Nothing you type is sent to us.
Data Processing Addendum
This Data Processing Addendum ("DPA") is between Dual Ninja LLC, a Wyoming limited liability company ("MetricRaven", "we", "us"), and the customer who uses the MetricRaven Service ("you"). It forms part of our Terms of Service and applies whenever we process personal data on your behalf as part of the Service. You accept it by accepting the Terms of Service; no signature is needed.
This DPA is effective as of 18 November 2026.
Last updated: 18 November 2026
1. Definitions
"Customer Site" means a website or app you add to MetricRaven. "Customer Site data" means the personal data we process for you from your Customer Sites, your servers and the accounts you connect. "Data protection law" means the laws that apply to that processing, including the EU General Data Protection Regulation ("GDPR"), the UK GDPR, the Swiss Federal Act on Data Protection ("FADP") and US state privacy laws such as the California Consumer Privacy Act ("CCPA"). "Standard contractual clauses" means the clauses approved by the European Commission in Decision (EU) 2021/914. Terms such as "controller", "processor", "data subject" and "personal data breach" have the meanings given in the GDPR.
2. Roles
You are the controller of Customer Site data, and we are your processor. If you are yourself a processor for someone else, we are your sub-processor. For your own account, billing and use of metricraven.com, we are a controller, and our Privacy Policy applies instead of this DPA.
3. Your instructions
We process Customer Site data only to provide the Service to you, on your documented instructions. Your instructions are the Terms of Service, this DPA, the settings you choose in MetricRaven and the calls you make to our APIs. We tell you if we believe an instruction breaks data protection law. If the law requires us to process Customer Site data in another way, we tell you first unless the law forbids it.
We do not sell Customer Site data, use it for advertising, or share it with other customers.
4. What we process
Subject matter, nature and purpose
We collect, store, analyse and display Customer Site data so you can measure traffic, goals, funnels, revenue and its sources, and the other reports the Service offers.
Duration and frequency
We process Customer Site data continuously, for as long as you use the Service, and then until it is deleted as described in section 13.
Data subjects
- Visitors to your Customer Sites and users of your apps
- Your customers whose payments you send to us or import from a payment provider you connect
Categories of personal data
Depending on the features you turn on, Customer Site data includes:
- Pageviews: page URLs, and if you turn them on, page titles and chosen URL parameters; referrers and UTM parameters
- Device data: device, browser, operating system, language and screen size, and approximate location derived from the IP address. IP addresses are used only to derive that location and a visitor ID that changes daily, and are not stored with analytics data. With the visitor's consent, a random ID is kept for one year in a first-party cookie (
ana_vid) and local storage - Visitor identifiers, and the first-party identifier kept in the browser once a visitor gives consent
- Goals and custom events, and if you turn them on, button texts, form identifiers (never form contents), downloaded file names and scroll depth
- Identify data you send: your user ID and, optionally, a name, email, image and up to 10 custom traits
- Payments matched to visitors: amounts, currencies, products and the related customer and subscription records from your payment provider, or that you report through our APIs. Emails used only to match payments are kept as a keyed hash, not as text.
- JavaScript errors, if you turn them on: error messages and stack traces from your own scripts, with query strings removed
- Page speed, if you turn it on: page load timings (Web Vitals)
- Session recordings, if you turn on session replay: page content and interactions (scrolls, clicks, page changes) on the pages you choose. Text typed into fields is always masked.
Special categories of data
The Service is not built for special categories of personal data, such as health data, or for payment card numbers. Do not send them to us. If you use session replay, make sure recorded pages do not show such data outside form fields, or hide it with the masking options described in our session replay docs.
5. Your responsibilities
You are responsible for having a lawful basis for the Customer Site data you send us, for telling your visitors about it in your privacy notice, for getting consent where the law requires it, and for making sure your instructions to us comply with data protection law. This includes session replay: by default it records only visitors who accepted your cookies. If you turn that setting off, you are responsible for making sure the law allows it.
6. Confidentiality
We make sure that people we allow to process Customer Site data are bound by a duty of confidentiality, and that they access it only as needed to run and support the Service.
7. Security
We take appropriate technical and organisational measures to protect Customer Site data. They include:
- Encryption in transit: the Service and our APIs are served only over HTTPS.
- Encryption at rest: our database provider (MongoDB Atlas) and our recording storage (Cloudflare R2) encrypt the data they store.
- Access control: only members of a website can see its data, according to their role. Share links, embedded dashboards and the public demo never list or play session recordings.
- Sessions and credentials: session tokens are stored as hashes and rotated on every sign-in. Access tokens and keys for the accounts you connect are stored encrypted and used only by our servers.
- Rate limits on sign-in, our APIs and tracking endpoints, and signature checks on incoming webhooks.
- Data minimisation: typed text is never recorded in session recordings, form contents are never collected, and query strings are removed from error reports.
- Session recordings are stored compressed, separately from the analytics database.
We may update these measures, as long as the overall level of protection does not go down.
8. Sub-processors
You give us general authorisation to use sub-processors. The current ones, with what they do and where, are on our sub-processors page. We bind each one by a written agreement with data protection obligations at least as protective as this DPA, and we remain responsible to you for their work.
We announce a new or replacement sub-processor on that page at least 14 days before it starts processing Customer Site data, and we email customers who asked to be told (email legal@metricraven.com to be added). You may object within those 14 days on reasonable data protection grounds by writing to the same address. We will work with you in good faith to resolve it. If we cannot, you may stop using the affected feature or end your subscription, and we refund any prepaid fees for the remaining term.
9. Where data is processed and international transfers
We process and store Customer Site data in the United States (US East). Session recordings are stored with Cloudflare (R2) in Eastern North America. Tracking requests may pass through Cloudflare's global network on their way to us.
Where Customer Site data is transferred from the European Economic Area to the United States, the standard contractual clauses apply and are incorporated into this DPA by reference: Module 2 where you are a controller, and Module 3 where you are a processor. You are the data exporter and we are the data importer. For those clauses:
- Clause 7 (docking clause) does not apply.
- Clause 9: option 2 (general written authorisation), with the 14-day notice period set out in section 8.
- Clause 11: the optional independent dispute resolution wording does not apply.
- Clause 13: the competent supervisory authority is the one that is competent for you as data exporter.
- Clauses 17 and 18: the clauses are governed by Irish law, and disputes go to the courts of Ireland.
- Annex I (parties, description of the processing) is filled in by the preamble and section 4 of this DPA, Annex II (security measures) by section 7, and Annex III (sub-processors) by the sub-processors page.
For transfers from the United Kingdom, the International Data Transfer Addendum to the standard contractual clauses issued by the UK Information Commissioner applies, with the parties' details and the selected clauses as above, and neither party may end it under its Section 19. For transfers from Switzerland, the standard contractual clauses apply with references to the GDPR read as references to the FADP, the Swiss Federal Data Protection and Information Commissioner as the competent supervisory authority where the FADP applies, and "member state" read to include Switzerland, so that data subjects there can bring claims where they live.
If the standard contractual clauses and this DPA conflict, the standard contractual clauses win.
10. US state privacy laws
Where the CCPA or a similar US state privacy law applies, we act as your "service provider" or "processor". We will not sell or share Customer Site data (as those laws define those words), will not keep, use or disclose it for any purpose other than providing the Service to you, will not use it outside our direct business relationship with you, and will not combine it with personal data we get from others except as those laws allow. We will tell you if we can no longer meet these obligations, and you may then take reasonable steps to stop and fix any unauthorised use.
11. Helping you with requests and obligations
The Service lets you answer requests from data subjects yourself. You can look up a person's profile and timeline in the dashboard or through our Visitors API, export your data as CSV or through our APIs, and erase a person's data from the dashboard or through our API (see Delete a person's data). Erasing a person also deletes their session recordings. If a data subject contacts us directly about Customer Site data, we pass the request to you and do not answer it ourselves unless you ask us to.
We give you reasonable help, taking into account the information we have, with your data protection impact assessments and consultations with supervisory authorities about the Service.
12. Personal data breaches
If we become aware of a personal data breach affecting Customer Site data, we notify you without undue delay, and no later than 48 hours after becoming aware of it, at the email address of your account. We tell you what we know about the breach, the data and people affected, its likely consequences and what we are doing about it, and we send more details as we learn them. We take reasonable steps to contain the breach and limit its effects. Notifying you is not an admission of fault.
13. Retention, return and deletion
- Analytics events, identity records and payments are kept while the website exists in your account, so your reports can cover its history.
- JavaScript error reports are deleted after 90 days.
- Page speed measurements are deleted after 90 days.
- Session recordings are deleted after 30 days.
- Deleting a website deletes all of its data, including its session recordings and data imported from connected accounts. Deleting your account deletes all of your websites.
- To get your data back, export it as CSV or through our APIs at any time, including before you delete a website or your account.
- When the Terms of Service end, you can delete your websites or account yourself. If you cannot, email support@metricraven.com and we will delete your Customer Site data within 30 days and confirm by email.
- Copies in backups are removed as those backups expire. We keep data longer only where the law requires it, and then only for that purpose.
14. Showing compliance and audits
On reasonable written request, we give you the information you need to show that we meet this DPA, and answer your questions about our processing. Send requests to legal@metricraven.com.
If that information is not enough, or a supervisory authority requires it, you may audit our compliance with this DPA, yourself or through an independent auditor bound by confidentiality, once in any 12 months (more often after a personal data breach). Give us at least 30 days' written notice and a plan for the audit. Audits take place during normal business hours, preferably by reviewing documents and remotely, do not give access to other customers' data or to our providers' systems, and are at your cost.
15. Liability and governing law
Each party's liability under this DPA is subject to the limits of liability in the Terms of Service, except where data protection law or the standard contractual clauses do not allow such a limit. This DPA is governed by the laws of the State of Wyoming, United States, and disputes under it go to the state and federal courts located in Wyoming, as in the Terms of Service. The standard contractual clauses are governed by Irish law, as set out in section 9.
16. Term and order of precedence
This DPA applies for as long as we process Customer Site data for you, and its obligations continue until that data is deleted. If this DPA conflicts with the Terms of Service, this DPA wins for the processing of personal data. If the standard contractual clauses conflict with either, the clauses win.
17. Changes
We may update this DPA to reflect changes in the Service or the law. We post the new version on this page. We will not lower the protection it gives Customer Site data without telling you at least 30 days in advance.
Contact Us
Legal Team
Dual Ninja LLC / MetricRaven
legal@metricraven.com