Reviewed Jul 2026

Privacy and Data Protection Notes

A practical overview of how Pabble should discuss privacy responsibilities without claiming verified GDPR compliance unless formal documentation exists.

Current Status

This page is not a GDPR compliance certification. It is a public note about privacy and data protection responsibilities while Pabble is in beta.

Pabble should not claim GDPR compliance, data residency, subprocessor commitments, breach notification timelines, or a formal Data Processing Agreement unless those documents are completed and approved.

Privacy responsibility diagram

Show the relationship between a Pabble customer, form respondents, submitted responses, and configured integrations.

Recommended visual: 1440 x 900

Customer Responsibilities

Teams using Pabble are responsible for deciding what information they collect, why they collect it, and what they tell respondents before submission.

For forms that collect personal data, customers should:

  • Ask only for information they need
  • Explain how responses will be used
  • Avoid collecting sensitive data unless they have a clear process for handling it
  • Review configured integrations because external tools may process response data outside Pabble

Pabble Responsibilities

Pabble should provide clear product controls for form creation, response review, deletion, export, and integration configuration. Public documentation should describe only the controls that exist in the product.

Related Resources