Trust begins with a clear explanation.
Financial information deserves careful engineering and plain language. Here is what Pennora does today—and what remains part of the launch work.
Account isolation
Every financial record is associated with a user account. Database row-level security checks the signed-in user before records can be read or changed, helping prevent one account from accessing another account’s information.
Authentication
Pennora uses managed authentication rather than implementing passwords and sessions independently. Password reset and email verification are handled through the authentication provider.
Storage and transport
Account information is stored in a hosted PostgreSQL database. Production deployment requires HTTPS, which protects information while it travels between the browser and service. Hosting and database region choices remain launch-gated decisions.
Your controls
- ExportDownload a JSON backup or spreadsheet-ready CSV from the product.
- Remove recordsClear financial entries from the dashboard’s danger zone.
- Account deletionEnd-to-end account deletion is still a launch requirement and will not be described as complete before it is verified.
- No sale of dataPennora’s product promise is that personal financial information is not sold.
Honest limits
Pennora does not currently connect to banks, initiate payments or move investments. Future integrations will require additional provider, regulatory and security review before release. Security is ongoing work, not a badge or a one-time claim.