Skip to content

Privacy Policy

What MyAd collects, how Google Ads data is used and shared with AI services, and how to disconnect or delete your data.

Last updated:

This Privacy Policy explains how MyAd.si ("MyAd", "we", "us") handles information when you use our website, dashboard and APIs (the "Service"). It covers visitors, registered users and people who contact us. MyAd is responsible for the information it processes to provide the Service. Contact privacy@myad.si about this policy or your data.

Signing in with Google, connecting Google Ads and using an AI service are separate choices. Signing in does not grant access to your advertising accounts. Connecting Google Ads does not itself send your advertising reports to a model; requesting an AI review sends the information described in section 5 to the service you configure.

Google API data: a plain-language summary

MyAd.si is an advertising management application. We use Google OAuth, the Google Ads API and the Data Manager API only to sign you in, discover Google Ads accounts you authorise, show account and campaign information, analyse performance, carry out advertising changes that you explicitly request, and send the conversion events you set up to your Google Ads account. We do not use Google APIs for unrelated advertising profiles, surveillance, credit decisions or any unlawful activity.

  • What we collect: your Google profile for sign-in; OAuth tokens and account identifiers for a connection; the campaign, keyword, budget, billing and performance data needed for the features you use; and the email addresses and access levels of an account's users, shown so you know which Google account to sign in with.
  • Why we collect it: to display your selected accounts, produce audits and recommendations, save drafts and reports, and apply campaign actions you approve.
  • Who receives it: Cloudflare hosts the Service and its encrypted database. When you request an AI feature, only the relevant inputs are sent to the AI gateway and model provider you choose in settings. If you set up notifications, alert messages, campaign updates, daily briefs and weekly reports go to the Feishu bot or webhook you choose. We do not sell Google user data or share it with data brokers, competing advertisers or other unrelated parties.
  • How to disconnect or delete it: disconnecting Google Ads removes the stored refresh token and access-check results. Email privacy@myad.si to request deletion of a connection, reports or your full MyAd account; after verification we process the request within 30 days, subject to the limited legal-retention details in section 7.

MyAd.si follows the Google API Services User Data Policy and its Limited Use requirements. We do not use Google user data, including derived or aggregated data, to train or fine-tune AI or machine-learning models. MyAd.si does not use Google APIs or Google user data to create, request, store or distribute AI-generated non-consensual intimate imagery (AI NCII); such use is prohibited by our Terms of Service.

1. Information we collect

Information you provide

  • Contact and support information: your name, email address, company, message and any content you choose to send us. Waitlist and affiliate applications may also include your website and a description of your audience.
  • Advertising planning inputs: product name and description, landing page URL, target countries and language, seed keywords, conversion goal, daily budget, maximum cost per click and optional target acquisition cost. We also store generated drafts, your edits and approvals, publishing records and analysis results.
  • Connection settings: connection names, Google Ads manager account IDs and, if you supply your own OAuth client, its client ID and client secret. AI settings include the service address, API protocol, model name, API key and optional gateway ID and gateway token.
  • Notification settings: a webhook address you save or, if you link a Feishu bot by scanning a QR code, the app ID and app secret Feishu issues for the bot app it creates in your Feishu organisation, the Feishu user ID (open_id) Feishu returns for the person who scanned, and the ID and name of the group you choose. To let you pick a group, MyAd reads the names of the groups the bot has joined; only the chosen group is stored.
  • Audit and analysis inputs, including an advertising account ID or account snapshot you submit. Submitting an account ID alone does not authorise access to that advertising account.

Information received from Google

Google Sign-In provides your email address, email verification status, name and profile picture. A separate Google Ads connection provides OAuth tokens, advertising account details and the data described in section 4. We never receive your Google password. The current live advertising connection is Google Ads; Meta and MCP demonstrations do not authorise or retrieve live advertising account data.

Technical information

Our hosting and security services process request information such as IP address, browser information, requested page or API route, referring page, timestamps, response status and diagnostic events. We use cookies for login and authorisation, and browser storage for preferences and unfinished drafts, as explained in section 12.

