Concepts
Data
What WOOL stores about your users, what it returns, and what you can delete.
What is stored
| Data | Where it lives | Returned by the API |
|---|---|---|
| Application name, description, icon, redirect URIs | With the application | Yes |
| Connection website, status, user id | With the connection | Yes |
| The encrypted sign-in for the connected website | With the connection | Never |
| Website entry URLs and reusable routes to sign-in | Shared discovery cache across the service | No |
| Execution prompt, start URL, output schema, result, error | With the execution | Yes, to the connection's token |
| Operational logs for support | With the execution | No |
| Billing account, purchases, and per-run usage records | With the developer | Only to the console; usage on an execution shows its credits |
Passwords and one-time codes are never stored. Results contain whatever your prompt asked the run to read from the user's account, so treat them as user data on your side as well.
The shared discovery cache records how to reach a website's sign-in flow. It excludes credentials, saved sign-ins, execution prompts, and task results. These navigation routes can help later users connect, including users of other applications.
What you can delete
- Revoke a connection. Tokens stop working and the saved sign-in is deleted. Past executions stay readable.
- Delete an application from the console. Removes the application, its connections, tokens, executions, saved sign-ins, and icon. Allowed once the application has no live connections, so revoke first if needed.
- Revoke a token.
POST /v1/oauth/revokeends one token and nothing else.
Next steps
Isolation and security covers the guarantees around the saved sign-in and each run.