Effective date: 2026-10-15 (Apple Ads, sections 2, 5, 7 and 8, added that day; clients - the name of each client stored next to its connections and keys, sections 2 and 7 - and one-time connect links, section 7, added that day; Stripe as seller of record, sections 5 and 11, updated 14 October 2026; billing, section 11, added 9 October 2026; the Service and client tokens, sections 1–2; feedback and the request log kept 28 days, sections 7 and 10, and replies to feedback, section 10, from 10 October 2026; feedback retention updated 7 October 2026; feedback added 5 October 2026; website analytics added 4 October 2026)
V-Kit (Marketing Kit) - marketing-kit.app: the website, its server and the ways you use it (the V-Kit plugin and connector in Claude, Claude Code, the ChatGPT plugin and GPT, and the Claude Desktop extension and skill), together “the Service” - lets you read your own advertising and analytics data from Google Analytics 4, Google Ads, Google Search Console, Meta (Facebook / Instagram) ads, TikTok Ads, Apple Ads, AppsFlyer, RevenueCat, App Store Connect, Google Play Console and the Apple App Store inside Claude and ChatGPT. This policy explains what we process, why, and how you control it.
Data controller:
VALAS OÜ – PODRUŽNICA V SLOVENIJI
Mlinska ulica 22, 2000 Maribor, Slovenia
VAT ID: SI57438285
Website: valas.team
Contact for privacy questions: connect@valas.team
| Data | Source | Purpose | Legal basis (GDPR) |
|---|---|---|---|
| Name, e-mail address, account identifier of the Google or Meta account you sign in with | Google or Meta, when you sign in | Creating and identifying your account on the Service | Contract (Art. 6(1)(b)) |
| OAuth access and refresh tokens for Google (GA4, Google Ads, Search Console, Google Play), Meta (Meta Ads, Facebook Pages, Instagram), TikTok Ads and Apple Ads, the scopes you granted, the account name and token expiry | Google, Meta, TikTok or Apple, when you press “Authorize” (for Google Play, “Connect Google Play”; for Apple Ads, “Connect Apple Ads”) on the Connections page | Reading your data from these services when you ask Claude or ChatGPT for it | Contract; your consent given on the provider’s consent screen |
| Tokens issued to the clients you connect - the Claude plugin or connector, Claude Code, the ChatGPT plugin or GPT, your own GPT (personal token), the Claude Desktop extension (stored as hashes) | The Service | Letting those clients call the server on your behalf | Contract |
| Request log: time, source and mode requested, request parameters without secrets, number of rows returned, duration | The Service | Security, abuse prevention, troubleshooting | Legitimate interest (Art. 6(1)(f)) |
| Technical data: IP address, browser type, in web server logs | Your browser | Operating and protecting the website | Legitimate interest |
Keys you enter by hand. You can paste your AppsFlyer API token, RevenueCat secret API key (V2, read-only is enough) and (optionally, under Advanced) a Google Ads login customer ID on the Connections page. V-Kit detects your Google Ads manager accounts by itself through the Google Ads API; the account IDs and names it finds are kept in server memory for up to an hour and are not stored. The Service stores them encrypted (AES-256-GCM) until you remove them or delete your account; they are never written to logs, returned to the browser in full (only the last characters are shown) or included in answers. Alternatively you can enter the same keys in the settings of the Claude Desktop extension on your own computer: the extension sends them with each request, the server uses them for that request only and does not store them; a key entered in the extension takes priority over a saved one. The Service only reads RevenueCat data (subscription metrics, charts, products, offerings, and - when you ask about one customer - that customer’s subscriptions; customer attributes such as email are not returned unless you explicitly ask for them).
Clients. You can split your connections and saved keys into up to three named groups, “clients” (for example one per customer), on the Connections page. The Service stores the name you give each client and a short identifier made from it next to that client’s connections and keys; it is used only to pick which group of connections answers a request, and is deleted with the client or with your account. Deleting a client disconnects its providers and deletes its keys the same way as “Disconnect” does. If you link a client to a Meta Business portfolio, the portfolio’s ID and name are stored with that client until you unlink it or delete the client; the portfolio’s assets are read from Meta on request and not stored.
App Store Connect API. If you connect App Store Connect, the Service reads from Apple, on your behalf, your apps, sales and subscription reports, analytics reports, customer reviews and app versions (including Product Page Optimization experiments). To do so you save a team API key - its Issuer ID, Key ID and private key (.p8) - and, for sales and subscription reports, your vendor number on the Connections page. They are stored encrypted (AES-256-GCM) and used only to sign short-lived requests to Apple on your behalf; they are never shown back, shared, written to logs or included in answers, and are deleted when you press “Remove” or delete your account (you should also revoke the key in App Store Connect when you stop using the Service). The only write the Service makes is creating an Analytics Reports request for an app, and only when you confirm it.
Google Play. If you press “Connect Google Play”, the Service reads from Google, on your behalf and only within the Play Console permissions of the Google account you choose, your apps, installs, estimated sales, earnings, subscription counts, reviews, refunds and Android vitals. It stores the OAuth tokens for this connection encrypted (AES-256-GCM), the e-mail address of the chosen Google account as the label of the connection, and the identifier of the Cloud Storage bucket with your Play Console reports that you paste on the Connections page (a bucket name, not a secret). The report data itself is fetched from Google only when you ask, is passed to your AI client and is not stored by the Service, except at most in the short-lived cache and, for a result too large for the chat, the download file described below. Some of this data is about the people who use your apps: reviews come with the reviewer’s name (when Google returns it), device and the review text, and refunds and sales reports come with order numbers and the buyer’s country; the buyer’s city, state and postal code contained in the sales and earnings reports are not returned. The tokens and the e-mail address are deleted when you press “Disconnect” or delete your account; the bucket identifier when you remove it or delete your account. The Service never changes anything in Play Console and never posts replies to reviews.
Apple Ads. If you press “Connect Apple Ads” and an Account Admin or Campaign Group Manager of your Apple Ads account signs in with Apple and allows access, the Service reads from Apple, on your behalf and only for the ad accounts of that grant, your ad accounts, campaigns, ad groups, keywords, negative keywords, ads, performance reports and impression share. It stores the OAuth tokens for this connection encrypted (AES-256-GCM) and, as the label of the connection, the name of the organization and of the ad accounts the grant covers. The report data itself is fetched from Apple only when you ask, is passed to your AI client and is not stored by the Service, except at most in the short-lived cache and, for a result too large for the chat, the download file described below. The tokens and the label are deleted when you press “Disconnect” or delete your account. Apple lists V-Kit in your Apple Ads account under Account Settings → API; the access itself is withdrawn there, with Revoke Access. The Service never creates, changes or deletes anything in Apple Ads.
Personal tokens for your own GPT. If you build your own ChatGPT GPT, you can create personal tokens on the Account page. The Service stores a SHA-256 hash of each token (never the token itself), its name, its last four characters and its created, last-used, expiry and revocation dates. A token is used only to authenticate your own GPT’s read-only requests to the Service; you can revoke it on the Account page at any time, and it is deleted with your account.
Download files. When a result is too large to show in the chat, the Service saves it as a file that is kept for up to 24 hours and can be downloaded only by the same signed-in user; afterwards it is deleted.
Remote connector (claude.ai). If you add the V-Kit connector in claude.ai, requests are sent from Anthropic’s servers to marketing-kit.app (/mcp) on your behalf, after you sign in and allow access; the Service answers them with the same data and limits as for the extension.
ChatGPT (OpenAI). If you install the V-Kit plugin from the ChatGPT plugin directory, add the V-Kit connector in ChatGPT Developer mode or use a V-Kit GPT, requests are sent from OpenAI’s servers to marketing-kit.app (/mcp/chatgpt, /mcp or /api/v1) on your behalf, after you sign in and allow access. The Service answers with the same data as for Claude; through the GPT it only reads (no changes to AppsFlyer), and large tables come back as a summary with download links. The access can be revoked on the Connections page at any time.
Your advertising and analytics data (spend, impressions, events, app reviews and the like) is fetched from the provider only when you ask for it, is passed to your Claude client, and is not stored by the Service beyond a short-lived in-memory cache (about 15 minutes, separate for each user) that avoids repeating identical requests. Device identifiers, IP addresses and customer user IDs contained in source data are removed by default before the data leaves the server.
We use the data only to provide the Service to you. We do not sell it, do not use it for advertising, do not build profiles, and do not use it to train AI models.
V-Kit’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Scopes requested: openid, email, profile (sign-in), analytics.readonly (read Google Analytics 4) and adwords (read Google Ads reports; the Service does not change your campaigns) and webmasters.readonly (read Google Search Console: your properties, search performance - clicks, impressions, CTR and position by query, page, country, device and date - sitemaps and URL index status; the Service does not add, remove or change properties or sitemaps). For Google Play, a separate connection (“Connect Google Play”, possibly with another Google account) requests openid and email (to label the connection with the account’s e-mail address), androidpublisher (the only scope of Google’s Play Developer API, with no read-only variant; the Service uses it only to read reviews and refunded purchases, and never to change anything or reply to reviews), devstorage.read_only (read the Cloud Storage bucket with your Play Console reports: installs, sales, earnings, subscription counts and reviews of past months) and playdeveloperreporting (read your list of apps and Android vitals: crash and ANR rates). Google user data is used only to show you your own data in Claude or ChatGPT, is not transferred to third parties except as necessary to provide the Service or required by law, is not sold, is not used for advertising, credit-worthiness or lending purposes or to train AI models, and is not read by humans except with your explicit consent, for security purposes, or as required by law.
With Facebook Login for Business the Service requests ads_read (read-only access to the ad accounts you choose), pages_show_list, pages_read_engagement and read_insights (your Pages, their posts and insights), instagram_basic and instagram_manage_insights (your professional Instagram accounts and their insights), and two optional permissions: business_management (read-only, to list your business portfolios and find the Pages, ad accounts and Instagram accounts of a portfolio, so that you can link a client to one portfolio) and pages_read_user_content (the number of reactions and comments on your Pages' posts, and the comments under a post). Comments under your Pages' posts are read only when you ask for them and are shown to you; they are not stored, only cached for up to 15 minutes like other answers from your sources, and the commenter's name or ID is neither requested nor shown. Meta data is used only to show you your own data in Claude or ChatGPT, in line with the Meta Platform Terms.
Transfers outside the EU (Cloudflare, Google, Meta, Anthropic, OpenAI, and Stripe’s group companies) rely on the EU–US Data Privacy Framework or Standard Contractual Clauses offered by those providers.
Provider tokens are encrypted at rest with AES-256-GCM. Tokens are never written to logs or returned to the browser or to Claude. All traffic uses HTTPS. Access to the server is limited to the operator’s administrators.
Step-by-step instructions: marketing-kit.app/data-deletion.html.
Under the GDPR you have the right to access, rectify, erase, restrict and port your data and to object to processing. You may also lodge a complaint with the Slovenian supervisory authority, the Information Commissioner (ip-rs.si).
The website uses one strictly necessary session cookie to keep you signed in, and Google Analytics cookies (_ga, _ga_*) to measure how the website itself is used: which pages are opened, from which country and on which kind of device. Google Analytics sees only visits to marketing-kit.app pages - never your connected accounts, keys, marketing data or what you ask your assistant. No advertising cookies. You can block analytics cookies in your browser or with Google's opt-out add-on; the Service works the same without them.
You can send a note to the V-Kit developer: from a chat with your assistant (the assistant asks you first and shows you the text) or from the forms on the website. What we store:
Replies. The developer may reply to your note. A reply is shown once in your assistant’s answer, in whichever client you use V-Kit from next, and in the Feedback block on the website (the Connections and Install pages); the delivery mark keeps it from being shown in a chat twice.
Why: so the developer can fix problems, answer you and improve V-Kit. Who sees it: only the V-Kit developer and you see your notes and their threads. How long: 28 days after you send the note, then it is deleted automatically together with its replies, your answers and their delivery marks; deleting your account deletes them at once.
To ask at most twice a day, the server records when it showed you a feedback question; you can tell your assistant “don’t ask again” and the question stops for the period you choose.
When the paid plan applies to your account, the Service counts your free trial and, if you subscribe, sends you to Stripe’s hosted checkout page; we never see or store your card details. Stripe processes the payment as the seller of record and is an independent controller for the payment data; how it uses that data is described in the Stripe Privacy Policy. Subscriptions started before Stripe became the seller of record keep VALAS as the seller: their payments are processed by Stripe Payments Europe, Ltd. (Dublin, Ireland) as our processor.
What we store:
What Stripe holds: your name or company name, billing address, VAT ID, the e-mail address you give at checkout, your payment method, and the invoices and receipts. Stripe uses them to take payments, calculate and collect the tax and issue receipts and invoices; it also processes this data under its own obligations (for example, tax, fraud prevention and anti-money-laundering rules), described in the Stripe Privacy Policy. As the seller, Stripe may also delete the data it holds under its own rules.
E-mails. The Service itself sends you no e-mails. Receipts, invoices, renewal and failed-payment messages are sent by Stripe to the e-mail address you give at checkout. Reminders about the end of the trial are shown in the chat with your assistant and on this website.
Why: to provide the plan you chose and to keep the payment records the law requires. Legal basis: contract (Art. 6(1)(b)) and legal obligation (Art. 6(1)(c)) for tax and accounting records.
Billing event log: we keep a technical log of billing events without personal data for 24 months - Stripe event identifiers, types, statuses, amounts and dates and the link to your account, with names, e-mail addresses, postal addresses and phone numbers removed before it is stored.
When you delete your account: an active subscription is cancelled immediately and our billing data about your account is deleted (a redeemed gift code stays marked as used, without any link to you); the billing event log loses its link to your account and is deleted 24 months after each event. Invoices and payment records stay with Stripe for as long as the tax law that applies to the seller requires (for subscriptions with VALAS as the seller, Slovenian law: 10 years); we do not use them for anything else.
The Service is intended for business users and is not directed to children under 16.
We will publish changes on this page and update the effective date. Material changes will be announced on the website before they take effect.
See also the Terms of Service.
© 2026 Valas Team