2. How we use information

  • Authenticate you and associate your settings, accounts and saved work with your MyAd account.
  • Discover Google Ads accounts, let you select accounts, and check whether your connection can access them.
  • Generate and save keyword and advertisement drafts from your inputs, and record your review decisions.
  • Validate and publish campaigns you approve, and carry out campaign enable or pause actions you request.
  • Retrieve advertising performance and provide analysis and recommendations when you request them.
  • Respond to support, waitlist and affiliate enquiries, diagnose errors, protect the Service and prevent abuse.
  • Meet applicable legal obligations and resolve disputes.

3. Limits on use and human access

  • We do not sell or rent your personal information, Google user data or advertising data.
  • We do not share Google user data with data brokers, competing advertisers or surveillance services, or use it for unrelated product marketing, advertising profiles or creditworthiness decisions.
  • We do not use Google user data, including aggregated, anonymised or derived data, to train or fine-tune AI or machine learning models. Our AI features use existing models to respond to a request (inference). Section 5 explains the separate terms of AI services you choose.
  • Human access to Google user data is limited to your affirmative permission to inspect specific data for support, necessary security or abuse investigations, compliance with applicable law, or aggregated information used for internal operations in accordance with applicable law. Staff and contractors must follow these restrictions.

MyAd's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. Google permissions and user data

Google Sign-In

We request openid, email and profile to sign you in. We use your verified email address to identify your MyAd account and store your email, name and profile picture to display your profile. The sign-in access token is used to retrieve this profile; it is not stored as a Google Ads connection. These permissions do not provide access to Gmail, Drive, Calendar, contacts or Google Ads.

Connecting Google Ads

When you choose to connect Google Ads, we request the https://www.googleapis.com/auth/adwords permission and offline access. This permission allows reading and managing Google Ads data, subject to your existing Google Ads permissions. It includes management capability when you authorise the connection; there is no separate read-only Google Ads scope in this connection. Offline access lets us refresh authorisation for subsequent requests without asking you to sign in to Google each time.

The same connection also requests the https://www.googleapis.com/auth/datamanager permission. We use it only to send conversion events, through Google's Data Manager API, to the Google Ads account and conversion action you choose. Each event contains the Google click identifier (GCLID, GBRAID or WBRAID) recorded when a visitor arrived from your ad, the event's time and ID, the conversion value and currency if you track them, the visitor's advertising consent status, and your own customer ID for that visitor if your site provides one. We do not send email addresses, phone numbers or other contact details with this permission, and we do not use it to read data from Google. Google's consent page lets you untick this permission: the rest of the connection keeps working, but MyAd cannot send conversions until you authorise again and grant it.

During connection and synchronisation we discover accessible accounts and manager-to-client relationships so you can choose which accounts to use. This includes account and manager IDs, names, currency, time zone, account status and access or authorisation errors. Discovery can include accounts you have not yet selected.

When a Google Ads authorisation completes, we ask Google which account granted it and store that email address on the connection. We use it to show the account on the connection card and to recognise a second authorisation of the same Google account as the same connection instead of creating a duplicate. It is not sent to an AI service.

For accounts and campaigns you use in MyAd, we retrieve campaign and ad group names, IDs and status; advertisement and keyword details; match types and search terms; budgets and bids; and performance such as impressions, clicks, spend, click-through rate, cost per click and conversions. Analysis of a snapshot you submit may also use its conversion values, quality scores and other fields you include.

When you open the funds and spend page, we read each saved account's status and settings (test-account flag, auto-tagging, conversion tracking status and optimisation score), its billing setups (status and the payments account and payments profile names), its account budgets (spending limit, adjustments, amount served and dates), and its campaign budgets and spend. To show which Google account opens each account in Google Ads, we also read the email address and access level of each user of the account we sign in to (the ad account itself, or the manager account we reach it through) and compare them with the email address you use to sign in to MyAd. These figures and user details are read from Google each time you open or refresh the page, are shown only to you, and are not stored or sent to an AI service.

When you enable managed delivery (autopilot) for a campaign, a copy of the data above is stored in our database so that the spend guard and the daily optimisation can work between Google API calls. This includes daily performance rows for the campaign, ad groups, keywords, ads and search terms; the current status of those entities; unresolved alerts; and every proposed, applied or reverted change with its before and after values, the reason given for it and the AI daily brief. Search-term rows are kept for 90 days and other daily performance rows for 400 days; alerts, change records and daily briefs remain while your MyAd account exists or until you request their deletion.

