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.
Cookies and optional analytics
Hisava uses essential cookies for sign-in, recovery and invitations. Optional PostHog product analytics remains off unless production privacy/configuration checks are complete and you explicitly allow it. Declining does not affect service access. You can change your preference below; it is stored for 180 days in this browser and is not linked to an account. Do Not Track and Global Privacy Control signals override opt-in.
If enabled and allowed, Hisava relays only fixed event names for successful signup, household creation, first budget creation, expense addition and invitation acceptance. Each event uses a new random identifier, with no link to an account, household or previous event. No expense amounts, descriptions, names, emails, account/household IDs, page URLs, browser IP addresses, screenshots or feedback text are sent. Hisava does not load PostHog browser scripts, session recording, person profiles or autocapture. Google Analytics remains disabled.
Hisava’s configured PostHog project processes these optional event counts in US Cloud, in the United States. PostHog’s current free plan retains these event counts for one year. Production tracking must remain disabled until the hosting region, provider settings, retention and contractual/privacy requirements have been reviewed. These counts do not track individual journeys.
Feedback and support
If you choose Send feedback, Hisava stores your message and optional screenshot privately, linked internally to your account and household. Other household members cannot see it. Authorized support administrators may review it and limited account/onboarding/invitation metadata to troubleshoot problems. Support access and review changes are audited. Screenshots are stripped of image metadata; please crop out financial details, credentials and anything you do not want support to see. Feedback and attachments are never sent to analytics. Primary feedback records are removed when the associated account or household is removed; limited administrative audit records and backups may remain. Contact contact@hisava.app to request review or removal.
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
Shared household financial records are intended to be accessible only to active members of that household. Within a household, private personal expenses are accessible only to their owner; shared personal expenses remain visible to both members. 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. Removing an expense excludes it from active views and totals but retains its stored record. Deleting a secondary member’s account removes sign-in access and pseudonymizes their account identity while preserving stored financial records, including private personal entries. It does not erase all records associated with that member. 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.