Legal

Privacy Policy

Last updated: November 15, 2026

The English version of this document is authoritative.

Overview

Promvia ("we", "us") helps website owners measure how much traffic and revenue AI assistants send their site, and whether AI recommends them. This policy explains what we collect and how we use it.

Information we collect

Account information you give us: your email address and a securely hashed password. If you sign in with Google, Google shares your name and email address with Promvia; we use the email address as your account address and do not store your name. Analytics data from the Promvia snippet you install on your own site: the referring AI source, the page path visited (query strings and fragments are removed before anything is stored), a pseudonymous visitor identifier (a keyed digest computed on our server — the raw browser id is never stored), and any conversion values you choose to send, labelled by a goal key you define. Goal keys are event identifiers (letters, digits and . _ : - only); anything shaped like an e-mail address or a URL is stored as 'other', and you must not put a person's name or other personal data in one — we cannot tell a name from an event name. We do not intentionally collect your visitors' names, emails, or other personal contact details; the snippet and its endpoints are built so that page URLs, referrers and visitor ids cannot carry them, and the goal key is the one field only you can keep clean. If you connect Google Analytics 4, we store an encrypted, read-only access grant and read aggregated daily figures from it — sessions, key events and purchase revenue per AI source — never individual visitors; disconnecting revokes the grant at Google and deletes those figures. For Get named elsewhere we read the public third-party pages that AI answers cite for your questions and store only what those pages themselves publish: the title, the author's name as printed, dates, the options the page lists, whether it discloses affiliate or sponsor arrangements, and the contact routes printed on the page or on the contact or about page it links to — an email address only if it is printed there; we never guess or construct one. The messages Promvia drafts for you are stored on your account and never sent by us. A page that has been out of your plan for 90 days is deleted, or, if you acted on it, keeps its address, title and your status but loses the author's name, the contact routes and the text copied from it; a draft written to it loses its text too. All of this is part of your export and is deleted with the site or the account.

Connected apps (Claude and other MCP clients)

You can connect an AI assistant such as Claude or ChatGPT to your Promvia account through our MCP connector at https://promvia.app/api/mcp. You sign in to Promvia, a consent screen shows what the app is asking for, and you decide what it may do; after that the app calls Promvia's tools on your behalf. Promvia does not receive or store your conversations with the assistant. The app sends us tool calls only — the name of a tool and its arguments, such as a site id, a question to track, a look-back window in days or an action item's new status — and we see nothing of the chat except what the app puts into those calls.

  • What a connection stores: the app's registration — the name it gives itself (shown to you as chosen by the app) and the addresses it may send you back to, and for an app that identifies itself by a web address, that address and when we last read it; and your approval — which app, the permissions you chose, when you approved it, when it was last used (updated at most once a minute) and, once you disconnect it, when.
  • Tokens: the app holds an access token that expires after one hour and a refresh token that lasts 30 days and is replaced by a new one each time it is used. Access tokens are not stored on our side at all; refresh tokens and the single-use sign-in codes (valid for ten minutes) are stored only as SHA-256 hashes, never as the tokens themselves.
  • Permissions are opt-in for every kind of change: approving grants the read access listed on the consent screen, and each kind of change the app asks for — adding or archiving tracked questions, starting citation checks and site scans, generating content briefs, changing the status of action items — is its own box that starts unticked. A read-only team seat can grant read access only, and an app can never add a permission you did not approve when it renews its token.
  • Each tool call: we use the arguments only to answer that call, for the sites your account can open, through the same checks as the dashboard. We do not keep a log of tool calls or their arguments. What we do record is a monthly count of requests against your plan's API allowance (part of your export) and rate-limit counters keyed to your account id and IP address, which expire after one minute. A tool that makes a change stores its result on your account just as the same button in the dashboard would — a tracked question, a content plan, a status. If a call fails, an error report goes to Sentry, described under service providers; request headers, and with them your token, are removed before it is sent, and email addresses in the error text are masked.
  • The answers: what a tool returns — your sites, check results, metrics — goes to the app you connected, and from there it is processed by that app's provider (Anthropic, for Claude) under that provider's own privacy policy and terms, not ours.
  • Disconnecting: Settings → Integrations → Connected apps lists each app with its access and last use, and Disconnect revokes it. An app can also revoke its own access at our standard revocation endpoint (RFC 7009), https://promvia.app/api/oauth/revoke. Revoking deletes the app's refresh tokens at once, and its access token is refused on its next request, because every request checks the approval. Setting a new password disconnects every app.
  • How long: a disconnected app's record (its name, the access it had and the dates) stays in your account history and your export. Your approvals, codes and tokens are all deleted with your account. An app's registration — its self-chosen name and return addresses — belongs to no account and is kept.
  • API keys: if you connect with a Promvia API key instead of signing in, the connector lets the key read only, we store a keyed hash of it rather than the key itself, and you revoke it under Settings → Integrations → API keys.

