Shown plainly

What operational metadata looks like

The fields below are a fabricated example, not a real account. This is the full shape of what “operational metadata” means anywhere we use that phrase — nothing from inside a vault is ever part of it.

Example record

One account, as our systems see it.

Every value here is invented for this page. The IP address uses a range reserved for documentation (RFC 5737) and is never a real visitor’s address.

Account email
alex@example.com
Account created
2026-03-14T09:02:11Z
Last sign-in
2026-09-28T14:47:03Z
Sign-in IP address
203.0.113.42
Device / browser
Safari on an Apple device

One line from an audit log

The kind of entry a sign-in generates.

Audit and error logs look like this: a timestamp, an account reference, and enough context to tell what happened, without any vault contents in the line.

2026-09-28T14:47:03Z sign_in success acct=acc_9f21 ip=203.0.113.42 ua="Safari/17.4"

What this is not

Nothing you put in the vault appears here.

File names, file contents, notes, and anything else you store are encrypted on your device before they reach us. Operational metadata is the account-level bookkeeping needed to run the service — it never includes what you keep in the vault.