Data Processing Agreement

Last updated 2026-11-16

This Data Processing Agreement (the “DPA”) forms part of, and is incorporated by reference into, the agreement between the Customer and FormRill governing the Customer’s use of the FormRill service (the “Principal Agreement”, being our Terms). It reflects the parties’ agreement on the Processing of Personal Data by FormRill on behalf of the Customer in connection with the Services.

This DPA applies automatically when the Customer creates a workspace, and that acceptance has the same legal effect as a signature. The individual creating the workspace represents that they are authorised to bind the Customer. If you need a countersigned copy for your records, email [email protected].

1. Definitions and roles

“Customer” is the account holder and the controller (or data fiduciary or business) for the personal data its forms collect (“Customer Data”). “FormRill” is the operator of the FormRill service, acting as processor (service provider, contractor) for Customer Data. If the Customer is itself a processor for someone else, FormRill is its sub-processor and these terms pass through. Each is a “party” and together the “parties”.

“Data Protection Laws” means all laws applicable to the Processing of Customer Data, including the GDPR, the UK GDPR and Data Protection Act 2018, the CCPA/CPRA and other US state privacy laws, and India’s Digital Personal Data Protection Act, 2023. “Controller”, “Processor”, “Data Subject”, “Personal Data”, “Processing” and “Personal Data Breach” have the meanings given in the GDPR. “Sub-processor” means a third party engaged by FormRill to Process Customer Data. “Services” means the FormRill form-backend service, with its spam checking, email notifications, webhooks and Google Sheets delivery.

2. Details of processing (Annex 1)

Subject matter and purposeReceiving, spam-checking, storing and showing form submissions, delivering them to the email addresses, webhook URL or Google Sheet the Customer sets, and deleting them on instruction. This is the “business purpose” under the CCPA.
DurationWhile the Customer’s account exists, then deletion as set out in section 8
Data subjectsVisitors who submit the Customer’s forms
Categories of dataWhatever fields the Customer’s forms collect (typically name, email, message), browser user agent, spam signals. File uploads are ignored and not stored. Visitor IP addresses are not stored with submissions.
Sensitive dataNone intended. The Customer must not send special-category data, health data, government IDs or payment card numbers unless it has a lawful basis and has judged section 4 adequate for them. FormRill does not need such data to provide the Services.
LocationThe region the Customer picks (EU or US). Access from India for support and operations.

FormRill Processes Customer Data only on the Customer’s documented instructions: these terms, the settings the Customer chooses, and the Customer’s use of the dashboard and API. The one exception is processing required by law, and FormRill will tell the Customer about such a requirement first unless the law forbids it. FormRill will tell the Customer if it believes an instruction breaks data protection law. When the Customer sets notification emails, a webhook URL or a Google Sheet for a form, it instructs FormRill to send each new non-spam submission there; the Customer controls those recipients and is responsible for them, and FormRill cannot delete copies already delivered. The Customer also instructs FormRill to compare one-way hashes of long text fields across workspaces for one hour, solely to detect bulk spam campaigns. The Customer is solely responsible for the accuracy and legality of Customer Data and for having a valid legal basis to Process it.

3. Confidentiality

Only the operator has access to Customer Data. Anyone given access in future will be bound by confidentiality and will Process Customer Data only as instructed.

4. Security of Processing (Annex 2)

FormRill implements technical and organisational measures appropriate to the risk, including:

These measures may be updated with technical progress, provided an update does not materially reduce the overall level of security.

5. Sub-processors (Annex 3)

The Customer authorises the sub-processors listed in the privacy policy: Cloudflare, Inc. (hosting, databases, Turnstile, DNS lookups, rate limiting); Amazon Web Services (Amazon SES, for sign-in and submission notification emails, EU Ireland); and Google LLC (Sheets API, only for forms the Customer connects to a Google Sheet). FormRill binds each one by written contract to terms at least as protective as these, and remains responsible for them.

FormRill posts any new sub-processor at least 30 days in advance. The Customer may object on reasonable data-protection grounds; if the objection can’t be resolved, it may stop using the Services and delete its account.

Where the Customer enables a webhook, notification email address or Google Sheet, Customer Data goes to the Customer’s own chosen destination. Those destinations act as the Customer’s own processors or controllers and are not FormRill’s Sub-processors, except Google LLC for the Sheets delivery described above.

6. Data subject rights and cooperation

7. Personal Data Breach

FormRill notifies the Customer without undue delay, and within 48 hours of becoming aware of a Personal Data Breach affecting Customer Data. The notice covers what happened, the data and people affected, likely consequences and the measures taken. Updates follow as facts emerge. A notice is not an acknowledgement of fault or liability.

8. Return and deletion

The Customer can export and delete submissions at any time, or set a retention period per form. Account deletion removes Customer Data from the live databases at once, and backups roll off within 30 days. FormRill keeps no copy unless the law requires it.

9. Audits and information

FormRill makes available the information needed to demonstrate compliance with this DPA and Article 28 of the GDPR: this DPA, written answers to reasonable security questionnaires, and its sub-processors’ certifications (Cloudflare, AWS and Google hold SOC 2 and ISO 27001). If that isn’t enough, or if a regulator requires it, the Customer may audit once a year on 30 days’ notice, at its own cost, under confidentiality. Audits do not extend to the systems of Sub-processors.

10. Service-provider terms (CCPA/CPRA and US state laws)

FormRill will not:

FormRill complies with the CCPA and gives Customer Data the same level of protection the CCPA requires. It will tell the Customer if it can no longer meet these obligations, and the Customer may then take reasonable steps to stop and fix unauthorised use. FormRill also meets the processor duties in the Virginia, Colorado, Connecticut, Utah, Texas, Oregon and other state privacy laws: confidentiality, deletion or return, providing compliance information, assessments, and flowing these terms down to sub-processors.

11. International data transfers

FormRill operates from India. Data is stored in the Customer’s chosen region (EU or US) and may be Processed in other countries through its Sub-processors’ infrastructure.

12. Liability and order of precedence

Each party’s liability under this DPA is subject to the limits and exclusions in the Terms, except where the SCCs or law don’t allow them. If they conflict, the SCCs and other mandatory transfer clauses win, then this DPA, then the Terms. This DPA is governed by the same law and jurisdiction as the Terms, unless Data Protection Laws or the SCCs require otherwise. If a provision is held unenforceable, the rest stays in force. FormRill may update this DPA to reflect changes in law, Sub-processors or security measures, without materially reducing the protections given to the Customer; material changes are notified as set out in the Terms.