GitHub connection (pull requests for fixes)

On plans with GitHub apply you can install the Promvia AI GitHub App and connect one repository to a site. Promvia then opens a pull request on that repository for each fix you approve — an llms.txt or robots.txt file, the Organization schema or canonical tag in your home page's <head> on a static HTML site, or a blog post from one of your content drafts. Promvia never merges: the pull request is yours to review, change, merge or close, and whoever merges it is the one who publishes it.

  • What the app may do on GitHub: read and write repository contents (to create a branch and commit the fix) and pull requests (to open them), plus the read-only metadata GitHub gives every app. You choose on GitHub's own screen which repositories it can see, and you pick one of them for each site; nothing is connected until you do.
  • What it reads: the list of file paths in the connected repository, and only the files a fix needs — your current robots.txt, to merge the change into it, your home page's index.html, to add that snippet inside its <head>, or one existing blog post, to match its format. File contents are used for that pull request and are not stored.
  • What we store: the repository's name, its default branch, the installation id, the folders and files Promvia may write to (your home page only after you confirm it) and who connected it; and for each pull request, the fix it carries, its branch, number, link and commit, whether and when it was merged or closed, and when the site was checked again afterwards. While you choose a repository, the list GitHub returned is kept for 30 minutes.
  • Tokens: the GitHub sign-in used to list your repositories is revoked at GitHub as soon as the list has been read. To open a pull request we ask GitHub for a token limited to the one connected repository; it expires after an hour and is held only in server memory, never in the database.
  • Events from GitHub: GitHub tells us when one of Promvia's own pull requests is merged, closed or reopened, and when the app is uninstalled or loses a repository; we act on those and ignore everything else. A merge starts one new Site check of that site.
  • Disconnecting: disconnect the site under Settings → Integrations, or uninstall the app on GitHub, which ends every connection it served. A connection and its pull-request records are deleted with the site or your account; the pull requests themselves stay on GitHub, in your repository.

ikas app (not available yet)

The Promvia AI app for ikas is not in the ikas app store yet. When it is listed, this is what applies: if you install it, ikas signs you in to Promvia and Promvia reads your store's e-mail address and store name to create your account and a site for your store. The app adds Promvia's measurement script to your storefront and asks ikas to tell Promvia when an order is created or updated. For your store's shoppers you are the data controller and Promvia processes their data on your behalf, under the Data Processing Agreement.

  • What the storefront script sends: the same pageview data as the Promvia snippet, ikas's own visitor id for that browser, and, when a checkout completes, the order's id and number with Promvia's visitor id, so the order can be matched to the visit that brought the buyer. In consent mode nothing that identifies a browser is sent before the shopper consents, and ikas's own cookie banner counts as consent. ikas's visitor id is stored only as a keyed digest, never as itself.
  • What we keep from an order: its total, its currency and when it was placed, plus the order id ikas gives it; a refund lowers the total. There is no customer name, e-mail, phone or address in what Promvia stores, and no product data.
  • Tokens: the access and refresh tokens ikas issues for your store are stored encrypted, and are used only to read your store's details, orders and Promvia plan, keep the storefront script installed and register the order events.
  • How long: the rows that join an order to a visit are deleted after 30 days, and the ids of ikas's webhook deliveries, kept only to ignore a retry, after 7 days. When you uninstall the app, the script is removed and the orders it recorded are deleted 48 hours later, unless you reinstall within those 48 hours.

Etsy connection (shops on Etsy)

