Data Processing Addendum
How Perforla processes personal data inside your websites on your behalf, under the GDPR, the UK GDPR and US state privacy laws.
Last updated Nov 2, 2026
1. About this addendum
This Data Processing Addendum ("DPA") forms part of the Terms of Service between you ("Customer") and Perforla LLC ("Perforla"). It applies automatically when Perforla processes Customer Personal Data in providing the Service; no signature is needed. If you need a countersigned copy for your records, write to legal@perforla.com.
If this DPA conflicts with the Terms, this DPA prevails on the processing of personal data. If it conflicts with the Standard Contractual Clauses, the Standard Contractual Clauses prevail.
2. Definitions
- Data Protection Laws means the laws that apply to the processing of Customer Personal Data under the Terms, including the EU General Data Protection Regulation 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and US state privacy laws such as the California Consumer Privacy Act as amended ("CCPA").
- Customer Personal Data means personal data in Your Content (as defined in the Terms) that Perforla processes on Customer’s behalf — for example, information about the visitors, customers and users of Customer’s websites.
- Controller, processor, data subject, personal data breach and processing have the meanings given in the GDPR; "service provider" and "business" have the meanings given in the CCPA.
- Standard Contractual Clauses or SCCs means the clauses approved by the European Commission in Implementing Decision (EU) 2021/914.
- Subprocessor means another processor engaged by Perforla to process Customer Personal Data.
3. Roles
Customer is the controller (or a processor acting for its own clients) of Customer Personal Data, and Perforla is its processor (or subprocessor). Under the CCPA, Perforla is Customer’s service provider. Customer is responsible for having a lawful basis for the data it collects through its websites and for the instructions it gives Perforla.
4. Perforla’s obligations
Perforla will:
- process Customer Personal Data only on Customer’s documented instructions — the Terms, this DPA and Customer’s use and configuration of the Service are those instructions — unless the law requires otherwise, in which case Perforla will tell Customer first where the law allows;
- tell Customer if it believes an instruction breaks Data Protection Laws;
- not sell or share Customer Personal Data, and not retain, use or disclose it outside the direct business relationship with Customer or for any purpose other than providing the Service;
- ensure that everyone authorised to process Customer Personal Data is bound by confidentiality;
- keep the technical and organisational measures in Annex II in place, and not reduce their overall protection;
- help Customer, taking into account the nature of the processing, to respond to requests from data subjects, and to carry out data protection impact assessments and prior consultations where Data Protection Laws require them;
- make available the information reasonably needed to show compliance with this DPA, as described in section 9.
5. Subprocessors
Customer authorises Perforla to engage the subprocessors listed on the Subprocessors page. Perforla binds each subprocessor by a written agreement with data protection obligations no less protective than this DPA, and remains responsible for its subprocessors’ performance.
Perforla will announce any new subprocessor on that page, and by email to customers who ask for notice at privacy@perforla.com, at least 30 days before it begins processing Customer Personal Data. Customer may object on reasonable data protection grounds within that period. If Perforla cannot reasonably address the objection, Customer may end the affected part of the Service and receive a refund of prepaid fees for the period after it ends.
6. Security and personal data breaches
Perforla will notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice will describe, as far as then known, what happened, the data and data subjects affected, the likely consequences and the steps taken. Perforla will take reasonable steps to contain and remedy the breach and will keep Customer updated as more becomes known. Notifying a breach is not an admission of fault.
7. Deletion and return
Customer can download its websites, including their databases, at any time through the panel. When the Service ends, Perforla will delete Customer Personal Data within 60 days of the end of the paid period, except where the law requires Perforla to keep it, in which case it stays protected under this DPA for as long as it is kept.
8. International transfers
Perforla processes Customer Personal Data in the United States and may transfer it to the countries where its subprocessors operate, as shown on the Subprocessors page.
- EEA. Where Customer Personal Data is transferred from the European Economic Area to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference: Module Two (controller to processor) where Customer is a controller, and Module Three (processor to processor) where Customer is a processor. Clause 7 (docking) applies; under Clause 9, option 2 (general written authorisation) applies with the notice period in section 5; the optional wording in Clause 11 does not apply; under Clauses 17 and 18 the law and courts of Ireland apply. Annexes I and II of this DPA complete the SCCs’ annexes, and Annex III is the Subprocessors page.
- United Kingdom. Transfers from the UK are made under the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner, incorporated by reference, with the information in its tables taken from this DPA.
- Switzerland. For transfers from Switzerland, the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as the competent supervisory authority.
9. Audits
Perforla will answer Customer’s reasonable written questions about its processing and security, and will make available summaries of relevant third-party certifications held by its subprocessors. If that is not enough to show compliance, or if a supervisory authority requires it, Customer may audit Perforla once a year, at Customer’s cost, with at least 30 days’ notice, during business hours, under confidentiality, and without access to other customers’ data.
10. Liability
Each party’s liability under this DPA is subject to the limits in the Terms of Service, except where Data Protection Laws do not allow those limits.
Annex I — Details of the processing
| Item | Details |
|---|---|
| Data exporter | Customer, the account holder named in the Perforla panel |
| Data importer | Perforla LLC, contact privacy@perforla.com |
| Importer’s address | 447 Broadway 2nd Floor #316, New York, NY 10013 |
| Subject matter | Hosting, securing, backing up and supporting Customer’s WordPress websites |
| Duration | For the term of the Terms of Service, then until deletion under section 7 |
| Nature and purpose | Storage, hosting, transmission, backup, restoration, caching, monitoring, email relay and support, as needed to provide the Service |
| Data subjects | Visitors, customers, users, subscribers and contacts of Customer’s websites; Customer’s staff whose data is stored in those websites |
| Categories of personal data | Whatever Customer’s websites collect: typically names, email and postal addresses, phone numbers, IP addresses, account credentials, order and form details, and messages |
| Special categories | Not intended. Customer will not use the Service to process special category data unless it puts appropriate safeguards in place |
| Frequency | Continuous |
| Competent supervisory authority | Determined under Clause 13 of the SCCs |
Annex II — Technical and organisational measures
- Encryption. All traffic to the panel and to websites is encrypted in transit with TLS. Portable backups are encrypted with AES-256-GCM by Perforla before they are stored.
- Separation of customers. Every customer’s records are separated in the database by row-level security, enforced by the database itself, not only by the application.
- Access control. Customer accounts use passwords stored with a slow one-way hash, a one-time email code on unfamiliar browsers, and a fresh password check before actions that open a way into a site. Team members have roles and can be limited to particular sites. Perforla staff use a separate sign-in with one-time codes, permissions by role, and every staff action is recorded in an append-only log.
- Secrets. Keys and credentials are held only on Perforla’s servers, never in browsers, logs or AI prompts.
- Backups and recovery. Two independent backup layers: backups kept beside each site for fast restores, and portable copies in separate storage that can be restored anywhere. Portable backups are read back and verified every week, and full restores onto plain WordPress are tested.
- Monitoring. Every live website is checked from outside every four minutes, and Perforla’s records are compared with the infrastructure every hour to catch anything out of place.
- Change management. Every release passes an automated suite of thousands of tests and a code review before it reaches production.
- Incident response. Security issues are investigated and contained by a named owner, and affected customers are notified as described in section 6.
- Data minimisation. Logs record what happened, not message contents or card data; email message text is cleared after 7 days unless the customer keeps copies.
Annex III — Subprocessors
The current list is on the Subprocessors page.
