Privacy Policy

Data We Store

Account email, optional profile metadata, hashed passwords for credentials users, hashed API key material, Stripe customer and subscription identifiers, and usage counters needed for plan enforcement and invoicing.

Operational Use

Data is used to authenticate requests, prevent abuse, enforce limits, generate billing records, and provide dashboard visibility. We do not expose private account data publicly or sell customer data to third parties.

Service Providers

Fulfilling a request means reaching the open web on your behalf, so the content of a request may be transmitted to infrastructure and search providers acting for fastCRW under contract, solely to produce the result you asked for. They are permitted to use it only for that purpose. Transmission is not retention: what fastCRW itself stores is described under Security & Retention, and an account with zero data retention enabled has none of its request content written to our systems at all.

Payments

Payment details are processed by Stripe. fastCRW stores only billing references returned by Stripe and does not store full card details on application servers.

Security & Retention

Access logs and usage telemetry are retained only as long as needed for security, analytics, and billing operations. Sensitive access credentials are not rendered back in full after creation.

Cookies & Analytics

We run our own first-party analytics. A cookie named _crw_anon holds a random identifier so we can count a visit once instead of twice. It is set by our own server, cannot be read by JavaScript in your browser, expires after one year, and is never shared with an advertising network. The page views it records are sent to analytics infrastructure we host ourselves, together with your IP address, approximate device and browser, and the page you arrived from. If you later create an account, that earlier activity is connected to it, so we can tell which pages bring people to fastCRW. We do not track you across other websites.

We also use Google Analytics 4 and Google Ads for usage analytics and to measure whether a visit followed one of our ads. Their script loads on every page, but it starts with analytics and advertising storage set to denied: no analytics or advertising cookies are written, and no identifiers are sent, until you grant consent in the cookie banner. Until then Google receives only aggregate, cookieless signals. You can grant or revoke consent at any time using the button below.

When an X (Twitter) advertising pixel is configured, it loads on every page and records page views and the click identifier X adds to links from our ads. It is a third-party script and it is not currently gated by the cookie banner.

Essential cookies required for authentication and session management are always active and do not require consent.