Skip to content
Wrenform

Legal

Data processing agreement

Last updated 2026-11-15

Version 1.0. This data processing agreement (“DPA”) forms part of the terms of service and meets the requirements of Article 28 of the GDPR and UK GDPR.

1. Parties and acceptance

  • Controller: the Wrenform customer that accepts this DPA (“you”).
  • Processor: Ihab Tag, trading as Qamarita Lab, based in Egypt, operator of Wrenform (“we”). Contact: hello [at] wrenform.com.

You accept this DPA by clicking to accept it in your account settings in the dashboard. We record the version and the time. If you need a signed PDF copy, email hello [at] wrenform.com. Where this DPA and the terms conflict about personal data, this DPA wins.

2. Subject matter, duration, nature and purpose

  • Subject matter: the processing of personal data contained in submissions to your forms, and in the notifications and webhooks we send about them.
  • Duration: for as long as you use Wrenform, and until the data is deleted under section 10.
  • Nature: receiving, filtering for spam, storing, displaying, exporting, emailing to your verified recipients, sending to your webhooks, and deleting.
  • Purpose: to provide the Wrenform form backend to you, as described in the terms and the docs.

3. Categories of data and data subjects

  • Data subjects: visitors to your websites who submit your forms, and anyone whose data they include.
  • Categories of personal data: whatever fields you choose to collect in your forms (typically name, email address, phone number and message), plus metadata about each submission: the origin and referring page, the browser user agent, a keyed hash of the IP address, and the time. We keep no web request logs. Our hosting provider and Cloudflare may process IP addresses transiently to deliver and protect the service.
  • Special categories: you must not use Wrenform to collect special-category data, passwords, payment card data or government ID numbers (see the acceptable-use policy).

4. Instructions

We process the personal data only on your documented instructions: this DPA, the terms, and your settings in the dashboard. If we believe an instruction breaks data protection law, we'll tell you. If the law requires us to process data otherwise, we'll tell you first unless the law forbids it.

5. Confidentiality

Everyone who can access the personal data on our side (today, the operator) is bound by confidentiality. We don't read submissions except to support you at your request, to investigate abuse, or where the law requires.

6. Security measures (Art. 32)

  • Encryption in transit: TLS for all traffic, including our email and webhook deliveries.
  • Encryption at rest: encrypted nightly backups; secrets such as webhook secrets and Turnstile keys encrypted in the database (AES-256-GCM).
  • IP addresses stored only as keyed hashes, with the key rotated every 30 days.
  • Access control: production access limited to the operator, with key-based authentication.
  • Isolation: databases aren't reachable from the internet.
  • Resilience: nightly encrypted backups kept for 30 days, with restore tests.
  • Abuse controls: rate limits, recipient verification by double opt-in, sending caps, and review of suspicious forms.
  • Monitoring: error tracking with personal data scrubbed, and uptime monitoring.

More detail is on the security page. We may improve these measures over time, but never lower the overall level of protection.

7. Subprocessors

You give us general authorisation to use the subprocessors on our subprocessor list. We bind each one by written contract to data protection obligations at least as protective as this DPA, and we remain responsible for them. We give you at least 30 days' notice of any new or replacement subprocessor, by email to paying customers and on the subprocessor page. You may object on reasonable data protection grounds; if we can't resolve it, you may cancel and get a refund of any prepaid time you haven't used.

SubprocessorPurposeLocationTransfer safeguard
Contabo GmbH (Germany)Server hosting; stores submissions and account dataFrance (EU)Within the EU/EEA; no transfer
CloudflareDNS, network and DDoS protection (all traffic passes through its network in transit)Global edge network (United States company)Provider's DPA with Standard Contractual Clauses and/or the EU–US Data Privacy Framework
Cloudflare R2Encrypted nightly database backups, kept 30 daysCloudflare R2, Western Europe location; encrypted on our server before upload, so Cloudflare cannot read itCloudflare's DPA with Standard Contractual Clauses
Zoho ZeptoMail (Zoho CPaaS)Sends sign-in emails and submission notificationsUnited States (Zoho's US data centre)Provider's DPA with Standard Contractual Clauses and/or the EU–US Data Privacy Framework
Zoho MailOur mailboxes for support, abuse, security and DMARC emailUnited States (Zoho's US data centre)Provider's DPA with Standard Contractual Clauses and/or the EU–US Data Privacy Framework
SentryError tracking for the app and background jobsEU (Sentry's EU data region)Within the EU/EEA; no transfer
PostHogCookieless product analyticsEU (PostHog Cloud EU)Within the EU/EEA; no transfer
Better StackUptime monitoring and the public status pageEU-based provider (Czech Republic)Provider's DPA; Standard Contractual Clauses for any processing outside the EU

Not subprocessors, listed so the picture is complete:

  • Paddle.com Market Limited (UK) sells our subscriptions as merchant of record. It is the seller and handles payments under its own privacy notice.
  • Google only if you choose "Sign in with Google": Google confirms who you are under its own privacy policy.

8. International transfers

  • Submissions are stored in the EU.
  • Where a subprocessor processes personal data outside the EU/EEA or UK (Zoho ZeptoMail and Zoho Mail in the US, and Cloudflare, including the backups in Cloudflare R2, which are encrypted before upload), the transfer is covered by that subprocessor's data processing agreement, using the EU Standard Contractual Clauses and/or the EU–US Data Privacy Framework (and the UK Addendum or UK extension where relevant).
  • The operator is based in Egypt and may access the data from there to run and support the service. To the extent that access is a transfer from the EU/EEA, the parties agree to the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Two (controller to processor), which are incorporated into this DPA by reference, with this DPA supplying the details of their annexes.

9. Assistance

  • Data subject rights: the dashboard lets you find, export and delete submissions. If a data subject contacts us directly about your forms, we pass the request to you without undue delay and help you respond.
  • Other obligations: we help you, as reasonably needed, with security, impact assessments and consultations with supervisory authorities (Articles 32 to 36).
  • Personal data breaches: we notify you within 48 hours of becoming aware of a breach affecting your data, with what we know and the steps taken, and keep you updated.

10. Deletion at the end

Submissions are deleted on the retention schedule you set for each form. When you delete your account, we delete all your data within 24 hours, and it ages out of our backups within 30 days. You can export your submissions to CSV before you go. We don't keep copies unless the law requires it.

11. Information and audits

On request, we give you the information you reasonably need to show compliance with Article 28, including answers to security questionnaires. Where that isn't enough, you may audit us once a year, with 30 days' notice, at your cost, in a way that protects other customers' data and our security.

12. Liability and term

The liability terms of the terms of service apply to this DPA, except where data protection law doesn't allow it. This DPA lasts as long as we process personal data for you.

Version

Version 1.0. We'll notify you of changes to this DPA by email at least 30 days before they take effect.