Privacy

Privacy built around minimal revenue access.

MRR Pilot is a beta revenue analytics product. We are building with privacy and security in mind and describe current behavior without claiming certifications we do not yet hold.

Last updated: July 3, 2026

Data we use

We process account, workspace, subscription-plan, feedback, and customer Stripe revenue data needed to provide metrics, risk signals, Revenue Actions, recovered-revenue tracking, and grounded AI answers.

Stripe revenue connections

Customer Stripe credentials and tokens remain server-side and are never shown in the browser, user interface, or admin tables. Imported revenue records are scoped to the connected workspace.

AI context minimization

AI requests use a compact workspace summary containing relevant metrics and action context. Stripe tokens, API keys, raw credentials, and unnecessary customer information are excluded.

Internal beta analytics

ProductEvent records track activation milestones such as onboarding, Stripe sync, action copies, and AI usage. They do not store Stripe credentials or private AI conversation content.

A first-party anonymous session cookie records page paths, landing page, limited referrer and UTM context, and a shortened user-agent hash. It does not contain credentials or payment data, and admin page views are excluded from the visitor conversion funnel.

Deletion requests

Beta users can request deletion or ask privacy questions by emailing hello@mrrpilot.com. Deletion tooling is not yet self-service and requests are reviewed securely.