Legal

Data Processing Agreement

When people answer your forms, we process their personal data on your behalf. This is the contract that governs how — required by Article 28 GDPR, and part of our Terms for every customer automatically.

Last updated 23 July 2026

1. What this is, and who it binds

This Data Processing Agreement (the "DPA") is between you — the customer who holds a ClarNow account, the controller — and us, the processor:

Kostiantyn Poliakov, sole trader (empresario individual / autónomo), trading as ClarNow
Tax ID: Z0047241G
Carrer de Rius i Taulet, 14, 1-1, 08970 Sant Joan Despí
Barcelona, Spain
[email protected]

This DPA is part of our Terms of Service and applies to every customer from the moment you create an account or accept the Terms — no signature needed. If it conflicts with the Terms on a data protection matter, this DPA wins. It stays in force for as long as we process personal data for you.

If your procurement or vendor-review process needs a countersigned copy, email [email protected] and we'll send one. It will be this same text.

2. Definitions

"Controller", "processor", "data subject", "personal data", "processing" and "personal data breach" mean what Article 4 GDPR says they mean. "GDPR" means Regulation (EU) 2016/679 and, where it applies to you, the UK GDPR as defined in the UK Data Protection Act 2018. "Respondent" means a person who submits, or starts to submit, an answer to a form you built with ClarNow. "Tracking integration" means a third-party script or pixel (for example a Facebook Pixel or a Google Tag Manager container) that you choose to enable on a specific form, using your own account with that provider.

3. What processing this covers

This DPA covers the personal data we process on your behalf: your respondents' form answers, the files they upload, and the submission metadata that comes with them. Annex I describes it precisely — the categories of data and data subjects, the nature and purpose of the processing, and how long it lasts.

It does not cover the data we hold about you as our own customer — your account, billing and usage data. There we are the controller, and our Privacy Policy applies instead. Nor does it cover what happens inside an AI provider or any other integration you connect with your own account or key, or inside a tracking integration you enable on a form — see section 7.

4. Processing on your instructions

We process your respondents' data only on your documented instructions, and only to provide the service. Your instructions are: this DPA, the Terms, and the actions you take in the product — building a form, sharing it, exporting responses, connecting an integration, enabling a tracking integration on a form, deleting data. Enabling a tracking integration is your instruction to load that specific script, using your own account with that provider, on that specific form only — it is your decision to make and yours to have a legal basis for. You can add further written instructions by email, and we may charge a reasonable fee where following them requires work beyond running the service.

If a law of the EU or an EU member state requires us to process the data in some other way, we will tell you before we do — unless that law forbids us from telling you on important grounds of public interest. If we believe an instruction of yours infringes the GDPR, we will pause it and tell you immediately.

We do not sell response data, we do not use it for advertising, and we do not use it to train AI models.

What our assistance costs

The product already lets you do most of this yourself: search, export, correct and delete responses, delete forms, close the workspace. Where you can do a thing in the product, doing it is free and it is the route we expect you to take.

Where you instead ask us to do work by hand — the assistance in sections 8, 9, 10 and 11, security questionnaires, vendor-review forms, DPIA input, bespoke reports, evidence-gathering, or acting on an instruction that goes beyond running the service — we may charge a reasonable fee for the time spent, at our then-current rates, and we will tell you the estimate before we start. We are not obliged to begin chargeable work before you accept the estimate.

One exception, and it is absolute: notifying you of a personal data breach under section 10 is never chargeable and is never delayed or withheld over a fee or an unpaid invoice.

5. Your responsibilities

