Key Concepts & Terminology
Essential terms and concepts for understanding Torvus Security
Understanding these core concepts will help you get the most out of Torvus Security and configure your vaults effectively.
Core Componentsβ
Vaultsβ
What it is: An encrypted container for storing documents and sensitive information.
Key Features:
- End-to-end encryption: Data encrypted on your device before upload
- Zero-knowledge architecture: Torvus cannot access your vault contents
- Flexible organization: Tag and categorize documents
- Shared or private: Control who can access your vault
Analogy: Think of a vault as a digital safety deposit box with programmable locks.
Example Use Cases:
- Personal vault for family documents
- Business vault for company records
- Legal vault for client files
- Cryptocurrency vault for wallet recovery keys
Recipientsβ
What it is: Trusted individuals designated to receive vault access when release policies trigger.
Key Features:
- Verification required: Recipients must verify their identity before gaining access
- Role-based permissions: Control what each recipient can do
- Multiple recipients: Add as many as your plan allows
- Notification system: Recipients are notified when vault is released
Permissions Levels:
- Viewer: Read-only access to documents
- Operator: Can view and upload documents
- Admin: Full access including vault management (cannot delete vault)
- Owner: Complete control including deletion
Example Scenario: You designate your spouse as "Admin" and your attorney as "Viewer" for your estate planning vault. If your inactivity policy triggers, both receive accessβyour spouse can manage documents while your attorney can review them.
Policiesβ
What it is: Automated rules that determine when and how your vault is released to recipients.
Why Important: Policies ensure your information reaches the right people at the right time, even if you can't deliver it yourself.
Policy Types:
1. Inactivity Policyβ
Releases vault if you don't check in for a specified period.
How It Works:
- You set check-in frequency (daily, weekly, monthly)
- System sends reminders before check-in is due
- If you miss check-in, grace period begins
- If grace period expires without check-in, vault releases to recipients
Best For:
- Personal emergency planning
- Travel safety
- Business continuity
2. Manual Releaseβ
Immediately releases vault with a button press.
How It Works:
- You click "Emergency Release" button
- System requires 2FA confirmation
- Vault immediately releases to all designated recipients
- Recipients receive instant notification
Best For:
- Emergency situations
- Medical emergencies
- Security threats
3. Date-Based Releaseβ
Automatically releases vault on a specific date.
How It Works:
- You set future release date
- System automatically releases vault at specified time
- Recipients receive access on that date
Best For:
- Future-dated information delivery
- Time capsules
- Scheduled disclosures
4. Death Certificate Verificationβ
Releases vault after verified death certificate is submitted.
How It Works:
- Designated contact submits death certificate
- Torvus verifies authenticity with issuing authority
- After verification, vault releases to recipients
Best For:
- Estate planning
- Will distribution
- Digital inheritance
Check-insβ
What it is: Your periodic confirmation that you're active and have access to your account.
How It Works:
- System sends reminder before check-in is due
- You complete check-in via email, SMS, mobile app, or API
- Next check-in is scheduled based on your frequency setting
- If you miss check-in, grace period begins
Check-in Methods:
- Email: Click link in email reminder
- SMS: Reply to text message with code
- Mobile App: Tap check-in button
- API: Automated check-in from your systems
Frequency Options:
- Daily: Every 24 hours (high-security use cases)
- Weekly: Every 7 days (frequent travelers)
- Biweekly: Every 14 days (balanced approach)
- Monthly: Every 30 days (most common)
Grace Period: Extra time if you miss a check-in (typically 24-72 hours depending on plan).
Security Conceptsβ
End-to-End Encryptionβ
What it is: Your data is encrypted on your device before being sent to Torvus servers.
Why Important: Even if Torvus servers were compromised, your data remains encrypted and unreadable.
How It Works:
- You upload a document
- Your browser encrypts the file using AES-256 encryption
- Encrypted file is sent to Torvus servers
- Only you (and recipients when released) can decrypt the file
Technical Details:
- Algorithm: AES-256-GCM
- Key Derivation: PBKDF2 with 100,000 iterations
- Salt: Unique per vault
- Zero-knowledge: Torvus never has access to encryption keys
Zero-Knowledge Architectureβ
What it is: Torvus Security has no knowledge of your vault contents, encryption keys, or passwords.
What Torvus Can See:
- Your email address
- Vault metadata (name, creation date, size)
- Check-in activity
- Recipient list (names and emails)
What Torvus Cannot See:
- Vault contents (documents)
- Document names (encrypted)
- File contents (encrypted)
- Your master password (hashed)
Benefit: Even under legal compulsion or data breach, your vault contents remain private.
Two-Factor Authentication (2FA)β
What it is: A second layer of security beyond your password.
Methods Supported:
- TOTP (Time-based One-Time Password): Authenticator apps (Authy, Google Authenticator)
- SMS: Text message codes
- Hardware Keys: YubiKey, Titan Security Key (Professional plan and above)
When Required:
- Login to Torvus Security
- Manual emergency release
- Changing account settings
- Adding/removing recipients
Verification Processβ
What it is: Identity verification required before recipients can access released vaults.
Verification Steps:
- Recipient receives release notification
- Recipient clicks secure link and creates account
- Recipient verifies identity (email verification + optional ID verification)
- Recipient gains access to vault contents
Why Important: Prevents unauthorized access even if someone intercepts release notification.
Advanced Conceptsβ
Vault Members vs Recipientsβ
Vault Members:
- Collaborate on vault while you're active
- Can view/upload documents in real-time
- Require explicit invitation from vault owner
- Permissions: Viewer, Operator, Admin
Recipients:
- Designated to receive vault access when policies trigger
- Do not have access until vault is released
- Automatically receive access when policy conditions are met
- Permissions: Set at time of designation
Example: You share a business vault with your COO as a "Vault Member" (Admin) for daily collaboration. You also designate your attorney as a "Recipient" (Viewer) who only gets access if your inactivity policy triggers.
Grace Periodsβ
What it is: Extra time after a missed check-in before vault releases to recipients.
How It Works:
- You miss scheduled check-in
- Grace period begins (24-72 hours depending on plan)
- System sends urgent reminders
- If you check in during grace period, release is canceled
- If grace period expires, vault releases to recipients
Grace Period by Plan:
- Free: 24 hours
- Standard: 48 hours
- Professional: 72 hours
- Enterprise: Custom (up to 7 days)
Use Case: You're traveling and miss a check-in due to lack of internet. Grace period gives you time to find connectivity and complete check-in before vault is released.
Release Notificationsβ
What it is: Alerts sent to recipients when a vault is released.
Notification Channels:
- Email: Detailed message with secure access link
- SMS: Brief alert with link (if phone number provided)
- In-App: Notification in Torvus mobile app (if installed)
What Recipients Receive:
- Notification that a vault has been released to them
- Vault name and description
- Reason for release (inactivity, manual, date-based, death certificate)
- Instructions for accessing vault contents
- Secure link to claim access
Audit Logsβ
What it is: Detailed record of all actions taken on your vaults.
What's Logged:
- Document uploads/downloads
- Check-in activity
- Policy changes
- Recipient additions/removals
- Vault member activity
- Emergency releases
Available On:
- Professional plan and above
- Console (admin panel)
- Exportable as CSV
Use Case: Track who accessed documents and when, useful for compliance and security auditing.
Terminology Quick Referenceβ
| Term | Definition |
|---|---|
| Vault | Encrypted container for documents |
| Recipient | Person designated to receive vault access |
| Policy | Rule determining when vault releases |
| Check-in | Periodic confirmation of activity |
| Grace Period | Extra time after missed check-in |
| Inactivity Policy | Releases vault if check-ins stop |
| Manual Release | Immediate vault release (emergency) |
| Date-Based Release | Scheduled future release |
| Death Certificate | Release after verified death |
| End-to-End Encryption | Encryption on device before upload |
| Zero-Knowledge | Torvus cannot access vault contents |
| 2FA | Two-factor authentication |
| Vault Member | Collaborator with real-time access |
| Owner | Creator of vault (full control) |
| Audit Log | Record of all vault activity |
Understanding Vault Lifecycleβ
Phase 1: Creationβ
- Owner creates vault
- Uploads initial documents
- Adds vault members (optional)
Phase 2: Active Useβ
- Owner and vault members upload/manage documents
- Owner configures release policies
- Owner designates recipients
- Owner completes regular check-ins (if inactivity policy active)
Phase 3: Release Triggerβ
- Policy condition is met (missed check-in, date reached, manual trigger, death certificate)
- System initiates release process
- Recipients are notified
Phase 4: Recipient Accessβ
- Recipients verify identity
- Recipients gain access to vault contents
- Recipients can view/download documents based on permission level
- Audit log records all access
Phase 5: Post-Releaseβ
- Vault remains accessible to recipients
- Owner (if alive and manual release was used) can revoke access
- Vault can be archived or deleted by owner
Common Misunderstandingsβ
β "Torvus can see my documents"β
Correction: Torvus uses zero-knowledge architecture. Your documents are encrypted on your device before upload. Even Torvus staff cannot access your vault contents.
β "Recipients have access to my vault immediately"β
Correction: Recipients only receive access when a release policy triggers. Until then, they have no access to your vault.
β "If I miss one check-in, my vault is immediately released"β
Correction: Grace periods give you extra time. If you miss a check-in, you have 24-72 hours (depending on plan) to complete it before release.
β "I can only have one policy per vault"β
Correction: Standard and Professional plans support multiple simultaneous policies. For example, you can have both an inactivity policy (monthly check-ins) AND a date-based release (specific future date).
β "Manual release is permanent"β
Correction: If you trigger a manual release accidentally, you can revoke recipient access before they claim it (within a short window, typically 1 hour).
Next Stepsβ
Now that you understand core concepts:
- Create Your First Vault: Put concepts into practice
- Configure Policies: Set up release conditions
- Add Recipients: Designate trusted individuals
- Best Practices: Learn recommended configurations
Related Pagesβ
- What is Torvus Security?: Platform overview
- Security Overview: Deep dive into security architecture
- FAQ: Common questions answered
Last Updated: October 7, 2025