What Can I Store in SafekeeperLife?

Version: Credentials Mode - Credential Protection Last Updated: October 2025

Table of Contents

• Quick Summary
• The Core Principle
• What You CAN Store
• What You CANNOT Store
• Common Use Cases
• Credential Templates
• FAQ

Quick Summary

SafekeeperLife is designed for storing credentials and access information, NOT files or documents.

Think of SafekeeperLife as a way to protect the Keys to your digital life, not as a vault for the content itself.

✅ Perfect for: Passwords, account logins, recovery codes, links to shared folders ❌ Not designed for: Photos, videos, documents, file backups

The Core Principle

SafekeeperLife helps you answer this critical question:

“If something happens to me, how will my loved ones access my important accounts?”

We protect access to your digital accounts, not the accounts’ contents. Here’s the distinction:

❌ Don’t Store the Content	✅ Store the Access Credentials
Your will.pdf (the file itself)	Credentials to access the Dropbox folder containing your will
Your photo library (thousands of files)	Login to Google Photos, iCloud or whereever your photos live
Your business documents	Password to your company cloud storage account
Your email messages	Email account login credentials

Analogy: SafekeeperLife is like giving trusted people the Key to your Safe or safety deposit box, not storing furniture in their garage.

What You CAN Store

What You CANNOT Store

SafekeeperLife is not designed for these use cases:

❌ Files and Documents

Don’t store:

• PDF files (wills, deeds, contracts)
• Photos or videos
• Scanned documents
• Microsoft Office documents
• Any file larger than a few KB

Instead: Store these files in cloud storage (Dropbox, Google Drive or similar) and protect the credentials to access that cloud storage in SafekeeperLife.

❌ Large Amounts of Data

Don’t store:

• Complete file backups
• Photo libraries
• Video collections
• Music collections
• Software installers

Why: SafekeeperLife is optimized for small, text-based credentials (a few KB), not large files.

❌ Frequently Changing Information

Don’t store:

• Information that changes daily/weekly
• Temporary passwords
• Single-use codes
• Real-time data

Why: Updating credentials in SafekeeperLife requires unlocking, editing, and re-locking the Safe - not practical for frequently changing data.

❌ Public Information

Don’t store:

• Information already available publicly
• Non-sensitive contact information
• Public social media profiles

Why: No need to cryptographically protect information that’s already public.

Common Use Cases

Use Case 1: Password Manager Emergency Access

Scenario: You use 1Password to manage 200+ passwords. If something happens to you, your family has no way to access your accounts.

Solution:

1. Create a Safe in SafekeeperLife
2. Store your 1Password master password, account email, and emergency kit location
3. Lock the Safe with additional triggers (inactivity and/or attestation)
4. Distribute Keys to 3 trusted family members (with a threshold set to 2)

Result: Your family can combine 2 Keys to reveal your 1Password credentials, then access all your accounts.

Use Case 2: Digital Estate Planning

Scenario: You have important documents (will, deeds, insurance policies) that your executor(s) needs(need) access to.

Solution:

1. Create a “Digital Estate” folder in Dropbox
2. Upload all important documents to that folder
3. Create a Safe in SafekeeperLife storing:
   • Dropbox account login
   • Link to the shared folder
   • Instructions for your executor
4. Designate your executor(s) and lawyer as Keyholders

Result: Your executor(s) can access all important documents without you having to store large files in SafekeeperLife.

Use Case 3: Cryptocurrency Estate Planning

Scenario: You hold cryptocurrency in a hardware wallet. The recovery phrase is the only way to access the funds.

Solution:

1. Store the 12/24-word recovery phrase in SafekeeperLife
2. Include the wallet address and exchange account logins
3. Lock with a 2-of-3 threshold
4. Include instructions on how to access the wallet

Result: Your beneficiaries can reconstruct the recovery phrase and access your cryptocurrency holdings.

Use Case 4: Business Continuity

Scenario: You run a small business. If you’re incapacitated, your business partner(s) needs access to critical accounts.

Solution:

1. Store credentials for:
   • Business bank accounts
   • Domain registrars
   • Email accounts
   • Payment processors (Stripe, etc.)
2. Use inactivity trigger (30 days)
3. Designate business partner(s) as Keyholders (if you only have a single business partner, use your accountant or legal representative too)