As controller, you are the one who decides why and how respondents' data is collected. That means you warrant that:

  • you have a lawful basis for everything your forms collect, and you obtain consent where consent is the basis;
  • you give your respondents the privacy information Articles 13 and 14 GDPR require;
  • your instructions to us comply with data protection law;
  • you handle special categories of data (health, beliefs, and so on) only where Article 9 GDPR permits you to — knowing that ClarNow applies one uniform level of protection, the measures in Annex II, whatever a form collects. We offer no heightened or separate safeguards for sensitive data, and you decide, on that basis, whether ClarNow is appropriate for what you are asking people;
  • you are responsible for the people you give access to your workspace — what they do with respondents' data, the exports they take and the integrations they connect are your acts, not ours;
  • if you enable a tracking integration (a Facebook Pixel, a Google Tag Manager container, or any other one we later add) on a form you publish, obtaining your respondents' consent before it fires, and having a lawful basis for it, is entirely your responsibility — whether through a consent banner we may offer you as an optional tool, your own consent management platform, a consent step inside your own Tag Manager container, or any other method you choose. We do not verify that consent was obtained, and we are not liable if it wasn't. The choice to enable the integration is yours, and so is making it lawful.

Answering data subjects, notifying supervisory authorities, and defending your processing are your responsibilities; sections 8 and 10 describe how we help.

Data you must not put into ClarNow

ClarNow is a general-purpose form product. It is not built, certified or priced for regulated high-risk data, and you must not use it to collect or store ("Prohibited Data"):

  • protected health information subject to HIPAA, or data under an equivalent sectoral health-data regime;
  • full payment card numbers, CVV/CVC codes or magnetic-stripe data — use the Payment field, which sends card data straight to Stripe and never through us;
  • government identifiers used for identity verification — passport, national ID, social security or equivalent numbers — and scans or photographs of such documents;
  • biometric or genetic data used to identify a person;
  • personal data of children below the age of digital consent in their country, unless you hold verifiable parental consent and can evidence it;
  • data subject to export control, national security or classification rules.

We do not monitor forms for Prohibited Data and have no practical means of detecting it. If it reaches us anyway, the risk is yours: our obligations and our liability in respect of that data are no greater than for ordinary response data, section 14 applies, and we may remove the data or suspend the form once we become aware of it.

Sending form data to an LLM of your choice

ClarNow offers an MCP server that lets an LLM client you connect yourself — such as Claude or ChatGPT, or your own agent — read and manage your forms, including respondents' answers. You connect it either by signing in through OAuth (Claude, ChatGPT and other clients that support it) or by issuing an API key for clients that don't. Either way, connecting the client is your documented instruction under this section: the client, and whatever provider stands behind it, is your choice, not ours, and what that provider does with the data it receives is governed by your agreement with them, not this DPA. Disconnecting the client — revoking the OAuth grant or the API key — is how you stop the transfer.

6. Confidentiality

Everyone we authorise to process respondents' data is bound by confidentiality — contractually, or by a statutory duty. Today production access is limited to a very short list of people, and we keep it that way.

7. Subprocessors

You give us general written authorisation to use subprocessors. The current list — provider, purpose, data and location — is the Subprocessors table at clarnow.com/subprocessors, which is Annex III of this DPA. Every subprocessor on it is bound by a written agreement imposing data protection obligations equivalent to this DPA's, and we remain fully liable to you for their work. The providers you connect yourself, shown in a separate table on that page, are not subprocessors — see the note at the end of this section.

We update that page before a new subprocessor starts processing respondents' data, and we email every account holder to tell you — you don't have to subscribe to anything to get that notice. You may object to a new subprocessor on reasonable data protection grounds within 30 days of that notice. If you object, we'll make reasonable efforts to offer a change of approach that avoids the subprocessor. If within a further 30 days we haven't — and we are not obliged to redesign the service, retain a more expensive provider, or degrade it for other customers — either of us may terminate the affected part of the service on written notice. Your only refund in that case is the unused portion of fees you have already prepaid for that part of the service, calculated pro rata from the termination date.

Objecting does not suspend the change, does not entitle you to withhold fees, and does not by itself put us in breach of this DPA. Termination and that pro-rata refund are your sole and exclusive remedies for an objection under this section.

