Privacy Policy

Admiral (“we”, “us”) is a paid-ads management product operated by 4UGUSTA Systems Private Limited, Gaya, Bihar, India. This policy explains what data we collect when you use Admiral at meetadmiral.com, why we collect it, and the choices you have.

What we collect

• Account data: your email address and name, used to sign you in and contact you about your account.
• Advertising data: when you connect an ad platform (Google Ads, Meta Ads), we access campaign structure, performance reports, budgets, keywords, search terms, and ads from the accounts you authorize. If you connect Google Merchant Center, we also read your product feed to build and audit Shopping campaigns.
• Creative you generate: the images and short videos Admiral generates for your ads from your website, logo, or product photos, stored so you can reuse them. If you enable Video, the generated ad video is uploaded to your own YouTube channel as unlisted and only its video ID is used in your campaign.
• Usage data: actions you take inside Admiral (approvals, reverts, settings), kept as an audit log so you can see and undo what changed.
• Voice: if you talk to Admiral by voice, what you say is turned into text, and the transcript is stored with the record of that conversation in your workspace. Admiral stores the transcript, never the audio.
• Your leads: if you connect Meta lead forms or a CRM, the names, email addresses and phone numbers of people who answered your ads. We hold them for you, show them only to your workspace, and send them only where you tell Admiral to.
• Payments: Dodo Payments, the merchant of record, holds your card details. We receive the plan, the amount and whether it was paid.

Google user data