Granting permission does not itself publish or enable advertisements. Publishing requires your review and requested publishing action; newly created campaigns are paused until you request activation. Campaign status changes follow the actions you request. An AI recommendation does not automatically apply changes to your account.

Storage, sharing and control

We store encrypted Google Ads refresh tokens and any custom OAuth credentials, account connection information, and saved plans, approvals, publishing records and analysis evidence. Google data is processed on Cloudflare infrastructure. When you request AI features, the relevant information is also sent to the service described in section 5. Recipients and purposes are listed in section 9; retention and deletion are explained in section 7.

5. AI processing and your choices

The AI service you configure

In AI settings you choose a service address, model and credentials. When you enable that configuration and request an AI feature, MyAd sends a request to that address. A gateway may forward it to its underlying model provider. The selected protocol describes API compatibility; it does not establish that the recipient is OpenAI, Anthropic or any other particular company.

  • Connection test: a fixed test instruction and sample request check the configuration. This test does not send your advertising reports or saved plans.
  • Draft generation: product name and description, landing page URL, countries and language, seed keywords, conversion goal, budget, bid limit and optional target acquisition cost are sent to draft keywords and ad copy. If you ask us to read your website first, the page text we fetch from it (title, description, headings and a text excerpt) is sent as well; we do not execute the page's JavaScript. We save the resulting plan in your MyAd account.
  • Performance review: product description and goals, budget and bid limits, currency, time zone, reporting period, campaign status and performance metrics are sent together with keyword and search-term rows, their ad group names and metrics. These rows can contain the original text, rather than only numerical totals. We save the evidence and resulting recommendations in your MyAd account.
  • Daily managed-delivery optimisation: once per day, when a managed campaign is not in monitoring-only mode, we send the following to your AI service so it can label search terms and choose among changes that our code has already bounded: your product name, product description excerpt, landing-page title and conversion goal; campaign name, currency, mode and caps (monthly cap, daily budget limit, click bid limit, optional target cost per conversion, whether bidding-strategy changes are allowed); impression, click, cost, conversion and cost-per-conversion totals for yesterday, the last 7 days and the last 30 days; up to 100 keyword rows with text, match type, status, bid, quality score and 30-day metrics; up to 150 search-term rows with text, ad group identifier and metrics; the specific candidate changes with their allowed value ranges; unresolved alert titles; and the types and affected entities of changes applied in the last 14 days. We store the returned daily brief and decisions (including a truncated copy of the request, capped at about 100 KB, for auditing) in your MyAd account.

We do not add your Google password, Google OAuth tokens, custom Google OAuth client secret, or Google Sign-In email or profile picture to model prompts. The selected AI service receives its API key or gateway token for request authentication. Names, URLs, search terms and text you provide can themselves contain identifying information; we do not promise that this content is automatically anonymised. Only include information needed for the requested feature.

A service you select may have its own logging, retention, training and international-transfer terms. We do not have a separate contract with every service address you can configure and cannot promise that all such providers prohibit training or retain nothing. Review the gateway's and underlying provider's terms and settings before enabling them. Only use services whose handling of Google user data complies with the Google API Services User Data Policy, including its Limited Use requirements, and does not use that data to train models.

Stop subsequent requests through your configured service by turning off "Enable AI service" and saving in AI settings. Disabling it keeps saved settings, credentials and results; request their deletion using section 7. It does not recall requests already sent. For copies held by a provider you selected, use that provider's privacy controls or contact it directly; we can help identify the service used.

Cloudflare Workers AI for snapshot analysis

The separate account-snapshot analysis feature can use Cloudflare Workers AI to explain calculated findings. It sends the submitted account ID and name, currency and date range, calculated metrics, missing-data indicators and finding evidence, which may contain campaign names, keywords and search terms. The website demonstration uses sample account information. If you submit your own snapshot to the analysis API, the corresponding fields from that snapshot are processed instead. This feature is separate from your configured AI service.

Cloudflare's Workers AI data usage terms state that customer content is not used to train its models or improve Cloudflare or third-party services without explicit consent. MyAd does not opt Google user data into such training or service improvement.

6. Legal bases for processing