Changing how a subprocessor already on the list runs is not the addition or replacement of a subprocessor, and does not trigger the notice or objection process above. That includes moving your data between the EU regions of a provider we already use, and changing the technology we run on one of them — for example the database engine or storage service we operate on Google Cloud — as long as the subprocessor stays the same and your data stays in the EEA. Removing a subprocessor we no longer use is likewise nothing you need to object to: we simply update the page.

A different case is a subprocessor we engage only for an optional feature that processes your own account data — not your respondents' answers — and that you choose to turn on, such as an AI assistant that helps you build a form. There, not enabling the feature is how you decline: the subprocessor behind it only ever receives your data if you use the feature, so if it isn't for you, leave it off and no data reaches it. For a feature of that kind, non-use replaces the terminate-and-refund process above — that process is for subprocessors you cannot avoid by a setting, and this is not one of them. Objecting on reasonable data protection grounds still gets you our safeguards in writing; it does not oblige us to drop a provider that only ever processes the data of customers who switched the feature on.

The providers shown in the two separate tables on that page — AI providers (Anthropic, OpenAI, Google's Gemini API, Groq) and the other integrations you can connect with your own account (CRM, email, helpdesk, task and similar tools) — are not subprocessors and form no part of Annex III. They only ever receive data if your organisation connects one with your own account or key, and then only the one you connect. Connecting one is a documented instruction from you under section 4 to send that feature's data to it, and because the account is yours, your agreement with the provider — not this DPA — governs what happens to the data there. The authorisation and objection mechanism above therefore does not apply to them: the choice is yours to make, and yours to reverse by disconnecting the provider.

The third table on that page — tracking integrations you can enable on a form you publish (a Facebook Pixel, a Google Tag Manager container, and any other we later add) — is also not subprocessors and no part of Annex III, for the same reason. The difference is where it runs: it loads directly in your respondent's browser, using your own pixel or container ID, only on the specific form where you turn it on. Enabling it is your documented instruction under section 4, section 5 sets out your consent and lawful-basis obligations for it, and the provider's own agreement with you — not this DPA — governs the data it receives.

8. Data subjects' rights

If a respondent contacts us to exercise their GDPR rights over answers they gave to your form, we won't act on the request ourselves — it's your data, and your decision. We will forward the request to you without undue delay, along with anything relevant we hold.

Taking into account the nature of the processing, we will assist you in fulfilling those requests with appropriate technical and organisational measures — in practice, the product lets you search, export, correct and delete individual responses yourself, which covers essentially every request without our involvement. That self-service capability is how we discharge this obligation. Where you ask us to run a request by hand instead, section 4 applies to the cost.

Verifying that a requester is who they say they are, deciding whether a right applies, and answering within the statutory deadline are yours. We do not assess the merits of a request and we are not liable for a deadline you miss, including where you asked us for assistance late in your own window.

9. Security

We implement the technical and organisational measures described in Annex II, appropriate to the risk under Article 32 GDPR, and we will not materially weaken them while this DPA is in force. We may change or replace an individual measure as the product and the threat landscape evolve, provided overall security is not materially reduced.

Taking into account the nature of the processing and the information available to us, we will reasonably assist you with your own obligations under Articles 32 to 36 GDPR — security, breach notification, and data protection impact assessments. That assistance is scoped to information we actually hold about how ClarNow processes your data; it is not an obligation to produce certifications, penetration-test reports, audit opinions or bespoke documentation we do not have, and section 4 applies to its cost.

Annex II describes the measures as they stand today, and we keep our own Article 32 assessment current — that duty is ours and this section does not pass it to you. Article 32 also applies to you in your own role, though: you know what your forms collect and how sensitive it is, we don't. Annex II is published so you can make that assessment, and choosing to run a particular kind of collection on ClarNow is your decision about your own risk.

10. Data breaches

If we become aware of a personal data breach affecting your respondents' data, we will notify you without undue delay — first, so you can meet your own 72-hour deadline — and give you what Article 33(3) GDPR requires: what happened, the categories and approximate numbers of data subjects and records affected, the likely consequences, and what we are doing about it, supplementing as we learn more. We will reasonably cooperate with your investigation and remediation.

We bear our own costs of investigating and remediating a breach caused by our failure to meet this DPA. Beyond that, the cost of your investigation, your notifications, your advisers, your remediation, and any extended support you ask of us is yours — including where the breach originated with you: credentials of your workspace users, an integration you connected, a webhook you pointed somewhere, or Prohibited Data you put into ClarNow. Notifying you is free and immediate either way (section 4).

Our notice to you is not an admission of fault or of liability under Article 82 GDPR, and we may make it while facts are still unclear without that counting against us.

Notifying your supervisory authority and your data subjects is your call and your responsibility — we won't do it on your behalf.

11. Audits

We will make available to you the information reasonably necessary to demonstrate compliance with this DPA — start by asking at [email protected]. Where written answers and documentation don't reasonably settle the question, you (or an independent auditor you mandate, who isn't our competitor) may audit us: at most once in any 12-month period, on 30 days' notice, during business hours, without disrupting the service, and at your cost — including our reasonable time at our then-current rates (section 4) — unless the audit finds a material breach of this DPA, in which case we bear the reasonable cost. A confirmed breach under section 10, or an instruction from your supervisory authority, justifies an additional audit.

