We understand your Google Search Console performance data is sensitive. Here is an exact, transparent breakdown of how SERPPatch protects your tokens, privacy, and metrics.
Google Search Console OAuth access & refresh tokens are encrypted using Node.js crypto AES-256-GCM with authenticated tags before storing in the database.
We exclusively request the read-only scope (auth/webmasters.readonly). SERPPatch cannot make changes, delete sitemaps, or mutate your live Google Search Console properties.
Your search queries, impressions, and internal metrics are processed strictly for generating your workspace fix briefs and are never used to train public foundation models.
All client-to-server communications and backend database connections require TLS encryption, with SSL mode enforced for all PostgreSQL queries.
Database records are strictly partitioned by Workspace ID and Clerk User ID, preventing unauthorized cross-tenant data access through relational constraints.
System actions such as user registrations, data imports, and team invitations are recorded in an internal audit table for visibility and traceability.
No. The Google OAuth scope requested is strictly read-only (auth/webmasters.readonly). SERPPatch cannot modify rankings, submit XML sitemaps, or alter GSC property configurations.
Metric rows and opportunity scores are stored in your dedicated PostgreSQL database tables (Neon cloud), isolated by Workspace and Project IDs.
Authentication is handled securely via Clerk. OAuth refresh tokens are encrypted at rest using AES-256-GCM symmetric cipher with a 32-byte secret key.
Yes. Deleting a project triggers database cascade deletions across all associated search metrics, dataset rows, and opportunity records.