Start with a sample.
Your client encrypts file contents and names before upload. The server stores encrypted bytes.
A LITTLE CONTEXT. KEPT PRIVATE.
Your files.
Your keys.
A fresh start.
A small space to try encrypted file storage. Save a sample, bring it back, and see how VaultContext fits into your workflow.
CLI & coding agents · Linux & macOS
PRIVATE BY DESIGN
sample.envJust a harmless example.
✓$ vaultcontext save …
↳ Encrypted before upload
$ vaultcontext compare …
↳ "same": true
$ vaultcontext restore …
↳ Exact bytes. Back with you.
Your passphrase stays with you.
A playground, not permanent storage.
The planned demo clears vault data every day at 00:00 UTC. Use sample files only.
NEXT MIDNIGHT UTC-- : -- : --Illustrative · based on your device clock
THE SIMPLE PART
Try the whole round trip.
Same familiar files. A little more peace of mind.
Know it’s the same.
Check whether your local file matches its saved version, without printing its contents.
Bring it back.
Restore exact bytes to a new path. You choose the destination and keep control of your files.
MAKE YOURSELF AT HOME
A few small steps.
Your own little vault.
The planned public demo welcomes all Google accounts, including personal Gmail and Google Workspace accounts.
✓ A personal space for synthetic files
✓ Your existing terminal or coding agent
↻ Vault data cleared at midnight UTC
This is an interactive preview.
Try the screens with a fictional identity. Google sign-in, enrollment and vault operations are not connected.
YOUR DEMOPreview only
Let’s get you started.
Explore the sign-in and onboarding flow.
No Google connection. Uses a fictional account.
D
Demo visitordemo@example.com · synthetic identity
YOU’RE EXPLORING THE NEXT STEP
Your terminal. Your keys.
Example instructions only. There is no live demo endpoint yet.
Let your agent help with setup.
“Read the VaultContext skill and help me try a synthetic file. I’ll enter my passphrase privately in my own terminal.”
The unlocked host and agent are trusted. Agents should never inspect file contents or ask for your passphrase.
0 of 3 guide steps reviewed
01Install your tools +
This preview does not connect to a download service. The live demo will provide a verified public client wheel and skill bundle. Do not use production credentials.
# Public downloads are not connected in this preview.
# Verified installation commands appear on a connected demo.
# Do not use production credentials.The source repository remains private. Live installation uses public downloads from the demo website and needs no GitHub access. No commands are run for you.
02Connect, then unlock +
Google identifies you; a separate passphrase unlocks your encryption keys. Enter it only in your private terminal. There are no recovery keys.
# Illustration only — .invalid is not a live service
export VAULTCONTEXT_URL=https://vault-demo.example.invalid
export VAULTCONTEXT_USER_EMAIL=demo@example.com
vaultcontext login --google
vaultcontext whoami
vaultcontext check
vaultcontext init
vaultcontext unlock --timeout 900
vaultcontext create 'Sample vault'A future daily reset will require a fresh demo setup. Never enter passphrases in chat, command arguments or environment variables.
03Save, compare and restore +
Create a harmless sample. Replace the example IDs with those returned by a live client. Restore to a separate path.
vault_demo_dir=$(mktemp -d)
vault_demo_dir=$(cd "$vault_demo_dir" && pwd -P)
printf 'APP_ENV=demo\nAPI_TOKEN=not-a-secret\n' > "$vault_demo_dir/sample.env"
vaultcontext save VAULT_ID "$vault_demo_dir/sample.env"
vaultcontext compare DOCUMENT_ID "$vault_demo_dir/sample.env"
vaultcontext restore DOCUMENT_ID --to "$vault_demo_dir/restored.env"
vaultcontext lockA server reset cannot erase files already restored to your computer. Review progress does not confirm that any CLI operation succeeded.
All three steps reviewed. That’s the preview — your actual vault journey starts when the demo goes live.
CLEAR FROM THE START
Temporary vault.
Thoughtful boundaries.
Proposed policies for the future demo.
This preview collects no enrollment data.
What am I agreeing to? +
The proposed demo terms permit evaluation with synthetic files only. Do not upload real credentials, confidential information or other people’s personal data. The demo is temporary, has no storage guarantee, and vault data resets at 00:00 UTC daily.
Sales contact and newsletter subscription are separate, optional choices. They are not required to try the demo. Final terms and controller details will be provided before any real enrollment.
What stays, and for how long? +
- Vault data
- Planned deletion every day at midnight UTC, including the demo’s encrypted files and keys.
- Email without marketing consent
- Proposed retention: 30 days after your last demo use.
- Marketing preferences and contact details
- Retained separately from vault data, with a review after 12 months and an option to withdraw consent. Minimal suppression records may remain to honor withdrawal.
- Operational logs
- Proposed retention: 30 days, without file content or passphrases; a documented security incident may require a limited investigation period.
- Isolated contact and security backups
- The proposed recovery-copy limit is an additional 30 days after live retention ends. Actual provider expiry must be verified before launch; a configured retention horizon alone does not prove deletion. Recovery copies are not available for ordinary marketing. Restored withdrawals and deletion requests must be reconciled before any sending; missing current suppression state blocks sending. This allowance does not apply to demo vault replicas.
The launched service must publish the full retention policy, withdrawal mechanism and any necessary consent-evidence exceptions. Here, nothing is submitted or saved; a refresh clears the interface choices.
What does the daily reset mean? +
The future demo will clear its accounts, encrypted keys and vault files daily, so you will start fresh after a reset. You may have less than 24 hours until the next reset. The countdown above is illustrative and uses your device clock; it does not report a running server job.
Files you download or restore, independent exports, and local client state are not erased by a server reset. Marketing records have their own retention policy.
Does Google sign-in unlock my files? +
No. Google authenticates your account. A separate passphrase protects your encryption identity. File contents and names are encrypted by the client before upload; account and operational metadata remain visible to the service.
Your execution host and unlocked agent are trusted. Losing your passphrase can mean losing access. There are no recovery keys.