When you connect Google Ads, Admiral requests the Google Ads API scope (https://www.googleapis.com/auth/adwords). We use it only to:

• read your campaign, ad group, keyword, search-term, and cost reports to detect wasted spend and show you dashboards;
• apply changes you explicitly approve in the app: pausing or enabling campaigns, ad groups, keywords and ads, blocking search terms, adding keywords or negative keywords, adjusting budgets or bids, editing ads, and creating new campaigns that arrive paused. Every successful change is logged with a receipt. Reversible changes include an undo where the platform permits it; final actions are labelled before approval.

If you choose to let Admiral install your conversion tag through Google Tag Manager, it additionally requests four Tag Manager scopes (tagmanager.readonly, tagmanager.edit.containers, tagmanager.edit.containerversions, tagmanager.publish). This is opt-in and separate from connecting Google Ads. We use them only to:

• list the Tag Manager accounts, containers and workspaces you can access, so you can choose which container to use;
• check whether a Google Ads conversion tag is already present, so we never install a duplicate;
• create one workspace containing a Google tag, a Conversion Linker, a conversion tag and a pageview trigger, and nothing else;
• create and publish a version of that workspace, so the tag goes live.

Admiral only modifies resources it created. Removing the tag republishes the version that was live before Admiral touched the container, or (if you have published changes since) removes only Admiral’s own named resources and leaves everything else alone. We do not read the contents of your other tags, and we do not use Tag Manager data for any purpose other than installing, verifying and removing your conversion tag.

If you turn on Video ads, Admiral requests the YouTube upload scope (https://www.googleapis.com/auth/youtube.upload). This is opt-in and separate from connecting Google Ads. We use it only to:

• upload the ad video Admiral generated for you to your own YouTube channel, set to unlisted, so it can serve as a Video campaign;
• reference that video’s ID in the Google Ads Video campaign you approve, and nothing else.

We do not read, list, modify or delete any other video on your channel, and we do not use YouTube data for any purpose beyond running the ad video you asked us to.

If you turn on Shopping ads, Admiral requests the Content API for Shopping scope (https://www.googleapis.com/auth/content) to reach your Google Merchant Center. This is opt-in and separate from connecting Google Ads. We use it only to:

• read your product feed and its item status, so we can build a Shopping campaign and audit it for disapproved products, stale items, and product groups spending with no conversions;
• surface the exact product and reason in your dashboard so you can fix it.

We do not use Merchant Center data for any purpose other than building and auditing your own Shopping campaigns, and we never sell it or share it with third parties.

If you turn on Search Console, Admiral requests the read only Search Console scope (https://www.googleapis.com/auth/webmasters.readonly). This is opt-in and separate from connecting Google Ads. We use it only to:

• list the Search Console sites your Google login can see, so you can choose the one that is your business’s website;
• read, for that one site, how often it appeared in Google’s free search results for each search over the most recent 28 days Google has finished counting, where it ranked, and how often people clicked;
• show that beside the searches your ads paid for, with one suggestion per search, and use it to answer your questions when you ask Admiral about them.

Admiral cannot change anything in Search Console. We do not read search data for any site other than the one you chose, and we do not use Search Console data for any purpose other than that comparison.

Admiral’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, do not use it for advertising of our own, and do not allow humans to read it except with your consent, for security, or to comply with law. Google user data is never transferred to third parties except as needed to provide the product’s user-facing features.

Beyond the hosting and database providers that store it, Admiral sends the Google data a task needs only to the AI model providers listed below, so they can return the result to you.

How data is stored and protected

• OAuth tokens are encrypted at rest. Raw advertising data is stored in our database (hosted in the United States) and used only to render your dashboards and run the checks you have enabled.
• All traffic is encrypted in transit (TLS). Access to production systems is restricted to the operator.
• We retain your data while your account is active. Disconnecting an ad account stops collection; deleting your account removes your stored data within 30 days.

What we never do

• We never sell your data or share it with advertisers.
• We never change your ad accounts without your approval, except rules you explicitly delegate (which are limited to pausing and blocking).
• We never use your advertising data to train machine-learning models unrelated to serving you.

Cookies and measurement

The first time you arrive we ask whether we may measure the visit. Nothing in the table below is set before you answer if you are in the EEA, the UK or Switzerland. Everywhere else measurement starts on arrival and the same banner, reachable at any time from Cookie choices in the footer, or from Settings once you are signed in, turns it off and deletes what was set.

• Keeping you signed in: your Admiral session, and a short-lived admiral_oauth_nonce that exists only while you are connecting an ad account. These are required for the product to work, are never used for advertising, and are not part of the choice above.
• Google (_ga, _ga_*,_gcl_au): Google Analytics 4 and Google Ads, so we can see which ad or search brought you here. We run Google Consent Mode: with your answer set to no, Google’s tag stores nothing on your device.
• Meta (_fbp here, fr on facebook.com). The Meta pixel, for the same question about Facebook and Instagram ads. With your answer set to no the pixel is never loaded at all, so no request reaches Meta.
• PostHog (ph_*): how the site and the product are actually used, and session replays that show us where people get stuck. Hosted in the United States.
• Microsoft Clarity (_clck, _clsk): a second set of session replays of the public pages, kept in case PostHog’s are unavailable. Like the Meta pixel, it is never loaded while your answer is no, and saying no later stops it. It records only public pages, never your own account: nothing you see signed in, and not the page you return to after paying.
• Sentry: crash reports when something breaks. It stores nothing on your device: it records the error, the page and the browser, so we can fix what broke. Because it stores nothing, it keeps running while you have not answered, but if you say no, it stops too.
• Cal.com: only on the booking page. Where we must ask first, or if you have said no, the calendar is not loaded until you pressShow the calendar; pressing it lets Cal.com store its own cookie so it can remember your booking. You can always book on cal.com instead, and nothing is loaded from them here.
• YouTube: videos on this site are embedded throughyoutube-nocookie.com, which sets nothing unless you press play.

What session replays do not contain. Every piece of text is masked before a replay leaves your browser: money figures, campaign names, and the names, email addresses and phone numbers of your own leads. What is recorded is the shape of the page and where you clicked. The same masking applies to the text of anything you click.

We do not use a cookie wall: refusing changes nothing about what the product does for you.

Third-party services we rely on

Each processes data only as needed to provide the product:

• Hosting and database: Amazon Web Services, Microsoft Azure and Supabase, in the United States.
• AI model providers: to read your website and accounts, draft ads, images, video and pages, answer your questions and transcribe voice. Each receives only the part of your data a task needs.
• Real-time voice infrastructure: for voice conversations only.
• Email delivery: for account and alert emails, and for the emails described under If we wrote to you.
• Dodo Payments: the merchant of record for purchases.
• Search and market data services: to show what people search for near you.
• Measurement: Google Analytics, Google Ads, the Meta pixel, PostHog (product analytics and session replay), Microsoft Clarity (session replay) and Sentry (crash reporting), only with your agreement: see Cookies and measurement.
• Cal.com: for booking a call.
• Calls you ask for: an AI voice service, a US telephone carrier and a text message verification service, only if you ask us to call you: see If you ask us to call you.
• The accounts you connect: the advertising, search and CRM accounts you authorise.

If you ask us to call you

On the contact page you can ask for a call back from an AI voice. It is offered only for US numbers. If you tick that box we keep the number you typed, the exact words you agreed to and their version, the time, the page, and the time zones we checked calling hours against. Before any call we text a code to the number to confirm it is yours; a text message verification service checks the code, and we never store it.

The call is placed by an AI voice service through a US telephone carrier. The voice service records and transcribes it. We keep only how the call ended and how long it lasted, never the recording or the transcript. We call a number at most once a month, and only within the hours the law allows.

Say “stop” on the call, or ring the do-not-call number the call gives you, and your number goes on our do-not-call list at once. We keep that number so that we never call it again.

If we wrote to you about Admiral

We sometimes write to a business that advertises, one person at a time, when a public sign from the last 30 days shows it runs ads now: an ad in a public ad library, or a job post for someone to run them. We found your work contact details on your company’s own pages, in that public sign, or through a contact data provider.

We keep your name, work email or phone, your company, the sign that brought us, and what we sent and what you replied, only to write to you and to remember your answer. Reply “stop” to any email and we will not contact you again; we keep only a note of your address so that we never do. Ask us and we will tell you exactly where your details came from, or delete them.

Contact

4UGUSTA Systems Private Limited (CIN U62011BR2026PTC084868) · Gaya, Bihar, India
Data protection, grievances and everything else: augusta@meetadmiral.com