If you sell on Etsy, you can connect your Etsy shop so that, when an AI answer links one of your listings, Promvia can tell you the page is yours rather than just an Etsy page. You sign in on Etsy's own screen and approve read-only access to your shop (shops_r), the only permission Promvia asks for. Promvia uses the Etsy API for nothing else: the AI answers are collected the same way as for any other site. Promvia never writes to your shop, never reads your buyers, orders, messages or addresses, and does not use your connection to read any other shop. The term 'Etsy' is a trademark of Etsy, Inc. This Application uses Etsy's API, but is not endorsed or certified by Etsy.

  • What we read and keep: your Etsy user id, your shop's id and name (Promvia creates a site for the shop at <shop name>.etsy.com, named after the shop, and follows it if you rename the shop on Etsy), and for each active listing its id, title and web address, for up to 5,000 listings.
  • How fresh: while your shop is connected we read the shop and its active listings again every 5 hours, and each complete read replaces the whole copy, so the copy we use is normally no more than 6 hours old. If reading fails, the old copy is deleted once its last complete read is 24 hours old, and is not used after that.
  • Tokens: the access and refresh tokens Etsy issues for your shop are stored encrypted and are used only for the reads above. If Etsy refuses them, for example because the access was withdrawn on Etsy's side, we delete the tokens and the listing copy at once and keep only your Etsy user id and the shop's id and name, with a note that the shop needs to be connected again.
  • Deleting: when you disconnect the shop in Promvia, the connection, its tokens and the listing copy are deleted at once; the site and the AI answers already recorded for it stay until you delete the site. When you delete the site or your account, the connection and everything above go with it. Etsy offers no way for an app to revoke a token, so deleting the encrypted tokens is what ends Promvia's access on our side.
  • Cookie: connecting sets one security cookie, etsy_oauth_state, which carries the sign-in's one-time security codes and your language for at most ten minutes, is sent only to /api/etsy, and is cleared when Etsy sends you back.
  • Your shop's visitors: Promvia's snippet cannot be added to an Etsy shop, so for an Etsy shop Promvia records no visits and no orders, and nothing about the people who visit or buy from your shop reaches Promvia.

How we use information

To provide your dashboards and recommendations, operate and secure your account, and improve the service. We do not use your account or your sites' data for advertising; only your visits to promvia.app itself are measured for our own ads, and only if you accept cookies, as described under Cookies.

Cookies

