Skip to main content

Configure Release Policies

Set up automatic vault release conditions

Policies determine when and how your vault is released to recipients. This guide covers all policy types and how to configure them.


Before You Begin​

Prerequisites:

  • βœ… Vault created
  • βœ… Documents uploaded
  • βœ… Recipients added

Policy Types Available:

  1. Inactivity Policy
  2. Manual Release
  3. Date-Based Release
  4. Death Certificate Verification

Policy Type 1: Inactivity Policy​

What it is: Releases vault if you don't complete regular check-ins.

Best For:

  • Personal emergency planning
  • Travel safety
  • Business continuity
  • Journalist/activist protection

Configure Inactivity Policy​

Step 1: Start Policy Creation​

  1. Navigate to vault
  2. Click "Policies" tab
  3. Click "Add Policy"
  4. Select "Inactivity Policy"

Step 2: Set Check-in Frequency​

Choose how often you'll check in:

Daily:

  • Check in every 24 hours
  • Best For: High-risk situations, journalists, activists
  • Example: Daily confirmation you're safe

Weekly:

  • Check in every 7 days
  • Best For: Frequent travelers, high-security needs
  • Example: Weekly travel safety check-in

Biweekly:

  • Check in every 14 days
  • Best For: Balanced approach
  • Example: Semi-regular activity confirmation

Monthly (Most Common):

  • Check in every 30 days
  • Best For: Personal vaults, estate planning
  • Example: Monthly confirmation you're active

Custom:

  • Set custom interval (Professional plan)
  • Range: 1 day to 90 days
  • Best For: Specific organizational needs

Step 3: Set Grace Period​

Grace period is extra time after missed check-in before vault releases.

24 Hours:

  • Free plan default
  • Vault releases 24 hours after missed check-in

48 Hours:

  • Standard plan default
  • Vault releases 48 hours after missed check-in

72 Hours:

  • Professional plan default
  • Vault releases 72 hours after missed check-in

Custom (Enterprise):

  • Up to 7 days
  • Custom grace period for specific needs

Recommendation: Use longest grace period your plan allows (gives you more time if you miss check-in while traveling, etc.)


Step 4: Configure Check-in Methods​

Select how you'll complete check-ins:

Email (Default, Always Enabled):

  • Click link in reminder email
  • One-click check-in
  • Works on any device

SMS (Optional):

  • Reply to text message with code
  • Faster than email for some users
  • Requires phone number in profile

Mobile App (Recommended):

  • Tap check-in button in app
  • Push notification reminder
  • Biometric authentication

API (Advanced):

  • Automated check-in from your systems
  • Webhook integration
  • Professional/Enterprise plans only

Best Practice: Enable multiple methods (email + mobile app) for redundancy.


Step 5: Set Reminder Schedule​

Configure when you receive check-in reminders:

Reminder Timing:

  • 3 days before: First reminder (for weekly/monthly)
  • 1 day before: Second reminder (for weekly/monthly)
  • Day of: Check-in due today
  • Grace period: Urgent reminders during grace period

Reminder Channels:

  • Email: Enabled by default
  • SMS: Optional (requires phone number)
  • Push Notification: If mobile app installed
  • In-App: Notification in Torvus interface

Custom Reminders (Professional):

  • Set custom reminder timing
  • Additional reminders
  • Custom reminder messages

Step 6: Select Recipients​

Choose which recipients receive vault access when policy triggers:

Options:

  • All recipients: Everyone in recipient list receives access
  • Selected recipients: Choose specific recipients
  • Tiered recipients: Different recipients at different times (Professional)

Best Practice: Select all recipients unless you have specific reason to exclude some.


Step 7: Review and Activate​

  1. Review policy configuration
  2. Click "Activate Policy"
  3. Complete first check-in immediately (establishes baseline)

What Happens Next:

  • Next check-in scheduled based on frequency
  • Reminders sent according to schedule
  • If check-in missed and grace period expires, vault releases to recipients

Policy Type 2: Manual Release​

What it is: Immediately releases vault with button press.

Best For:

  • Emergency situations
  • Medical emergencies
  • Security threats
  • Immediate disclosure needs

Configure Manual Release​

Step 1: Enable Manual Release​

  1. Navigate to vault
  2. Click "Policies" tab
  3. Click "Add Policy"
  4. Select "Manual Release"

Step 2: Set Security Requirements​

Two-Factor Authentication:

  • βœ… Always required (cannot be disabled)
  • Prevents accidental or unauthorized release

Confirmation Dialog:

  • βœ… Required by default
  • "Are you sure you want to release this vault immediately?"

Cooldown Period (Optional, Professional):

  • 15-minute cooldown before release takes effect
  • Allows you to cancel accidental release
  • Disable for true instant release

Step 3: Select Recipients​

Choose who receives vault access when you trigger manual release:

Options:

  • All recipients: Everyone receives access
  • Selected recipients: Choose specific recipients
  • Emergency-only recipients: Separate list for manual release (Professional)

Step 4: Add Emergency Message (Optional)​

Personal message sent to recipients with manual release notification:

