What we store, and why.

Account. Your email address, name, a hashed password if you sign up with one, or the identifier and email from GitHub or Google if you sign in with them. Sign-in sessions record the IP address and browser used, so you can spot a session that is not yours.

Jobs. The URL, method, headers, body, schedule, time zone and notification settings you configure, and for each run the status, duration, HTTP status and up to 4 KB of the response. Credentials for authenticated jobs (Basic, Bearer, API key, OAuth2, HMAC) are encrypted at rest with AES-256-GCM and are never shown again after you save them.

Endpoints. The response you configure, and, when logging is on, each request the endpoint receives: method, path, headers, up to 16 KB of body, the caller's IP address and the status we answered. Authorization, Cookie and API key headers are redacted before storage. Fault-sequence counters store a hash of the idempotency key, not the key itself.

Billing. Your plan and the Stripe customer and subscription identifiers. Card numbers never reach us; Stripe holds them.

Usage. Page views and clicks on the site (which guide page brought you in, which buttons you used, which A/B variant you saw) and product events such as job created or plan limit reached, tied to your account when you are signed in.

To run the service you asked for (contract): accounts, jobs, endpoints, run history, alerts, billing. To keep the service safe and within its limits (legitimate interest): rate limits, abuse detection, session records. To understand which pages and features people use so we can improve them (legitimate interest, with the analytics described below). To meet tax and accounting law (legal obligation): invoices.

We do not use your data for advertising, and we do not train models on it.

We set a session cookie when you sign in, a cookie that remembers which A/B variant of a page you saw (90 days), and a cookie that remembers which guide page first brought you here (90 days, so we know which pages are worth writing more of). Google Analytics sets its own cookies. None of them are used for advertising and there is no cross-site tracking.

You can see and change your jobs, endpoints and account details in the app at any time, and export your jobs and run history through the API. Deleting your account from the account page removes your data within 24 hours, except billing records we must keep. You can also email us to access, correct, export or erase your data, to object to processing, or to complain; if you are in the EU or UK you can also complain to your data protection authority. We answer within 30 days.

All traffic is encrypted in transit. Credentials are encrypted at rest with a key kept outside the database. Passwords are hashed. Sessions and API tokens can be revoked from the account page. Access to production data is limited to the people who run the service, and only when needed to fix a problem you report. If a breach affects your data we tell you without undue delay.

The service is not aimed at anyone under 18 and we do not knowingly collect their data. We may update this policy; material changes are announced by email and on this page before they take effect, and the date at the top is the version that applies.