Information Hisava stores
Hisava stores account information such as your name, email address, password hash, email-verification status, and active sessions. It also stores information you and your household enter, including household membership, budgets, categories, purchases, expense splits, goals, planned purchases, settlements, and decision-journal entries.
Google sign-in
If you choose Google sign-in, Hisava receives your name, email address, verification status, and a Google account identifier to connect you to your Hisava account. Hisava does not retain Google access or refresh tokens or request access to Gmail, Drive, or other Google account content.
How this information is used
We use this information to authenticate you, operate your household workspace, calculate shared spending and balances, provide exports, support invitations and password resets, prevent abuse, and maintain the service.
Bank connections and receipts
A bank connection is not required. If you choose to submit a receipt image, Hisava temporarily processes it to suggest purchase details for your review. The original image is removed from temporary application storage after processing; confirmed purchase information and receipt metadata are stored in your household records. Email providers process the account emails Hisava sends, including their recipient and message content.
Who can access household information
Household financial records are intended to be accessible only to active members of that household. The service uses application access checks and database tenant controls to separate household data. Authorized service providers may process limited information to host the application, store data, or deliver account email.
Sharing and sale
Hisava does not require you to provide bank credentials. We do not sell household financial data. Information may be disclosed when required by law, to protect the service and its users, or to vendors acting on our behalf under appropriate instructions.
Security and retention
We use reasonable technical safeguards, but no hosted service can promise absolute security. Hisava does not currently claim end-to-end encryption. An owner can permanently delete a household from Settings after password confirmation. Deleted information may remain temporarily in database backups and limited operational logs until those systems expire or are rotated.
Your choices
You can choose what household financial information to enter, export supported expense data, and use the owner-controlled deletion workflow to remove a household and its member accounts from the primary database. Questions about correction or deletion can be sent to contact@hisava.app. Some limited information may need to be retained when required by law or to protect the service.
Contact and changes
Questions can be sent to contact@hisava.app. We may revise this policy as the service changes and will update the date above.