Example Messages:

  • "Emergency situation. Please access documents immediately and contact authorities."
  • "Medical emergency. Contact my doctor Dr. Smith at 555-1234."
  • "Security threat. Vault contains evidence. Contact attorney."

Step 5: Activate Policy​

  1. Review configuration
  2. Click "Activate Policy"

What Happens Next:

  • Manual release button appears in vault interface
  • When pressed, vault immediately releases (after 2FA confirmation)
  • Recipients receive notification with emergency context

How to Trigger Manual Release​

  1. Navigate to vault
  2. Click "Emergency Release" button (red button)
  3. Confirm action in dialog
  4. Complete 2FA verification
  5. Recipients receive immediate notification

Cancel Release (Professional, if cooldown enabled):

  • Click "Cancel Release" within cooldown period
  • Release is canceled before recipients are notified

Policy Type 3: Date-Based Release​

What it is: Automatically releases vault on specific date.

Best For:

  • Future-dated information delivery
  • Time capsules
  • Scheduled disclosures
  • Delayed inheritance

Configure Date-Based Release​

Step 1: Start Policy Creation​

  1. Navigate to vault
  2. Click "Policies" tab
  3. Click "Add Policy"
  4. Select "Date-Based Release"

Step 2: Set Release Date​

Date Picker:

  • Select future release date
  • Must be at least 24 hours in future
  • Can be years in advance

Time Selection (Optional):

  • Specific time of day (default: midnight UTC)
  • Timezone selection

Examples:

  • January 1, 2030 (future inheritance)
  • Your 65th birthday (retirement vault)
  • December 31, 2025 (annual disclosure)

Step 3: Add Release Message​

Personal message sent to recipients on release date:

Example Messages:

  • "Happy 18th birthday! This vault contains information I wanted you to have when you turned 18."
  • "This vault was scheduled to release on this date. Contents are time-sensitive."
  • "Future disclosure as planned. Vault contains documents relevant to [project/event]."

Step 4: Configure Pre-Release Notifications​

Notify Recipients Before Release (Optional, Professional):

  • 30 days before
  • 7 days before
  • 24 hours before

Why Useful: Gives recipients heads-up to expect vault access.


Step 5: Select Recipients​

Choose who receives vault access on release date.


Step 6: Activate Policy​

  1. Review configuration
  2. Click "Activate Policy"

What Happens:

  • Policy is scheduled
  • On release date, vault automatically releases to recipients
  • Recipients receive notification with your message

Managing Date-Based Policies​

Modify Release Date:

  1. Navigate to policy
  2. Click "Edit Policy"
  3. Update release date
  4. Save changes

Cancel Scheduled Release:

  1. Navigate to policy
  2. Click "Delete Policy"
  3. Confirm deletion
  4. Release is canceled

Policy Type 4: Death Certificate Verification​

What it is: Releases vault after verified death certificate submitted.

Best For:

  • Estate planning
  • Will distribution
  • Digital inheritance
  • Life insurance information

Configure Death Certificate Policy​

Step 1: Start Policy Creation​

  1. Navigate to vault
  2. Click "Policies" tab
  3. Click "Add Policy"
  4. Select "Death Certificate Verification"

Step 2: Designate Verification Contact​

Who Can Submit Death Certificate:

  • Any recipient: Any recipient can submit (default)
  • Specific person: Designated individual (executor, attorney)
  • Multiple designated: Require submission from 2+ people (Professional)

Contact Information:

  • Name of person authorized to submit
  • Email address
  • Phone number
  • Relationship (executor, attorney, family member)

Step 3: Set Verification Requirements​

Automatic Verification:

  • Torvus verifies death certificate with issuing authority
  • Checks authenticity against government databases
  • Professional/Enterprise plans only

Manual Verification (Standard):

  • Torvus staff manually review submitted certificate
  • Verify against known fraud patterns
  • Response within 3-5 business days

Step 4: Configure Release Delay (Optional)​

Immediate Release:

  • Vault releases immediately after verification

Delayed Release:

  • Add delay after verification (7 days, 30 days, etc.)
  • Allows time for estate settlement, legal processes
  • Professional plan feature

Step 5: Select Recipients​

Choose who receives vault access after death certificate verified.


Step 6: Activate Policy​

  1. Review configuration
  2. Click "Activate Policy"

What Happens Next:

  • Policy is active but dormant
  • When death certificate submitted and verified, vault releases
  • Recipients receive notification

How Death Certificate Submission Works​

For Designated Contact:

  1. Contact receives notification with secure submission link
  2. Contact uploads death certificate (PDF or image)
  3. Torvus verifies authenticity
  4. After verification, vault releases to recipients
  5. Recipients receive notification

Multiple Policies Per Vault​

Policy Combinations​

Free Plan: 1 active policy per vault

Standard Plan: Up to 3 active policies per vault

Professional Plan: Unlimited active policies per vault


Common Policy Combinations​

Example 1: Personal Vault

  • Policy A: Inactivity (monthly check-ins)
  • Policy B: Manual release (emergency)
  • Policy C: Death certificate verification

