Last updated 17 October 2026.
oassis is an API that fetches web pages on behalf of whoever calls it. This page says exactly what we keep while doing that. It describes the system we actually run, and it changes when the system does.
| What | Why | Kept |
|---|---|---|
| Optional website account: email, display name, verification status, password hash or linked OAuth provider id and encrypted OAuth tokens | To create and authenticate your website account | Until the account is deleted |
| Website sessions, IP address and user-agent | Secure login and abuse prevention | Sessions expire after 7 days; expired records may remain until account deletion |
| Authentication rate-limit records | Prevent repeated password guessing | Until operational cleanup or account deletion where identifiable |
| Legacy billing account id, balance, API key hash | To charge the right balance | Until the account is deleted |
| One row per billable call: time, amount, route, reference | So a charge can be explained and disputed | Until the account is deleted |
| Browser sessions and jobs: when opened, how much charged | Billing and support | Until the account is deleted |
| Feedback you choose to send | To fix what is broken | Until acted on |
| Rendered pages, cached | So a repeat read is cheaper for you | Short-lived, then discarded |
| A short request log: time, route, status, how long it took, your IP, your user-agent, and a truncated copy of the request and the answer | So a call can be explained when something goes wrong | 30 days, or until the current UTC calendar month ends if longer (up to 31 days) |
Signing in sets essential, Secure, HttpOnly session cookies for oassis.dev. They are not advertising cookies. Your browser may store your last successful sign-in method to display “Last used”. If you choose an enabled Google or GitHub sign-in, that provider authenticates you and shares your profile and email with Oassis under its own privacy policy. Social sign-in may not be available until configured.
Calls made with no key and no account are not counted per address: there is no daily allowance to keep. The request log above still records the address of each call.
We keep a short operational log of recent requests so that a call can be explained when something goes wrong. It is retained for 30 days without a row-count limit. The current UTC calendar month is also kept complete, for up to 31 days; older entries are removed during maintenance. The bodies are stored truncated — enough to see what was asked for, not a copy of the answer. Large responses are recorded as a size and never read. It is read by us, to run the service, and by nobody else.
We request the url you give us and return the result to you. The content is held only as long as it takes to answer, plus a short cache so that asking twice costs you less. We do not keep a copy of scraped content in our database, and we do not build a corpus out of what our users read.
When enabled, Stripe processes card payments and billing details. We retain your customer identifier, saved payment-method identifier if you consent, purchase and refund records, balance movements and automatic top-up settings. Authentication and billing bodies are excluded from tool traces. Financial records may need retention for accounting and disputes after account deletion.
We do not sell data, we do not share it for advertising, and we do not pass it to anyone not listed above.
oassis is a developer tool and is not directed at children.
If this policy changes, the date at the top changes with it.
Write to support@oassis.dev. A person reads it.