Last updated: August 20, 2026
Data Processing Addendum
This Addendum governs RevenueUI's processing of personal data on behalf of a customer.
This Data Processing Addendum (“DPA”) forms part of the RevenueUI Terms of Service between Masafumi Suzuki (“RevenueUI”) and the customer using RevenueUI (“Customer”). It applies when RevenueUI processes personal data on Customer’s behalf.
1. Roles and scope
- Customer is the controller, or a processor acting for another controller, for personal data collected from Customer’s measured websites and connected data sources.
- RevenueUI is Customer’s processor for that data. RevenueUI remains an independent controller for RevenueUI account administration, subscription billing, security, and its direct communications with Customer.
- Customer determines the purposes and lawful basis of website measurement and must provide required notices, consent controls, and methods for data subjects to exercise their rights.
2. Documented instructions
RevenueUI will process Customer Personal Data only to provide, maintain, secure, support, and delete the service in accordance with the Terms, this DPA, Customer’s configuration, and other written instructions RevenueUI accepts. RevenueUI will notify Customer if an instruction appears to violate applicable data-protection law, unless prohibited by law.
3. Processing details
| Item | Description |
|---|---|
| Subject matter | Website analytics, revenue analytics, attribution, import, storage, display, support, security, export, and deletion |
| Duration | The service term, the applicable event-retention period, the 90-day recovery period, and the time required to complete deletion and backup rotation |
| Data subjects | Visitors to measured websites, Customer personnel, trial users, subscribers, and payers represented in connected provider records |
| Data categories | Visitor and session IDs; page path; external referrer host; campaign fields; event and consent times; browser, operating system, device type, and country code; payment, refund, customer, invoice, Checkout Session, Payment Intent, subscription, and trial identifiers and values |
| Special-category data | Not intended or permitted. Customer must not submit special-category data, credentials, payment-card numbers, or sensitive values in measured fields |
| Frequency | Continuous while collection is enabled; periodic provider imports and subscription synchronization |
4. Confidentiality and security
RevenueUI will limit access to persons who need it to operate the service and who are subject to confidentiality obligations. Measures include tenant authorization, encryption in transit, encryption of Stripe restricted keys and webhook secrets at rest, signed internal delivery, webhook verification, validation, rate limiting, logging, backup controls, and deletion procedures. RevenueUI will review these measures as risk and technology change.
5. Subprocessors
Customer grants general authorization for RevenueUI to use the providers on the Subprocessor List. RevenueUI will require subprocessors to protect Customer Personal Data under written terms appropriate to their role. RevenueUI will publish intended additions or replacements before they begin processing where reasonably practicable, so Customer may raise a data-protection objection.
6. Data-subject requests
RevenueUI will reasonably assist Customer with access, correction, restriction, portability, objection, and erasure requests. The service provides authenticated JSON export and erasure tools for visitor and session identifiers. Customer remains responsible for verifying the requester and handling records held independently in Stripe or another source system. Additional requests may be sent to palty.support@gmail.com.
7. Security incidents
RevenueUI will notify affected Customers without undue delay after confirming a personal-data breach involving Customer Personal Data and will provide available information reasonably required for Customer’s notification and remediation duties. Customer is responsible for notifications it must make as controller.
8. Deletion and return
- Customer may export account data and visitor-linked data through the service.
- Customer may erase visitor-linked RevenueUI events and remove RevenueUI identifiers from stored payment and trial records.
- Account or website deletion removes the associated local data after required external webhook cleanup.
- When paid or trial access ends, RevenueUI deletes websites and their analytics and connected revenue data after the 90-day recovery period.
- Deleted information may remain in access-restricted backups until the applicable rolling backup cycle completes and will not be restored except for disaster recovery.
9. Audits and compliance information
On reasonable written request, RevenueUI will provide information necessary to demonstrate compliance with this DPA, subject to confidentiality and security restrictions. If that information is insufficient, the parties will agree on a proportionate audit that avoids unnecessary access to other customers’ information and disruption to the service.
10. International transfers
Each party will use a valid transfer mechanism where GDPR-protected personal data is transferred outside the EEA. Depending on the transfer, this may include an adequacy decision or the European Commission’s Standard Contractual Clauses. Customer authorizes RevenueUI to enter the processor-to-processor modules needed for an authorized subprocessor. Transfer details depend on Customer’s and the providers’ configured regions.
11. Priority and termination
If this DPA conflicts with the Terms on personal-data processing, this DPA controls. It remains effective until RevenueUI has deleted Customer Personal Data as described above.