Result: After 30 days of inactivity, your business partner(s) can access critical accounts to keep the business running.

Credential Templates

For ease of data entry, SafekeeperLife includes pre-built templates for common services. Here’s what you can store with each:

FAQ

Q: Can I store my will in SafekeeperLife?

A: No, but you can store access to your will. Upload your will to Dropbox/Google Drive, then store the login credentials in SafekeeperLife.

Q: How much data can I store in a single Safe?

A: SafekeeperLife is optimized for text-based credentials (passwords, account numbers, notes). While there’s no hard limit, think in terms of KB (kilobytes), not MB (megabytes). A typical Safe might contain 5-20 credentials totalling a few KB.

Q: Can I store backup codes as images/screenshots?

A: While technically possible to paste base64-encoded images into a field, it’s not recommended. Instead, type out the backup codes as text (one per line). This is more reliable and easier for Keyholders to use.

Q: What if my password changes?

A: You can update credentials anytime by:

1. Unlocking your Safe
2. Editing the credentials
3. Locking again (this generates new shared Keys)

Important: Changing credentials after sealing IS NOT POSSIBLE

Q: Can I store multiple accounts in one Safe?

A: Yes! You can store multiple credentials in a single Safe. For example, one Safe could contain:

• Google Account login
• Dropbox login
• Bank account credentials
• 1Password master password

All of these would be revealed together when Keyholders combine their Keys.

Q: Should I create one Safe for everything or multiple safes?

A: It depends on your approach to risk and threats:

One Safe approach:

• ✅ Simpler to manage
• ✅ Fewer Keys to distribute
• ❌ All credentials revealed at once

Multiple safes approach:

• ✅ Granular control (different Keyholders for different Safes)
• ✅ Different triggers per Safe
• ❌ More complex to manage

Recommendation: Start with one Safe. As your needs grow, create additional Safes for different purposes (personal, business, estate planning).

Q: What if I accidentally store sensitive info I shouldn’t have?

A: You can always:

1. Unlock the Safe
2. Edit out the sensitive information
3. Lock again

Remember: Once a Safe is Sealed, Keys are distributed, Keyholders have the ability to reveal the Safe’s contents. Be thoughtful about what you store.

Q: Can I store API Keys or access tokens?

A: Yes! API Keys, access tokens, and webhook secrets are perfect for SafekeeperLife. Just remember:

• If they change frequently, SafekeeperLife might not be the best solution
• Make sure to include expiration dates if applicable
• Include instructions on how to use or regenerate them

Best Practices

1. Store access, not content: Always ask “Am I storing the Key or the thing itself?”

2. Include context: Add notes explaining:

   • What this credential is for
   • How to use it
   • What to do after accessing it

3. Test your credentials: Before locking, verify the credentials actually work by logging in.

4. Keep credentials current: Review your Safes periodically (every 6-12 months) to ensure the credentials are still valid.

5. Use the right tool for the job:

   • Small credentials? → SafekeeperLife ✅
   • Large files? → Cloud storage + SafekeeperLife credentials ✅
   • Daily passwords? → Password manager ✅

6. Document your setup: Include a note in your Safe explaining:

   • What Keyholders should do with the revealed information
   • Who to contact for help
   • Any additional steps needed

Summary

SafekeeperLife Credentials Mode is designed for:

• ✅ Credentials (passwords, account logins)
• ✅ Access information (links, account numbers)
• ✅ Recovery codes and Keys
• ✅ Small text-based secrets

SafekeeperLife is NOT designed for:

• ❌ Files (PDFs, photos, videos)
• ❌ Large data backups
• ❌ Frequently changing information

Golden Rule: If you can type it into a form field, it belongs in SafekeeperLife. If it’s a file you download or upload, it belongs in cloud storage (and you store the cloud storage credentials in SafekeeperLife).

Next Steps

1. Try the Getting Started guide: Visit /getting-started for a visual walkthrough
2. Review credential templates: See which templates fit your use case
3. Create your first Safe: Start with your password manager credentials
4. Read about emergency triggers: Learn how to automate sealing with Emergency Triggers Guide
5. Understand Keyholder best practices: Review Keyholder Best Practices

Questions? Check out the User FAQ or reach out to support.