Privacy Policy

HomeXpense is a web app for tracking rental properties, mortgages, income and expenses. It is operated by the HomeXpense team (“we”, “us”). This policy explains what personal information we collect, why, where it is stored, and the choices you have. For any privacy question or request, email support@homexpense.com.

• Account information. When you sign in with Google, we receive your name, email address and profile picture link from Google. If you sign up with an email address and password instead, we store your email address and email you a link to confirm it; your password is stored only as a secure hash by our authentication provider.
• Portfolio information you enter or import. Properties (their name, country and state or province, purchase details and estimated values), mortgages and their payments, rental income, expenses, transactions, and the rules you set up.
• Bank statement lines. When you upload a bank statement, the file is read in your own browser. Only the lines you import (date, description, amount and the account they belong to) and a fingerprint of the file, so we can recognise a file you upload twice, are sent to us and stored. The statement file itself and its file name are neither sent nor stored. We also keep a one-way fingerprint of where a statement comes from, so we can match your next upload to the same bank account: for an OFX file it is made from the bank and account numbers in the file (the numbers themselves are not kept); for a CSV file, only from its column headings (or its number of columns when it has none). For OFX files we also keep the bank’s own id for each line, by which the same line is recognised and never imported twice; it stays with the line when the line’s text is erased.
• Spreadsheets. When you import a spreadsheet from the Transactions page, the file is read on your device, in your browser, and only the rows you choose to import are sent to us; rows you leave out at the final check are not kept. We keep: the rows you import (for each, its date, amount, category and property, and the description and notes from the columns you choose, kept like any description you type; a row with no description of its own is described by the name of its HomeXpense category); for each import, a fingerprint of the file, so we can recognise one you import twice, with how the sheet was laid out, the dates the import covered and three counts (rows added, updated and matched to rows you already had); for a sheet laid out a certain way, a one-way code made from its column headings, with the position of each column you chose; and for your own category and property names, a one-way code for each name with what you said it means, never the name itself. The file, its name, its column headings and the columns you do not use are never sent to us. A HomeXpense template you fill in and upload is the one exception: it is sent to our server to be read and is not kept once it has been read.
• Bills and receipts. When you add a bill or a receipt (a PDF, a scan or a photo), it is read on your device, in your browser, unless you choose to have it read by Microsoft (“Reading by Microsoft Azure Document Intelligence” below). We keep the payee, the amount, the due date (or the receipt’s date), the property and category you choose, whether each of them was read from the document or entered by you, and a fingerprint of the file with its page count, text length and which reader read it, so we can recognise a bill you add twice. We never keep the document, its file name, an account number or a service address.
• Property manager statements. When you add a property manager’s owner statement, it is read on your device, in your browser, unless you choose to have it read by Microsoft (below). We keep: the lines and figures you confirm (the period, the balances and totals, and each line you add, with its date, amount, description and category, and the property manager’s printed label for it, kept in the row’s notes); the property manager’s name; a fingerprint of the file with its page count, text length and which reader read it, so we can recognise a file you add twice; each unit’s rent and balance, stored under an irreversible code rather than the unit’s text or a tenant’s name; the year-to-date figures the statement prints, under each account’s name (such as “Rent received”, with any numbers and names in it removed); the manager’s labels you ask us to remember, with the category you chose for each; which bank lines settled which payout, and the bank descriptions we learn from deposits you confirm as that manager’s payouts; and your decisions on payout differences, with any note you type. We never keep the document, its text or its file name. We remove the names of tenants and other people we find from line descriptions before you review them, and you can edit any description before you add the statement.
• Scans and photos. If you add a scanned PDF or a photo, its words are read on your device, in your browser, by a text recognition (OCR) program that HomeXpense serves from its own site. This reading sends the file nowhere.
• Reading by Microsoft Azure Document Intelligence. For a bill, a receipt or a property manager’s statement, HomeXpense may offer “Read it again with Microsoft Azure Document Intelligence”, for example when a scan or a photo reads poorly or a statement’s figures do not add up. If you choose it for a document, and confirm, that one file is sent through our server to Microsoft Azure Document Intelligence, a document reading service, to be read. Nothing is sent unless you make that choice, each time, for that document. A photo is re-drawn on your device before it is sent, so the location and other details your camera stores in the picture file are not sent with it. We ask Microsoft to delete the file and its reading as soon as it is read; Microsoft deletes both within 24 hours in any case. We do not store the file or its text, and we keep only the figures you confirm. For each of these reads we keep a record of when it happened, what kind of document it was (a bill, a receipt or a statement), how many pages it had, how long it took and whether it worked, never its content. We use it to limit how many reads an account can make, and it is erased with your account.
• Booking platform payouts. When you import a booking platform’s payout file (such as Airbnb’s transaction history), it is read on your device, in your browser. We keep, for each payout you add: its date, amount and currency, any tax the platform withheld from it, and how much its lines and the amount paid differ; each line it records, with its date, amount, category, property and a fixed description such as “Short-term stay · Jun 2026”; the platform’s name with the currency, as the account the payouts belong to; a one-way code made from a one-way code of the payout’s reference or, when the file has none, from its date, its amount and one-way codes of its booking confirmation codes, so we can recognise a payout you add twice; for each listing, a one-way code made from its name, with the property you chose for it, never the listing’s name; and which bank lines settled which payout, with the bank descriptions we learn from deposits you confirm as that platform’s payouts. The file, its name, listing names, guest names, confirmation codes and the bank details in the file are never sent to us.
• Technical information. Cookies that keep you signed in, and standard server logs kept by our hosting providers (such as IP address, browser type and the pages requested), which are used for security and troubleshooting and kept for a short period.