An audit covers our processing of your respondents' data and nothing else. It gives no access to our source code, our infrastructure credentials, our own corporate or financial records, or any data belonging to another customer, and it does not extend to our subprocessors' premises or systems — for those we will pass on the audit rights and reports we hold under our agreements with them. The auditor must sign a confidentiality undertaking before starting, and findings are confidential to you.

12. International transfers

Respondents' data lives in the European Union — the database, the application and the files in the EU regions listed on the subprocessor page. Where a subprocessor involves a transfer outside the EEA (for example, US-based email delivery), it is covered by the European Commission's Standard Contractual Clauses and, where the provider is certified, the EU–US Data Privacy Framework. You can ask us for details of the safeguard behind any given transfer.

If you are outside the EEA

If you are established outside the EEA in a country without an adequacy decision, our sending your respondents' data back to you is itself a transfer. For that case, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Four (processor to controller), are incorporated into this DPA by reference, with us as data exporter and you as data importer, and:

  • Clause 7 (docking) and Clause 11 (independent redress) are not used;
  • in Clauses 17 and 18, Spanish law governs and the courts of Spain have jurisdiction;
  • Annex I of the SCCs is completed by Annex I below, with the parties as identified in this section and section 1.

If you are in the UK, the ICO's International Data Transfer Addendum to the EU SCCs (version B1.0, in force 21 March 2022) is incorporated by reference and amends the SCCs as its mandatory clauses require, with the tables completed by the same information.

13. Deletion & return of data

You can export your respondents' data from the product at any time while your account is open — that is how "return" works here. You can also delete individual responses, forms, or your whole workspace yourself, and deletion in the product is a deletion instruction under this DPA.

When your account closes, we delete its forms, responses and uploaded files within 30 days, and the copies in backups age out with the backup window shortly after. Closing the account is your instruction to delete; if you want an export, take it first. The only data that survives is our own controller data — billing records we are legally required to keep, as described in our Privacy Policy — which contains no respondent answers. We'll confirm deletion in writing if you ask.

14. Liability & governing law

Our liability under this DPA is subject to the same exclusions, limitations and monetary cap as the Terms. That cap is a single aggregate cap covering the Terms and this DPA together: claims under this DPA are not separate from claims under the Terms, do not get their own cap, and do not increase it.

Processing on your instructions

We are not liable for loss, claims, fines or damage that result from us processing respondents' data in accordance with your instructions (section 4), from the lawfulness of what you decided to collect, from the privacy information you did or did not give your respondents, or from a lawful basis you relied on and turned out not to have. Those are controller decisions, and you made them.

