This Data Processing Agreement ("DPA") forms part of the Terms of Service between Introtrace ("Processor") and the Customer ("Controller") and is designed to satisfy the requirements of Article 28 of the General Data Protection Regulation (GDPR).
1. Definitions
- "Controller" means the Customer who determines the purposes and means of processing Personal Data
- "Processor" means Introtrace, which processes Personal Data on behalf of the Controller
- "Personal Data" means any information relating to an identified or identifiable natural person
- "Processing" means any operation performed on Personal Data
- "End-User" means visitors to the Controller's website whose requests may pass through the Processor's infrastructure
2. Subject matter and nature of processing
The Processor provides a proxy service that routes certain web requests from the Controller's website through the Processor's servers. The purpose is to recover analytics data that may be blocked by browser extensions or privacy tools.
Nature of Processing: The Processor forwards HTTPS requests, may add visitor IP information for supported analytics integrations, and maintains limited session and recovery-reporting records. Visitor IP addresses are processed during forwarding and crawler verification without being stored in the worker’s application databases.
Categories of Data Subjects: End-Users (visitors to the Controller's website)
3. Duration of processing
Raw proxy payloads are processed while forwarding each HTTPS request. The worker also retains temporary session identifiers and recovery metadata, but does not store visitor IP addresses in its application databases. The Privacy Policy describes expiration, scheduled cleanup, and backend reporting records.
The DPA remains in effect for the duration of the Controller's use of the Introtrace service.
4. Processor obligations
The Processor commits to the following:
4.1 Payload handling and retained metadata
The Processor distinguishes request forwarding from stored operational and reporting records:
- Raw request headers and payloads are not stored in recovery reporting tables
- Temporary session identifiers, organization IDs, timing, proxy status, and counts are stored by the worker
- Visitor IP addresses are processed for forwarding and crawler verification without being stored in the worker’s application databases
- Diagnostic logs are used to investigate errors and maintain the service, separately from recovery reporting records
Session records expire after 10 minutes without recovered requests and are moved to a reporting queue by scheduled processing. Queue records are removed when consumed, with scheduled cleanup for entries older than 24 hours. The backend discards the session identifier before storing reporting metadata.
4.2 Confidentiality
The Processor ensures that all individuals authorized to process Personal Data are committed to confidentiality obligations.
4.3 Security measures
The Processor implements appropriate technical and organizational measures including:
- TLS encryption for all data in transit
- Secure infrastructure provided by Bunny.net
- Regular security reviews and updates
4.4 Assistance to controller
The Processor will provide reasonable assistance with data subject requests involving retained records where technically feasible. Raw analytics payloads are not stored in the recovery reporting tables.
5. Sub-processors
The Controller provides general authorization for the Processor to engage the following sub-processors:
| Sub-processor | Purpose | Location |
|---|---|---|
| Bunny.net | Cloud infrastructure for proxy servers | Global Edge Network |
| PayPal | Payment processing (Controller data only) | USA / Global |
The Processor shall notify the Controller of any intended changes to sub-processors, giving the Controller the opportunity to object.
6. International data transfers
The Processor uses Bunny.net’s global edge network for request forwarding. Limited operational and reporting records are stored separately:
- Processing includes temporary session identifiers and recovery-reporting metadata
- Retention and scheduled cleanup are described in the Privacy Policy
- Standard Contractual Clauses are available upon request for compliance purposes
7. Data breach notification
In the event of a security incident that could affect the Controller's data, including retained session and recovery-reporting records, the Processor will:
- Notify the Controller without undue delay (and within 72 hours where feasible)
- Provide available information about the nature of the incident
- Cooperate with the Controller's investigation
8. Audit rights
The Processor shall make available to the Controller all information necessary to demonstrate compliance with Article 28 obligations. The Controller may conduct audits, including inspections, provided reasonable notice is given and such audits do not disrupt the Processor's operations.
9. Termination
Upon termination of the service:
- No End-User Personal Data requires deletion (as none is retained)
- Controller account data will be deleted immediately upon request
- The Processor will cease all processing related to the Controller
10. Controller responsibilities
The Controller acknowledges and agrees that:
- The Controller is responsible for ensuring lawful basis for processing End-User data
- The Controller must obtain any necessary consents from End-Users
- The Controller's privacy policy must accurately describe the use of proxy services
- The Controller shall not use the service in violation of applicable data protection laws
11. Contact
For any questions regarding this Data Processing Agreement:
Email: hello@introtrace.com
Introtrace is a service operated by independent developers based in the European Union.