We do not ask for or store your online banking username or password, and we do not collect payment card numbers.

• To provide HomeXpense: store your portfolio, calculate figures such as cash flow, equity and yields, and show them to you.
• To keep your account and data secure, and to prevent abuse.
• To answer your questions and requests.
• To meet our legal obligations.

We do not sell your personal information, we do not use it for advertising, and we do not use your data to train artificial intelligence models.

When you choose “Continue with Google”, we request only your basic profile (name, email address and profile picture). We use it solely to create your HomeXpense account, sign you in and show who is signed in. We do not access your Gmail, contacts, files or any other Google data, and we do not share information received from Google with anyone except the service providers listed below that host HomeXpense.

HomeXpense’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We share personal information only with the service providers that run HomeXpense for us, and only as needed to do so:

• Supabase — database and sign-in (servers in the United States).
• Resend — sends account emails such as sign-up confirmation and password reset (United States).
• Vercel — hosting of the web app (United States).
• Google — sign-in, if you choose it.
• Cloudflare — domain name service and forwarding of email sent to our support address.
• Microsoft — Azure Document Intelligence reads a document only when you choose to send it there (see “Reading by Microsoft Azure Document Intelligence” above).

We may also disclose information if the law requires it, or to protect the rights, safety or property of our users or others.

Your information is stored and processed in the United States. While it is there, it is subject to the laws of the United States, and may be accessible to courts and authorities there under those laws. Our service providers are bound to protect it and to use it only to provide their services to us.

We use only what HomeXpense needs to work: cookies that keep you signed in, a cookie that remembers whether the sidebar is open, your theme choice (light or dark) saved in your browser, and a host-only preference cookie (homexpense-hide-amounts) that remembers whether amounts are hidden in this browser on this host for one year. It is not tied to your account or shared with a third party. We do not use advertising or analytics cookies.

We keep the names of your properties with their country and state or province. We keep the description of each transaction you confirm, and the names of your property managers, lenders and bill payees, so we can recognise them next time; they stay until you delete them. The original text of a bank line is erased 90 days after you confirm or ignore it, and a line you never deal with is erased 180 days after upload. We never keep a document or its file name. We never take an account number or a tenant’s name from a document, and we never ask for one, or for a property’s street address: a property’s name is whatever you choose to call it. A name or number that appears in a bank line you confirm stays in that transaction’s description until you edit or delete it.

We keep your information for as long as your account exists. You can delete your account yourself on the account page; it deletes at once the portfolios you are the only owner of, with everything in them. If you ask us to delete your account, we delete your account and portfolio data within 30 days. Anything erased or deleted, by you or by us, stays in our encrypted backups until those backups expire, within a further 90 days.

You can ask us to give you access to the personal information we hold about you, to correct it, or to delete your account and data. You can also withdraw your consent to our handling of your information, which means closing your account. Email support@homexpense.com from the address on your account; we will respond within 30 days.

If you are not satisfied with our response, you can contact the Office of the Privacy Commissioner of Canada.

Information is encrypted in transit (HTTPS) and at rest by our providers, and database access rules ensure each account can see only its own data. No system is perfectly secure, so please use a strong, private sign-in and tell us at support@homexpense.com if you suspect a problem.

HomeXpense is intended for people aged 18 or older. We do not knowingly collect information from children.

We will update this policy before we change how we handle personal information — for example, before adding paid subscriptions or bank connections. The date at the top shows the latest version. If a change is significant, we will tell you in the app or by email before it takes effect. See also our Terms of Service.