Security and access
What Operax asks Google and Meta for, what it can do with it, and what it cannot do at all.
What access Operax asks for
| Platform | Permission requested | Why |
|---|---|---|
| Google Ads |
| Read campaigns, search terms, keywords, ads, budgets and results; apply the changes you approve. Google offers a single permission for Google Ads. It always includes the ability to make changes; there is no read-only version. Operax enforces read-only on its own servers: on a read-only connection, the code path that sends changes to Google is blocked. |
| Google Ads (revenue feedback) |
| Send the value of jobs you actually won back to Google, so its bidding learns from revenue instead of from form fills. Asked for separately, and only when you turn on revenue feedback or customer-list matching. Declining it changes nothing else. |
| Google Business Profile |
| List the locations your Google login manages, read the reviews of the ones that are your business’s, and publish the review replies you approve. Asked for only when you connect Google Business Profile. Google offers one permission for these APIs, so there is no narrower one. |
| Google Search Console |
| Read which searches your website appears for, its position and the page that ranked, for the SEO keyword and ranking screens. Asked for only when you connect Search Console. It is read-only: Operax cannot change anything in Search Console. |
| Google Tag Manager |
| Read your Tag Manager containers, add the Google and Meta tags your ads need in a new version you approve first, publish it, and put the version it replaced back if you ask. Asked for separately, only if you choose to have Operax build your Tag Manager container, and only once that option is switched on. Declining it changes nothing else; the other ways to put tags on your website need no Google permission. |
| Google Analytics |
| Read the Google Analytics accounts and properties your Google login reaches, and, after you approve the plan, create your property, its web stream and the link to your Google Ads account; remove what Operax created if you ask. Asked for separately, only if you choose to have Operax set up Google Analytics 4, and only once that option is switched on. Operax reads no visitor data from Google Analytics, and declining it changes nothing else. |
| Meta (read-only audit) |
| Read campaigns, ad sets, ads and results. This is all a read-only Meta connection asks for. Lead forms are not captured while a connection is read-only. |
| Meta (managed) |
| Apply the changes you approve, and receive the leads people submit through your Facebook and Instagram lead forms. Requested only when you switch Meta to managed access, in a second sign-in you can decline. |
Read-only and managed connections
A read-only connection can be analysed and reported on, and nothing else. Every path that would send a change to Google or Meta is refused on our servers before it reaches the platform.
A managed connection can also apply the changes you approve. You choose per connection, and you can switch back to read-only at any time.
You can remove Operax’s access at any time. Disconnecting a channel in Operax deletes the access token Operax stored for it and asks Google or Meta to revoke Operax’s access. Google withdraws access for a whole Google login at once and Meta for a whole Facebook login, so Operax skips that request while another Operax connection may still depend on the same login; the Privacy Policy, section 8, says exactly when. You can also remove it yourself, for Google at myaccount.google.com/permissions and for Meta in Facebook under Settings, then Business integrations. After you remove it at Google, Operax’s next request to Google fails and the connection is shown as needing to be reconnected; after you remove it in Facebook, Facebook tells Operax, which disconnects the connection and deletes the token.
What the AI can do
- Change a campaign budget
- Pause a campaign
- Add negative keywords so your ads stop showing on searches that never convert
- Add keywords
- Rewrite responsive search ad headlines and descriptions
- Turn on a paused campaign it created
- Adjust a Google Ads target cost per conversion (target CPA) or target return on ad spend (target ROAS)
What the AI cannot do
- Access your payment methods or billing details in Google Ads or Meta.
- Create or remove users on your ad accounts.
- Act at all on a read-only connection.
- Exceed a guardrail you set.
- Act while the kill switch is on.
- Turn on something it created without that being approved as its own change.
- Send your data to other advertisers, or use it to train models for other customers.
- Operax reports on Local Services, Smart, Shopping, Display and Video campaigns but does not change them.
- Retail (Shopping and feed-based Performance Max) campaigns are reported, not managed.
Guardrails
Guardrails compare against what your ad accounts report, not against numbers written by the AI.
- A daily spend ceiling and a monthly spend ceiling for the whole account.
- A maximum budget change per step, so no single action can move a budget by more than a set percentage.
- A maximum number of actions per day.
- An approval threshold in money: anything above it always asks, whatever else is switched on.
- Protected brand terms, so your own name is never blocked or bid away.
- Quiet hours for anything that contacts a customer.
A spend ceiling is a limit Operax enforces on itself. It is not a hard stop inside Google or Meta: an ad platform can spend more than a daily budget on a given day, and no software outside the platform can prevent that.
Approvals, rollback and the kill switch
An approval shows the change, the evidence behind it, what it expects to happen and how it will be undone. Approving is one click; so is undoing it afterwards, because the previous state was captured before the change was sent.
The kill switch stops every AI action for your whole account immediately. Rollback keeps working while it is on, so switching it off is never a trap.
How your data is handled
- OAuth tokens are encrypted at rest with Fernet, under a key kept in the server environment and never in the database.
- Your data is used to provide the service to you, and is not sold.
- Data from the accounts you connect is sent to an AI provider so the agents can analyse it and draft proposals and replies: Anthropic, with OpenAI for some features. Under their API terms it is not used to train their models. Which data goes to which provider is in the Privacy Policy, section 4, and every sub-processor is named in section 5.
- The account owner can ask for the account’s data to be deleted, as section 8 of the Privacy Policy describes.
- Operax’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. What that commits Operax to is in section 9 of the Privacy Policy.
- Operax gives data to a public authority only when the law requires it; see section 11.
- The full detail is in the Privacy Policy.
Technical and organisational measures
The same list our data processing agreement carries as its Annex II. Each one is something the software itself does.
- Encryption. Connections to the Service, and its calls to the sub-processors in Annex III, are encrypted in transit with TLS. The production site redirects plain HTTP and sends HSTS.
- Encryption. OAuth tokens and provider credentials are encrypted at rest with Fernet, under a key kept in the server environment and never in the database.
- Sign-in. Passwords are stored only as Argon2 hashes, and repeated failed sign-ins lock the account for a period.
- Sign-in. Every user can turn on two-step verification with an authenticator app; recovery codes are stored only as hashes and work once.
- Access control. Inside an account, what a person may see and do follows their role (owner, admin, manager, analyst, viewer), and a person invited for one business sees that business only.
- Access control. Every request is limited to the caller's own account, and an automated test walks every endpoint to prove another account's rows are invisible.
- Records of access and change. When a member of staff opens a customer's data in the administration area, the access is recorded first, and the page is refused if the record cannot be written.
- Records of access and change. Sign-ins, failed sign-ins, password and two-step changes, and the account's legal acceptances are recorded in the account's security log.
- Safe changes to connected accounts. A new ad-account connection is read-only, and every path that would change a connected account is refused on the server while it stays read-only.
- Safe changes to connected accounts. Every change sent to a connected account records who or what approved it, and the account's kill switch stops every automatic action at once.
- Data minimisation. Phone numbers, email addresses and card numbers are removed from call transcripts before an AI model reads them, and customers' contact details are never given to the AI agents.
- Retention and deletion. The words of call transcripts are deleted after the business's retention period, 90 days unless the business chooses otherwise.
- Retention and deletion. A customer's details can be erased from every record that holds them, and Meta's data-deletion callback is honoured.
- Records of access and change. An accepted data processing agreement is stored with the exact words and annexes accepted, and the database refuses any later edit of it.
Controls proven right now
Each statement below is shown only while the check behind it passes: the setting it depends on is on in production, and its latest evidence, produced on its own schedule, passed. When a check fails or its evidence is overdue, the statement leaves this page.
This list is read live from Operax’s servers, so it only ever shows what is proven at the moment you look. Loading it now.
Accessibility
The console and this site are tested against WCAG 2.2 Level A and AA on every release. Our Accessibility Conformance Report (based on VPAT® 2.5, International Edition) states, criterion by criterion, what those tests show and what has not been evaluated yet: read the Accessibility Conformance Report.
Limits of our responsibility
Your ad spend is yours: it is charged by Google and Meta directly to your payment method, and Operax cannot see or control it. What Operax is responsible for, and what it is not, is set out in the Terms of Service.
Report a security issue
Write to the security contact named in our security.txt, with enough detail to reproduce it. Please do not test against another customer’s account.
Vulnerability disclosure
Scope. The Operax website, console, API and the public pages Operax serves, and Operax’s own integrations with Google, Meta and the other providers. Not the providers’ own systems, not customers’ own websites, and no denial-of-service or social-engineering testing.
Rules. Test only against an account you own. Never access, change or delete another customer’s data, and never change anything in an ad account you do not own or start or raise ad spend. If you reach data that is not yours by accident, stop, keep no copy, and say so in your report. Keep the details confidential until we have agreed a disclosure date with you.
Safe harbour. Research carried out in good faith and within this policy is authorised. We will not bring or support legal action against you for it or report you to law enforcement, and we treat it as exempt from the restrictions of our Terms of Service on circumventing protections and unauthorised access. If someone else takes action against you for research within this policy, we will make it known that it was authorised. Unsure whether something is in scope? Ask before you go on.
What we do with a report. We acknowledge it, assess it, keep you told while it is fixed, agree when it may be disclosed, and credit you if you wish. There is no bounty programme.
Try Operax free for 14 days
Start with your website. Connect your ad accounts when you are ready. No card needed.