Where the GDPR or similar law applies, we process information to perform our contract with you (sign-in, connections and requested features), for legitimate interests (security, support and service reliability), to comply with legal obligations, and on the basis of consent where required, including optional data transfers. You can withdraw authorisation by disconnecting Google or disabling your configured AI service. Withdrawal does not affect processing already lawfully completed.

7. Retention, disconnection and deletion

What happens when you disconnect or stop using a feature

  • Google Ads tokens: disconnecting in Advertising accounts removes the stored refresh token for that connection, clears its account-discovery and access-check results, and disables linked accounts in MyAd. The saved connection name and any custom OAuth client settings remain available for reconnection until you request their deletion.
  • Account details and advertising history: your profile, saved advertising account details, plans, approvals, publishing records, reports, analysis evidence and recommendations remain while you keep your MyAd account, including after disconnection. Disconnecting, signing out or stopping use is not an account-deletion request. You can request deletion of particular advertising data without closing your account.
  • AI settings: the service address, model and encrypted credentials remain until you replace them or request deletion. Switching AI off stops subsequent requests through that configuration, but does not erase settings or previously saved plans and recommendations.
  • Notifications: a webhook address you save is stored encrypted (AES-256-GCM) and is never shown back to you in full or included in messages. If you link a Feishu bot, its app secret is stored encrypted the same way, and the app ID, the scanning account's Feishu user ID and the chosen group's ID and name are stored to deliver messages; the secret and user ID are never shown back. The one-time code used during a scan is stored encrypted and deleted when the scan ends or expires, within 10 minutes. Alert messages contain the alert title and detail; campaign updates describe events such as a launch, an approval by Google, a first conversion, a settings change or suggestions about to expire; daily briefs and weekly reports contain campaign spend, clicks, conversions, the keywords that cost the most, and the AI's summary and pending suggestions. All of them can include campaign names, keywords and amounts, plus a dashboard link. Saving a new address replaces the old one; removing it, or unlinking Feishu, deletes the stored values and stops notifications through that channel. Unlinking does not delete the bot app from your Feishu organisation; you can disable it in the Feishu developer console. Messages other than alerts wait in a delivery queue until they are sent; the queue keeps their text for up to 7 days and then deletes it. For alerts we record only when, and at which level, they were last notified.
  • Synced performance data: daily performance rows for a managed campaign are deleted automatically after 400 days, and search-term rows after 90 days; both limits are applied by our daily synchronisation. Alerts, change records (including the activity log of AI suggestions, approvals, guard actions and notifications sent) and daily briefs are kept while your account exists and are removed when you request deletion.
  • Support and technical records: correspondence is retained while needed to resolve your enquiry or an associated dispute. Security and diagnostic records are retained for troubleshooting, abuse prevention and applicable legal obligations, subject to our infrastructure providers' retention settings.

You can also revoke Google's authorisation from your Google Account connections. Revocation prevents further use of that authorisation; it does not delete information already saved in MyAd. Disconnecting or deleting MyAd data does not pause or remove advertisements in Google Ads. Manage or pause those advertisements in Google Ads if you no longer want them to run.

How to request deletion

  1. Email privacy@myad.si from the email associated with your MyAd account, or submit the contact form. State whether you want to delete a connection's data, AI settings, particular reports or your entire MyAd account. Include relevant account or report IDs if available. Do not send passwords, OAuth tokens or API keys.
  2. We verify that you are entitled to make the request and clarify its scope when needed.
  3. We process verified requests manually and delete the requested personal and advertising data from active MyAd systems within 30 days. Full account deletion includes the profile, stored credentials, connected account records, plans, publishing history, reports, analysis results and associated support content.

If a legal obligation, security investigation or dispute requires limited records to be retained, we explain the categories and reason unless law prevents us from doing so, restrict their use to that purpose, and delete them when that requirement ends. Cloudflare D1 database recovery history may retain older copies for up to 30 additional days after deletion from the active database. Recovery copies are not used for routine processing; a restoration must reapply completed deletion requests. Copies already held by Google, an AI provider you selected, or your own exports remain subject to those services' policies or your control. Browser drafts and preferences can be removed by clearing this site's browser storage.

