How Ooty Protects Your Marketing Data

1. Your AI assistant sends the request to Ooty's servers, authenticated with your license key.
2. Our server validates your identity and retrieves your encrypted credentials.
3. We decrypt those credentials in memory, call the upstream platform (Google Analytics, in this case), and get your data.
4. The response flows back through our server to your AI assistant.
5. Your AI synthesises the data and presents the answer.

The whole round-trip takes under a second. Your marketing data flows through our servers but is never stored. We're a conduit, not a warehouse.

How we handle authentication

When you connect a platform like Google, you go through their standard OAuth consent screen. This is the same "Allow access?" prompt you've seen when connecting any app to your Google account.

Here's what matters:

• We never see your password. OAuth means the platform authenticates you directly. We receive a token, not your login credentials.
• We request minimum permissions. Each Ooty product only asks for the scopes it needs. Ooty Analytics doesn't request advertising permissions. Ooty Video doesn't request Search Console access. This follows GDPR data minimisation principles.
• Tokens are encrypted at rest. Your OAuth tokens are encrypted using industry-standard encryption before they're stored. The encryption keys are kept separate from the database, so compromising one doesn't compromise the other.
• Tokens are never stored in plaintext. Not in our database, not on disk, not in logs.

What we store vs. what we don't

We store:

• Your Ooty account credentials (email, hashed password)
• License key records
• Encrypted OAuth tokens for connected platforms
• Usage logs (which tool was called and when, not what data came back)

We don't store:

• Your marketing data (analytics reports, ad performance, search queries)
• API response payloads
• Your ad creative or campaign content
• Your platform passwords

For a deeper look at the security model, see our MCP security guide.

What you can do

You're never locked in and always in control.

• Revoke access anytime. Go to your Google, Meta, or Amazon account settings and remove Ooty's access. The tokens we hold become useless immediately.
• Delete your account. If you delete your Ooty account, all stored tokens are destroyed. There's nothing left to decrypt.
• Check connected platforms. Your Ooty dashboard shows every platform you've connected and when you connected it.
• Works across your devices. Your license key works on any machine running an MCP-compatible AI assistant. Set it up on your work laptop and home machine with the same credentials. No local processes to manage.

Our getting started guide walks through the full setup in five minutes.

When Ooty takes action on your accounts

Ooty doesn't just read your marketing data. It can take real actions across Google Ads, Meta Ads, TikTok Ads, and Microsoft Ads. Pause campaigns. Adjust bids. Add negative keywords. Swap ad creatives. Boost posts.

On top of the dashboard approval gate, we've added extra guardrails for the changes that could hurt the most:

• Bid adjustments over 50% require an additional confirmation step
• New campaigns always start paused. Ooty will never create a live campaign on your behalf.
• Budget increases over 10x require a separate force confirmation
• Every write action returns before-and-after state so you can verify exactly what changed

The honest trade-offs

It wouldn't be transparent to present this as all upside.

Trust surface. You're trusting Ooty with your marketing account tokens. We've designed the system to minimise that risk (encryption, no payload storage, narrow scopes, revocable tokens), but you are trusting a company. If you're not comfortable with that, a self-hosted architecture where you hold your own keys is the alternative.

Latency. Every tool call goes through our servers. Compared to a direct API call from your local machine, there's an additional network hop. In practice, 50-150ms of additional latency. Acceptable for interactive use, but worth knowing about for high-throughput automated workflows. For when to use direct APIs instead, see our MCP vs API decision framework.

Scope to our products. The proxy architecture only supports the platforms we've built integrations for. If you need to connect your AI assistant to an internal API or a platform we don't support yet, you'd need a different approach.

No offline use. This is an internet-connected product. It doesn't work offline.

Why we built it this way

The alternative is what most early MCP tools do: give each user instructions for setting up their own API keys with every upstream service and running local servers that hold those keys.

For marketing professionals, that creates too much friction. Setting up a Google Ads OAuth app, a Meta developer account, a YouTube API project, an Amazon PA-API application, all before seeing any value, is where most people stop.

Ooty's approach: sign up, choose your products, go through familiar OAuth consent screens, paste one URL and one key into your AI assistant's config. That's it. No API key management, no developer accounts, no local process management.

The trade-off is trusting us with your tokens. We've tried to make that trust as narrow and as safe as possible.

Why we're telling you all this

We publish how Ooty works because we think you deserve to understand the systems you depend on. If an architecture can only be trusted when users don't understand it, it's the wrong architecture.

If you have questions about how we handle credentials, want to see our data processing documentation, or need anything else, reach us at hello at ooty dot io. We'd rather explain the design than have you make decisions based on assumptions.