the short version
we store what we need to run your account and bill you, plus per-request metadata about the domain and the outcome. we never store the headers you send or the page content that comes back, and we record the domain you fetch rather than the full url. two exceptions: google search results are cached for up to one hour so repeated searches are free, and the error message of a failed fetch, which can include its full url, is kept as that site's last error.
what we store
- account — your email, name, a hashed password (argon2) or the id from github/google sign-in, whether your email is verified, and your last sign-in time.
- team and billing — your team name, plan and quota, and your stripe customer and subscription ids. card details stay with stripe; we never see them.
- api keys — a keyed hash of each key, its last four characters and the name you gave it. the full key is shown once at creation and is not stored.
- request metadata — for each scrape: the target domain (not the path or query), a timestamp, which tier served it (http or browser), the http status, whether it succeeded or was blocked, the anti-bot system detected, the exit country, the time taken and an error type. no headers, cookies, page content or screenshots are stored. these rows feed your console and are deleted after about 30 days. per-site learning also keeps one row per domain (and per proxy) with the last status and the last error message; when a fetch fails, that message can include the full url. those rows are overwritten by later requests rather than deleted on a schedule.
- google serp cache — the parsed results of a search (query, country, language, page and the result list) are cached for up to one hour so an identical search is served without a live fetch. responses that include raw html are not cached.
- in-flight responses — a browser render passes through our queue for up to a minute while it is handed back to you, then expires. nothing is kept.
- audit log — account actions such as keys created or revoked and members added or removed, with the ip address and browser user agent that made them.
- contact form — the name, email, company, message and project details you send us, with the ip address and user agent of the submission.
cookies and analytics
- session cookies — the console sets an access cookie, a refresh cookie and a csrf token so you stay signed in. no advertising cookies.
- marketing site — pageview analytics (datafast) count visits to scantir.com.
- console — product analytics (posthog) record which console pages you visit and a few events: signing up, running a scrape from the playground and submitting the contact form, tied to your account id and email after sign-in. dom content is never captured, so urls you type in the playground stay out of analytics.
who else sees data
- stripe — billing.
- posthog and datafast — the analytics above.
- our email provider — verification, password-reset and invite emails.
- proxy providers — a request routed through the residential pool reaches the target via a third-party proxy, which sees the target address like any network hop.
- our hosting provider — the servers everything runs on.
we do not sell data and we do not share it with anyone else unless the law requires it.
your choices
email hey@scantir.com to export or delete your account. we delete within 30 days, except billing records we must keep by law. you can revoke keys and leave teams from the console at any time.
who is responsible
the data controller is [company legal name], under the laws of [governing jurisdiction, e.g. the state of X / country Y]. the terms of service cover the rest. if we change this policy in a way that matters, we email account holders first.