Help: Account and security
How your data is protected
This page summarizes how funwatcher handles what your agents send it. It describes the software. How the server itself is secured is the responsibility of whoever operates your deployment.
What funwatcher never has
- It never carries out an action. Your agents do that.
- It never holds credentials for your bank, mail, cloud or other accounts, and never asks for them. Someone who broke into funwatcher could approve, deny or falsify records. They could not move money or send mail through it.
- It never opens a link or address found inside a request. Request content is stored, shown to you and returned to the agent, nothing more.
What is encrypted
These are stored encrypted in the database:
- Each request's summary, counterparty and payload, and the policy explanation.
- Each decision's note and edited payload.
- Each execution report's reference and detail.
- The details behind every ledger event.
- The text and condition of your rules.
- The secret behind your two-factor authentication.
- The addresses and keys your browsers registered for push notifications, and the content of queued notifications.
These are stored in a one-way scrambled form that can be checked and never read back: your password, your recovery codes and agent keys.
These are stored as they are, because they are needed for sorting, counting and matching: ids, statuses, times, amounts and currency codes, and the hashes of the ledger. To tell whether a counterparty is new, funwatcher stores a keyed fingerprint of the counterparty's name, not the name.
Encryption protects a copy of the database that someone obtains without the server's keys. It does not protect against someone who controls the running server and its keys.
What notifications leave out
A notification about a request, by email or push, contains the agent's name, the action type, the amount and a link. It never contains the summary, the counterparty or the payload. You sign in to read those.
A monthly statement never contains payloads, summaries or counterparties either.
What logs leave out
- The server's request log records the method, the address, the result code, the time taken and ids. It never records what was sent or shown.
- If the operator uses an error reporting service, request content and any summary, counterparty, payload, note, detail or reference are removed before a report is sent.
How long things are kept
| What | How long |
|---|---|
| Ledger events (type, time, actor, hashes) | For good. They cannot be changed or deleted. |
| The details behind ledger events | For the account's payload retention: 90 days unless an owner sets between 7 and 3650. Then they are deleted. See Payload retention. |
| The content of finished requests (summary, counterparty, payload, edited payloads, notes, report references and details) | For the same payload retention, counted from the request's last ledger event. Then it is erased. Requests that are still open are not purged. |
| The rest of each request, decision and execution report (ids, action type, amount, status, times, who decided) | As long as the account exists. |
| Monthly statements | As long as the account exists. |
There is no screen to delete an account or its data. See Closing an account.
Who can see your data
- Only members of an account can see anything in it. See Roles.
- An agent's key works for one account only and cannot read another account's requests.
- Sessions end after a set time and all your other sessions end when you change your password.
Your part
- Treat agents as untrusted. funwatcher checks, limits and records what an agent sends. It cannot stop an agent that ignores the answer or never asks, and the ledger does not prove that an agent did what it reported.
- Keep agent keys secret and revoke one the moment it may have leaked. See Rotate or revoke an agent key.
- Keep ledger exports and monthly statements somewhere outside funwatcher. See Export and verify the ledger.
- Switch on two-factor authentication. See Two-factor authentication and recovery codes.
Previous: Rotate or revoke an agent key
Next: Closing an account
All help pages
Inbox
- Read a request
- Approve, deny or edit a request
- Held actions
- Expired requests and history
- Request statuses
Rules
- How rules work
- The default rules
- Write a rule in plain English
- Build a rule with the form
- Reorder, enable and disable rules
- Suggested rules
- Set a default policy for an agent
- Export your rules
Teams
Ledger
- What the ledger is
- Browse and filter the ledger
- Export and verify the ledger
- Payload retention
- Monthly statements
Billing
Account and security
- Change your password
- Two-factor authentication and recovery codes
- Rotate or revoke an agent key
- How your data is protected
- Closing an account