Legal
Data Processing Agreement
Last updated: November 15, 2026
The English version of this document is authoritative.
On this page
When you install the Promvia snippet, you decide what is collected and why — that makes you the controller and us your processor. GDPR Article 28 says that arrangement has to be written down before it starts. This is that contract. It takes effect when you accept the Terms of Service and applies for as long as you have an account; no signature is needed, though we will sign a copy on request.
The parties are you, the customer, as controller, and Atlaven (eenmanszaak (sole proprietorship) of Aysenur Kurtulus Sayar; KvK 42199783), which runs Promvia, as processor. Where this agreement says "Promvia", "we" or "us", it means that processor.
1. What we process, and for whom
This agreement covers the personal data Promvia processes on your behalf: what the snippet collects from visitors to your website, and what our servers see while handling those requests. It does not cover your own account data — your email, your sites, your billing — for which we are the controller and the privacy policy applies. Annex I sets out the subject matter, duration, nature, purpose, data types and categories of data subject.
2. We act only on your instructions
We process the data only on your documented instructions, including for transfers to other countries. Your instructions are these terms, the DPA, and what you configure in the product — the sites you add, the questions you track, the integrations you turn on. If we ever believe an instruction breaks data protection law we will tell you rather than quietly carry it out. If law requires us to process for another reason, we will tell you first unless that law forbids it.
3. Confidentiality
Access is limited to the people who need it to run the service, each bound by confidentiality obligations that survive the end of their engagement. Promvia is operated by a small team; the list of people with production access is short and is available on request.
4. Security
We take the measures required by Article 32, described concretely in Annex II. They are stated as what the system actually does rather than as a category, so you can check them.
5. Other processors we use
You give us general authorisation to use the sub-processors listed in Annex III, each engaged under a written contract imposing the same obligations we owe you. We stay responsible to you for their performance. Before adding or replacing one we will give you at least 14 days' notice by email; if you object on reasonable data-protection grounds within that period, you may terminate the affected part of the service and receive a refund of anything paid for a period not yet served.
6. Helping you answer your visitors
If one of your visitors asks to see, correct, export or delete their data, that request is yours to answer — you are the controller. We assist you with appropriate technical measures: your dashboard, the export in Settings, and site deletion cover the ordinary cases, and where they do not, we help on request. If a request reaches us directly we will not answer it ourselves; we will pass it to you.
7. Breaches, and helping you assess risk
If we become aware of a personal data breach affecting your data we will notify you without undue delay and in any event within 72 hours, with what we know: what happened, which data and roughly how many people are affected, the likely consequences and what we are doing about it. If we do not know everything at first we will send what we have and follow up rather than wait. We also assist you, taking account of what we know, with data protection impact assessments and prior consultation.
8. What happens to the data when you leave
You choose: on termination we delete the data or return it to you. Deleting a site removes that site's data; deleting your account removes your information from active systems immediately, and the export in Settings gives you everything as JSON beforehand. Backups roll off on their own schedule within 30 days. We keep nothing afterwards except where law requires it, in which case we keep it only for as long as that law requires and go on protecting it.
9. Showing our work
We make available the information you need to show that these obligations are met, and we allow for and contribute to audits. In practice that means documentation and answers to your security questionnaire, which is what almost every request needs. Where documentation genuinely will not do, you may inspect — once a year, with 30 days' notice, at your cost, by you or an auditor we both accept, without disrupting the service or exposing another customer's data. A supervisory authority may audit at any time without those limits.
10. International transfers
The application's server code runs in Frankfurt (Vercel region fra1) and the database in Frankfurt (Neon, AWS eu-central-1); Vercel's edge network delivers pages and files from the location nearest each visitor. Most sub-processors are companies established in the United States — Vercel and Neon among them, although their servers for this service are in the EU — and some process data in the United States. Annex III states, for each one, the country it is established in and where it processes the data, separately. Data reaches them under their own data processing agreements, which incorporate Standard Contractual Clauses or their EU–US Data Privacy Framework certification. We do not transfer your data anywhere else on our own initiative.
11. Precedence and liability
Where this agreement conflicts with the Terms of Service on the processing of personal data, this agreement wins. Everything else — including the limitation of liability — is governed by the Terms. Nothing here limits either party's liability under data protection law towards a data subject or a supervisory authority.
12. Changes
We may update this agreement to keep it accurate or to meet a legal requirement. For a change that affects your rights, we email the account owner at least 30 days before it takes effect, as our Terms do, and announce it in the product; you can object and cancel before then. Corrections and clarifications take effect when they are published. A new or replaced sub-processor follows the 14-day notice in clause 5. The date above always reflects the version in force.
13. Visitors in Türkiye: transfers under KVKK
If your site collects data from people in Türkiye, you are also the controller for that data under Türkiye's Personal Data Protection Law (KVKK), and sending it to us is a transfer abroad to your processor. KVKK Art 9 asks for the standard contract published by the Personal Data Protection Board for that transfer (controller to processor). Ask us at support@promvia.app and we sign it with the Board's text unchanged; its annexes are filled from this agreement: Annex I for the data, the people it concerns, the purpose and the duration, Annex II for the technical and organisational measures, and Annex III for the sub-processors. Notifying the Personal Data Protection Authority within 5 business days of signing is yours to do, as the party transferring the data. So is informing your visitors under KVKK Art 10; Annex I holds what that notice needs to say about Promvia.
Annex I — Details of the processing
- Subject matter
- Providing the Promvia AI-visibility and traffic attribution service to you.
- Duration
- For as long as you have an account, plus the deletion window in clause 8.
- Nature of the processing
- Collection, storage, structuring, analysis and display; deletion on your instruction.
- Purpose
- Showing you which AI assistants send you traffic, whether they cite you, and what to change — for your purposes only.
- Types of personal data
- A first-party pseudonymous visitor identifier; the page visited and the referring source; conversion values you choose to send, labelled by a conversion goal key you define (an event identifier that must not contain personal data); IP addresses, seen transiently for rate limiting and when fetching a page you asked us to audit, and not stored against a visitor (a request that presents itself as an AI crawler keeps its IP address with that crawler visit, and briefly in the ingest queue, so the crawler can be verified). For a store you connect through Shopify or ikas: each order's id (on ikas also its number), total, currency and the time it was placed, matched to the visit that brought the buyer; for a Shopify store, also the products in the order (their id, title, quantity and amount); for an ikas store, ikas's own visitor id for the browser, stored only as a keyed digest. Promvia does not store the buyer's name, e-mail, phone or address, even where the platform's order message carries them.
- Categories of data subject
- Visitors to the websites you add to Promvia, and buyers from the stores you connect to it.
- Special category data
- None. Promvia is not designed to process it and you should not send it.
- Retention
- As set out in the privacy policy's retention table, which reflects what the code actually prunes.
- Frequency
- Continuous, for as long as your site sends events.
Annex II — Security measures
Stated as what the system does, so each line can be checked rather than taken on trust.
- Traffic to the application and to the database is encrypted in transit; the database is encrypted at rest by the provider.
- Passwords are stored only as salted hashes, never in a recoverable form, and new passwords are checked against known breach corpora.
- The application's server code runs in Frankfurt (Vercel region fra1) and the database in Frankfurt (Neon, AWS eu-central-1). Both providers are US companies; Annex III gives every provider's country and processing location.
- Every read and write is scoped by account, enforced in the data layer rather than in the interface, and covered by tests.
- Public endpoints are rate limited; the limiter sees counters keyed to an address, not content.
- Outbound fetches made on your behalf go through a guard that refuses private and link-local addresses, so an audited URL cannot be used to reach internal systems.
- Error monitoring is configured not to send IP addresses, cookies or request headers, and to redact email addresses out of error text.
- Production access is limited to named people using individual accounts with two-factor authentication at each provider.
- The database provider keeps a 6-hour point-in-time recovery window, in the same Frankfurt region and under the same encryption. Separately, a nightly copy of the database is encrypted with AES-256 before upload and kept for 30 days by GitHub (Annex III), so the data survives losing the database provider.
- Sessions expire after 30 days and are cleared on a schedule.
Annex III — Sub-processors
Everyone who can see personal data processed on your behalf. Providers marked optional are reached only if you turn on the feature that uses them.
| Provider | Purpose | Company established in | Where the data is processed | Transfer basis |
|---|---|---|---|---|
| Vercel | Application hosting | United States | EU — server code in Frankfurt (region fra1); pages and files delivered from Vercel's global edge network | Provider DPA (SCCs / DPF) |
| Neon | The database | United States | EU — Frankfurt (AWS eu-central-1) | Provider DPA (SCCs / DPF) |
| Upstash | Rate limiting; a short queue for incoming visits and crawler hits | United States | EU region | Provider DPA (SCCs / DPF) |
| Resend | Transactional and digest email | United States | United States | Provider DPA (SCCs / DPF) |
| Sentry | Error monitoring (EU region) | United States | EU — Sentry's EU data region (Germany) | Provider DPA (SCCs / DPF) |
| Stripe (optional) | Payments, on a paid plan | United States | United States | Provider DPA (SCCs / DPF) |
| OpenAI (optional) | Runs your tracked questions | United States | United States | Provider DPA (SCCs / DPF) |
| Anthropic (optional) | Runs your tracked questions | United States | United States | Provider DPA (SCCs / DPF) |
| Google (optional) | Runs your tracked questions | United States | United States | Provider DPA (SCCs / DPF) |
| Perplexity (optional) | Runs your tracked questions | United States | United States | Provider DPA (SCCs / DPF) |
| DataForSEO (optional) | Google AI Overviews and AI Mode results | Estonia (EU) | EU (Germany) and United States | Provider DPA (SCCs / DPF) |
| xAI (optional) | Grok, only if it is offered on your plan and you add it. It then receives your tracked question, not your account. | United States | United States and other countries | Provider DPA (SCCs / DPF) |
| GitHub | Keeps the nightly encrypted database backup for 30 days | United States | United States — an encrypted copy only | Provider DPA (SCCs / DPF) |
Contact
Questions about this agreement, or want a signed copy? Email support@promvia.app.