The short version
- Anonymous calculations will not be intentionally persisted by Retired Kevin.
- Saving will require a verified Retired Kevin account.
- Supported account plans are intended to be encrypted before central storage.
- Identity information and encrypted plan information will be separated.
- No website or device can be guaranteed completely secure.
Planned protection for saved plans
- Encrypted connection. HTTPS/TLS protects information while it travels between the browser and service.
- Application-level encryption. Supported plan payloads are intended to be encrypted before being written to the account database.
- Separate key management. Managed encryption keys, versions and rotation procedures will be kept apart from encrypted records.
- Encrypted backups. Backups will be encrypted, access-controlled and subject to tested restoration and deletion procedures.
- Least-privilege access. Production access will be limited to the people and systems that require it.
- Payload-free operations. Logs, analytics, email and support systems should not receive financial-plan payloads.
Account access
Retired Kevin intends to use a reputable managed identity provider behind Retired Kevin branding. The first release should use verified email with a magic link and/or passkey, secure session cookies, provider-managed recovery, rate limiting and reauthentication for sensitive actions.
Retired Kevin does not intend to build or store its own password database. Every plan request must be checked server-side to confirm that the signed-in user owns the record.
The identity provider must be named in the final Privacy Policy.
Anonymous sessions and browser memory
New anonymous work will remain only for the open experience where technically possible. Refreshing, closing the page or ending the session may erase it.
Temporary browser memory is not a secure vault. Decrypted account information will also exist temporarily in browser memory while in use and should be cleared from the active experience after sign-out.
Data minimization
The tools do not need a SIN, bank password, brokerage credential, full account number or government-account login. Retired Kevin will collect and retain only the information needed for a stated planning, account, security or communication purpose.
Security operations
Before launch, Retired Kevin needs documented access controls, dependency and patch management, backup and restoration tests, key rotation, provider review, vulnerability response, rate limits, audit records and a tested incident-response process.
Privacy breaches must be assessed, recorded and—where legally required—reported to the appropriate regulator and affected individuals.
Important limits
Encryption reduces risk but does not eliminate it. The account service will not be described as end-to-end encrypted, zero-knowledge, anonymous or impossible to breach unless those claims are specifically built and independently verified.
Exports and shared links leave the account-storage boundary. Their security depends on where you keep them and who receives them.
How to use the service safely
- Use a trusted, updated device and protect access to your email account.
- Sign out when using a shared device.
- Do not enter passwords, tax identifiers, full account numbers or unnecessary medical information.
- Review exports before sharing and store them appropriately.
- Use the account controls to review and delete saved information you no longer need.
Report a concern
Use the Contact page to report a security or privacy concern. Describe the page and what happened, but do not include passwords or sensitive financial information.