Privacy Policy
Last updated 29 September 2026. Questions: admin@orchadstrate.com
Who we are
Orchadstrate is a budget orchestration platform for Google Ads, made and operated by The Third Way, Sydney, Australia. This policy explains what we collect, why, who sees it, how it is protected, how long we keep it, and what we never do with it. It applies to this website and to the Orchadstrate application at orchadstrate.com/app.
Contact: admin@orchadstrate.com
What we collect
Your account details. Your name, email address and profile picture from the Google account you sign in with, and the organisation you say you belong to. We use these to sign you in and to contact you about the service.
Google Ads data, when you connect an account. With your authorisation, through the Google Ads API, we read from the Google Ads accounts you choose to connect:
- campaigns, their names and status
- campaign budgets and their amounts
- performance metrics: cost, clicks, impressions, conversions, conversion value
- each campaign's bidding strategy type and, where one is set, its target cost per action or target return on ad spend, which we show beside your own targets and never change
- the account's name, time zone and currency
We read this so we can learn how each campaign spends through the day and pace its budget. We do not read your ads, your keywords, your audiences, your billing information, or anything about the people who see your ads.
What we write back. The only change we ever make to a Google Ads account is adjusting a campaign's daily budget amount, within limits you set. Every change is logged and visible to you.
Payment details. Handled entirely by Stripe. We never see or store your card number.
Cookies on this website. The site itself sets nothing until you choose. If you accept, Google Analytics measures how people arrive and which pages they read, and an advertising cookie lets us tell which advertising brought you here. Where that cookie exists, we also tell the advertising platform when you go on to sign up or subscribe, so we can see which ads are worth paying for: what we send is that cookie's identifier, the fact that it happened, and a one-way hash of your email address — never the address itself, never your name, and nothing about any Google Ads account. Decline, and the cookie is never set and nothing is ever sent. If you accept analytics, Amplitude also records how the product itself is used, including a replay of what happened on screen: pages, clicks and movement. Everything you type is masked before it leaves your browser, so we cannot see what was entered into any field. Replays are used to find and fix problems with the product, are never sold or shared for anybody else's purposes, and are deleted on Amplitude's retention schedule. Decline analytics and no replay is ever recorded. Nothing here reads the Google Ads data of anybody who has connected an account. You can change or withdraw your choice at any time from Cookie preferences, and the Cookies link in the footer of every page reopens the same choice.
Ordinary technical logs. IP address, browser, and pages viewed, kept for security and to diagnose faults.
How we use it
Google Ads data is used for one purpose: to provide and improve the budget pacing features you signed up for, on your own account. That means learning each campaign's spending pattern, deciding whether and by how much to extend a budget within your limits, showing you what happened and why, and measuring what your account actually spends so that your subscription plan is set correctly. Account details are used to sign you in, to bill you, and to tell you about changes to the service or to this policy.
Who sees it
We do not share, transfer or disclose Google user data to anyone except the following, and only to the extent needed to run the service:
- Google Cloud hosts the application and stores the data, in Australia.
- Stripe processes payments. Stripe receives your name, email address and card details; it never receives Google Ads data.
- Google Analytics, on this website only and only if you accept cookies, receives page views. It never receives Google Ads data.
- Amplitude, on this website and in the application, only if you accept analytics, receives page views, clicks and a masked session replay. It never receives Google Ads data: no account identifiers, campaign names, budgets or spend figures.
- How you are identified to them. When you are signed in, Google Analytics and Amplitude receive an irreversible keyed hash of your account, and the id of the workspace you are looking at. Neither receives your email address or the identifier Google issued for you.
Beyond those, we disclose data only where the law requires it, or as part of a merger or acquisition, in which case this policy continues to apply to it. Our own staff do not read your Google Ads data except with your explicit permission, for security purposes, to comply with the law, or where it has been aggregated and anonymised.
What we never do
- We do not sell your data, and we never will.
- We do not use Google user data for advertising of any kind: not targeted, personalised, retargeted or interest-based advertising, and not to serve advertisements to you or anyone else.
- We do not sell, license or transfer it to data brokers, information resellers, or advertising networks.
- We do not use it to determine credit-worthiness or for lending purposes.
- We do not use it to build databases or profiles of people, businesses or accounts for any purpose other than pacing your own account.
- We do not use Google user data to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models. What the service learns about your campaigns is used only for your account, and it is deleted when you close your account.
Limited Use disclosure
Orchadstrate'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.
How we protect your data
Security procedures are in place to protect the confidentiality of your data, including the Google Ads data we receive through Google APIs. These are the mechanisms, in plain terms.
- Encryption in transit. Every connection is encrypted with TLS: between your browser and us, between us and Google, and between us and Stripe. Nothing travels in the clear.
- Encryption at rest. All stored data, including everything read from your Google Ads account, is held in Google Cloud in Australia (australia-southeast1) and encrypted at rest using AES-256.
- Credentials kept apart from data. The Google Ads refresh token that lets us read your account is stored in Google Secret Manager, one secret per customer. It is never written to our application database, never written to logs, and never shown in the product. Revoking our access at your Google account destroys its usefulness immediately.
- Least privilege. Each part of the service runs under its own identity with only the permissions it needs. The service that talks to Google Ads is separate from the one that serves the application, and only production services can reach production data. There are no shared administrator keys.
- Separation between customers. Every request is bound to the workspace it is signed in to and can reach no other. Your data is never visible to another customer, and this is enforced in the code on every request, not by policy alone.
- Sign-in. You sign in with Google. We store no passwords. Sessions are signed, secure, HTTP-only cookies that expire.
- Human access. Our staff do not read your Google Ads data except with your explicit permission, for security purposes, to comply with the law, or where it has been aggregated and anonymised. Access to production is logged.
- Logging. Every budget change we make is recorded with its reason. Logs never contain your credentials, and they are kept only for security and fault diagnosis.
- Payments. Card details go directly to Stripe, a PCI DSS Level 1 provider, and never pass through our systems.
- Backups and deletion. Production data is backed up with point-in-time recovery. When you close your account, everything is deleted within 30 days, backups included, except records we are legally required to retain.
- If something goes wrong. If we become aware of a breach affecting your data we will tell you without undue delay, and within 72 hours where the GDPR applies, with what happened and what we are doing about it.
How long we keep it
While you are a customer: for as long as your account is open.
When you disconnect a Google Ads account: we stop reading it immediately and we no longer hold anything that lets us read it again. What it learned about that account's spending is kept, so that reconnecting it does not start from nothing. Ask us to delete it and we will.
When you close your account: everything is deleted within 30 days, including what we learned, except records we are legally required to retain such as invoices.
Your rights
You can ask us to show you the data we hold about you, correct it, delete it, or export it. Email admin@orchadstrate.com and we will respond within 30 days.
You can disconnect a Google Ads account at any time from within the product, and you can revoke our access directly at myaccount.google.com/permissions. Revoking access stops every read and every change immediately.
If you are in the EU or UK you have rights under GDPR, including the right to complain to your local supervisory authority. If you are in Australia, the Privacy Act 1988 applies.
Changes
If we change this policy materially, including any change to how we use Google user data, we will email you before it takes effect and update the date at the top of this page.