Privacy Policy

Account information (email), API-key metadata, and usage/billing telemetry (request counts, timestamps, and target hostnames — kept for abuse prevention and our SSRF egress guard). We do not retain full scraped page content long-term.

You direct what we fetch. Extraction results are stored transiently in our job queue and result cache (about 24 hours) so you can retrieve them, then expire. We do not build a long-term store of your scraped content, sell it, or train models on it.

We use: Vercel (API hosting), Upstash (queue & cache), Razorpay (payments), Apify (the bring-your-own-LLM path only), and our own on-prem GPU compute for the managed-AI path — meaning AI extraction is processed in memory on hardware we own, not sent to a third-party LLM provider. We will give notice of material changes to this list.

For any personal data contained in pages you instruct us to fetch, you are the data controller and we act as your processor on your documented instructions. We will not respond to data-subject requests directly; we forward any we receive to you and assist you within a reasonable period. We will notify you of any personal-data breach without undue delay (target within 24 hours of becoming aware). For EU↔India transfers we rely on Standard Contractual Clauses. A Data Processing Addendum is available on request.

Account data while your account is active; extraction results about 24 hours; abuse/security logs for a limited period.

Subject to applicable law (India DPDP Act 2023; GDPR for EU residents), you may request access, correction, export, or deletion of your account data. Contact us using the address below. Our grievance officer can be reached at the same address.

Secrets are stored by location (never in code), traffic is encrypted in transit, API keys are stored hashed, and database access is least-privilege. An egress guard blocks requests to private/internal hosts.