Zarpia ("we", "us", "our") helps property owners collate and organise the documents and figures relevant to their tax obligations in Spain and Australia, and — through Zarpia Worldwide — helps Australian tax residents organise the income and gains from accounts they hold outside Australia. This policy explains what data we collect, why, and how we protect it.
What we collect
Account information: your email address and basic profile details when you sign up.
Property and financial data you provide directly: property addresses, expenses, income, and related figures you enter manually or that we extract from documents you upload.
Email content, if you connect Gmail or Outlook: read-only access to find and extract genuine invoices, receipts, and rental statements matching rules you configure yourself. If you run the optional sender scan, we read only the sender, subject line and date of emails from the last 12 months to suggest which senders look like bills or rental income. Only if you also choose the thorough scan, and only for that scan: where a property is still missing a regular document (for example home insurance or council rates), we search the last 3 years for matching emails with attachments and open a few of them (at most 30 per scan) to check whether that sender regularly sends a document for your property. Anything found is only a suggestion: nothing is collected from a sender unless you accept it. Zarpia works fully without either scan. We do not read your email for any other purpose, and we never send, delete, or modify anything in your mailbox.
Overseas account statements (Zarpia Worldwide, Australian tax residents only): bank, broker and bond statements you upload or forward to us, and the details we read from them — the institution, the account number or IBAN, the securities held, interest, dividends, distributions and coupons received, purchases and sales, and any foreign tax withheld. Statements from accounts held in Australia are outside Worldwide: where we can tell from the document itself, we decline them without sending them to our AI provider. We keep a copy of each statement we read, compressed to save space, so that you and your accountant can always see the source of every figure; it is stored privately, only you can open it, and it is deleted when you remove the statement or delete your account.
Inheritance and joint-ownership details you enter for Worldwide: a short label for each estate you inherited from (for example "Father"), the date of death and your share, and your ownership share of a joint account. We use these only to work out the cost base of inherited holdings and your share of joint income. Please enter them only where you are entitled to use that information for your own tax affairs.
Website usage statistics: when you visit zarpia.app we record which pages you view, which free tools you use, the website or campaign link that brought you, your country (worked out from your connection; we do not store your IP address) and whether you use a phone, tablet or computer. We use no cookies for this: a random visit number is kept in your browser only until you close the tab. If you create an account during that visit, we note on your account where the visit started (for example a search engine or one of our posts). We use these statistics only to understand which pages are useful and how people find Zarpia.
Advertising measurement (Google Ads): on the zarpia.app website (not in our Android or iOS apps) we use Google's advertising tag, which sets a cookie, to find out whether someone who clicked one of our Google ads went on to create an account. When a new account first opens its dashboard, the tag tells Google that a sign-up happened; it sends no page content, nothing you enter and nothing from your mailbox. We don't use it for remarketing or personalised ads. In the EU, UK and Switzerland the cookie is only used if you accept it in our cookie banner. Wherever you are, you can change your choice here:
Deadline reminders: if you ask one of our free tools to remind you about a deadline, we keep your email address and the deadline only to send those reminders. Nothing is sent until you confirm by email; you get at most two reminders, and every email has a link to stop them. We delete the address 30 days after the deadline, or after 7 days if you never confirm.
Payment information: handled entirely by Stripe, our payment processor. We never see or store your card details ourselves.
Your corrections to what we read: when you change the amount, date, category, property or supplier of a record our AI read for you, or delete one, we note what it had read, what you changed it to, the supplier and the type of document. This is how we find the kinds of documents our reading gets wrong. These notes are part of your account data and are deleted with it.
How we use your data
We use your data solely to provide the service: extracting and organising figures from your documents into a clear, structured record you can review and use however you need, maintaining your account, and keeping that reading reliable — for example by counting which suppliers' documents owners most often have to correct. We do not sell your data, and neither we nor Anthropic use it to train AI models. We only open one of your documents ourselves if you ask us to, or if you choose to share it with us as described below.
Sharing a document to help us fix a reading error
If you correct something our AI read wrongly, Zarpia may ask whether you're willing to share that document with us so we can fix how we read documents like it. This is entirely optional, you are asked about one document at a time, and nothing is shared unless you say yes.
If you agree to share a document:
Who sees it: only the Zarpia team (currently our founder) may open the document and your correction, to understand what went wrong. It is never shown to other owners or published.
How it's used: we keep a copy in a private test set, used only to check that changes to our reading work correctly. Those checks send the document to Anthropic under the same terms as normal reading — never used to train their models.
Hearing back: once the problem is fixed we may tell you, and offer to re-read the document. Nothing in your records changes unless you accept it.
How long and how to stop: we keep the copy for up to 24 months. You can withdraw your permission at any time in your account settings, or by emailing us; we then delete our copy within 30 days. Deleting your account deletes it too.
How we protect your data
Encryption at rest: OAuth tokens for connected mailboxes are encrypted using AES-256-GCM before storage, with the encryption key held separately from the database itself. All stored data is also encrypted at rest by our database provider.
Encryption in transit: all data is transmitted over HTTPS.
Data isolation: our database enforces row-level security, meaning your data is only ever accessible to your own authenticated account, enforced at the database layer, not just in application code.
Minimal access: our Gmail/Outlook integration requests read-only access — we cannot send, delete, or otherwise modify anything in your mailbox.
How we handle Google user data
If you choose to connect a Gmail account, Zarpia requests read-only access to your Gmail messages (the gmail.readonly scope). This section explains specifically what that access involves, separate from the general description above.
What we access: the content of email messages from senders you explicitly configure yourself (for example, your energy provider or property manager), and — only if you use Zarpia Worldwide — messages whose subject begins with "Investment" that you forward to your connected mailbox, together with their attachments. If you run the optional sender scan, we also read the sender, subject line and date of emails from the last 12 months; and only if you choose the thorough scan, we open a small number of emails with attachments (at most 30 per scan) that match a document one of your properties is missing, as described in "What we collect" above. We never access any other messages.
Why we access it and how we use it: to identify genuine invoices, receipts, and rental income statements matching your configured senders, and the overseas account statements you forward for Worldwide, and to extract structured figures (amounts, dates, suppliers, securities) from them into your Zarpia account. We do not use this data for any other purpose, including advertising.
Who we share it with: the content of matching messages is sent to Anthropic, our AI extraction provider, solely to extract the figures described above from that specific message, or to check what a scanned email is — never for any other purpose, and never to train Anthropic's models on your data. We do not otherwise share, sell, or transfer your Gmail content to any other third party.
How it's protected: your Gmail OAuth tokens are encrypted at rest using AES-256-GCM before storage (see "How we protect your data" above); the connection is strictly read-only — Zarpia cannot send, delete, or modify anything in your mailbox; and you can disconnect Gmail access at any time from your account settings, which immediately revokes Zarpia's access.
Zarpia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. No person at Zarpia reads your email content, except a specific document you have chosen to share with us (see "Sharing a document to help us fix a reading error" above), or where necessary for security or to comply with the law.
Our mobile apps (Android and iOS)
This section applies specifically to the Zarpia Android and iOS apps, in addition to everything above — each app is a native wrapper around the same Zarpia service described throughout this policy, not a separate product with its own data handling.
Sign-in: the apps use the same Google, Microsoft and (on iOS) Apple sign-in, or a one-time email code, through your device's native account picker rather than a web browser. From Apple we receive only your name and the email address you choose to share (which may be an Apple private relay address). No additional data is collected beyond what's described in "How we handle Google user data."
Biometric unlock: the apps ask for your device's fingerprint, face or passcode check before showing your data. That check is performed entirely by your device's operating system — Zarpia only receives a pass/fail result and never receives or stores any biometric data.
Payments: the app opens Stripe checkout in your device's own browser, not inside the app itself — the Zarpia app never handles your payment details directly.
Files on your device: when you download or view a report, the app saves that file to your device's local storage so you can access it, and can share it through another app (for example, email or a file manager) if you choose to use your device's native share feature. These files stay under your control on your own device, like any other download.
Permissions: the app requests network access only — it does not access your camera, microphone, contacts, precise location, or advertising identifier.
Data retention
We keep your data for as long as your account is active. Zarpia is designed to work as your long-term document archive, not a temporary processing tool — some of the figures Zarpia tracks are only useful because they cover many years, in some cases decades. We do not automatically delete your documents or data based on their age, and we do not currently delete accounts or data due to inactivity.
You control deletion, not us. You may request permanent deletion of your account and all associated data at any time, from your account settings. Once requested, your data is retained for a further 14 days — in case you change your mind or want to export a copy first — after which it is permanently removed from our systems. We recommend exporting a copy of your data before requesting deletion if you may need it later, since deletion cannot be undone.
As the property owner, you remain responsible for retaining your own records for as long as required under the law that applies to you, which can vary depending on your circumstances. This is your own legal obligation, and continues regardless of whether or how long you keep using Zarpia.
Third parties we work with
Supabase — our database and authentication provider.
Vercel and Railway — host the Zarpia website and the background service that reads your documents.
Stripe — our payment processor.
Anthropic — powers the AI extraction of figures from documents and statements you provide.
Google, Microsoft and Apple — if you choose to sign in with them, or to connect Gmail or Outlook.
Google Ads — measures whether our ads lead to sign-ups, as described above. Nothing from your mailbox or your Zarpia data is ever shared with it.
Public market and exchange-rate data — we look up published Reserve Bank of Australia exchange rates, and for inherited securities the published closing price (for example from Borsa Italiana). Only the security identifier (ISIN) and date are sent; no personal data.
Each of these providers has its own privacy policy governing how they handle data on our behalf.
Your rights
If you're in the EU or UK, you have rights under GDPR including access, correction, deletion, and data portability. If you're in Australia, similar rights apply under the Privacy Act 1988 and the Australian Privacy Principles, including access to and correction of your personal information. Wherever you're based, you can exercise most of these rights directly from your account settings — exporting or deleting your data — or contact us using the details below for anything else.