Promvia itself sets eight cookies on this site, one of them only if you accept it (the cookies of the two outside tools that Accept also starts are described below):

  • One to keep you signed in.
  • One that records nothing but the fact that you are signed in so a page can show the right menu without being rebuilt for you.
  • One to remember your language.
  • One for light or dark mode.
  • One that remembers whether you hid the dashboard's side menu.
  • One that remembers whether you folded the dashboard's signals panel.
  • One that remembers your answer to the cookie banner.
  • One analytics cookie.
  • Language, theme, side menu, signals panel and the banner answer are set only when you press the switch yourself (one exception: opening Promvia from the Shopify admin before you have chosen a language sets it to the admin's).
  • Connecting a Shopify store adds two short-lived security cookies for the length of that flow plus a ten-minute one that carries the Shopify admin's language through the install.
  • Connecting Google Analytics adds one short-lived security cookie for the length of that flow.
  • Connecting GitHub adds one short-lived security cookie for the length of that flow.
  • Connecting an ikas store (once the ikas app is listed) adds one short-lived security cookie for the length of that flow.
  • Connecting a T-Soft store (once the T-Soft app is listed) adds one short-lived security cookie for the length of that flow.
  • Connecting an Etsy shop adds one short-lived security cookie for the length of that flow.
  • Opening the link in your confirmation email adds one security cookie that lasts until you confirm (at most an hour).
  • Signing up with an email address adds one cookie that remembers that address for a day so the check-email page can resend the confirmation.
  • Signing in to an account with two-step verification on adds one security cookie that lasts until you enter the code (at most five minutes).
  • Signing in with Google adds one short-lived security cookie for the length of that flow.
  • The analytics cookie (aita_vid, kept for 12 months) is Promvia's own first-party visitor identifier: it lets us see which AI answers send visitors to promvia.app and, if you sign up, which visit led there. It is set only after you press Accept. If you press Reject, the visit is still counted, but nothing is stored on your device to recognise you.
  • While you are signed in to Promvia, and on the app and sign-in pages themselves, your page views are not recorded at all: the analytics are about visitors to the site, not about you using the product.
  • You can change your answer at any time with Cookie settings at the bottom of every page.
  • Pressing Accept also starts two outside tools, on the public pages of promvia.app and never inside the app: Google Analytics, which sets its own cookies (_ga, and _ga_ followed by an id, kept up to two years) to count visits, and the Meta Pixel, which sets _fbp (kept three months) and can read the cookies Meta has already set if you use Facebook or Instagram, so that our ads there can be measured and shown to people who have visited.
  • Both also learn when you reach our sign-up or payment confirmation pages and, for a payment, the price of what was bought excluding VAT, never your email address, name or account. Our server sends Meta that same confirmation directly too, for browsers that block the Pixel, carrying only which confirmation it was, an id for that one event that is not your account, the page's address, your IP address, your browser's name and Meta's own _fbp and _fbc cookies, and only after Accept.
  • Google (Google Ireland Limited) and Meta (Meta Platforms Ireland Limited) use that data as controllers under their own privacy policies, and for collecting it here and passing it to them we and Meta are joint controllers. If you press Reject, neither tool loads, and their cookies on promvia.app are deleted.
  • The Promvia snippet on your own site sets the same kind of first-party visitor identifier so conversions can be attributed to the visit that drove them; it is not used for cross-site advertising or tracking, and it can wait for your own visitors' consent (data-consent="required").

Who is responsible for what

For your account — your email, your sites, your billing — the data controller is Atlaven (eenmanszaak (sole proprietorship) of Aysenur Kurtulus Sayar; KvK 42199783), which runs Promvia; you can reach the controller at info@atlaven.com, and its registered details are on the company details page. For the visitor data our snippet collects on your website, you are the controller and Promvia is your processor: we hold and process it on your instructions and for your purposes, never our own. That distinction decides who answers if one of your visitors asks what is held about them — it is you, and we help you answer.

Where your data goes

Promvia's server code runs in Frankfurt (Vercel region fra1) and the database is in Frankfurt too (Neon, AWS eu-central-1); pages and files are delivered from Vercel's global edge network, from the location nearest the visitor. Most of the providers below are United States companies — Vercel and Neon among them — and some of them process data in the United States. Sending personal data there, or letting a US company reach it where it is stored in the EU, is a restricted transfer under EU law, and it happens on the basis of Standard Contractual Clauses or the EU–US Data Privacy Framework, depending on the provider. Annex III of our Data Processing Agreement lists, for each provider, the country it is established in, where it processes the data and the transfer basis, so you can check that for yourself.

How we share information

We do not sell your data. We share it only with the service providers listed below, each under confidentiality obligations and only to the extent they need in order to run part of Promvia. The one other recipient is the ad measurement you can accept on promvia.app: if you press Accept, Google and Meta receive your visits to its public pages, as described under Cookies. If you enable live AI-citation checks, the search questions you choose to track are sent to the AI provider that runs them.

Service providers we use

Naming them, rather than describing them in general terms, is the point: you cannot judge how your data is handled without knowing who handles it.

  • Vercel — application hosting. Sees requests to the app.
  • Neon — the database. Holds your account, sites and analytics data.
  • Upstash — rate limiting, and a short queue that holds incoming visits and AI-crawler hits until they are written to the database: the page path, the referring source, the site-scoped visitor identifier digest, and a crawler's IP address. The queue is normally written out within the hour; anything that cannot be written is set aside for us to fix, and deleted after 30 days.
  • Resend — transactional and digest email. Sees your email address and the message.
  • Sentry (EU region) — error monitoring. Configured NOT to send IP addresses, cookies or request headers, and to redact email addresses out of error text.
  • Stripe — payments, when a paid plan is used. Card details go to Stripe directly and never reach us.
  • OpenAI, Anthropic, Google and Perplexity — the AI assistants that answer your tracked questions. They receive the question, not your account.
  • DataForSEO — Google AI Overviews and AI Mode results for your tracked questions.
  • xAI — Grok, only if it is offered on your plan and you add it. It then receives your tracked question, not your account.
  • Telegram — operational alerts to us (signups, payments, failures), carrying counts and plan names rather than anyone's email address or name. The one exception is a question sent through this site's contact form: its first 60 characters reach us there, with any email address removed. Telegram handles none of our customers' data on their behalf, so it is not a sub-processor in the DPA's Annex III.
  • GitHub — keeps our nightly backup of the database for 30 days, encrypted with AES-256 before it is uploaded, so the data survives losing the database provider. If you connect a repository, GitHub also carries the pull requests Promvia opens there, as described above.

How long we keep things

Most of it lives as long as your account does — deleting a site removes that site's data, and deleting your account removes your information from active systems immediately. The parts that expire on their own schedule are listed here so you do not have to take a general promise on trust.

  • Sign-in sessions — 30 days, then expired and cleared.
  • Visits and AI-crawler hits waiting in the ingest queue (Upstash) — normally less than an hour; any that cannot be written are kept for review for at most 30 days, then deleted.
  • Payment event records — 30 days (the invoice history itself stays with Stripe).
  • AI crawler visits seen by our edge snippet — 180 days.
  • AI crawler visits from your CDN logs and your own reports — 90 days. From a CDN log we keep only lines from AI crawlers, with the query string removed and without the IP address.
  • GEO coaching plans — the most recent 12 per site.
  • Analytics events, conversions, citation checks and audits — for as long as the site exists, and deleted with it.
  • The addresses you send scheduled reports to — kept with a random id so the opt-out link in their mail keeps working, and deleted once they are on no schedule and no report has gone to them for 90 days, or at once when your account is deleted. An address that opted out stays on the opt-out list, so it is never mailed again.
  • Feedback you send from the Feedback button — the message and what was captured with it (page, plan, site, browser, window size, app version, last error code) for as long as your account exists; pictures you attach for 90 days.

Your rights

You can see, correct, export or delete your data yourself, without asking us. Settings has a one-click export of everything on your account as a JSON file, and a delete that removes it. You can also object to non-essential email with the unsubscribe link on any digest — that never affects the mail we must send you, such as password resets. If you would rather we did it, or you want to complain, email us; if you are in the EU or Türkiye you may also complain to your national data protection authority.

If you are in Türkiye: KVKK notice

Under Art 10 of Türkiye's Personal Data Protection Law No. 6698 (KVKK): the data controller for the personal data on your account is Atlaven (eenmanszaak (sole proprietorship) of Aysenur Kurtulus Sayar; KvK 42199783), and you can reach us at info@atlaven.com. Promvia is not established in Türkiye; this section restates what is described above under the headings KVKK asks for.

  • What we process, and why: your email address and a hash of your password, to open your account and keep it safe; your sites, the questions you track and the integrations you connect, to provide the service; plan and billing records, to take payment and invoice you (card details never reach us, they stay with Stripe); your feedback and support messages, to help you. We do not use that data for advertising; only your visits to promvia.app itself are measured for our own ads, and only with your consent.
  • How it is collected, and on what legal basis: electronically, when you enter it on the signup, settings, payment and feedback screens. The legal bases are the formation and performance of our contract (Art 5/2-c), legal obligations such as keeping invoices (Art 5/2-ç), and our legitimate interest in keeping accounts secure and preventing abuse (Art 5/2-f). The analytics and advertising cookies on promvia.app, Google Analytics and the Meta Pixel among them, are written only with your explicit consent (Art 5/1): if you do not press Accept none of them is written, and you can withdraw consent at any time with the Cookie settings link.
  • Who receives it, and where: the providers named under "Service providers we use" above and in Annex III of the Data Processing Agreement, as far as each needs it to run the service. Our servers run in the EU (Frankfurt) and most providers are US companies, so this is a transfer abroad within the meaning of KVKK Art 9. Annex III states each provider's country and where it processes the data. If you pressed Accept on promvia.app, your visits to its public pages also go to Google and Meta, which process them in the United States among other places. We do not sell your data.
  • Your rights (KVKK Art 11): to learn whether your data is processed; to request information if it is; to learn the purpose of the processing and whether the data is used for it; to know the third parties in Türkiye or abroad it is transferred to; to have it corrected if it is incomplete or wrong, and erased or destroyed when the conditions of KVKK Art 7 are met, and to have those steps notified to the recipients; to object to a result against you that comes solely from automated analysis; and to claim compensation for damage caused by unlawful processing.
  • How to apply: write to info@atlaven.com from your account's email address. We answer free of charge within 30 days at the latest. If you are not satisfied with our answer, or get none in time, you may complain to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu). The export and delete in Settings let you use most of these rights straight away, without asking anyone.
  • Your site's visitors: for the data our code collects on your site you are the controller and Promvia is your processor, so informing your visitors is yours to do. The Data Processing Agreement sets out what you need for that, and the standard contract we sign for transfers from Türkiye.

Security

What we do to protect your data — where it runs, encryption, who can reach it, backups, connected-app tokens and how to report a vulnerability — is set out line by line on our security page. No method of storage or transmission is 100% secure, and we cannot guarantee absolute security.

Changes to this policy

We may update this policy from time to time. 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; corrections and clarifications take effect when they are published. The "last updated" date above reflects the current version.

Contact

Questions about your privacy? Email support@promvia.app.

Company details Security Data processing agreement