Privacy policy

Last updated 6 October 2026

Controller

Simon Grimm, Achstraße 47, 6844 Altach, Austria. Email: hello@simongrimm.at, phone +43 677 61333176. See the Impressum for full legal details.

What MetricPort does

MetricPort is a hosted Model Context Protocol (MCP) server. When you connect a Google account, MetricPort requests permission to read your Google Search Console, Google Ads and Google AdSense data and makes that data available to AI clients that you authorize with an API key or OAuth login.

Google user data we access

• Your Google account email address and account id, to label the connection.
• Search Console: list of properties, search analytics, URL inspection results, sitemaps (scope webmasters.readonly).
• Google Ads: list of accessible customer accounts and reporting data retrieved through Google Ads Query Language (scope adwords). MetricPort never creates, edits or pauses anything.
• AdSense: accounts, sites, ad units, reports, alerts and payments (scope adsense.readonly).

How we use and store it

• The OAuth refresh token for each connection is encrypted with AES-256-GCM before it is written to our database, hosted by Supabase in Frankfurt, Germany (EU).
• The list of properties (site URLs, Ads customer ids and names, AdSense account ids) is cached so tools can resolve ids. Report data, query rows and earnings figures are fetched on demand, returned to your AI client, kept in memory for at most five minutes and never written to disk.
• For each tool call we log the tool name, property id, duration, success flag and error message for usage display, quota enforcement and debugging. Logs are deleted after 90 days.
• We do not use Google user data for advertising, do not sell it, and do not share it with third parties except the processors listed below. MetricPort’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Google user data is never used to develop, improve or train generalized AI or machine learning models.

Processors

• Vercel Inc. (hosting, functions)
• Supabase Inc. (database, EU region)
• Clerk Inc. (authentication)
• Stripe Payments Europe Ltd. (payments)

Your AI client

Data returned by a tool is sent to the AI client you connected (for example Anthropic’s Claude or OpenAI’s ChatGPT). Those providers process it under their own terms. MetricPort has no control over what a client does with a response.

Cookies and local storage

MetricPort uses only technically necessary cookies: the Clerk session cookie after you sign in, and a short-lived state cookie during the Google connection flow. We do not use advertising or analytics cookies and do not show consent banners because none are required.

Account and payment data

Your email address and name are stored by Clerk for authentication. If you subscribe, Stripe stores your payment details and billing address; MetricPort stores only the Stripe customer id, subscription id, plan and renewal date. Invoices are issued by Stripe on our behalf.

Retention

Google tokens and property lists are kept until you disconnect the account or delete your MetricPort account. Tool call logs are kept for 90 days. Billing records are kept for seven years as required by Austrian tax law.

Revoking access

Disconnect a Google account in the dashboard to delete its token and properties immediately. You can also revoke MetricPort at myaccount.google.com/permissions. Deleting your MetricPort account deletes all connections, keys and logs.

Your rights

Under the GDPR you may request access, rectification, erasure, restriction or portability of your data, and lodge a complaint with the Austrian Data Protection Authority. Write to hello@simongrimm.at.