Privacy

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 we never collect

What we store, and for how long

WhatWhyKept
Optional website account: email, display name, verification status, password hash or linked OAuth provider id and encrypted OAuth tokensTo create and authenticate your website accountUntil the account is deleted
Website sessions, IP address and user-agentSecure login and abuse preventionSessions expire after 7 days; expired records may remain until account deletion
Authentication rate-limit recordsPrevent repeated password guessingUntil operational cleanup or account deletion where identifiable
Legacy billing account id, balance, API key hashTo charge the right balanceUntil the account is deleted
One row per billable call: time, amount, route, referenceSo a charge can be explained and disputedUntil the account is deleted
Browser sessions and jobs: when opened, how much chargedBilling and supportUntil the account is deleted
Feedback you choose to sendTo fix what is brokenUntil acted on
Rendered pages, cachedSo a repeat read is cheaper for youShort-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 answerSo a call can be explained when something goes wrong30 days, or until the current UTC calendar month ends if longer (up to 31 days)

Website cookies and social sign-in

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 with no key and your IP address

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.

About the request log

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.

About the pages you ask us to fetch

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.

Card payments and prepaid balance

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.

Who else sees anything

We do not sell data, we do not share it for advertising, and we do not pass it to anyone not listed above.

Your choices

Children

oassis is a developer tool and is not directed at children.

Changes

If this policy changes, the date at the top changes with it.

Contact

Write to support@oassis.dev. A person reads it.