--- title: "How do I revoke access? · GSC PAP" source: https://gscpap.com/faq/how-to-revoke-access updated: 2026-09-18 --- [All questions](https://gscpap.com/faq) Privacy & Security # How do I revoke access? By the [GSC PAP team](https://gscpap.com/about) · Updated September 18, 2026 You have three independent ways to revoke. First, revoke a single MCP token from /account/tokens - this kills only that bearer, leaving other tokens (e.g. on different machines) working. Useful if you suspect one token has been exposed but want to keep using GSC PAP elsewhere. Second, revoke the entire Google OAuth grant from your Google Account at myaccount.google.com/permissions - this severs our ability to call the Search Console API at all, even with a valid bearer. Useful if you want to cut us off completely without deleting your account. Third, delete your account from /account/profile (Danger zone). This is the nuclear option: every MCP token is revoked, the Google OAuth grant is revoked at Google's side, your encrypted refresh token is marked revoked in our database, and a 30-day soft-delete grace period begins. After 30 days everything is hard-deleted including your Personal Archive. The grace period exists so you can recover an accidentally deleted account by signing in again before the timer expires. ## Related questions [All questions](https://gscpap.com/faq) [ Privacy & Security ### Can other users see my data? No. Your Search Console data, OAuth tokens, MCP sessions, archive, and tool call history are all isolated to your user account in our database. Every query passes through bearer-token authentication that resolves to a specific user, and every database query scopes results by user_id. There is no UI, API endpoint, or feature that exposes one user's data to another user. ](https://gscpap.com/faq/can-other-users-see-my-data)[ Privacy & Security ### What Search Console data can GSC PAP access? GSC PAP requests the webmasters.readonly OAuth scope - the same read-only level you would grant to any third-party Search Console viewer. Specifically we can read your verified site list, search analytics (clicks, impressions, CTR, position by query, page, country, device, date), sitemap submission status, and URL inspection results. This is exactly the data you see in your own Search Console UI. It also has the same gaps: Google leaves anonymized queries out of query rows in both the UI and the API, so GSC PAP cannot reveal them either. If you also connect Google Analytics, GSC PAP holds the analytics.readonly scope as well, and any Analytics data it keeps for you follows the same rules as your archive. ](https://gscpap.com/faq/what-data-does-gsc-pap-access)[ Limits & Pricing ### Does GSC PAP use fewer tokens than calling the Search Console API directly? Yes, about a third fewer. We measured it on 1,000 real rows from three different properties, serialising the same rows two ways: the shape the Search Console API returns, and the compact format our server sends. The raw API response came to 34,044, 34,535 and 36,237 tokens. The same data from GSC PAP came to 22,933, 23,260 and 23,975. That is 33 to 34% fewer tokens for identical numbers, measured with tiktoken cl100k_base. ](https://gscpap.com/faq/token-usage-vs-search-console-api) ### Built for SEO consultants, devs, and product teams 36 tools cover the workflows we kept doing by hand: quick wins, content decay, indexing diagnostics, weekly health reports, and the cross-tool join between organic clicks and GA4 conversions. [Browse all tools](https://gscpap.com/tools) **Plug-and-play SEO copilot for your AI assistant** 36 SEO tools, one token, your AI assistant. Sign in with Google to start. [Sign in with Google](https://app.gscpap.com/login) Did this answer your question? If not, email [support@gscpap.com](mailto:support@gscpap.com) and we will revise.