1. Who we are
ClarNow is a conversational form builder. It is a trading name, not a separate legal entity. The data controller is:
Kostiantyn Poliakov, sole trader (empresario individual / autónomo)
Tax ID: Z0047241G
Carrer de Rius i Taulet, 14, 1-1, 08970 Sant Joan Despí
Barcelona, Spain
[email protected]
We are established in Spain, so this policy is governed by the EU General Data Protection Regulation (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD). Our supervisory authority is the Spanish Data Protection Agency (AEPD).
We have not appointed a Data Protection Officer. We are not required to: we do not carry out large-scale monitoring, and we do not process special categories of data as a core activity. Privacy questions go to [email protected].
2. Our two roles
The distinction below decides who is responsible for what. It matters more than anything else on this page.
For your account — the data you give us when you sign up, pay us, email us, or browse clarnow.com. We decide why and how that data is processed, and sections 3 to 4 describe it.
For the answers people submit to your forms. You decide what to ask and why; we only store and process it on your instructions. You are the controller of that data, and you are the one your respondents will come to with their requests. See section 5.
3. What we collect as controller
Account data
When you create an account we store your email address, and — if you sign in with Google — your name and profile picture as Google returns them. We also record which sign-in method you used and when the account was created. We never receive your Google password.
Workspace and billing data
We store your organisation name, logo, team members and their invitations, plan tier, storage and response usage counters, and the identifiers Stripe assigns to your customer and subscription records. Your card number never reaches our servers — Stripe collects and stores it directly. We can see the billing details Stripe exposes to us: name, email, country, tax status, and the last four digits of the card.
Usage and technical data
When you use the app or browse this website, our infrastructure and analytics tools record your IP address, browser and device type, the pages you visited, and the actions you took. On clarnow.com, and in the app during the first day of a new account, we also record session replays — a reconstruction of your clicks and scrolling — through PostHog. Google Analytics counts visits and traffic sources on clarnow.com and, so that we can tell whether a visit led to a sign-up, inside the app as well. See section 6.
When you create an account we also record where you came from: the campaign
parameters on the link you followed (utm_source, utm_medium
and the like), the website that linked to us, if it told your browser to share that,
and the first page of clarnow.com you opened. To carry this from clarnow.com to the
app we keep it in your browser tab's session storage until the tab closes and add it
to the sign-up link; it is saved to your account once, when the account is created,
and never to anything else. We use it to understand which channels bring people to
ClarNow, on the basis of our legitimate interests, and it is not shared with
advertising or analytics providers. You can object at any time — see section 11.
Support communication
If you email us, we keep the message and our reply so we can help you and, if needed, show what was agreed.
4. Why we are allowed to do this
Under Article 6 GDPR, each activity rests on one of these grounds:
| What | Why | Legal basis |
|---|---|---|
| Account and workspace data | To give you the service you signed up for | Contract — Art. 6(1)(b) |
| Billing data and invoices | To take payment; to keep the books Spanish law requires | Contract — Art. 6(1)(b); Legal obligation — Art. 6(1)(c) |
| Server logs, abuse prevention, backups | To keep the service running, secure and recoverable | Legitimate interests — Art. 6(1)(f) |
| Analytics and session replay | To understand where the product confuses people | Consent — Art. 6(1)(a) |
| Service emails (receipts, security notices) | To administer your contract with us | Contract — Art. 6(1)(b) |
| Support correspondence | To answer you and keep a record | Legitimate interests — Art. 6(1)(f) |
| Billing identifiers, kept after account closure | To resolve billing disputes and defend legal claims | Legitimate interests — Art. 6(1)(f) |
Where we rely on legitimate interests, we have weighed them against your rights and concluded they do not override yours. You can object at any time — see section 11.
5. Form responses — data that isn't ours
When someone fills in a form built with ClarNow, we store what they typed, when they started and finished, the URL parameters and referring page that brought them there, whether the form was embedded, and any files they uploaded. If the form has a Payment field, we store the identifier of the Stripe payment, not the card.
We do not log respondents' IP addresses against their answers. We do not sell response data, we do not use it to advertise to anyone, and we do not use it to train AI models. We only process it to run the service and on the documented instructions of the customer who built the form.
If you answered someone's ClarNow form and want your data corrected or deleted, contact the organisation that ran the form — they are the controller and only they can decide. If you cannot reach them, write to us and we will pass the request on.
If the organisation that runs a form connects its own Google Analytics, Google Tag Manager or Meta Pixel to it, those tags run in your browser under that organisation's accounts. For that data the organisation is the controller and Google or Meta are its vendors, not our subprocessors. We send them nothing from our servers and put none of your answers in these events; if the form shows a consent banner, nothing loads until you accept. Whether a form asks for that consent is the organisation's decision and its responsibility: we provide the banner, the organisation chooses whether to turn it on.
The organisation can also connect integrations that send each new response somewhere else — a Slack channel, a HubSpot account, a Telegram chat, a Google Drive folder or Sheet, or a webhook to its own server. We send the response only to the destination that organisation chose, and that destination is its vendor, not our subprocessor.
Slack. When an organisation connects a form to Slack, we store the
channel's incoming-webhook URL, the channel's name and ID, the Slack workspace's name
and ID, and when it was connected. We use them only to post a message about each new
response — the form name, the answers, the score and result, and a link back to
ClarNow — into that one channel. The only Slack permission we ask for is
incoming-webhook: we cannot read messages, list channels or see members,
and Slack sends us no data beyond the details above. We keep them until the channel is
disconnected in ClarNow, the form is permanently deleted, or the account is closed
(then within 30 days, as in section 9). If the app is removed from the Slack workspace
instead, we delete them the next time Slack refuses a message. To have them
deleted sooner, disconnect the channel or write to
[email protected]. Messages already posted live in
the organisation's Slack workspace under Slack's terms; we cannot change or delete
them.
Our Data Processing Agreement governs this processing. It is part of our Terms and applies to every customer automatically; if your vendor-review process needs a countersigned copy, request one at [email protected]. It incorporates the subprocessor list in section 7.
7. Subprocessors
These are the companies that process personal data on our behalf. Every one of them is bound by a data processing agreement we hold directly, and we stay liable to you for their work. We keep the full list — provider, purpose, data and location — on its own page, so it can change without editing this policy: clarnow.com/subprocessors. We update that page before adding anyone new, and we email every account holder before a new subprocessor starts — see section 14.
The AI providers (Anthropic, OpenAI, Google's Gemini API, Groq) are not subprocessors of ours, which is why that page lists them separately. They are bring-your-own-key: your organisation connects one with an API key you supply, and we neither pick a provider nor hold a key of our own. If nobody in your workspace connects one, none of these four ever receives your data, and only the one you connect ever does. Because it's your own account with that provider, your agreement with them — not a data processing agreement of ours — governs how they handle it there, including whether they train on it; that varies by provider and API tier, so check the one you connect.
8. International transfers
Your account data and your respondents' answers live in the European Union, in the EU regions listed on the subprocessor page.
Our product analytics and session replays run on PostHog's EU infrastructure
(eu.i.posthog.com), and under our agreement with PostHog keeping that data
in the EU is their responsibility. To the extent any access from outside the EEA occurs
in supporting that service, it is covered by the Standard Contractual Clauses in that
agreement.
Some other processing nonetheless reaches the United States: Stripe, Google and Amazon Web Services all have US-based group companies that support their EU entities. Those transfers rely on the European Commission's Standard Contractual Clauses, and — where the provider is certified — the EU–US Data Privacy Framework. You can ask us for a copy of the safeguards for any given transfer.
If you connect an AI provider (Anthropic, OpenAI, Google's Gemini API, or Groq) with your own API key, whatever you send it also reaches the United States — but that transfer runs on your own agreement with that provider, not a contract of ours, so its safeguards are between you and them.
9. How long we keep data
| Data | Retention |
|---|---|
| Account and workspace data | Until you close the account, then deleted within 30 days |
| Billing identifiers (email, Stripe customer & subscription IDs, plan and payment history) | Up to 6 years after account closure — the same period we must keep invoices for |
| Form responses and uploaded files | Until you delete them, or until the account is closed and the 30 days elapse |
| Forms you move to the trash | Kept until you empty the trash, or the account is closed |
| Invoices and accounting records | 6 years, as required by the Spanish Commercial Code (art. 30) |
| Integration connections (e.g. a Slack channel's webhook URL and name) | Until disconnected, the form is permanently deleted, or the account is closed and the 30 days elapse |
| Webhook delivery logs | Deleted automatically once they expire |
| Backups | Rolling window; deleted data disappears as old backups age out |
| Analytics events and session replays | Per PostHog's retention, currently up to 30 days for replays |
Deletion of an account removes its forms, responses and files, and the rest of your workspace data. We keep one exception: your email address and Stripe identifiers, so we can tell what you paid for and when — for up to six years, matching the period we are legally required to keep invoices for under the Spanish Commercial Code (art. 30). We align the two so that an invoice we're required to keep is never orphaned from the account it belongs to. That record is used only to resolve billing disputes or defend a legal claim, on the basis of our legitimate interest in doing so — the general civil-claims limitation period under Spanish law (Civil Code, art. 1964) would let us stop at five, but there is no reason to delete it a year before the invoice itself ages out.
This exception is narrow. Form responses and other workspace content are deleted on the same 30-day schedule regardless of any dispute — that data belongs to you as controller, not to us, and we don't get to decide to keep it longer. Invoices survive on the same 6-year schedule, because we are legally required to keep them.
10. Security
Traffic is encrypted with TLS, and data is encrypted at rest by our hosting and
database providers. Access to production is limited to the people who need it, which
today is a very short list. Our signature and identity cookies (_ums,
dsso) are marked HttpOnly. Payment card data never touches
our infrastructure.
If a breach is likely to put your rights at risk, we will notify the AEPD within 72 hours of becoming aware of it, and tell you without undue delay. Where we act as your processor, we will tell you first so that you can meet your own deadline.
11. Your rights
Under Articles 15–22 GDPR you may ask us to:
- Access the personal data we hold about you, and get a copy.
- Rectify anything inaccurate or incomplete.
- Erase your data, where we have no overriding reason to keep it — including the legal-claims exception described in section 9.
- Restrict processing while a dispute about it is resolved.
- Port your data to another provider in a machine-readable format.
- Object to processing we base on legitimate interests.
- Withdraw consent at any time, without affecting what came before.
Write to [email protected]. We answer within one month, and will say so if we need the extension the GDPR allows. We do not charge for this unless a request is manifestly excessive.
If you are unhappy with our answer, you can complain to the Spanish Data Protection Agency (www.aepd.es), C/ Jorge Juan 6, 28001 Madrid — or to the supervisory authority where you live.
If your request concerns answers you gave to somebody's ClarNow form, we will forward it to that customer rather than act on it ourselves. It is their data, not ours.
12. Children
ClarNow is not directed at children, and you must be at least 18 to hold an account — our Terms of Service set the account age and its one narrow exception. Age matters on the other side of the form too: 14 is the age of digital consent in Spain, and it varies across the EU. If you build forms that collect data from children, you are responsible for obtaining whatever consent the law where your respondents live demands.
13. Automated decision-making
We do not make decisions about you with legal or similarly significant effects by automated means, and we do not profile you. Quiz scoring and calculations inside a form are logic our customers write themselves; the results belong to them, and this policy does not govern how they use them.
14. Changes to this policy
The subprocessor list reflects who we use today; we update it whenever it changes. When we change something that affects what happens to your data — a new purpose, a shorter retention window, or a change to our subprocessors — we will update the date at the top and email account holders. We email every account holder before we add or replace a subprocessor, so you get that notice whether or not you asked for it, and section 7 of our Data Processing Agreement gives you 30 days to object. Past versions of this policy are available on request.
15. Contact
Privacy requests, questions about our Data Processing Agreement, and anything else about this page: [email protected].
Everything else: [email protected].