How Skate handles your app and your users.
Skate runs in the user’s tab, as that user. Here is what it sees, what it sends, and what you control.
Acts as the user
Same session, same permissions. No backend access and no API keys from you.
Keys stay on the server
The script in your page holds no secrets. Browsers on pages outside the origins you register are refused. A script outside a browser can claim any origin, so each site also has a daily AI spending limit that stops every caller once it is reached.
What leaves the page
- The user’s request.
- Visible controls, labels and text of the current screen.
- Path, method and status of same-origin requests. Response bodies are off by default.
What never leaves
- Password, card-number and one-time-code fields.
- Text that looks like a token or card number. Redacted in the browser.
- Cookies, request headers and request bodies.
- Anything inside
data-private.
Approvals
Skate asks before it deletes, sends, publishes, or changes who has access. The approval card says what will happen. Typed confirmations are left to the person.
Owner controls
- Turn it off per site at any time, in Settings › Sites & install.
- Spend caps per site and per visitor.
- A session log, plus an inbox for results flagged as wrong.
Checked results
Skate says done only when the page shows the result.
In progress
A DPA, a retention policy and a security contact process are being prepared. Design partners get them before going live. Questions: write to us.