This Data Processing Agreement ("DPA") forms part of the Terms of Use between Painless Content (operated by Pure App Studio) ("Processor") and the business customer ("Controller") and governs the processing of personal data on behalf of the Controller.
In this DPA, the following terms have the meanings set out below. Terms not defined here carry the meanings given in the GDPR.
| Term | Meaning |
|---|---|
| Controller | The business customer that determines the purposes and means of processing personal data. |
| Processor | Painless Content (operated by Pure App Studio), which processes personal data on behalf of the Controller. |
| Data Subject | An identified or identifiable natural person whose personal data is processed. |
| Personal Data | Any information relating to an identified or identifiable natural person. |
| Processing | Any operation performed on personal data (collection, storage, use, disclosure, deletion, etc.). |
| Sub-Processor | Any third party engaged by the Processor to carry out processing activities on behalf of the Controller. |
| GDPR | Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016. |
| UK GDPR | The GDPR as retained in UK law by the European Union (Withdrawal) Act 2018. |
Subject matter: The Processor provides a content-repurposing SaaS platform delivered via Telegram bot and web application. In doing so, the Processor processes personal data submitted by or on behalf of the Controller's end users.
Duration: This DPA remains in force for the duration of the subscription agreement between the parties and terminates automatically upon expiry or termination of that agreement, subject to Section 11 (Deletion and Return).
Nature and purpose: Processing is carried out to provide, maintain, and improve the Painless Content service, including generating platform-specific content from voice notes and text inputs provided by end users.
The Processor processes the following categories of personal data on behalf of the Controller:
| Category | Examples | Data Subjects |
|---|---|---|
| Account identifiers | Name, email address, OAuth provider ID | Controller's end users |
| Content inputs | Text messages, voice note transcriptions submitted to the bot | Controller's end users |
| Usage data | Daily repurpose counts, platform selections, session timestamps | Controller's end users |
| Payment identifiers | Stripe customer ID, subscription ID (no raw card data) | Controller's billing contacts |
| Communication data | Feedback form submissions, contact form messages | Controller's end users |
The Processor does not intentionally collect special categories of personal data (Article 9 GDPR). The Controller must not submit special category data through the service without prior written agreement.
The Controller warrants and undertakes that:
The Processor shall, in relation to personal data processed on behalf of the Controller:
The Controller grants general authorisation for the Processor to engage the following Sub-Processors. The Processor will notify the Controller of any intended changes (additions or replacements) at least 30 days in advance, giving the Controller the opportunity to object.
| Sub-Processor | Purpose | Location | Safeguard |
|---|---|---|---|
| Manus (AI Platform) | LLM inference, storage, OAuth, notifications | United States | Standard Contractual Clauses (SCCs) |
| Stripe, Inc. | Payment processing, subscription management | United States | SCCs + Privacy Shield successor framework |
| Resend, Inc. | Transactional email delivery | United States | SCCs |
| TiDB Cloud (PingCAP) | Managed MySQL-compatible database | United States | SCCs |
| AWS (Amazon Web Services) | Object storage (S3) for user-uploaded assets | United States | SCCs |
| Telegram Messenger | Bot delivery channel | UAE / Global | Terms of Service; no personal data stored by Telegram beyond message delivery |
The Processor shall impose data protection obligations on each Sub-Processor equivalent to those set out in this DPA. The Processor remains fully liable to the Controller for the performance of Sub-Processors' obligations.
Where personal data is transferred to a country outside the European Economic Area (EEA) or the United Kingdom that does not benefit from an adequacy decision, the Processor shall ensure that appropriate safeguards are in place in accordance with GDPR Article 46, including Standard Contractual Clauses (SCCs) as approved by the European Commission (Decision 2021/914) and, for UK transfers, the UK International Data Transfer Agreement (IDTA) or Addendum.
The Processor maintains the following technical and organisational security measures:
| Measure | Implementation |
|---|---|
| Encryption in transit | TLS 1.2 or higher on all API endpoints and web interfaces |
| Encryption at rest | AES-256 encryption for database storage via TiDB Cloud |
| Access control | Role-based access; admin procedures gated by server-side role check |
| Session management | JWT sessions with 7-day TTL; secure, HttpOnly, SameSite=Strict cookies |
| Rate limiting | Per-IP rate limits on all API endpoints to prevent abuse |
| Dependency management | Regular dependency audits; automated vulnerability scanning |
| Incident response | Documented breach response procedure; 72-hour GDPR notification target |
The Processor shall assist the Controller in responding to data subject rights requests within the timescales required by applicable law. Upon written request, the Processor will:
In the event of a personal data breach affecting data processed under this DPA, the Processor shall notify the Controller without undue delay and, where feasible, within 48 hours of becoming aware of the breach. The notification shall include, to the extent available:
The Controller remains responsible for notifying the relevant supervisory authority within 72 hours under Article 33 GDPR and, where required, notifying affected data subjects under Article 34 GDPR.
Upon termination or expiry of the subscription agreement, the Processor shall, at the Controller's election:
The Processor may retain personal data beyond this period only to the extent required by applicable law (e.g., financial records retention obligations), and shall inform the Controller of any such retention.
The Controller may, upon reasonable written notice of at least 14 days, conduct an audit or inspection of the Processor's data processing activities covered by this DPA, either directly or through a mutually agreed third-party auditor. The Controller shall bear the costs of any such audit unless the audit reveals a material breach by the Processor.
As an alternative to a direct audit, the Processor may provide relevant third-party audit reports, certifications, or security assessments to satisfy the Controller's audit rights, subject to confidentiality obligations.
Each party's liability under this DPA is subject to the limitations and exclusions set out in the Terms of Use. Where both parties are responsible for damage caused by processing in breach of GDPR, each party shall be held liable for the damage attributable to its own breach, in accordance with Article 82 GDPR.
This DPA is governed by the laws of England and Wales (for UK/EU customers) or the laws of the State of Delaware, USA (for US customers), consistent with the governing law clause in the Terms of Use. Any disputes shall be resolved in accordance with the dispute resolution provisions of the Terms of Use.
This DPA is incorporated by reference into the Terms of Use. By subscribing to Painless Content and accepting the Terms of Use, the Controller agrees to the terms of this DPA on behalf of the business entity it represents.
For enterprise customers requiring a countersigned DPA or custom amendments, please contact [email protected]. We aim to respond within 5 business days.
Enterprise customers can request a countersigned copy of this DPA for their compliance records. Complete the form below and we will respond within 2 business days.
Prefer email? [email protected]