Why: Covers multiple scenariosβ€”missing check-ins, immediate emergency, or death.


Example 2: Business Vault

  • Policy A: Inactivity (weekly check-ins)
  • Policy B: Manual release (emergency)

Why: Business continuity (missing check-ins) + immediate access if needed.


Example 3: Time Capsule

  • Policy A: Date-based release (specific future date)
  • Policy B: Manual release (option to release early if desired)

Why: Scheduled release with option to release sooner if circumstances change.


Policy Priority​

When Multiple Policies Trigger:

  • All triggered policies execute
  • Recipients receive one notification mentioning all triggered policies
  • Recipients gain access level based on highest permission

Example: If inactivity policy and manual release both trigger, recipients receive notification mentioning both, but only need to verify identity once.


Policy Testing (Professional Plan)​

Test Policy Feature​

Purpose: Verify policies work correctly before real emergency.

How It Works:

  1. Navigate to policy
  2. Click "Test Policy"
  3. System simulates policy trigger
  4. Test notification sent to recipients
  5. Recipients can practice accessing vault
  6. Test access expires after 24 hours
  7. Vault returns to normal state

Best Practice: Test policies annually to ensure recipients know how to access vault.


Policy Management​

Edit Active Policy​

  1. Navigate to Policies tab
  2. Click policy name
  3. Click "Edit Policy"
  4. Update settings
  5. Click "Save Changes"

What You Can Change:

  • Check-in frequency (inactivity policy)
  • Grace period (inactivity policy)
  • Release date (date-based policy)
  • Recipients
  • Notification settings

What You Cannot Change:

  • Policy type (must delete and create new policy)
  • Past policy activity (audit log is immutable)

Pause Policy​

  1. Navigate to policy
  2. Click "Pause Policy"
  3. Confirm pause

What Happens:

  • Policy stops monitoring
  • Check-in reminders stop (inactivity policy)
  • Policy will not trigger
  • Can be resumed anytime

Use Cases:

  • Extended vacation (don't want check-in reminders)
  • Temporary situation where policy shouldn't trigger

Resume Policy​

  1. Navigate to paused policy
  2. Click "Resume Policy"
  3. Complete check-in if inactivity policy (establishes new baseline)

Delete Policy​

  1. Navigate to policy
  2. Click "Delete Policy"
  3. Confirm deletion

Important:

  • Policy permanently deleted
  • Cannot be recovered
  • If scheduled release (date-based or death certificate), release is canceled

Policy Audit Logs​

What's Logged​

  • Policy creation
  • Policy modifications
  • Check-in completions
  • Missed check-ins
  • Grace period triggers
  • Policy triggers
  • Recipient notifications
  • Manual releases

Access Audit Logs​

  1. Navigate to Policies tab
  2. Click policy name
  3. Click "Audit Log" tab

Best Practices​

βœ… DO​

  • Enable multiple policy types: Cover different scenarios (inactivity + manual + death certificate)
  • Test policies: Use test feature to verify recipients can access (Professional)
  • Set realistic check-in frequency: Choose frequency you can maintain long-term
  • Use longest grace period available: Gives you time if you miss check-in while traveling
  • Add personal messages: Help recipients understand context when vault releases
  • Review policies regularly: Ensure policies still match your needs (every 6-12 months)

❌ DON'T​

  • Set check-in frequency too high: Daily check-ins are burdensome unless truly necessary
  • Skip grace period: Always use grace period to prevent accidental release
  • Forget to complete first check-in: Establishes baseline for inactivity policy
  • Ignore check-in reminders: Missed check-ins trigger grace period
  • Add policies without recipients: Policies need recipients to be useful

Troubleshooting​

Not Receiving Check-in Reminders​

Possible Causes:

  • Email in spam folder
  • Email address incorrect
  • Notification settings disabled

Solutions:

  1. Check spam folder
  2. Whitelist @torvussecurity.com emails
  3. Verify email address in profile
  4. Check notification settings in vault

Missed Check-in, Need to Cancel Release​

During Grace Period:

  1. Complete check-in immediately
  2. Release is canceled
  3. Next check-in scheduled normally

After Grace Period Expired:

  • Vault has already released to recipients
  • Cannot be automatically reversed
  • Contact recipients and ask them not to access (if false alarm)
  • Professional plan: Can revoke recipient access manually

Policy Not Triggering​

Possible Causes:

  • Policy is paused
  • Policy conditions not met
  • Policy deleted

Solutions:

  1. Verify policy is active (not paused)
  2. Check policy conditions (correct date, check-ins up to date, etc.)
  3. Check audit log for policy activity

Want to Change Policy Type​

Solution: Cannot change policy type directly

  1. Delete existing policy
  2. Create new policy with desired type
  3. Configure new policy settings

Next Steps​

After configuring policies:

  1. Manual Check-in: Complete first check-in (inactivity policy)
  2. Vault Settings: Customize notifications and settings
  3. Best Practices: Optimize vault configuration


Need Help?​


Last Updated: October 7, 2025