Last updated: March 31, 2026
Short version: StackXray connects to your Google properties with read-only access. We never store your clients' raw analytics data. All AI analysis runs in-memory and is discarded after your report is generated. We store only what's necessary to run the service.
StackXray is operated by The Kern Group LLC, a Missouri limited liability company. References to "StackXray," "we," "us," or "our" refer to The Kern Group LLC and the StackXray service at stackxray.io.
Contact: privacy@stackxray.io
When you create an account, we collect:
When you connect a client's Google properties, you grant StackXray OAuth access with the following read-only scopes:
| Platform | Scope | Purpose |
|---|---|---|
| Google Analytics 4 | analytics.readonly, analytics.manage.users.readonly | Read GA4 property config, data streams, and conversion events |
| Google Tag Manager | tagmanager.readonly | Read container tags, triggers, and variables |
| Search Console | webmasters.readonly | Read search performance, coverage, and sitemap data |
| Google Ads | adwords (read-only via API) | Read campaign structure, conversion tracking, and bidding config |
| Merchant Center (coming soon) | — | Not yet available. Will be added in a future release. |
We request read-only permissions only. StackXray cannot create, modify, or delete any data in your Google properties. This is enforced at the OAuth scope level.
We collect standard server logs including IP addresses, browser type, pages visited, and audit timestamps. This data is used for security monitoring and service improvement.
We do not store:
When you run an audit, StackXray:
The raw Google API data exists only in memory during the analysis window. It is never written to disk or a database.
After analysis is complete, we store:
To support scheduled audits and re-runs, we store your Google OAuth refresh tokens. These are encrypted at rest using AES-256-GCM encryption before being stored in our database. The encryption key is stored separately from the encrypted tokens. You can revoke access at any time from your Google Account security settings or from your StackXray account settings, which deletes the stored tokens immediately.
We use the following subprocessors to deliver the StackXray service:
| Subprocessor | Purpose | Data Shared |
|---|---|---|
| Anthropic | AI analysis (Claude API) | Structured audit data during analysis — no raw client PII |
| Vercel | Application hosting | Server logs, request data |
| Supabase (via AWS) | Database and file storage | Account data, report findings, encrypted tokens |
| Clerk | Authentication | Email address, name, session data |
| Stripe | Payment processing | Billing information — card data never touches our servers |
| Trigger.dev | Background job processing | Audit job payloads (audit IDs, org IDs) — no raw analytics data |
| Resend | Transactional email | Email address, report delivery |
StackXray's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
We retain data as follows:
You have the right to:
To exercise any of these rights, email privacy@stackxray.io. We will respond within 10 business days.
We implement the following security measures:
StackXray uses cookies only for authentication session management (via Clerk). We do not use advertising cookies, tracking pixels, or third-party analytics cookies. We do not use Google Analytics on this site.
StackXray is a business-to-business service intended for marketing professionals and agencies. We do not knowingly collect data from anyone under 18 years of age.
We will notify you by email if we make material changes to this privacy policy. Continued use of StackXray after notification constitutes acceptance of the updated policy. The "Last updated" date at the top of this page reflects the most recent revision.
For privacy questions, data requests, or to report a concern: