Month17 archives Google Search Console data past Google's 16-month retention limit and serves it over MCP. This page describes what personal data that involves, why we hold it, and how to get it corrected or removed. Month17 is operated from the Netherlands; you can reach us at hello@month17.com for anything on this page.
What we collect, and why
Waitlist signups. If you join the early-access list we store your email address and name (from your Google profile) and the UTM tags of the link that brought you here. We use this to let you in at the founding price, to email you about the launch, and to see which of our ads actually work. We don't use it for anything else and we don't share it.
Accounts. Login works with magic links, so we store your email address and short-lived login tokens. No passwords exist on our side.
Search Console data. This is the product. When you connect a Google account we store an OAuth token (encrypted at rest in our database) and, for each property you choose, its Search Console performance rows: queries, pages, clicks, impressions, CTR, position, and related dimensions. We request read-only access and never modify anything in your Google account.
Billing. Payments run through Mollie, our payment processor. Mollie handles your payment details under its own privacy policy; on our side we store your subscription status, not your card or bank numbers.
Analytics. The website uses Betterlytics, a cookieless analytics service. It gives us aggregate page counts, not profiles of individual visitors, and it sets no tracking cookies.
Google user data and Limited Use
Month17's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice: your Search Console data is used to provide the archive and query features you signed up for, is never sold, is never used for advertising, and is never read by humans except with your permission for support, for security reasons, or where the law requires it.
The AI text watermark remover. The free tool at /tools/ai-text-watermark-remover/ checks pasted text for hidden characters on our own server and stores none of it. Its optional rewrite step is the one place where text you give us leaves the EU. When you press that button, we send the text to DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd., China) through their API to be paraphrased. Their API terms and privacy policy govern what they do with it, which may include keeping it and using it to train their models. We send nothing until you press the button, we do not attach your IP address or any account detail, and we keep no copy. Do not use the rewrite for text that contains personal data or anything confidential.
Where your data lives
Everything runs on servers in the European Union, with the one exception of the watermark remover's rewrite step described above: hosting on Hetzner (Germany), email through mailbox.org (Germany), and Cloudflare in front of the site as a CDN and proxy. OAuth tokens are encrypted in the database using PostgreSQL's pgcrypto.
How long we keep it
- Waitlist data: until we've finished launch communication, or immediately on request.
- Account and archive data: for as long as your account exists. Disconnecting a property stops its sync; deleting your account removes your tokens and archived data.
- Whatever the law obliges us to keep longer (invoices, for instance), we keep exactly that long and no longer.
Your rights
Under the GDPR you can ask us for a copy of your data, ask us to correct or delete it, take it elsewhere, or object to how we handle it. Email hello@month17.com and we'll respond within 30 days. If you're not satisfied with how we handle a request, you can complain to your data protection authority.
What we don't do
We don't sell data. We don't run advertising. We don't use your Search Console data to train models, build benchmarks, or inform anything beyond your own account.
Changes
If this policy changes in a way that matters, we'll email account holders before the change takes effect. The date at the top always reflects the current version.