Choose which vaults keep a history
Enable logging separately for a vault on this device. Its encrypted history retains the latest 500 local events. Disable or clear it in settings when you no longer need the record.
How it worksApp features
Optional encrypted vault activity logs
Review interactions with a vault on this device through an optional encrypted activity history, controlled separately for each vault.
Download RevaultSecurity modelSometimes you want a record of what happened inside a vault. Optional activity logging gives its owner a local history without creating a central account activity feed. It is off by default and opened from the unlocked vault’s settings.
Keep contents out of the log
Activity records do not include file contents, patterns or encryption keys. The local history does not sync, and locked background cloud transfers are not logged. A failed pattern alone cannot identify which vault someone intended to open.
Understand shared-access events
Controlled shares created while logging is enabled can retain the latest 100 access-session timestamps on the server. Only the owner’s management capability can read those events. They do not record recipient identity, IP address, filenames or decryption keys.
How it works
- Open Activity in the unlocked vault’s settings.
- Enable encrypted logging for this vault on this device.
- Review the recorded events, or clear and disable the local history.
Decide whether this vault needs a history
An activity log is useful when you want to review recent interactions, such as imports, file changes or sharing actions. Leaving it disabled avoids keeping a history you do not need. The choice belongs to the individual vault on this device, so a record-keeping collection can have logging while a personal photo vault does not.
Local activity and remote share access are different records
The ordinary vault history is encrypted locally, retains up to 500 recent events and does not become a synchronized account feed. Controlled shares created with logging enabled can separately retain recent server-granted access-session times. These show that an access capability was used, not that a named person opened a particular page or successfully understood its contents.
Example: review a document handoff without tracking a person
Enable logging before creating an invitation if you want its supported access-session history. Later, unlock your vault and review the share through its management controls. A session timestamp can help you decide whether to follow up, but ask the recipient directly to confirm receipt or completion. Clearing your local log is not the same operation as revoking the independent invitation.
Practical checklist
- Enable logging before the interactions you want recorded; it does not reconstruct earlier events.
- Keep local vault activity separate from server sharing-session history when interpreting a record.
- Use the dedicated settings to clear or disable this vault’s history when it is no longer useful.
Frequently asked questions
Does the activity log record file contents or encryption keys?
No. Its purpose is a local history of supported actions, not a copy of your files, patterns or key material. Filenames and other private content should not be inferred from a generic activity label.
Can the log tell me who tried to unlock the vault?
A failed pattern cannot identify its intended vault or the person entering it. Optional break-in alerts may capture a device-attempt photo when permitted, but neither those photos nor the activity log establish a verified identity.
Is this a tamper-proof audit trail for legal or compliance use?
No. The history is an owner convenience, can be cleared and has bounded retention. It is not an independently verified record, a complete log of every device action or a substitute for a required records system.
Keep exploring
Put this into practice in your vault
Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.
Download RevaultExplore related features
Private vaults without an account
Create separate encrypted spaces on your phone. Each pattern opens only its matching vault, without a Revault account or sign-up.
Automatic vault locking
Lock immediately when the app goes into the background, with a configurable inactivity timeout that defaults to 60 seconds per vault.
Optional break-in photo alerts
Opt a vault into encrypted local photo alerts after repeated failed patterns. Review the evidence only after unlocking that vault.