Policy Types Explained
Overview: Torvus Security offers multiple policy types to control when and how your vault contents are released to recipients. Each policy type serves different use cases and can be combined for comprehensive protection.
Policy Types Overview
| Policy Type | Best For | Automation | Check-ins Required |
|---|---|---|---|
| Manual Release | Full control, journalism | Manual | Optional |
| Inactivity Policy | Digital legacy, emergencies | Automatic | Yes |
| Date-Based Release | Scheduled delivery, wills | Automatic | No |
| Death Certificate Verification | Legal compliance, estates | Semi-automatic | No |
Manual Release
What It Is
Manual Release gives you complete control over when your vault is released. Recipients only gain access when you explicitly trigger the release yourself.
How It Works
- You create a vault and add recipients
- Recipients wait for your manual release
- When ready, you click "Release Vault Now"
- Recipients are immediately notified and granted access
- Vault contents become available to all designated recipients
When to Use
- Journalism: Release evidence to editors when your investigation is complete
- Legal Documents: Share documents when a specific event occurs (court filing, contract signing)
- Business Continuity: Release access credentials when transitioning projects
- Whistleblowing: Control exact timing of disclosure
Advantages
✅ Complete Control: You decide exactly when recipients get access ✅ No Automation: No risk of accidental early release ✅ Immediate Release: Access granted instantly when you trigger it ✅ Flexible Timing: Change your mind anytime before release
Considerations
⚠️ Requires Action: You must manually trigger the release ⚠️ No Emergency Backup: If incapacitated, vault won't release automatically ⚠️ Single Point of Failure: Only you can trigger release
Best Practices
- Combine with Inactivity Policy: Add a backup inactivity trigger (e.g., 90 days) for emergencies
- Document Criteria: Keep notes about when/why you'll trigger release
- Test Notifications: Ensure recipients will receive release alerts
- Plan for Absence: Consider what happens if you're unable to release
Inactivity Policy
What It Is
Inactivity Policy automatically releases your vault if you fail to "check in" for a specified period. This is the most popular policy type for digital legacy and emergency scenarios.
How It Works
- You set a check-in frequency (daily, weekly, monthly, etc.)
- You receive automated reminders to check in
- If you don't check in before the deadline, a grace period begins
- If grace period expires without check-in, vault automatically releases
- Recipients are notified and granted access
Example Timeline:
Week 1: ✅ Check-in completed
Week 2: ✅ Check-in completed
Week 3: ❌ Missed check-in → Grace period begins (7 days)
Week 4: ❌ Grace period expires → Vault releases automatically
When to Use
- Digital Legacy: Ensure loved ones get important documents if you pass away
- Emergency Contacts: Release critical info (medical, financial) if you're incapacitated
- Business Continuity: Provide access to credentials if you're unavailable
- Traveler Safety: Share location/contacts if you don't return from high-risk travel
Configuration Options
| Setting | Options | Purpose |
|---|---|---|
| Check-in Frequency | Daily, Weekly, Biweekly, Monthly, Quarterly | How often you must check in |
| Grace Period | 1-90 days | Extra time after missed check-in before release |
| Reminder Timing | 1-7 days before | When to send check-in reminders |
| Reminder Methods | Email, SMS, Push notification | How you receive reminders |
Advantages
✅ Automatic Protection: Releases even if you can't manually trigger ✅ Flexible Timing: Adjust check-in frequency to your needs ✅ Grace Period Safety: Prevents accidental release from missed reminder ✅ Peace of Mind: Family gets access if something happens to you
Considerations
⚠️ Requires Discipline: Must remember to check in regularly ⚠️ False Positives: Extended travel/hospital stays might trigger unintended release ⚠️ Reminder Dependency: Must receive and act on check-in reminders
Best Practices
- Set Realistic Frequency: Choose a check-in schedule you can reliably maintain
- Active users: Weekly or biweekly
- Busy professionals: Monthly
- Retirees: Monthly or quarterly
- Use Sufficient Grace Period: Add 7-14 days grace period to prevent accidental releases
- Enable Multiple Reminders: Email + SMS for redundancy
- Test Your Reminders: Ensure they reach you and aren't marked as spam
- Update Before Travel: Extend grace period or pause policy before long trips
- Document for Recipients: Explain why vault may release so they're not surprised
Common Configurations
Digital Legacy (Standard):
- Frequency: Monthly check-ins
- Grace Period: 14 days
- Reminders: 3 days before deadline (email + SMS)
Emergency Release (Cautious):
- Frequency: Quarterly check-ins
- Grace Period: 30 days
- Reminders: 7 days before deadline
High-Risk Journalism:
- Frequency: Weekly check-ins
- Grace Period: 3 days
- Reminders: 2 days before deadline
Business Continuity:
- Frequency: Monthly check-ins
- Grace Period: 7 days
- Reminders: 5 days before deadline
Date-Based Release
What It Is
Date-Based Release automatically releases your vault on a specific date and time you choose in advance. Perfect for scheduled deliveries and time-sensitive documents.
How It Works
- You set a specific release date and time (e.g., January 1, 2026 at 9:00 AM)
- Vault remains locked until that date/time
- On the scheduled date/time, vault automatically releases
- Recipients are notified and granted immediate access
- No check-ins or manual action required
When to Use
- Wills & Estate Planning: Release estate documents on a specific date
- Scheduled Announcements: Share information at a predetermined time
- Time Capsules: Create digital time capsules for future anniversaries
- Contractual Obligations: Release documents per contract terms
- Gift Deliveries: Surprise someone with digital gifts on birthdays/holidays
Configuration Options
| Setting | Options | Purpose |
|---|---|---|
| Release Date | Any future date | When vault releases |
| Release Time | Specific time (timezone-aware) | Exact release time |
| Pre-Release Notifications | Days/weeks before | Warn recipients of upcoming release |
| Timezone | Your local timezone | Ensures correct release time |
Advantages
✅ Set and Forget: No ongoing action required ✅ Precise Timing: Released exactly when you specify ✅ Predictable: Recipients know when access will be granted ✅ No Check-ins: No maintenance or reminders needed
Considerations
⚠️ Irreversible (Near Date): Difficult to stop release close to scheduled time ⚠️ No Flexibility: Releases on schedule regardless of circumstances ⚠️ Requires Planning: Must know release date in advance
Best Practices
- Set Far Enough Ahead: Give yourself time to change plans if needed
- Use Pre-Release Notifications: Warn recipients 1-2 weeks before release
- Document the Why: Explain to recipients why this date was chosen
- Consider Time Zones: Double-check timezone to avoid wrong-time release
- Review Periodically: Check if release date still makes sense as time approaches
Common Scenarios
Estate Will Release:
- Release Date: 90 days after creation (allows time for legal processes)
- Pre-Release Notification: 14 days before
- Use Case: Executor gets access to estate documents after probate begins
Birthday Gift Delivery:
- Release Date: Recipient's birthday at 8:00 AM
- Pre-Release Notification: None (surprise!)
- Use Case: Digital scrapbook, memories, or special messages
Business Contract Terms:
- Release Date: Contract end date + 1 day
- Pre-Release Notification: 7 days before
- Use Case: NDA-protected documents released when NDA expires
Anniversary Time Capsule:
- Release Date: 10-year anniversary of wedding
- Pre-Release Notification: 30 days before
- Use Case: Photos, videos, letters from past selves
Death Certificate Verification
What It Is
Death Certificate Verification is a semi-automatic policy that releases your vault only after your death is officially verified through submission of a government-issued death certificate.
How It Works
- You configure the policy and designate which recipients can submit death certificates
- Upon your death, a recipient (usually executor or family member) submits death certificate
- Torvus Security staff verify authenticity of the death certificate
- If verified, vault is released to all designated recipients
- If rejected (fraudulent, insufficient info), submitter is notified and can resubmit
Verification Timeline:
Day 1: Recipient submits death certificate via secure portal
Day 1-3: Torvus Security staff verify certificate authenticity
Day 3: If verified → Vault releases to all recipients
If rejected → Submitter notified, can resubmle
When to Use
- Legal Compliance: Estate documents requiring proof of death
- High-Value Assets: Crypto wallets, bank info requiring strong verification
- Family Protection: Prevent premature or fraudulent release attempts
- Insurance Claims: Documents needed for life insurance claims
- Regulatory Requirements: Industries requiring death verification (finance, healthcare)
Configuration Options
| Setting | Options | Purpose |
|---|---|---|
| Authorized Submitters | Select recipients | Who can submit death certificate |
| Verification Level | Standard, Enhanced | How thorough verification process is |
| Backup Policy | Inactivity fallback | What happens if no certificate submitted |
| Notification Settings | Email recipients | Who gets notified of submission/verification |
Advantages
✅ Legal Certainty: Requires official proof of death ✅ Fraud Prevention: Prevents unauthorized release attempts ✅ Regulatory Compliance: Meets legal requirements for estate documents ✅ Professional Verification: Torvus Security staff verify authenticity ✅ Flexibility: Can combine with backup inactivity policy
Considerations
⚠️ Requires Certificate: Someone must obtain and submit death certificate ⚠️ Verification Delay: 1-3 business days for staff verification ⚠️ Knowledge Requirement: Recipients must know vault exists and how to submit certificate ⚠️ Enterprise Feature: May require Business or Enterprise plan
Best Practices
- Designate Multiple Submitters: Allow executor + 1-2 family members to submit
- Document Location: Tell authorized submitters where vault exists and how to access submission portal
- Combine with Inactivity: Add 12-month inactivity backup in case no certificate submitted
- Include Instructions: Provide step-by-step guide for obtaining death certificate
- Test Communications: Ensure recipients know about this vault and their responsibilities
Certificate Requirements
Accepted Documents:
- Official death certificate from government vital statistics office
- Certified copy with raised seal or official stamp
- Digital scan or photo showing all details clearly
Required Information:
- Deceased person's full legal name (must match vault owner)
- Date of death
- Certificate number or registration number
- Issuing authority (state, province, country)
- Official seal or stamp
Verification Process:
- Document quality check (legible, complete)
- Issuing authority validation (real government office)
- Name matching (deceased name matches vault owner)
- Fraud indicators review (altered documents, fake seals)
- Final approval by senior staff member
Combining Multiple Policies
Why Combine Policies?
Combining multiple policy types creates a robust, multi-layered approach to vault release:
- Primary Policy: Your intended release method
- Backup Policy: Fallback if primary policy fails
- Layered Protection: Multiple safeguards prevent unintended consequences
Common Combinations
1. Manual Release + Inactivity Backup
Use Case: Journalist vault with emergency fallback
Primary: Manual Release (full control over when to publish)
Backup: 90-day inactivity policy (releases if journalist incapacitated)
Rationale: You control release timing, but evidence releases automatically if something happens to you.
2. Death Certificate + Inactivity Fallback
Use Case: Estate documents with legal compliance
Primary: Death Certificate Verification (legal proof required)
Backup: 12-month inactivity (releases if no certificate submitted)
Rationale: Prefer official death verification, but vault still releases if family can't obtain certificate.
3. Inactivity + Date-Based Maximum
Use Case: Digital legacy with absolute deadline
Primary: 30-day inactivity policy (releases if you stop checking in)
Maximum: Date-based release in 5 years (absolute deadline)
Rationale: Releases via inactivity (preferred), but guaranteed to release by specific date regardless.
4. Multiple Inactivity Tiers
Use Case: Staged release to different recipients
Tier 1: 30-day inactivity → Releases to spouse/partner only
Tier 2: 90-day inactivity → Releases to children
Tier 3: 180-day inactivity → Releases to executor
Rationale: Phased access ensures most trusted recipients get access first.
Policy Selection Flowchart
START: What do you need?
┌─────────────────────────────────────┐
│ I want complete control over timing │
└────────────┬────────────────────────┘
│
▼
┌──────────────┐
│ Manual Release │
└──────────────┘
┌──────────────────────────────────────┐
│ I want automatic release if I'm gone │
└────────────┬─────────────────────────┘
│
▼
┌───────────────────┐
│ Inactivity Policy │
└───────────────────┘
┌────────────────────────────────────┐
│ I know exact date/time for release │
└────────────┬───────────────────────┘
│
▼
┌──────────────────┐
│ Date-Based Release │
└──────────────────┘
┌──────────────────────────────────────┐
│ I need legal proof of death required │
└────────────┬─────────────────────────┘
│
▼
┌────────────────────────────┐
│ Death Certificate Verification │
└────────────────────────────┘
Frequently Asked Questions
Can I change a policy after creating it?
Yes! You can modify or replace policies at any time before the vault releases. Go to Vault Settings → Policies → Edit.
Can I have multiple policies on one vault?
Yes. You can combine policies (e.g., Manual Release + Inactivity Backup). The first policy to trigger releases the vault.
What happens if I miss an inactivity check-in?
The grace period begins. You have extra time (e.g., 7-14 days) to check in before vault releases.
Can I pause a policy temporarily?
Yes. You can pause inactivity policies before travel or hospital stays. Remember to un-pause when you return.
Can I cancel a date-based release?
Yes, but only if the release date hasn't passed yet. Go to Vault Settings → Policies → Cancel Release.
How do recipients know what policy type I'm using?
Recipients can see basic policy info (e.g., "Vault will release if owner inactive for 30 days") but not your check-in history or exact dates.
Can policies trigger partial releases?
Not yet. When a policy triggers, all recipients get access to all vault contents. Staged releases are planned for future versions.
What if multiple people submit death certificates?
All submissions are reviewed. The first verified certificate triggers release. Subsequent submissions have no effect.
Related Pages
- Configure Policies - How to set up policies
- Manual Check-in - How to complete check-ins
- Vault Settings - Manage vault configuration
- Add Recipients - Who gets access when vault releases
Last Updated: October 8, 2025