Skip to content
  • Pricing
  • Compare
  • Docs
  • Blog
  • Tools
  • Security
Sign inGet started

Legal

  • Overview
  • Terms of Service
  • Privacy Policy
  • Data Processing
  • Subprocessors
  • Refund Policy
  • Acceptable Use
  • Cookie Policy
  • Impressum
  • Security

Legal

Data Processing Agreement

How we process your visitors' and buyers' data on your behalf, under Article 28 of the GDPR. It is part of our Terms, so you do not need to sign anything.

Effective November 18, 2026

The short version

  • Already in place

    This agreement is part of our Terms. It applies automatically, with nothing to sign.

  • Your instructions only

    We process your visitors' data only to run your tests, never for our own purposes.

  • One subprocessor

    Only Cloudflare processes your visitors' data for us. New ones are announced 14 days ahead.

  • Deleted with your account

    Deleting your account deletes your visitors' data at once, and backups within 30 days.

A summary to help you read. The full text below is what applies.

1Scope

  1. This Data Processing Agreement (the "DPA") is part of the agreement between you (the "Customer") and Dmytro Katyukha, sole proprietor, Germany ("Leverprice"; postal address in the Impressum) under our Terms of Service. It applies whenever Leverprice processes personal data on the Customer's behalf, and it meets the requirements of Article 28 of the General Data Protection Regulation ("GDPR") and of the UK GDPR where that applies.
  2. It takes effect when the Customer accepts the Terms and lasts as long as Leverprice processes Customer Personal Data.

2Definitions

  1. "Customer Personal Data" means personal data about the Customer's website visitors and buyers that Leverprice processes on the Customer's behalf to provide the Service, as described in Annex 1.
  2. "Subprocessor" means a third party that Leverprice engages to process Customer Personal Data.
  3. Other terms, such as "controller", "processor" and "personal data breach", have their GDPR meaning.

3Roles and instructions

  1. The Customer is the controller of Customer Personal Data, and Leverprice is its processor.
  2. Leverprice processes Customer Personal Data only on the Customer's documented instructions, unless the law requires otherwise, in which case Leverprice tells the Customer before processing where the law allows. The Customer's instructions are the Terms, this DPA, the settings the Customer chooses in the Service and any further written instructions Leverprice agrees to.
  3. Leverprice tells the Customer without delay if it believes an instruction infringes data protection law.
  4. Leverprice does not sell Customer Personal Data and does not use it for its own purposes, except to create aggregated statistics that identify no person, as the Terms allow.
  5. For data about the Customer's own account, such as the names and email addresses of its users, and for billing, Leverprice is an independent controller under its Privacy Policy.

4The Customer's obligations

  1. The Customer ensures that it has a legal basis for the processing, gives its visitors and buyers the information the law requires and obtains any consent required, including for the cookies the SDK and no-code links set on its behalf.
  2. The Customer does not send Leverprice special categories of personal data (Art. 9 GDPR), data about criminal convictions, or direct identifiers such as names, email addresses or phone numbers in IDs, metadata or any other field.
  3. The Customer tells Leverprice without delay if it finds errors or irregularities in the processing.

5Leverprice's obligations

  1. Leverprice ensures that every person authorised to process Customer Personal Data is bound to confidentiality.
  2. Leverprice implements the technical and organisational measures in Annex 2 and may improve them, as long as the overall level of protection does not fall.
  3. Taking into account the nature of the processing, Leverprice helps the Customer answer requests from data subjects. The Customer can view, export and delete its data in the Service; for anything else, Leverprice responds to the Customer's written request. If a data subject contacts Leverprice directly, Leverprice refers them to the Customer.
  4. Leverprice helps the Customer, with the information available to it, with security, breach notifications, data protection impact assessments and prior consultations (Arts. 32 to 36 GDPR).
  5. Leverprice makes available the information needed to demonstrate compliance with this DPA, as set out in section 9.

6Subprocessors

  1. The Customer gives Leverprice general authorisation to engage Subprocessors. The current Subprocessors are listed on our Subprocessors page.
  2. Leverprice updates that page at least 14 days before a new Subprocessor starts processing Customer Personal Data. If you would like an email when it changes, write to security@leverprice.com.
  3. The Customer may object to a new Subprocessor on reasonable data protection grounds within those 14 days. If we cannot address the objection, the Customer may end the agreement before the change takes effect, and Leverprice refunds prepaid subscription fees for the time after that date.
  4. Leverprice imposes on each Subprocessor data protection obligations that offer at least the same protection as this DPA, and remains responsible to the Customer for its Subprocessors.

7International transfers

  1. Leverprice is established in Germany. Where a Subprocessor processes Customer Personal Data outside the European Economic Area, the transfer relies on an adequacy decision, such as the EU-U.S. Data Privacy Framework for certified recipients, or on the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914.
  2. If the Customer is established outside the European Economic Area in a country without an adequacy decision, Module 4 of those Standard Contractual Clauses (processor to controller) is incorporated into this DPA by reference, where the GDPR requires it.