Your indemnity

You indemnify us, on the terms of section 9 of the Terms, against claims, fines and costs arising from your breach of this DPA or of your own obligations as controller under the GDPR — including a claim brought against us by one of your respondents in respect of data you collected, and any Prohibited Data reaching us under section 5.

Recourse between us

Where we pay compensation, a fine or costs for damage for which you are wholly or partly responsible, we are entitled to claim back from you the part corresponding to your share of responsibility, as Article 82(5) GDPR provides. The same right runs in your favour where you pay for damage we are responsible for, subject to the cap above.

Nothing in this section limits liability towards data subjects or supervisory authorities where the GDPR does not permit it to be limited; Article 82 GDPR governs that allocation. This DPA is governed by Spanish law, like the Terms.

15. Changes to this DPA

We may update this DPA as the product or the law changes — updated SCC sets, new guidance, new features. For a material change we will update the date at the top and email account holders at least 30 days before it takes effect; if you don't agree with a material change, you can close your account before it applies. Fixing typos or adding detail that doesn't reduce your protections takes effect on posting. Past versions are available on request.

Annex I — Description of the processing

Where the SCCs apply under section 12, this Annex also serves as Annex I.B of the SCCs; the parties (Annex I.A) are identified in sections 1 and 12, and the competent supervisory authority is the Spanish Data Protection Agency (AEPD).

Subject matter Hosting and processing of the responses submitted to the forms you build with ClarNow.
Duration For as long as you have a ClarNow account, plus the 30-day deletion window in section 13.
Nature of the processing Collection, storage, organisation, display, export, transmission to the integrations you connect, and deletion.
Purpose Providing the ClarNow service to you — nothing else.
Categories of data subjects Your respondents, and any third parties they mention in their answers.
Categories of personal data Whatever your forms ask for — typically names, contact details and free-text answers — plus uploaded files, payment identifiers (never card numbers) where you use the Payment field, and submission metadata: timestamps, referring page, URL parameters, embed context. We do not log respondents' IP addresses against their answers.
Sensitive data Only if your forms are designed to collect it, and only within the limits of section 5. Sensitive data receives the same measures as all other response data (Annex II) — there is no heightened regime — and Prohibited Data must not be submitted at all.
Frequency Continuous, as respondents submit forms.
Retention Until you delete it or close the account — see section 13.

Annex II — Technical and organisational measures

  • Encryption. All traffic is encrypted with TLS. Data is encrypted at rest by our hosting, database and storage providers.
  • Access control. Production access is limited to the people who need it — today a very short list — behind provider-level authentication. Session and identity cookies are HttpOnly; sessions are signed.
  • Data minimisation by design. Respondents' IP addresses are not logged against their answers. Payment card data never touches our infrastructure — Stripe collects it directly. A form carries no advertising or tracking script unless its owner deliberately enables one, and none loads by default.
  • Hosting. EU data centres run by providers holding ISO 27001 and SOC 2 certifications, with physical security handled at that level.
  • Availability and recovery. Managed, regularly-exercised backups with a rolling retention window; deleted data ages out of backups with that window.
  • Tenant isolation. Every piece of respondent data is bound to one workspace, and every query is scoped to it.
  • Incident response. A defined path from detection to customer notification, per section 10.
  • Confidentiality. Everyone with production access is bound by confidentiality obligations (section 6).
  • Review. We reassess these measures as the product and the threat landscape change, and won't materially weaken them (section 9).

Annex III — Subprocessors

The authorised subprocessor list is the Subprocessors table maintained at clarnow.com/subprocessors, which forms part of this DPA. Section 7 governs how it changes and how you can object.

The providers you can connect yourself — and the tracking integrations you can enable on a form you publish — listed in the two separate tables on that page, are not subprocessors and form no part of this Annex.