You stay in control.
GX360 is built around one rule: agents and experts can prepare the work, but nothing that touches your live site or accounts happens without your approval.
How a change actually
reaches your site.
Every change follows the same path — prepared by an agent, approved by you, carried out by the agent, and logged.
- Agents watch & propose
- AI agents monitor your connected sources, surface findings and prepare draft fixes.
- You approve
- Anything that touches your live site or accounts waits for your yes. We ask by email, WhatsApp or a call, and record who approved, how and when.
- GX360 carries it out
- The agents make the approved change on the connected account and log it. Fixes that need code are made by the Fixing Agent on a local git branch for your developer to review (Growth and Scale), or handed to your developer as an exact brief. Nothing goes out unapproved, ever.
- Every change is logged
- What changed, when, why and who approved it stays in an audit trail.
What we promise
- Your Google data stays in your Google account
- We read through Google’s API with the access you grant. We don’t copy your accounts out, and you can revoke access any time.
- AI assistant access is read-only
- The optional MCP connector reads your data only — it cannot change anything, and nothing is connected until you do it.
- No public change without approval
- Agents and specialists can prepare anything, but nothing public ships until you approve it.
What each connector shares,
and for how long.
You grant access connector by connector. Here is what GX360 reads, where it lives and how long we keep it.
| Connector | What GX360 accesses | Where it’s stored | Retention |
|---|---|---|---|
| Google Search Console | Read-only: search queries, impressions, clicks and index coverage. | Stays in your Google account; read via Google’s API. | Report snapshots kept for the engagement; removed on request. |
| Google Analytics (GA4) | Read-only: traffic, conversions and channel performance. | Stays in your Google account; read via Google’s API. | Report snapshots kept for the engagement; removed on request. |
| Google Ads | Read, plus the changes you approve: search terms, keywords, conversion goals. | Stays in your Google account; approved changes applied by an admin on your team. | Change log retained; account data is not copied out. |
| Microsoft, Meta and LinkedIn Ads | Read campaign results; pauses and budget changes only after you approve them. Meta is read-only today. | Your ad accounts stay in your own business managers; GX360 keeps an encrypted access token and the account IDs. | Daily results kept for the engagement; access revocable any time. |
| Google Business Profile and Bing | Profile, reviews and Bing search data; replies, edits and URL submissions only after approval. | Stays in your Google and Microsoft accounts; read via their APIs. | Snapshots kept for the engagement; removed on request. |
| Website / CMS | Public pages we crawl; CMS edit access only when publishing is in scope. | Crawled content stored with your GX360 workspace. | Kept for the engagement; removed on request. |
| CRM / pipeline (optional) | Read-only deal and lead stages, only when pipeline tracking is agreed. | Aggregated into your workspace reports. | Kept for the engagement; removed on request. |
| Payments | Card payments go straight to Razorpay (INR) or Stripe (USD). | GX360 keeps the plan, invoices and payment status — never card numbers. | Invoices kept as required by tax law. |
| AI answer engines | Only the questions you track, e.g. “best CRM for small teams”, to see whether you are cited. | Answers stored with your workspace for trend charts. | Kept for the engagement; removed on request. |
| Your website's code (Fixing Agent) | The Work items you choose for one website. Claude Code or Codex makes each fix on your developer's machine, on its own local git branch with one commit. It never touches secrets, .env files, CI or deploy configuration, and nothing is pushed, merged or deployed. | Your code stays in your repository on your developer's machine and is not uploaded to GX360. GX360 receives the branch name, commit, the names of the changed files, a short summary, and whether your check command passed with the last part of its output. | The key covers one website, expires and can be revoked at any time. The fix report is kept with the Work item. |
| AI model providers | Only the text needed for a specific task, e.g. an audit prompt or a draft. | Processed by the provider to return a result and not used to train its models. Requests to OpenAI are sent with storage turned off. | Not retained for training; transient processing only. |
Which AI sees
your data.
GX360 uses large language models to draft and analyse. Today that means OpenAI, Anthropic (Claude) and DeepSeek, set per company for quality and cost. Only the text needed for a task is sent, and your data is not used to train any provider’s models.
Requests to OpenAI are sent with storage turned off, so they are not kept in the account’s OpenAI dashboard. Each provider still handles requests under its own API data policy.
Customers with stricter requirements can request an OpenAI-only configuration, enforced on every task, so no task is routed to any other provider. AI visibility checks send only your tracked questions to the engines being checked. When you connect Claude, it reads your GX360 data — read-only — under your Anthropic account.
On the Managed plan, GX360 can run on your company’s own OpenAI or Anthropic API key, so AI usage is billed to your provider account. Our team sets the key for you. It is stored encrypted, shown only as its last four characters, and removed whenever you ask.
The Fixing Agent uses Claude Code or Codex, signed in under your developer's own Anthropic or OpenAI account on their machine. Those tools read your code there, under that account's terms; GX360 does not receive or store your source code.
- OpenAI
- Anthropic
- DeepSeek
- Claude Code
- Codex
- OpenAI-only option