The short answer
Queries run live against your Google accounts; audit reads are cached for up to an hour, a saved audit's findings are kept for 180 days, and the server's system log records each Google Ads query for about 7 days. AdCopilot also keeps your Google-confirmed email and the first name on that Google account, an encrypted Google refresh token, your connection record, a ledger entry per tool call, a record of when you accepted our terms and this policy, your workspace's business profile, the latest daily check of each Search Console site you connect (until 14 days after its last check), the billing, email and anti-abuse records listed below, and nightly database backups: 14 days on our server, and about 36 days in an encrypted off-site copy. It never sees your Google password and trains no model. To improve its checks, we analyse aggregated statistics across workspaces, which name no person, workspace or account, with AI models from Anthropic, which our staff also use when they investigate a bug or a problem you ask us about; Anthropic's commercial terms do not permit it to train models on our data. Access ends the moment you revoke it in your Google account.
Who we are
AdCopilot is operated by Atromx Intelligence Private Limited (CIN U62099AP2026PTC126398), India, trading as Atromx Intelligence, registered office R.S. No. 21-10, D.No. 36-3-48, near Sampath Vinayaka Temple, Tanuku, West Godavari, Andhra Pradesh 534211, India. AdCopilot is a hosted connector: it lets an AI assistant you already use read, and when you ask it change, the Google Ads, Analytics, Search Console and Tag Manager accounts you grant it. For data-protection purposes we are the controller of the account data described below.
For anything about this policy, your data, or a request to delete it, and for company or commercial matters, write to support@adcopilot.cloud.
What we collect
What the service keeps about you and your workspace, why, and for how long.
| What | Why | Kept for |
|---|---|---|
| Your name and email | To identify your connector and contact you about it. The email is the one Google confirms when you sign in, not just the one you typed, so a connector can be tied to the account that actually authorised it — that is what lets us refuse a reconnection from a different Google account. We also store the first name from the Google account you sign in with, to address our emails to you, and update it each time you sign in. Google's sign-in shares your name and profile picture with us; we keep your email address, that first name and the ID Google gives your account, which is how we tell your Google account from another, and nothing else about your identity. | Until you ask us to delete it. |
| A Google refresh token | Issued by Google when you sign in. It is what lets the connector call Google's APIs as you. Encrypted at rest. | Until you choose Disconnect Google on the dashboard's Google products page, which deletes it, sign in with Google again, which replaces it, or ask us to delete it. Withdrawing access at Google stops it working at once, but its encrypted copy stays stored until then. Disconnecting a single product in the dashboard does not remove it either. |
| Your connection record | Which AI-client connection is yours, tied to your Google sign-in, and the access it was given. The connector URL itself is public and the same for everyone — not a secret. | No set period. Switching it off ends its access at once and it is kept, marked revoked; withdrawing access at Google does not remove it. |
| The Google accounts behind each connection | The address of the Google account that granted each product connection, which can differ from the one you sign in with, and the ID Google gives that account; the IDs and names of the Google Ads accounts, Analytics properties, Search Console sites and Tag Manager containers it reaches, with the Google Ads accounts you switched on. It is how your team sees whose Google account a connection is, and how the connector knows which accounts it may act on. | Updated each time you connect. Not deleted automatically when you disconnect. |
| A ledger entry per call | Which tool ran, against which account ID, whether it succeeded, and when, with a short note of the outcome: why a call was refused, or the acknowledgement recorded when a change above the budget you set goes ahead. This is how “what did it do on Tuesday” is answerable, and how refusals are proven. For an audit, the note also records its depth, the sections it read and how many findings it returned. In a team, the workspace owner sees every member’s entries by name on the dashboard, and gets a weekly team email that counts them by person (which assistant, calls, operations, changes made, refused or failed, and the kinds of tools used); the dashboard and the email also show when each member’s assistant was connected or disconnected, a member who has not connected one is named in a reminder email to the owner, and a member sees only their own. | 180 days, then deleted. |
| Saved audit results | When an audit's results are saved to your dashboard: the account ID, any score and grade, the account-level figures it measured, such as total conversions and conversion value, with the currency, time zone and date range, a written summary of the result, and each finding with its description, the changes it suggests and up to 10 example rows from your account, so the dashboard can show the audit again. The next section says what those rows contain. | 180 days, then deleted. |
| Your Search Console site checks | If you connect Search Console, the latest result of the daily check of each site (see The daily check of your Search Console sites): the site's address and the home page address it inspected; Google's verdict on that page, its coverage, and whether indexing, robots.txt or fetching the page was blocked; whether the home page was found shown and whether the searches that find the site held steady or fell; the average impressions a day over the last 7 days and over the 28 days before them, with the day those figures end; a short error code if a read failed; when the home page was first found not shown; which of your workspace's Google connections read it; and when. So your assistant can tell you what the check found. | Replaced at each check. Deleted 14 days after the site was last checked, or when you ask us to delete your data. |
| A short-lived read cache | The rows an audit reads from Google Ads, held so a repeated audit does not ask Google twice: performance reports for 15 minutes, account settings for an hour. The account summary your assistant opens a conversation with is held in the connector's memory for 10 minutes. | Up to an hour, then it expires on its own. |
| Your workspace's business profile | What it builds as you work, so the next conversation, in any AI client, starts where the last one stopped: the business details and budget you give it, how your conversions are tracked, the first campaign it built, a log of decisions, a note on the last session, and the result of its last check of your accounts (their currency, time zone and whether they could be read). | Until the workspace owner deletes it. |
| Your routine preference | With Google Ads connected, on every plan including Free, AdCopilot switches the daily check-in on itself, and the Monday summary beside it; you can also set up a check-in in your own assistant. For each: whether it is on, the AI client it runs in, the day, hour and time zone, how you want it delivered, the goal you gave it, and when it was switched on — with your email address when that was done from the dashboard, or a note that AdCopilot did it. So AdCopilot knows when to send the check-in, and the assistant knows the routine you chose. | No set period. Switching it off keeps the day, hour, time zone and goal, and it is not cleared when the business profile is deleted. |
| Billing records | Your plan and its status and how many operations your workspace ran each day; once you start a checkout, the Razorpay customer and subscription IDs and the plan, currency, seats and billing interval you picked, whether or not you then pay; if you add a card during the trial, that a card is on file, the plan you chose and the date of the first charge, and the time you agreed to that charge and the version of the wording you agreed to (the card details themselves are collected and held by Razorpay or Dodo Payments, never by us); when the trial paused at its operations limit and which accounts that switched off; if you check out with Dodo Payments, the checkout, customer and subscription IDs it gives us and the email address you pay with; and a record of each payment event: its status, amount, any tax, currency and any failure reason and, for a payment Dodo Payments took, the link to its invoice, which shows the details you bought with, such as your name and any tax ID. When you start a checkout from the Billing page, we also keep the time zone your browser reports and the country it is in, and when you first pay, the billing country Dodo Payments read at checkout and whether you gave a tax ID (never the ID itself). So plan limits, billing and payment support work, and so we can count, by country, how many buyers reach checkout and how many pay. | No set period; not deleted automatically. |
| Email records | Which email we sent, to which address and when, and, for emails whose links pass through app.adcopilot.cloud, whether a link in it was followed (when first, and how many times), so we can tell which emails help; whether our email provider, Resend, delivered each email and when and, for our formatted (HTML) emails, whether and when it was opened and a link in it clicked, because those emails carry a small tracking image and their links go through Resend's tracking address first (plain-text emails have neither, so they are not tracked this way); for the link in a message AdCopilot gives your AI assistant when you have used half, three quarters or all of your plan's daily limit, or when an account it asked for is switched off because your plan's account limit is reached, whether it was followed (the day, when first, and how many times), so we can tell whether people see it; the kinds of email you opted out of; and the undeliverable list, the addresses that hard-bounced or complained, so we stop sending to them. | Sent-email records 180 days, then deleted. So are the delivery and open records Resend reports for each email, and the counts for those messages' links. Opt-outs and the undeliverable list until changed, with no set period. |
| Team invitations | When a workspace owner invites a teammate, we keep the email address the owner enters, the role, and when the invitation stops working, so that the invitation's link works only for a Google sign-in to that inbox and the owner can see, re-send or revoke it. We email that address the invitation on the owner's behalf. The email names the owner by their email address and names the workspace, and we send it again only when the owner asks, never to an address that has bounced or asked us to stop. To keep one person from being sent too many, we also keep a keyed one-way fingerprint of the address, so one inbox gets at most three invitation emails a day from all workspaces together. The email is plain text and is not tracked. We use the address for nothing else: it is not added to any mailing list, and the person is sent no other email unless they accept and join. | The invitation works for 7 days, or until it is used or revoked. Our record of it (the address, kept encrypted; its fingerprint; the address in a masked form such as m***@gmail.com; and the dates) stays with the workspace's records until the workspace is deleted. The person invited can ask us at support@adcopilot.cloudto delete the encrypted address and the fingerprint sooner, and we do it on every workspace that invited them; the masked form and the dates stay with the workspace's records. The record of each invitation email is kept 180 days, as for every email. |
| Trial markers | A keyed one-way fingerprint of each of the email addresses and Google Ads account IDs that have already had a free trial, so the trial stays one per person. It is not the address or ID itself: it can only confirm an address or ID we are given again. | No set period; not deleted automatically. |
| The ad click that brought you | If you arrived from one of our Google ads and measurement was on for you on this website (see This website, and cookies): the click ID Google added to the link, when you landed and on which page, whether you had chosen Accept or measurement was on by default where you were, and the country our network provider saw your connection come from. It is kept with the workspace your first sign-in creates, so we can measure which ads lead to signups. We do not send it to anyone. | The click ID 90 days after the click, then deleted. When you landed, the page, whether you had chosen Accept and the country stay with the workspace until it is deleted. |
| The link that brought you | When you follow a sign-up link on our website or one we publish, the link names the page or channel it sits on (for example blog, docs or a social profile). When your workspace is created we store that label once, with nothing else about your visit. It is never changed, is used only to count which of our pages bring sign-ups, and is sent to no one. A sign-in that starts from an AI app’s connector is recorded as that kind of source, with no app name. | Kept with the workspace until it is deleted. |
| Sign-in sessions | A random session ID, stored only as a one-way hash, and your email address, while you are signed in to the dashboard. | Until you sign out, or 30 days after you signed in, whichever comes first; using it does not extend it. An ended session's record is deleted within a day. |
| Policy acceptances | Which version of our terms and of this policy you accepted, when, and where you did it (when you signed up, on the Approve page your AI app opens, on the dashboard, or from the link in our email), with your Google-confirmed email and your workspace. It is how we can show you accepted them. We do not keep your IP address or browser with it. | While your account exists, and deleted with it. |
| Operational records | A one-line record of each error the service logs, the results of our scheduled jobs (trial ends, billing checks, emails queued, the plan each workspace held each night), and a log of any action our staff take on your workspace, with its parameters. They can include identifiers such as your workspace, an account ID or your email address. Our job queue also keeps each job's result. They are how we find faults and account for what we did. | Errors and scheduled-job results 180 days, then deleted. The log of staff actions has no set period and is not deleted automatically. The job queue's copy of a result expires after a day. Our daily totals for the whole service (such as tool calls, sign-ups and payments) name no workspace or person and have no set period. |
| Our staff's AI working sessions | The record of a session in which one of our staff worked with the AI models described under Google user data: what they asked, and what the models read and answered. A session that investigated a bug, abuse or a problem you asked us to help with can hold the records it read, such as system log entries with your Google Ads account ID and the query that ran. | On the staff member's computer until 30 days after the session was last used, then deleted. Anthropic deletes its copy within 30 days, keeping it longer only where its terms allow or the law requires it. |
| The server's system log | What the service writes as it runs, which is how we find faults. For each Google Ads request, the account ID and the kind of request, and the text of each query your assistant or an audit ran, which can name campaigns, keywords or search terms. For a request Google rejects, its full content, such as the keywords, ad text or budget it tried to set. It also carries error messages and the results of our scheduled jobs, which can include your workspace or your email address. | About 7 days, then routine log rotation deletes it. |
| Web server logs | The standard access log of this website, its docs and the dashboard: the IP address a request came from, the time, the page and the browser. Requests to the connector at mcp.adcopilot.cloud are not access-logged. | About 14 days, then routine log rotation deletes them. |
| Database backups | A nightly copy of the whole database, so the service can be restored after a failure. It holds every record in this table that the database keeps, the refresh token still encrypted. It is kept on our server, and a second, encrypted copy is kept off-site with Amazon Web Services in Mumbai, India. | 14 days on our server, then deleted. The encrypted off-site copy is kept for about 36 days, then deleted. A record deleted from the service stays in a backup until that backup is deleted. |
| Anything you type into a form on this website | To answer your enquiry. | In our email, until it is no longer needed. |
Your advertising data
Campaigns, search terms, spend and conversions are read live from Google when you or your assistant ask, and passed to your AI client. On every plan, including Free, AdCopilot also reads your connected Google Ads account once a day on its own, to email you the daily check-in (on Mondays, the Monday summary in its place): a short audit of the account that changes nothing, whose result is kept like any saved audit. The email itself carries the account's figures (yesterday's spend, clicks, impressions and conversions, and the keywords and search terms that spent, were clicked, showed or converted the most over the last 30 days; on Mondays, the same for last week), so they pass through the email provider named under Who else touches it. You can pause it on the dashboard's Routine card, or with the unsubscribe link in the email. Four things that come from them are kept, each a row of the table above:
- The read cache. An audit's reads are cached for up to an hour, and the account summary your assistant opens with for 10 minutes, so a repeat does not ask Google twice.
- Saved audit results. A saved audit keeps the account-level figures it measured, such as total conversions and conversion value, and a written summary, and, for each finding, its description and the changes it suggests, with up to 10 example rows per finding, such as search terms, keywords, ad group and campaign names, landing-page URLs, conversion-action names, cost and conversions. They are kept for 180 days and then deleted.
- The business profile. It can name the first campaign it built, and its notes can mention what a session found in your account. It is kept until the workspace owner deletes it.
- The server's system log. It records each Google Ads request with the account ID and the text of the query your assistant or an audit ran, and the full content of any request Google rejected, such as the keywords or ad text it tried to set. Routine log rotation deletes it after about 7 days.
Each nightly database backup also holds a copy of the saved audits and the business profile. The copy on our server is deleted after 14 days, and the encrypted off-site copy after about 36 days.
The ledger notes which account was touched and the outcome, never the rows that came back. The conversation itself, with whatever the connector returned into it, lives with your AI client's vendor under its policy and your plan settings.
The daily check of your Search Console sites
If you connect Search Console, AdCopilot also checks your sites once a day on its own, starting at 02:30 UTC, with the Search Console access of the Google account that connected each site. It checks up to five sites a workspace a day, taking turns when there are more, and makes two reads of each: Google's inspection of the site's home page (for a site added as a whole domain, the home page your other Search Console sites or your business profile name, or else the domain's own address), and how many times Google Search showed the whole site on each day of about the last five weeks, as one total a day, with no searches, pages or countries. Google's answer also carries each day's clicks, click-through rate and average position, which we neither use nor keep. It is there to tell you if Google is not showing your home page, or if the searches that find your site fell sharply. Only your assistant tells you, at the start of a conversation within two days of the check, and only if your own Search Console connection lists that site; it is never in an email and not on the dashboard. It changes nothing in Search Console and uses none of your daily operations. It is not a tool call, so the ledger does not record it. We keep the latest result for each site, as the table above lists, and each nightly backup holds a copy for 14 days on our server and about 36 days off-site. To stop it, disconnect Search Console on the dashboard's Google products page, or remove AdCopilot's access in your Google Account. In a team, a site that another Search Console connection in your workspace also reaches, such as a teammate's, is still checked through that one until it is disconnected too. Pausing the daily check-in on the Routine card does not stop it.
What we never collect or keep
- Your Google password. You authenticate with Google directly. We never see it and could not receive it.
- Training data. Nothing you do here trains any model. We do not have a model to train.
This website, and cookies
The connector at mcp.adcopilot.cloud sets no cookies. This website, adcopilot.cloud, loads Google Tag Manager for analytics and advertising measurement, and what it does before you choose depends on where you are. In the European Economic Area, the United Kingdom, Switzerland and India, consent is defaulted to denied: until you choose Accept in the banner, no analytics or advertising cookie is set and Google's tags record nothing that identifies you. Declining, or ignoring the banner, leaves it that way. Everywhere else, analytics and advertising measurement are on by default, and choosing Decline in the banner turns them off. If your browser sends a Global Privacy Control signal, we treat it as Decline. Google's tag works out the region from your connection. Your choice, either way, is kept in one first-party cookie named adcp_consent so we do not ask again for six months. If you arrive from one of our Google ads and measurement is on for you under these rules, we also keep the click ID Google adds to the link (gclid, gbraid or wbraid), with when you landed and on which page, in a second first-party cookie named adcp_click, so we can measure which ads lead to signups. It lasts 90 days and only our servers can read it. Its domain is adcopilot.cloud, so your browser also sends it to our subdomains; your next sign-in at app.adcopilot.cloud deletes it, after copying it onto your workspace if that sign-in creates it. Choosing Decline deletes it too. You can verify all of this in your browser's developer tools.
Google user data, and the Limited Use rule
AdCopilot’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In practice that means what the rest of this page already says, stated in Google’s terms: we use your Google data only to provide and improve AdCopilot’s user-facing features (what you or your assistant ask for; the audit, its checks and the dashboard that shows them; the daily check-in email, which the dashboard's Routine card shows and lets you pause; and the daily check of your Search Console sites, whose findings your assistant gives you at the start of a conversation and which disconnecting Search Console stops), we do not use it for advertising, we do not sell or rent it to anyone, we do not transfer it except to the sub-processors named below, and no human at Atromx reads it except as the aggregated statistics described next, where you ask us to help with a specific problem, where we must investigate a bug, abuse or another security problem, or where the law requires it.
In a team, the workspace owner can let a teammate's assistant use your Google login, read-only or to make changes and only for the accounts the owner picks, once you switch on “Let teammates use this login” on the Team page. Google's change history then shows your account, so AdCopilot records which teammate made each call; you and the owner can see that list and stop the sharing at any time, nobody else uses it while your seat is paused, and it ends 14 days after you leave the workspace.
To improve those features, for example to find an audit check that wrongly flags most of the accounts it runs on, we compute aggregated statistics across workspaces, such as how often each check fails or how many accounts run each campaign type. We compute them on our own server, from the data this page says we keep, and leave out our own and demonstration workspaces, any workspace whose owner, or anyone who connected a Google account to it, has not yet accepted this policy, and any workspace whose owner switched the statistics off or asked us to (see Your rights). They name no person, workspace, account, campaign, keyword or search term, and no figure in them describes fewer than five accounts: we withhold any figure about fewer than five accounts, any part of a group whose rest is fewer than five, so that it cannot be worked out by subtraction, and any lowest or highest value, which always belongs to one account. We use AI models from Anthropic to analyse these statistics and to develop the audit's rules, and for that work Anthropic receives the statistics only, not the rows they are computed from.
Our staff also use Anthropic's models as a working tool when they build, run and support AdCopilot, so the models can read the service's own records, such as your email address and name and your workspace's plan, billing and usage records. The models read the data that comes from your Google products only when one of our staff investigates a bug, abuse or a problem you asked us to help with, and then only the records that investigation needs, such as the system log entries of a failed audit, which carry the Google Ads account ID and the query that ran. In both uses Anthropic processes the data on our behalf as a sub-processor (listed below), under its commercial terms, which do not permit it to train models on our data, and deletes what it receives within 30 days, keeping it longer only where those terms allow, for example where its systems flag a breach of its usage policy, or where the law requires it. On our side, the record of each such working session is kept as the table under What we collect says, and the aggregated statistics, which describe no single account, are kept with our development notes for as long as we use them to improve the checks.
Where it runs
The connector, its database and your encrypted credential run on a virtual server operated by Hostinger International Limited in Kuala Lumpur, Malaysia. If you are in the UK or the EEA, that is a transfer outside your region, and there is no adequacy decision covering Malaysia — we would rather state that plainly than leave you to discover it. An encrypted copy of each nightly database backup is also kept with Amazon Web Services in Mumbai, India, which has no adequacy decision either. Ask us if you need contractual terms covering either.
Who else touches it
Only because of choices we made. Google's own APIs are not on this list: you grant access to your own Google accounts, and the data moves under your own credential, so there Google is your provider rather than our sub-processor.
| Who | What they do | Where |
|---|---|---|
| Hostinger International Limited | Virtual server hosting. The connector, the database and the encrypted credentials sit on a machine they operate. | Kuala Lumpur, Malaysia |
| FormSubmit (formsubmit.co) | Delivers the enquiry forms on this website to our inbox. It sees whatever you type into a form; it is not involved in the connector or in any advertising data. | United States |
| Google (Tag Manager and Analytics) | Website analytics and advertising measurement on adcopilot.cloud. In the European Economic Area, the United Kingdom, Switzerland and India it starts with consent denied and switches on only if you accept the banner; elsewhere it is on until you choose Decline, or your browser sends a Global Privacy Control signal. Not involved in the connector. | United States |
| Razorpay Software Private Limited | Takes subscription payments. It receives the workspace name and the owner's email address to set up the billing customer, and the card, UPI or bank details you enter at checkout go to it directly; we never see or store them. | India |
| Dodo Payments | Our reseller and merchant of record for payments in US dollars or euros from outside India: when it sells you a plan, you pay it, and it issues the invoice and collects any tax due. It receives the workspace name and the owner's email address for the purchase, and the card or other payment details, billing address and any tax ID you enter at its checkout go to it directly; we never see or store your card or payment details. As the seller, it keeps its own records of the sale. | To be confirmed: Dodo Payments has not yet told us in writing which company in its group sells to you. |
| Resend | Sends the service's emails: account, billing and product notices, and the daily check-in, which carries the Google Ads account's spend, clicks and conversions and its top keywords and search terms. It receives the recipient's address and the message, and reports back whether each email was delivered and, for our formatted (HTML) emails, whether it was opened and a link in it clicked. | United States |
| Amazon Web Services (Simple Email Service) | The configured alternative route for the same emails. When it is used, it receives the same address and message. | India (Mumbai region) |
| Amazon Web Services (S3) | Stores the encrypted off-site copy of each nightly database backup, so the service can be restored if our server is lost. The copy holds every record the database keeps, the refresh token still encrypted; the key that decrypts the token is never sent to it. Each copy is deleted after about 36 days. | India (Mumbai region) |
| Cloudflare | Sits in front of adcopilot.cloud and www.adcopilot.cloud as a content-delivery network and proxy, so it handles each request to this website, including your IP address. The connector, the dashboard and the admin console are not routed through it. | Global network; United States company |
| Anthropic, PBC | Provides the AI models our staff work with, in two ways. They analyse the aggregated statistics described under Google user data and develop the audit's rules from them; for that, Anthropic receives the statistics only, which name no person, workspace, account, campaign, keyword or search term and hold no figure about fewer than five accounts. And they are our staff's working tool when they build, run and support the service: the models can read the service's own records, such as your email address and name and your workspace's plan, billing and usage records, and, only while one of our staff investigates a bug, abuse or a problem you asked us to help with, the data from your Google products that investigation needs, such as system log entries that carry a Google Ads account ID. Anthropic processes all of it on our behalf, under its commercial terms, which do not permit it to train models on our data, and deletes it within 30 days, keeping it longer only where those terms allow or the law requires it. | Stored in the United States. Requests may be processed in the United States, Europe, Asia or Australia; safety review, support and incident response may take place wherever Anthropic or its affiliates operate |
How it is protected
- Your Google refresh token is encrypted at rest, with the key in a separate file on the server that only the AdCopilot service can read, outside the database, so a copy of the database alone does not yield a usable credential.
- The connector URL is public and the same for everyone, so its request paths carry no secret. What matters — your Google refresh token — is encrypted and never written to logs or the ledger.
- Everything travels over HTTPS, and the connector refuses expired, deactivated or out-of-scope requests before any call reaches Google.
- We hold no SOC 2 or ISO 27001 certification. We would rather say so than imply otherwise.
Your rights, and the fastest route to each
- Withdraw access immediately — your Google Account's third-party access page. Removing AdCopilot there revokes the credential at source, without our involvement and without waiting for us.
- Have your data deleted — email support@adcopilot.cloud. We remove your account, your encrypted credential, what it remembered and your ledger. We keep billing records, without your name or email, for as long as tax law requires, and a one-way code of your email address so a free trial cannot be claimed twice. Backups that still hold your data are deleted within 14 days on our server and within about 36 days off-site. If Dodo Payments sold you a plan, it keeps its own records of that sale, as the seller.
- Ask what we hold — same address. We will tell you everything we hold about you and your workspace; the table above lists the kinds of record.
- Object or complain — write to us first, and you retain the right to complain to your local data-protection authority. To object to the aggregated statistics described under Google user data, the workspace owner can switch them off in Settings on the dashboard, or write to us; either way we leave your workspace out of them from then on.
Where the UK GDPR or EU GDPR applies, we process your account details and credential to perform our contract with you, keep the ledger on the legitimate interest of being able to show what a connector did, keep the trial markers on the legitimate interest of preventing repeat free trials, keep the record of the terms and policy you accepted on the legitimate interest of being able to show you accepted them, compute and analyse the aggregated statistics described under Google user data on the legitimate interest of improving the service, and investigate bugs and abuse, with the AI models described there, on the legitimate interest of keeping the service working and secure.
Children
AdCopilot is a business tool and is not directed at anyone under 18. We do not knowingly collect their data.
Changes
If this policy changes materially, we will update the date at the top, email the workspace owner a short notice, and ask you to accept the new version the next time you sign in to the dashboard.