Privacy and policy

What we keep, what we do not, and where it lives. This page ships with the code, so its version is the footer's version.

The documents you send#

The image is not stored. It is read, and what stays behind is a hash of the upload and the result: the fields, plus any validation violations.

The hash is there for one reason: a re-sent document can be recognised without keeping the page itself. It cannot be turned back into an image.

What the console holds#

Stored	Why
Your account and session	To know who is calling
The is_admin flag	Set by operations in SQL; grants no route

Nothing else. The projects, the schema, the delivery configuration and the key itself live in the core, and the key is shown once and never stored. Not by us, not by the core.

No passwords: sign-in is GitHub, and the console never sees a credential for it.

Sessions#

A signed session cookie keeps you signed in. It is httpOnly, tied to this domain, and dropped when you sign out. Nothing about the session is stored in the browser's localStorage.

Telemetry#

Requests are traced from the browser through the console to the core, so a failure can be followed instead of guessed at. A trace carries the request's path, its timing and an id, not the document, and not the extracted fields.

Your access#

Rotating a project's credential invalidates the previous secret immediately. Editing a schema changes what the next read is asked for; results already kept stay as they were read.

Writing to us with a trace id is the fastest path: it identifies the request without identifying you.

The creator#

Built by dimasbaguspm. The console is open in the same repository it is documented in.