Netlas LLC is committed to safeguarding our users’ personal data and maintaining transparency in the management of third-party access. This document outlines the subprocessors engaged by Netlas LLC to support our services.
These subprocessors process limited personal data on our behalf for specific purposes in compliance with GDPR requirements. This document provides information on the subprocessors we engage, their roles, and the data they process. It is part of our broader commitment to transparency and GDPR compliance.
List of Subprocessors
The following subprocessors are engaged by Netlas LLC to perform specific functions:
| Subprocessor | Purpose | Categories of Data Processed | Location |
|---|---|---|---|
| Paddle.com | Payment service provider | Payment details, email addresses, transaction history | United States, EU |
| Pipedrive | Customer relationship management (CRM) | Customer names, email addresses, communication history | EU |
| Postmark (ActiveCampaign) | Email delivery for transactional messages | Customer names, email addresses, email content | United States |
| Cloudflare | Content delivery network, DDoS protection | IP addresses, request metadata, full access to transmitted data | Global |
How We Select Subprocessors
Netlas LLC selects subprocessors with the utmost care, ensuring they meet the following criteria:
- Compliance with GDPR: All subprocessors adhere to GDPR or equivalent data protection standards.
- Minimal Data Access: Subprocessors are granted access only to the personal data required to perform their specific services.
- Security Measures: Subprocessors maintain robust technical and organizational safeguards to protect data.
Notification of Changes
This document will be reviewed regularly and updated as necessary to reflect changes in our subprocessors or processing practices. We are committed to keeping you informed about changes to our subprocessors. In the event of changes, Netlas LLC will:
- Update this document to reflect the changes.
- Notify affected users via email or platform announcements at least 15 days in advance of the change (unless required sooner for immediate service delivery).