How Secure Is My Vault?

Created by IronClad Family Support, Modified on Sat, Nov 29 at 6:40 PM by IronClad Family Support

How secure is my IronClad Family vault?

Your vault is built with the same mindset we use for our own families: assume attackers are creative, assume people are busy, and design for both. Here is how IronClad Family protects your information and where your responsibility starts.

Zero-knowledge encryption illustration

Zero-knowledge encryption

IronClad Family uses a “zero-knowledge” model, which means we cannot read the contents of the documents you store in your vault. Even our support team can only see that a file exists, not what is inside it.

  • Your documents are encrypted in transit and at rest.
  • Decryption keys are tied to your account and permissions.
  • Only you and the recipients you authorize can ever see your content.
Daily security scans illustration

Ongoing security checks

Our systems are scanned regularly for vulnerabilities and misconfigurations. We keep our infrastructure and third-party services updated and monitored so that known issues are fixed quickly.

Your data your control illustration

Your data, your control

  • You decide who your recipients are.
  • You decide which folders or documents each person can see.
  • You decide when access should be granted (date, event, or manual).
Your part in security: use strong, unique passwords; turn on two-factor authentication when available; keep your devices updated; and sign out on shared computers.

No online system can be guaranteed 100% secure, but IronClad Family is designed by cybersecurity professionals to significantly reduce the risk of unauthorized access while keeping your vault easy to use in real life.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article