Privacy policy

Last updated October 17, 2026.

How Scrapely handles personal data — written to be read, not just agreed to.

Summary

We collect what we need to run your account and the API, and nothing more. We do not sell personal data, and we do not use the pages you scrape for anything other than delivering them to you.

What we collect

Account data: your name, email address, organisation, and billing details processed by our payment provider, Stripe (we never see or store full card numbers; we keep only the card brand, last four digits and expiry to show you which card is saved).

Usage data: request metadata such as target domain, status code, credits spent, timing and the options used. This powers your dashboard, usage reports and billing.

Site analytics: privacy-friendly, aggregated page analytics on our marketing site, subject to your consent choices.

Content you scrape

Page bodies are processed in memory to deliver your response. Results of asynchronous jobs are stored encrypted for up to 72 hours so you can retrieve them, then deleted. We do not inspect, index or train on scraped content.

How we use data

To provide and secure the service, bill accurately, prevent abuse, answer support requests and tell you about changes that affect your account. Product announcements are opt-in.

Retention

Request logs are kept for 90 days. Account and billing records are kept while your account is open and afterwards for as long as tax law requires.

Sharing

We share data only with processors that help us run Scrapely — hosting, payments, email, support chat and sign-in — under contracts that limit their use of it. We disclose data to authorities only when legally required.

Your rights

You can access, correct, export or delete your personal data at any time. Most of this is self-serve in the dashboard; for anything else, email us and we will respond within 30 days.

To make a formal access or deletion request, use our privacy request form at https://cookiemunch.net/r/dv-mvafspn9-eoll1m17 (run by Cookie Munch, our consent and privacy-request provider). It records where you live, which sets the legal deadline, and reaches every system that holds your data, including your sign-in account at Atlas. Email works too.

Cookies and browser storage

Necessary, set by Scrapely: scrapely_session (keeps you signed in, 30 days), scrapely_signed_in (a readable hint that you are signed in, with no identity in it), scrapely_demo (you chose to look around the read-only demo; until the browser closes), atlas_state, atlas_verifier, atlas_provider and atlas_next (protect a sign-in while it is in progress, 10 minutes), forumulate_return (the docs page to return to after signing in, 15 minutes) and scrapely_sidebar (whether you collapsed the dashboard sidebar, 1 year).

Necessary, set by the services we use: Atlas, our sign-in provider, keeps your sign-in session on its own domain; Forumulate, which hosts our docs, community and status page, sets forumulate_lang (your reading language, 12 months) and, when you sign in there, forumulate_session, fm_signed_in and cflx_vis_* (12 hours); and Cookie Munch stores your consent choice in the CookieMunch cookie (1 year).

Support chat: only once you open it, Chatly stores a visitor token in your browser’s local storage (keys starting chatly:) so the conversation is still there next time. The docs remember the code-sample language you picked in local storage.

We use no advertising or cross-site tracking cookies. Anything optional waits for your choice in the cookie banner, and you can change it at any time from the banner’s settings.