Help: Ledger
Payload retention
Payload retention is the number of days funwatcher keeps the content of your records: the details recorded with each ledger event, and what each finished request contained. After that the content is erased and only hashes and the bare facts remain. An owner sets the number for the account.
The default is 90 days. You can set any whole number from 7 to 3650 days.
See the current setting
- Open the Ledger.
- Read "Retention" next to the export links.
Every member sees the value. For an owner it is a link to the setting.
Change the setting
Only an owner of the account can change it.
- On the Ledger page, select the "Retention" link.
- On the page "Payload retention", type the number of days in "Retention in days". Leave the box blank to go back to the default.
- Select "Save".
The ledger opens with the message "Retention saved". If the number is outside the allowed range, the page shows a message that starts "Retention must be between" and nothing is saved.
Every change is itself written to the ledger as an event of type ledger.retention_changed.
What is purged
- The payloads of ledger events that are older than the retention period.
- The content of finished requests: the summary, the counterparty and the payload, the edited payload and note of each decision, and the reference and detail of each execution report. A request is finished when its status is denied, cancelled, expired, executed, failed, prohibited. Its content is erased once its last ledger event is older than the retention period.
- Purged content is erased for good and cannot be brought back.
- The purge runs every night at 3:00 UTC. A shorter setting takes effect at the next run.
What remains
- Every event stays in the ledger for good: its sequence number, type, time, actor, request link and all three hashes.
- The chain still verifies after a purge, because each payload's hash is kept.
- In the timeline a purged event shows "purged" in the "Payload" column. In an export its payload is empty.
- A purged request keeps its id, agent, action type, amount, reversible flag, status, times, the explanation of which rule decided, who decided and whether the agent reported success. Its card reads "Content purged" and its page shows the hash of the payload it had.
- "New counterparty" rules keep working. funwatcher keeps a keyed fingerprint of each counterparty, from which the name cannot be read.
- Monthly statements are unaffected. They never contain payloads.
What retention does not cover
- Requests that are not finished are never purged, however old. That includes a request that was approved, released or auto allowed and for which the agent never reported a result.
- Your rules are not purged. They stay until you change them.
- Exports you downloaded earlier are your own files. A purge does not reach them.
- Purging is not a way to hide an event. The event and its hash remain, and anyone who holds the original details can show that they match the hash.
See also How your data is protected.
Previous: Export and verify the ledger
Next: Monthly statements
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