8. How we protect information

  • Google authorisation uses OAuth; your Google password is entered at Google, not in MyAd.
  • Stored refresh tokens, custom OAuth secrets, AI credentials, notification webhook addresses and Feishu app secrets are encrypted with AES-256-GCM.
  • Web traffic and outbound Google and AI requests use HTTPS encryption in transit.
  • Authenticated dashboard requests check ownership of connections, plans and advertising records.
  • Publishing and campaign status actions are recorded to help trace changes and investigate problems.
  • Administrative access is limited to authorised personnel for the purposes described in this policy.

9. Service providers and data sharing

The following recipients process information in connection with the features described above:

Cloudflare, Inc. — hosting, storage, security and snapshot AI

Cloudflare runs our website and application processing, database and storage services, and security and diagnostic infrastructure. It processes information submitted to or stored by MyAd, including profiles, connection records, encrypted credentials, advertising plans, reports and request metadata. Cloudflare Workers AI also processes the snapshot-analysis inputs described in section 5. See Cloudflare's Privacy Policy and its Data Processing Addendum.

Google LLC — sign-in and the advertising platform you connect

Google receives authorisation exchanges and API requests needed to sign you in, discover accounts, read reports and execute requested advertising actions. Requests can include account and campaign identifiers and the ad copy, keywords, targeting and budget settings you approve. Google operates under its own Privacy Policy.

Your selected AI gateway and model provider

The recipient depends on the service address and model you save in AI settings. That service and any underlying model provider receive the feature-specific inputs and authentication information described in section 5. You can see the request address in settings. These are services you select; they are not all contracted MyAd sub-processors. Review their privacy policies, processing locations and retention settings.

Notification services you link

If you link a Feishu bot, Feishu receives the bot's credentials when MyAd signs in as the bot, the messages described in section 7 and the ID of the group or user they go to. The bot app is created in your own Feishu organisation and Feishu handles it under your organisation's terms with Feishu. When proposals need your decision, the Feishu bot sends a card whose buttons open a single-use MyAd approval link. Each link works once, expires with the proposal (at most 7 days) and is only sent to a private chat with the person who linked the bot. MyAd keeps only a hash of each link, plus an encrypted copy of the card so it can update the buttons in place; anyone you forward the message to could use a link until then. If you save a webhook instead, the service behind that address, such as Feishu, WeCom or Slack, receives the same messages. These are services you choose; they are not MyAd sub-processors.

We may disclose the minimum necessary information to meet a binding legal requirement or investigate fraud, abuse or a security incident, subject to the Google data restrictions in section 3. If you independently copy or export information to another application, its handling of that copy is governed by your arrangement with it.

10. International processing

Cloudflare operates a global network, and Google and the AI services you choose may process information outside your country, including in the United States. A custom AI gateway's and underlying provider's processing locations depend on your configuration and their terms. Where applicable law requires safeguards for transfers from the EEA or UK, the relevant processing arrangements must provide an approved mechanism, such as Standard Contractual Clauses. Contact us about the safeguards applicable to MyAd's processing; consult a provider you select about its own transfer arrangements.

11. Your privacy rights

Depending on your jurisdiction, you may have rights to access, correct, export or delete your personal data, restrict processing, object to processing based on legitimate interests, withdraw consent and complain to your local data protection authority. Contact privacy@myad.si or use our contact form. We respond within 30 days and explain any lawful exception or extension. See section 7 for deletion instructions.

12. Cookies and browser storage

  • A login session cookie keeps you signed in for up to 30 days; signing out removes that cookie.
  • Authorisation cookies, lasting up to 10 minutes, protect Google sign-in and connection flows.
  • Local storage remembers your theme preference until you change it or clear the site's storage.
  • Session storage preserves unfinished advertising-plan inputs during your browser session.

We do not use third-party advertising cookies on this site. You can control cookies and browser storage in your browser; blocking necessary cookies prevents sign-in and account connections from working correctly.

13. Children

The Service is intended for adults. We do not knowingly collect personal information from anyone under 18.

14. Changes to this policy

We update the date at the top of this page when this policy changes. For material changes we provide a prominent notice in the Service or contact affected users. Before using Google user data for a new purpose or accessing additional types of data, we update the disclosures and obtain any required consent before that processing begins.

15. Contact

Privacy, data access and deletion: privacy@myad.si. General support: hello@myad.si. You can also use the contact form and identify your message as a privacy request.