How AstruLegacy protects your information
Security is part of the product design because legacy information can be more sensitive than ordinary website content.
Encrypted data at rest
The active AstruLegacy data store and AstruLegacy backup snapshots use authenticated AES-GCM encryption. The encryption key is kept separately from the encrypted data and should have an independent recovery copy.
Two-factor authentication
Accounts can use standard TOTP authenticator-app codes plus one-time recovery codes. Sensitive trusted-access and recovery actions require the stronger authenticated session where applicable.
Controlled trusted access
A trusted person does not automatically see legacy records after accepting an invitation. Access is separately requested and released, and released information is presented read-only.
Verified backups
Backups are checksum-verified and decrypted after creation before being treated as valid. A separate off-server backup location is supported for disaster recovery.
Session and login protection
Authentication endpoints are rate limited. Important password and 2FA changes invalidate older signed-in sessions. Authentication cookies are HTTP-only and production cookies are configured to require HTTPS.
Data control
Signed-in users can export a readable copy of their AstruLegacy data and can permanently remove their active account and legacy records through protected account-security controls.
What you should do
- Use a unique password stored in a reputable password manager.
- Enable two-factor authentication and keep recovery codes offline.
- Do not store actual account passwords in ordinary legacy notes.
- Keep your will and other legally operative originals in an appropriate independent location.
- Review your AstruLegacy information periodically and revoke trusted access that is no longer appropriate.
Report a security concern
Configure Support:ContactEmail before launch so security concerns have a published reporting address.