Privacy policy
Last updated: 10 November 2026
Who we are
Meshads OÜ, registry code 16615525, Viru väljak 2, 10111 Tallinn, Estonia ("Mesh", "we"). We are the controller for personal data processed through this website. You can reach us at business@meshads.com.
What this policy covers
This policy covers the meshads.com website and the Google user data our internal tool Mesh Hub receives from Google APIs (section "Mesh Hub and Google user data"). Data processing inside our advertising services is governed by the agreements we sign with clients and partners.
Data we process
1. Email inquiries. When you write to us, we process your name, email address, company and whatever you include in the message. Legal basis: taking steps at your request before entering into a contract (Art. 6(1)(b) GDPR) or our legitimate interest in responding (Art. 6(1)(f) GDPR).
2. Technical data. Our hosting provider (Vercel Inc.) processes IP addresses and request metadata in server logs to deliver the site and keep it secure. Legal basis: legitimate interest (Art. 6(1)(f) GDPR).
3. Aggregated analytics. We use cookieless, privacy-friendly analytics (Plausible Analytics) on meshads.com. It stores no cookies, collects no personal data and produces only aggregated counts. Legal basis: legitimate interest in understanding site usage (Art. 6(1)(f) GDPR).
4. Meeting bookings. If you book a slot for an event through our Calendly page, Calendly LLC (US) processes your name, email address and any notes on our behalf and we receive them. Legal basis: our legitimate interest in scheduling the meeting, and taking steps at your request before entering into a contract (Art. 6(1)(f) and 6(1)(b) GDPR). Transfers to Calendly LLC rely on the EU Standard Contractual Clauses.
Mesh Hub and Google user data
Mesh Hub is our internal operations tool. Only Mesh staff use it. A staff member can connect a Google account to Mesh Hub to give it read-only access to the Google Ads accounts that account manages for us.
What Mesh Hub accesses. Through the Google Ads API (scope https://www.googleapis.com/auth/adwords) it reads: the list of Google Ads accounts under our manager accounts with their names, status, currency and time zone; campaign settings (name, status, bidding strategy and targets such as target CPA or target ROAS); campaign performance per day and hour (cost, clicks, impressions, conversions, impression share); and our Google Ads invoices and billing setups. It does not request access to Gmail, Drive, Calendar, contacts or any other Google data.
How we use it. Only for reporting to our clients, monitoring their advertising spend and invoicing them. Mesh Hub never creates, changes or deletes anything in Google Ads: it sends only a fixed set of read requests.
Storage. The access token for each connected account and the numbers Mesh Hub reads are stored on our own server, hosted by Hetzner Online GmbH in Helsinki, Finland (EU).
How we protect Google user data. We treat the access tokens and the Google Ads data as sensitive data and protect them as follows:
- Encryption in transit: every connection to Mesh Hub and from Mesh Hub to Google uses TLS (HTTPS). Mesh Hub has no open web port; it is reached only through an encrypted Cloudflare Tunnel.
- Access control: only signed-in Mesh staff can open Mesh Hub (Cloudflare Access), and each person sees only the areas and clients their role allows. Google Ads data is shown only to staff with access to it.
- Token protection: tokens are kept in a server settings file readable only by the account that runs Mesh Hub. They are never stored in the database or in source code, never shown in the app, never written to logs, and sent only to Google.
- Server hardening: the database is not reachable from the internet. Administrator access to the server is limited to a short list of approved network addresses and requires a cryptographic key (no passwords).
- Encrypted backups: nightly database backups are encrypted (AES-256) before they leave the server and are stored in the EU.
- Least privilege and audit: Mesh Hub requests read-only Google Ads access and sends only a fixed set of read requests. Changes inside Mesh Hub are recorded in an audit log that cannot be edited.
Sharing. We do not sell, share or transfer Google user data to anyone, do not use it for advertising, and do not use it to develop, improve or train AI or machine learning models. Our clients see reports about their own accounts only.
Retention and deletion. Performance numbers and invoices are kept as long as we need them for reporting and as accounting law requires (up to 7 years for invoicing records). A token is deleted when the connected account no longer needs to be read. You can revoke Mesh Hub's access at any time at myaccount.google.com/permissions (Mesh Hub, Remove access), or ask us to delete the data by writing to business@meshads.com.
Mesh Hub's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What we do not do
We set no tracking cookies. We do not sell personal data. We do not profile visitors of this website.
Retention
Inquiry emails are kept for as long as needed to handle the conversation and any business relationship that follows, then deleted. Server logs are retained by our hosting provider for a short, rolling period.
Recipients and transfers
We share data only with the processors named above (hosting, analytics, meeting booking, and for Mesh Hub our server host Hetzner Online GmbH and Cloudflare, Inc. for access control), bound by data processing agreements. Where a processor operates outside the EEA, transfers rely on adequacy decisions or standard contractual clauses.
Your rights
Under the GDPR you can request access, rectification, erasure, restriction of processing and data portability, and you can object to processing based on legitimate interest. Write to business@meshads.com. You can also lodge a complaint with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or your local supervisory authority.
Changes
We update this policy when our processing changes. The date above shows the current version.