Privacy
What Loopod reads from the accounts you connect, what it keeps, and who else sees it.
Last updated 19 August 2026
Who we are
Loopod is operated by Sealmetrics. For anything in this policy, including a request to delete your data, write to rafa@sealmetrics.com.
What we access, and only that
Loopod analyses marketing performance for the accounts you choose to connect. Nothing is read until you complete the connection, and you pick which property or account each connection covers.
| Source | What we read |
|---|---|
| Google Analytics 4 | The list of properties you can already read, so you can choose one. Then daily totals only: sessions, page views, key events, revenue, add-to-carts, and the advertising cost, clicks and impressions a linked Google Ads account reports. |
| Google Ads | The list of accounts you can reach, then spend, impressions, clicks, conversions and conversion value, by campaign and by day. |
| Google Search Console | Your verified sites, and search performance rows: query, clicks, impressions, click-through rate and average position. |
We store aggregates, never raw events. What we keep is one figure per account, metric and day — the same numbers you would see in a report. We do not request, receive or store data about the individual visitors to your website: no identifiers, no profiles, no event-level records, no personal data of your end users.
Read-only, and enforced in the code
Loopod does not change anything in your advertising or analytics accounts. It does not adjust budgets or bids, pause or start campaigns, or create ads. It produces recommendations, and a person decides whether to act on them in their own account.
For Google Analytics and Search Console we request read-only permission, so writing is not possible at all. The Google Ads API publishes only one permission, covering both reading and writing; there, the guarantee is in our own code, which contains no method capable of modifying an account.
What we do with it
We use the connected data to do the job you hired the product for: analyse performance, explain what changed, judge whether the spending is profitable at the margins you tell us, and write the reports and alerts you ask for. Every analysis is stored with the data it reasoned over, so a conclusion stays explainable later.
We do not sell it. We do not use it for advertising or ad targeting. We do not use it to build profiles of anyone, and we do not combine one customer's data with another's.
Who else processes it
The analysis is performed by large language models that we do not host. Figures derived from your connected accounts are included in what we send them.
- Anthropic — the models that write the analysis you read.
- Scaleway (EU) — an open model used for some cheaper internal steps.
- Supabase (Frankfurt) — the database.
- Railway (Amsterdam) — where the application runs.
Each acts as a processor on our instructions, under contract. Your data is not used to train their models. Where a channel you configure sends a report or alert out — email or Slack — it goes only to the destination you set.
Google user data
Loopod's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
In practice: Google data is used only to provide the features you connected it for; it is shared only with the processors named above, and only so those features can work; it is never sold, and never used for advertising. No person at Loopod reads your Google data except where you ask us to look at your own account to help you, or where the law requires it.
Your credentials
The token that authorises a connection is encrypted at rest in a dedicated secrets store, referenced only by an identifier. It is never written into an ordinary database column, a log line, an error message, or the record of an analysis. A signed-in member of your workspace can see that a connection exists; nobody can read the token behind it through the application.
Where it lives, and for how long
Data is stored in the European Union. We keep the aggregates and the analyses for as long as your workspace exists, because the record of what was decided and what it produced is the point of the product — a recommendation from months ago has to stay explainable by what was known then.
Delete your workspace and the connected data goes with it. You can also ask us to delete it at any time, at the address above.
Turning it off
You can disconnect a source inside Loopod, which revokes our access and stops any further reading. You can also revoke it from Google directly, at your Google Account permissions. Either way, access stops immediately.
Your rights
Under the GDPR you can ask for a copy of the personal data we hold about you, correct it, delete it, restrict or object to how we use it, or take it elsewhere. Write to rafa@sealmetrics.com and we will answer within a month. You may also complain to your national data protection authority.
Note that the account data you connect is largely not personal data: it is aggregated marketing performance. The personal data we hold about you is what you gave us to have an account — your name, your email, and what you have done in the product.
Changes
If we change this policy in a way that matters, we will tell the workspaces it affects rather than quietly changing the date at the top.