Spark Ranklab is the SEO and marketing platform of Kaige Productions, based in Breda, the Netherlands, registered with the Dutch Chamber of Commerce under number 70315019. This policy covers the whole platform, including the AI Marketing Assistant add-on and the assistant Vonk. Last updated: 19 November 2026. Nederlandse versie.
Two roles
For the data of your own account (name, email address, login details) Kaige Productions is the controller. If you use Ranklab for your own clients, we process that client data on your behalf as a processor; you remain responsible for what you put into the platform. For that situation we sign a separate data processing agreement.
Which data we process
- Account data: name, email address and profile photo from your Google login, plus your role within an organisation. We never see or store your password.
- Search performance: clicks, impressions, positions and search terms from Google Search Console for the websites you connect.
- Website statistics: visitors, sessions, traffic sources, key events and revenue from Google Analytics, if you turn that connection on.
- Tag Manager and Analytics settings: the containers, tags, triggers and variables from Google Tag Manager and the accounts, properties, data streams and key events from Google Analytics of the websites you connect. We read them to check your measurement setup. If you give separate permission, we can also create and change them on your behalf, but only after your approval (see below).
- Advertising and profile data: campaigns, ads, search terms, costs and results from advertising platforms, products and disapprovals from Google Merchant Center, and figures from a Google Business Profile, a YouTube channel or business social profiles, when you connect them. What we request per Google service is listed below.
- Meta data (Facebook and Instagram): when you connect Meta, we read, per selected account, the campaigns, ads (texts, link, image and audience), costs and results from the ad account, the statistics of the Facebook Page (followers, views, interactions) and of the Instagram professional account (followers, reach, views, interactions and figures of recent posts), plus your name at Meta and the permissions you granted. When you give separate permission, we also read the pixels and datasets of the selected business, so we can check the Meta pixel and set it up after your approval. See the Meta section below.
- LinkedIn data: when you connect LinkedIn, we read, from the selected ad accounts, the campaign groups, campaigns, ads, budgets, costs and aggregated results (impressions, clicks, conversions), and from the selected Company Page the followers, posts and their statistics, plus your name at LinkedIn and the permissions you granted. See the LinkedIn section below.
- Website content: public pages of connected websites that our crawler fetches to run technical checks. The crawler keeps a calm pace and respects robots.txt.
- Conversations with Vonk: your questions and the answers, plus whether you rated an answer as good or insufficient. We use that to improve the assistant.
- Usage and security logs: technical log lines and an audit log of important actions, such as connecting, disconnecting and applied changes.
- Usage data: when you sign in, which Ranklab pages you view, how long you actively use them (only while the tab is visible and you interact) and which features you use, such as completing an action, approving a proposal, connecting an account, reading a report or calling a tool through the AI connection. We measure this ourselves, in our own database, without third-party cookies or trackers. Only Ranklab administration sees this data, and we use it solely to improve the platform. We keep it for thirteen months and then delete it automatically.
Purposes and legal basis
We use this data to deliver the platform: showing reports and dashboards, calculating improvements, producing monthly reports and letting the assistant answer based on your own figures. The legal basis is the performance of the contract with your organisation. For security, abuse prevention and improving the platform we rely on our legitimate interest.
Changes on your behalf in Tag Manager and Analytics
Ranklab can create and change Google Tag Manager containers and Google Analytics properties on your behalf, for example a data stream, a key event or a container with the measurement tags of your web shop. The following applies:
- Only after approval: every change starts as a proposal showing the difference between what is there now and what it will be. Ranklab only applies it after a person approves the proposal in Ranklab. Publishing in Tag Manager is a separate step with its own approval.
- Separate permission: Ranklab requests the permissions to make changes separately, per part, and only when you use that feature. Your regular connection stays read-only.
- Safe and reversible: in Tag Manager, Ranklab always works in its own workspace and every tag waits for the visitor's consent. The previous version is kept, so you can always roll back a publication. Every change is logged with its date and approver.
The assistant Vonk
When you ask Vonk a question, we send your question, the ongoing conversation and the requested figures to an AI provider that drafts the answer. That provider does not use this data to train models. Vonk does not calculate by itself: all figures come from your own connected sources. Changes to ads start as a proposal showing before and after. Your organisation sets per client, in the action policy, whether a person confirms every proposal or whether the AI connector may apply certain kinds of changes on its own. Every applied change is logged and can be rolled back.
Sharing with others
We do not sell your data and do not use it for advertising. We do use providers that are needed to run the platform:
- Google, for login and for the Search Console, Analytics, Tag Manager, Ads, Merchant Center, Business Profile and YouTube data you connect.
- Meta Platforms, for the Facebook and Instagram data you connect.
- LinkedIn, for the ad account and Company Page data you connect.
- A data provider that handles connections with advertising and social platforms.
- An AI provider that drafts the assistant's answers.
- An AI assistant you connect yourself through Ranklab's AI connector; it then receives data from Ranklab at your request.
- A provider of SEO market data, when those features are on.
- Our hosting provider, where the platform and database run.
Each of these parties is bound by agreements on confidentiality and security. You can request the current list of sub-processors via support@kaige.nl. Some providers process data outside the European Economic Area; the European Commission's standard contractual clauses apply to that.
Where the data is stored and how it is protected
The platform and database run on a server in the European Union. Connections use HTTPS. Access tokens of connected services are stored encrypted (AES-256-GCM) and are not readable in the database. Every page and every query is scoped per organisation, so data of different clients can never mix. Server access is limited to staff who need it for their work.
Retention and deletion
Data is kept as long as the website or account is connected. If you disconnect a website, we delete the related data; the audit log remains because we must be able to show who did what and when. If you revoke a connection with an external platform, fetching stops immediately and we delete the stored access token. You can revoke a Google connection in Ranklab (revoke write permission or disconnect) or on the Apps with access to your account page at myaccount.google.com/permissions. To have all your data deleted, email support@kaige.nl. If you cancel the service, we delete your data within thirty days after the end, unless we are legally required to keep something longer.
Meta (Facebook and Instagram)
- What we read: only the accounts you select, and of those only the figures listed above. We do not read private messages, friend lists or data about the people who see your ads; Meta only provides aggregated figures.
- What for: reports, improvements and Vonk's answers about your own ads and Pages. Changes to ads (pause, resume, daily budget) are only applied after a person explicitly confirms them. Pixels and datasets are used to check that your measurement works; creating a dataset or adding a pixel in Tag Manager only happens after your approval.
- Not sold, not used for advertising: we do not sell Meta data, do not share it with others except the providers above that are needed to run the platform, and do not use it for advertising or profiling.
- Retention: the access token is stored encrypted (AES-256-GCM) and deleted as soon as you disconnect or revoke access at Meta. Daily figures are kept while the connection exists, so you can compare months and years; on disconnecting we delete them.
- Deletion: choose Disconnect Meta in Ranklab, remove the app in your Facebook settings, or email us. The details are on Delete Meta data.
LinkedIn
- What we read: only the ad accounts and Company Pages you select, and of those only the figures listed above. We do not read private messages, connections or member profiles; LinkedIn only provides aggregated figures.
- What for: reports, improvements and Vonk's answers about your own campaigns and Pages. Changes to campaigns (pause, resume, budget) start as a proposal and are only applied after approval according to your organisation's action policy. Every change is logged and can be rolled back.
- Audiences: if you create a LinkedIn audience from your own contact data through Ranklab, email addresses are hashed with SHA-256 first; the address itself is never sent to LinkedIn or written to our logs.
- Not sold, not used for advertising: we do not sell LinkedIn data, do not share it with others except the providers above that are needed to run the platform, and do not use it for advertising, profiling or training AI models.
- Retention and deletion: the access token is stored encrypted (AES-256-GCM) and deleted as soon as you disconnect or revoke access in your LinkedIn account settings. Daily figures are kept while the connection exists; on disconnecting we delete them. You can also email support@kaige.nl.
Cookies
Ranklab only uses functional cookies: a cookie to keep you logged in and a short-lived cookie while connecting with Google, Meta or LinkedIn. Your theme preference is stored in your browser. We do not use advertising or tracking cookies and therefore have no cookie banner.
Your rights
You have the right to access, correct, delete and port your data, and you can object to processing. Send your request to support@kaige.nl; you will receive an answer within four weeks. If you disagree with how we handle it, you can file a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Google services: per service
Ranklab asks for permission separately per Google service, and only for services you connect yourself. Below is what we request per service and what for.
- Sign in with Google
What we request: your name, email address, profile picture and the identifier of your Google account.
What for: recognising you, linking you to your organisation and recording who made a connection or change.
Permission at Google: openid, userinfo.email, userinfo.profile - Google Search Console
What we request: the list of your sites and per site clicks, impressions, positions, queries, pages and index status. Read-only.
What for: showing search performance in dashboards and reports, calculating declines and opportunities, and measuring the effect of improvements.
Permission at Google: webmasters.readonly - Google Analytics
What we request: accounts, properties and data streams, and per property visitors, sessions, traffic sources, events and revenue. With a separate permission (edit Analytics): creating and changing properties, data streams and key events.
What for: showing website figures next to search performance, checking your measurement setup and setting up measurement at your request.
Permission at Google: analytics.readonly, analytics.edit - Google Tag Manager
What we request: accounts, containers, workspaces, tags, triggers, variables and versions. With separate permissions: creating and changing tags, triggers and variables in a dedicated workspace, creating a version, and publishing that version.
What for: checking that your measurement is correct and setting up measurement tags at your request.
Permission at Google: tagmanager.readonly, tagmanager.edit.containers, tagmanager.edit.containerversions, tagmanager.publish - Google Ads
What we request: the accounts you can access and, for the selected account, campaigns, ad groups, ads, keywords, search terms, budgets, bidding strategies, conversion actions, audiences, recommendations, cost and results. Ranklab can also apply changes, such as pausing, adjusting a budget or bid, managing keywords and exclusions, and setting up campaigns.
What for: reporting on advertising performance, finding waste and opportunities, and applying changes according to the action policy your organisation sets per client. Every change is logged with before and after and can be rolled back.
Permission at Google: adwords - Google Merchant Center
What we request: the accounts you can access and, for the selected account, products and their status, disapprovals, data sources (feeds), shipping, promotions and reports. Ranklab can change product data when that feature has been enabled for the account; Ranklab never changes price, availability or shipping.
What for: warning about disapproved products, differences with your website and feeds that were not fetched, and improving product data.
Permission at Google: content - Google Business Profile
What we request: the accounts and locations you manage, the daily figures of the selected location (views, calls, website clicks, direction requests) and the reviews with their replies. Ranklab can post a reply to a review on your behalf.
What for: reporting local visibility and letting you reply to reviews.
Permission at Google: business.manage - YouTube
What we request: your channels (name, subscriber count) and per day views, likes, comments, shares and subscribers gained and lost from YouTube Analytics. In addition the right to upload a video to your channel; this only happens for a video you scheduled and approved in Ranklab yourself.
What for: showing your channel's performance next to your other channels, and uploading the videos you scheduled in the planner.
Permission at Google: youtube.readonly, yt-analytics.readonly, youtube.upload
For all these services
- Retention: we keep the fetched data and the encrypted access token as long as the connection exists, so you can compare periods. When you disconnect, we delete the fetched data of that connection and the access token. The log of applied changes is kept.
- Sharing: we share Google data only with our hosting provider (storage), with the AI provider that drafts an answer from Vonk when you ask Vonk a question, and with an AI assistant you connect yourself through Ranklab's AI connector. We do not sell it, do not use it for advertising, and do not use it to develop or train generalised AI models.
- Revoking access: disconnect the service in Ranklab in the settings of the client or site; Ranklab then also revokes the access at Google. The read access that belongs to your Google sign-in (reading Search Console, Analytics and Tag Manager) can be revoked at myaccount.google.com/permissions. There you can also revoke all of Ranklab's access at once.
- Deletion: email support@kaige.nl to have all your data deleted; you will receive an answer within four weeks.
Ranklab uses the YouTube API Services. The Google Privacy Policy also applies to data from YouTube: policies.google.com/privacy.
Google user data
The use of data from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. RankLab's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use data from Search Console, Analytics, Tag Manager, Ads, Merchant Center, Business Profile and YouTube only to provide the features you see in Ranklab, do not share it with others except as described above, do not use it for advertising, do not use it to develop or train generalised AI models, and do not let people read that data unless you consent, we need it for security, or the law requires it.
Changes
We update this policy when the platform changes. The date at the top shows when that last happened. For significant changes we let you know via the platform or by email.