This policy covers inseeq.com, the inseeq platform and MCP server, and our applications on Google, Meta and LinkedIn. It is written to be read, not to be survived.
This policy explains what personal and business data inseeq UG (haftungsbeschränkt) collects, why, who processes it for us, how long we keep it, and how to have it deleted. It covers our website at inseeq.com, the inseeq platform (the client portal at app.inseeq.com, our reporting and data services, and the inseeq MCP server at api.inseeq.com), and our applications on Google, Meta and LinkedIn.
If you are reviewing one of our applications: Google's section is section 4, Meta's is section 5, LinkedIn's is section 6. To have data deleted, see section 3.7 or our data deletion page.
The controller for the processing described in this policy is:
inseeq UG (haftungsbeschränkt)We are not required to appoint a Data Protection Officer (Art. 37 GDPR, § 38 BDSG) and have not appointed one. Privacy enquiries go to legal@inseeq.com; we answer within 30 days.
Two roles. inseeq is a growth agency: businesses engage us on retainers to run their marketing, and the inseeq platform supports that work. For data about our own website visitors, business contacts and client users, we are the controller. For data that comes from a client's own connected accounts (for example their ad accounts or their CRM), the client is the controller and inseeq processes it on the client's behalf under a data processing agreement (Art. 28 GDPR).
Each client gets a private organisation on the platform. Into it flow the data from the marketing, analytics and CRM accounts the client has connected, the projects and content we work on together, and the reports we produce. The client's team sees it in the portal and, if they choose, through an AI assistant of their own (such as Claude or ChatGPT) connected to the inseeq MCP server. inseeq staff assigned to the client work with the same data to deliver the service.
Access to advertising platforms is read-only. Our connections to Google Ads, Meta and LinkedIn read reporting and account data; neither the portal nor the MCP server can change a client's campaigns. Where a client engages us to manage campaigns, inseeq staff make those changes under their own staff accounts, using the agency access the client grants on the platform itself (for example Business Manager partner access, a Google Ads manager-account link or a LinkedIn Campaign Manager role), at the client's instruction.
A client connects an account in one of three ways, depending on the platform:
We access only the accounts the client has connected and only within the permissions granted. We never ask for a platform password.
| Platform | What we retrieve | What we do not retrieve |
|---|---|---|
| Google Ads | Account and campaign structure (campaigns, ad groups, ads, keywords), budgets and bids as settings, daily performance (impressions, clicks, cost, conversions, conversion value), search-term and breakdown reports (device, network, geography, demographics) | Anything about individual people; Google returns aggregates only |
| Google Analytics 4 | Aggregated reports: sessions, users, key events and revenue by date, page, channel, source, device and country | User-level or event-level records |
| Google Search Console | Search performance (clicks, impressions, position) by query, page, country and device | Anything about individual searchers; Google anonymises queries |
| Meta (Facebook and Instagram ads) | Ad account details, campaign, ad set, ad and creative structure, daily performance (impressions, reach, clicks, spend, conversions), and aggregated breakdowns (age, gender, region, placement, device) | Lead form responses, Page content, Instagram media, messages, or anything about individual people |
| LinkedIn Ads | Ad account, campaign group, campaign and creative structure, daily performance (impressions, clicks, spend, conversions, video and lead-form counts), and aggregated audience breakdowns (job function, seniority, company size, industry, geography) | Member profiles, member-level data, lead form responses, organic posts |
| HubSpot (CRM) | The client's CRM records: contacts, companies, deals, owners and lists, and their activity records (emails, calls, meetings, notes, tasks) | HubSpot properties marked sensitive; anything outside the connected portal |
| Lemlist (outbound) | Campaign and sequence structure, sending and reply statistics, and the leads in the connected campaigns (name, company, job title, email address, campaign status and replies) | Anything outside the connected Lemlist workspace, including mailbox content outside the campaigns |
| Clay (enrichment) | The tables the client connects: company and contact records with the enrichment fields the client has added (for example company size, industry, job title and business email) | Tables or workspaces the client has not connected |
| Peec AI | AI-search visibility measurements for the client's brand and competitors, from inseeq's own Peec account or from the client's own Peec account if the client connects it | Personal data |
We also record, per connection, who authorised it, when, and which permissions were granted.
Only to deliver the services the client has engaged us for: the client's dashboards and reports, answers to the client's questions in the portal and through their AI assistant, and our own analysis and recommendations for that client. We do not sell platform data, use it to advertise to anyone, build profiles of individuals, or use it for any client other than the one it belongs to.
Platform data is stored in our reporting warehouse, a PostgreSQL database hosted by Supabase in the EU (Frankfurt). Every record carries the client organisation it belongs to, and every read is scoped to one organisation. One client's data is never visible to another client.
Access credentials (tokens and keys) are kept in encrypted secret storage, separate from the data, and are never shown to clients, written to logs or handed to AI models. Once clients connect through our self-serve connect page, those credentials will be held by Nango, our credential vault (not yet in use). Google grants need no stored credential: we authenticate with short-lived tokens that Google issues to our service identity.
The software that reads and processes the data runs on Vercel in the United States (see section 12).
| Data | Retention |
|---|---|
| Google, Meta, HubSpot, Lemlist, Clay and Peec data | For the duration of the client engagement; deleted within 30 days after the engagement ends, or within 10 days of the client's request |
| LinkedIn advertising data | At most 12 months, then deleted; deleted within 10 days after the engagement ends or of the client's request. Account, campaign and creative IDs may be kept for the duration of the engagement. |
| Access credentials | For as long as the connection is active; deleted immediately when the client revokes access or asks us to, and at the latest within 10 days after the engagement ends |
| MCP interaction log (section 7) | 12 months, then deleted automatically |
| Encrypted database backups | Roll off automatically within days of a deletion; deleted records are never restored from them |
Withdrawing access stops all further retrieval immediately. It does not by itself delete data already retrieved; for that, see 3.7.
Email legal@inseeq.com with the subject Data deletion request, naming the business and the accounts concerned. For a client's platform data, we delete it and confirm in writing within 10 days, free of charge. If you are a LinkedIn member and ask us to delete data we hold about you that came from LinkedIn, we delete it immediately. Records we must keep by law (invoices and accounting records, 10 years under § 257 HGB and § 147 AO) are restricted instead of deleted. Step-by-step instructions are on our data deletion page.
This section applies to all data inseeq receives from Google APIs, including Google Ads, Google Analytics and Google Search Console, whether a client connects by signing in with Google or by granting access to an inseeq identity.
https://www.googleapis.com/auth/adwords, used for reading only), view Google Analytics data (…/analytics.readonly) and view Search Console data (…/webmasters.readonly).ads_read, to read advertising data of the connected ad accounts, and public_profile, which Meta includes in every login. The app does not request permission to manage ads, Pages, Instagram content, lead forms or messages.r_ads and r_ads_reporting, to the LinkedIn ad accounts an administrator at the client authorises: account, campaign and creative details and advertising performance reporting, including LinkedIn's aggregated audience breakdowns. We do not retrieve member profiles or member-level data, lead form responses or organic content.A client can connect an AI assistant of its choice to its own inseeq organisation through the inseeq MCP server, using a key we issue to that client. The assistant can then read the client's data and, within the client's portal permissions, work with its projects, tasks and content. It cannot change anything on a client's advertising platforms.
The inseeq platform calls AI models from the following providers through their APIs, as our processors, for inference only. Each processes the data the platform sends on our instructions, under commercial terms that prohibit it from training models on that data.
| Provider | What the platform uses it for | Receives connected-platform data? |
|---|---|---|
| Anthropic, PBC (Claude) | inseeq's assistant in client Slack channels; scheduled analysis and report runs | Yes, for the client being served |
| OpenAI, L.L.C. | Measuring how brands appear in AI search answers; drafting content | No |
| OpenRouter, Inc. | Routing the same AI-search measurements and drafting tasks to several model providers | No. Every request instructs OpenRouter to use only model providers that do not store or train on the data |
Of these providers, only Anthropic receives data from a client's connected platforms. Data the inseeq platform sends to these providers is not used to train AI models, by us or by them. Separately, if a client connects its own AI assistant (section 7), that assistant's provider is the client's choice and the client's processor, not ours.
Our reporting warehouse, which holds the data from connected platforms, is in the EU. Our platform database, hosted by Supabase, is in the United States, as are several of our processors, including our hosting provider's compute (Vercel), our AI providers and our credential vault. Transfers rely on the recipient's certification under the EU-US Data Privacy Framework where it has one, and otherwise on the European Commission's Standard Contractual Clauses, with encryption in transit and at rest. A copy of the relevant safeguards is available from legal@inseeq.com.
Under Art. 6(1) GDPR we rely on:
Where we process data on a client's behalf, the client determines the legal basis and we act on its documented instructions (Art. 28 GDPR).
You have the right to access your data (Art. 15 GDPR), to correction (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20), to object to processing based on legitimate interests (Art. 21), and to withdraw consent at any time with effect for the future (Art. 7(3)). Write to legal@inseeq.com; we answer within 30 days, free of charge. If your request concerns data we hold for a client, we tell you which client and pass the request on.
You may also complain to a supervisory authority. Ours is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin.
Data is encrypted in transit (TLS) and at rest. Credentials are held in encrypted storage separate from the data. Each client's data is isolated to its own organisation, and staff access is authenticated, limited by role and logged. Report vulnerabilities to legal@inseeq.com.
Our services are for businesses. We do not knowingly collect data from anyone under 16.
We update this policy when our processing changes; the date at the top reflects the current version. Before we access a new kind of data from a platform, we update this policy first. Where a change materially affects clients, we tell them directly.
legal@inseeq.com, or by post to inseeq UG (haftungsbeschränkt), Linienstraße 115, 10115 Berlin, Germany.