8Personal data breaches

  1. Leverprice notifies the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, by email to the workspace owner.
  2. The notice describes, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences and the measures taken or proposed. Leverprice provides further information as it becomes available.

9Audits

  1. Leverprice answers the Customer's reasonable written questions about its compliance and provides the relevant documentation, including this DPA, Annex 2 and the Subprocessors list.
  2. If that is not enough to demonstrate compliance, or if a supervisory authority requires it, the Customer may audit Leverprice once per calendar year, with at least 30 days' notice, during normal business hours, at its own cost, and through an auditor bound to confidentiality. An audit may not give access to other customers' data or interrupt the Service.

10Deletion and return

  1. The Customer can export its data at any time through the dashboard and the API, and should do so before ending the agreement.
  2. When the Customer deletes its account, Leverprice deletes Customer Personal Data at once. Copies in backups are overwritten within 30 days. Data that the law requires Leverprice to keep is kept only for that purpose and as long as required.
  3. While the account exists, Customer Personal Data is kept as described in the Privacy Policy. In particular, records of which visitor saw which price are deleted 30 days after the test ends.

11How this DPA fits with the Terms

  1. The limits in the Terms also apply under this DPA, as far as the law allows. The rights of data subjects under Art. 82 GDPR are not affected.
  2. If this DPA conflicts with the Terms, this DPA prevails for the processing of personal data. If the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses prevail.
  3. German law governs this DPA, and the disputes section of the Terms applies.

12Annex 1: Details of the processing

Details of the processing
Details
Subject matterRunning price tests for the Customer's products and measuring the revenue each price earns
DurationAs long as the Customer's account exists, plus the deletion periods in section 10
Nature and purposeAssigning visitors to prices, recording which price each visitor saw, attributing purchases and refunds to prices, computing results and moving traffic between prices
Data subjectsVisitors to the Customer's websites and apps, and buyers of the Customer's products
Categories of dataKeyed hashes of visitor or user IDs; random visitor IDs for no-code links; test, price and time of first view; country; order, subscription, trial, invoice and refund IDs; amounts and currencies
Special categoriesNone. The Customer must not send them.
LocationCloudflare's global network; see the Subprocessors page

13Annex 2: Technical and organisational measures

  • Encryption in transit. All traffic to the dashboard, API and SDK endpoint uses TLS 1.2 or later, with HSTS.
  • Pseudonymisation. The SDK hashes visitor and user IDs with a key before they leave the Customer's server. No names, emails or card data are accepted.
  • Credentials. API keys, access tokens and session tokens are stored only as SHA-256 hashes. Webhook signing secrets are encrypted with AES-256-GCM. Revoking a key takes effect worldwide in seconds.
  • Integrity. Price configurations are signed with keys held outside the database and checked by the SDK. Purchase attribution is signed with HMAC, and purchases from the Customer's payment provider are verified by signature.
  • Access control. Access to the dashboard requires sign-in by emailed code, GitHub or Google. Sessions use HttpOnly, Secure cookies. Access to production systems is limited to the operator.
  • Accountability. Every change made in a workspace is written to an audit log the Customer can read.
  • Availability. The Service runs on Cloudflare's network with protection against attacks, rate limits and automatic retries. The database keeps a 30-day point-in-time history for recovery, and the SDK falls back to the Customer's own price during an outage.
  • Data minimisation. Records of which visitor saw which price are deleted 30 days after a test ends. IP addresses are used only transiently and not stored.
  • Separation. Test and live data are stored separately, and every query is scoped to the Customer's workspace and project.

14Annex 3: Subprocessors

The list of Subprocessors forms part of this DPA and is published on our Subprocessors page.

Questions about data processing?

Write to us. A person reads every message.

dev@leverprice.com

On this page

  1. 1Scope
  2. 2Definitions
  3. 3Roles and instructions
  4. 4The Customer's obligations
  5. 5Leverprice's obligations
  6. 6Subprocessors
  7. 7International transfers
  8. 8Personal data breaches
  9. 9Audits
  10. 10Deletion and return
  11. 11How this DPA fits with the Terms
  12. 12Annex 1: Details of the processing
  13. 13Annex 2: Technical and organisational measures
  14. 14Annex 3: Subprocessors

Find the price that earns you the most

Product

  • Price testing
  • PPP pricing
  • Pricing
  • Docs
  • Security
  • Lifetime deal

Resources

  • Blog
  • Guides
  • Integrations
  • Free tools
  • Glossary
  • Compare
  • Alternatives

Solutions

  • SaaS
  • Indie hackers
  • AI apps
  • Developer tools
  • Agencies

Account

  • Sign in
  • Get started
  • About
  • Contact

Legal

  • Terms
  • Privacy
  • Refunds
  • DPA
  • Cookies
  • Impressum
  • All legal

© 2026 Leverprice. Prices are computed on your server, never in the browser.

Theme