Skip to content
Docs

Security

How RankX AI protects your account. Server-side sign-out, MCP tokens with fixed scopes, read-only Google access, and what to do if a credential leaks.

RankX AI account security covers three things: your own sign-in and sessions, the credentials your account issues to AI agents, and the credentials your account holds for WordPress and Google.

The credentials your account holds reach outside RankX AI, so they deserve the most care. This page covers each kind and what to do if one leaks.

How does sign-out work?

RankX AI revokes your session on the server when you sign out, not just in the browser. A copied session cannot be renewed after sign-out.

To end sessions elsewhere, open Settings, then Privacy & Security. You can sign out of your other sessions, or everywhere at once. A session on another device ends within the hour.

Which credentials does my account issue?

Your account issues MCP personal access tokens and OAuth connections to AI agents such as Claude and ChatGPT. Both can spend credits and, with the right scopes, change a live website, so RankX AI applies three rules:

  • Only the account owner can issue a token or approve a connection.
  • Scopes are fixed when the credential is issued. A credential cannot be widened later, so a read-only token can never write.
  • Every credential is listed with its last use. Settings, then AI Agent Access shows each token's scopes, client, creation date, expiry and last use.

Tokens expire after 90 days by default. See MCP authentication.

Which credentials does my account hold?

A WordPress Application Password, if you connected a WordPress site. WordPress issues it when you approve RankX AI on WordPress's own screen, or you create and paste it yourself. RankX AI acts as that WordPress user and can never do more than that user can, so connecting as a user with only the capabilities RankX AI needs is a real control.

Google OAuth grants for Search Console and Analytics, which are read-only. RankX AI never writes to either.

To revoke either, revoke it at the source: delete the Application Password in your WordPress profile, or remove RankX AI in your Google account. Both take effect immediately, and RankX AI shows the connection as needing attention.

What do I do if a credential leaks?

An MCP token. Revoke it in Settings, then AI Agent Access, and it stops working on its next request. If something depends on it, issue the replacement first, so the switch has no downtime.

An OAuth connection. Disconnect it in the connected apps list in RankX AI, not only in the AI client. Disconnecting in RankX AI ends the connection and its current access together.

A WordPress Application Password. Revoke it in the WordPress profile it belongs to. RankX AI holds no other credential for your site.

Then check what happened. The last-used time on each credential shows any use you did not expect.

Which protections are on by default?

Replaying a used OAuth credential ends the connection. If an authorisation code that was already exchanged, or a refresh token that was already rotated, is presented again, RankX AI treats it as theft and revokes the whole connection.

The MCP rate limit fails closed. If RankX AI cannot read the rate limiter, it refuses the request rather than letting it through.

What happens when someone leaves?

Remove the person in Settings, then Team. Their access ends, and any MCP credential they created stops working on its next request, because RankX AI checks the creator's membership every time a credential is used.

Before removing someone who set up integrations, reissue anything still needed from an account that will remain. See team and seats.

What will RankX AI never do?

Each of these is refused by design:

  • RankX AI never creates a WordPress user or application password. The one application password it holds is the one WordPress issues when you approve the connection, or the one you paste in.
  • RankX AI never installs, activates or updates a plugin or theme.
  • RankX AI never permanently deletes WordPress content. Removal goes to the trash.
  • RankX AI never writes to Search Console or Analytics. Both connections are read-only.

Where to go next

Questions

Can RankX AI change anything in my Google Search Console or Analytics?

No. RankX AI asks Google for read-only access to both, so it can read your data and never write to either.

How long does an MCP token last?

A RankX AI personal access token expires after 90 days by default, and you can choose up to 365 days when you create it. Revoke it at any time in Settings, then AI Agent Access.

Who can create MCP tokens or approve AI connections?

Only the account owner. See MCP authentication for scopes and revocation.

Last updated

Cookie settings

Choose which cookies we can use. You can change this at any time from “Cookie settings” in the footer.

Essential

Security, bot protection and remembering your choice. The site needs them to run, and they do not identify you. Always on.

Google Analytics cookies that tell us which pages are read and which links are followed, so we can improve them. Off until you switch it on.

Tells advertisers when their advert led to your visit. Includes the Meta (Facebook) pixel and the LinkedIn Insight Tag, which set cookies on this domain (LinkedIn also on linkedin.com) and can be told if you later start a trial.

More in the cookie policy and the privacy policy.