[EnthusiastShiv]

Thanks for your feedback! Here’s a quick response to your concerns:

1. Private Key Storage: Private keys are derived locally from your security factors when you set up them.

2. Time Capsule Keys: The release of "time capsule" keys is governed by strict protocols, ensuring they’re only accessible at the specified time.

3. AES Encryption: We use AES-256, not 512, will fix that typo.

4. End-to-End Encryption: yes, End-to-end encryption requires both you and your beneficiaries to enable security factors.

[201984]

Thanks for responding!

What are these "security factors" you keep mentioning? It's a vague term and I don't see a definition on your website. Can you also describe how private keys are derived from them? That's what I'm most curious about. Is this derivation process something that could be replicated by an attacker?

[EnthusiastShiv]

We've added a page to explain "What are Security Factors?" https://www.cipherwill.com/how-factors-work

[Daviey]

Can you expand on "strict protocols" please?

[EnthusiastShiv]

"strict protocols" refer to our will execution schedule, which ensures that the keys are only accessible after the switch is triggered. Even if someone were to hack the system and access the keys before execution, only the designated beneficiaries would have the ability to decrypt the data.

[crtasm]

What exactly is preventing someone with the key decrypting the data before some other code in your system runs?

[EnthusiastShiv]

Only the people who you've added in your beneficiaries can decrypt the data if Cipherwill is hacked.

[crtasm]

This is basically saying "trust us" and does not instill confidence in your system.

[EnthusiastShiv]

will definitely fix this