Privacy policy
This is a working translation. The Polish version is the reference text.
compa:mio is a phone app for settling shared expenses on trips, in shared flats and at parties. Below we describe what data we collect, why, and how you can delete it.
Who is responsible for the data
For now the data controller is a private person, Damian, the organiser of the app test (the company that is to run the app does not exist yet). Once it is set up we will change the controller in this document and tell you in the app.
Contact: hello@compamio.app.
What data we collect
| Data | Who provides it | Why |
|---|---|---|
| Email address | the event organiser (types it in, or their Google account passes it on when signing in with Google) | signing in to the app |
| Name from the Google account profile | Google, only when the organiser signs in with Google | recognising the organiser's account |
| Participants' first names | the organiser, and guests where needed | showing who paid for what and who owes whom |
| Expenses: amounts, currencies, rates, descriptions, categories, event name | event participants | calculating the settlement |
| Receipt photos | participants, if they want to attach a photo to an expense | proof of the expense in the event |
| BLIK phone number or bank account number | a participant, voluntarily | showing others where to send what they owe |
| Anonymous guest identifier | the app creates it when someone joins with a code | recognising a guest in the event without an account |
We do not collect location, phone contacts, advertising ID or data for ads. The app contains no ads and no marketing analytics.
Where the data is stored
Data goes to the Supabase service, on servers in the European Union (Frankfurt, Germany). Supabase processes it only on our behalf. The connection to the server is encrypted (HTTPS). Only the participants of an event can access its data, which is enforced by the database (row-level security).
The app also works offline: data is saved on the phone first and synced to the server when the phone is online.
Artificial intelligence and receipts
We do not send expense descriptions or participants' data to external artificial intelligence services. A receipt photo goes to such a service only in the single optional case described below.
Reading the amount from a receipt works only on the phone (Google ML Kit library, offline mode). The photo is not sent anywhere for recognition. The ML Kit library may send Google technical diagnostic data about how the library works (e.g. version, error codes), without photo content or recognised text.
Optional, more accurate receipt reading (AI)
This feature is off by default. Only the app administrator can turn it on for an event, with a cost limit per event and per person. When it is on, a participant can tap “Read more accurately (AI)”. On first use on a given phone we show a notice and ask for consent; without consent nothing is sent.
- Recipient: Anthropic (USA), provider of the Claude model; the photo reaches it through a function of our server in Supabase (EU). The photo is sent outside the European Economic Area.
- Purpose: only reading the amount, currency, date, shop name and expense category from the receipt. The result is just a suggestion that the user confirms with “Use”.
- What we send: only the receipt photo chosen by the user. We do not send expense descriptions, participants' names or other event data.
- What we store ourselves: only a usage log (event, account, time, number of tokens, cost). It contains neither the photo nor the recognised text.
- Model training: under Anthropic's rules for commercial products (API), API data is not used to train models by default. Anthropic's terms may change; the provider's rules apply.
Reading on the phone (ML Kit) works independently and still sends nothing.
Signing in with Google
The organiser can sign in with a Google account (“Continue with Google”). Sign-in happens in the Android system window; Google passes us the account's name and email address, and we store them in the organiser's account in Supabase (EU). The app has no access to your contacts, mail or other Google account data and sends nothing beyond the Google sign-in itself. Google sign-in is optional: you can use email and password. Guests joining with a code do not sign in with Google and have no account.
The guest page in the browser
A person without the app (e.g. with an iPhone) can join an event on the compa:mio web page in the browser (a link with an invite code). The page uses the same data and access rules as the app: it creates an anonymous session without an account, and in browser storage it keeps only that session and the chosen language. We use no tracking cookies, no analytics and no third-party scripts. The invite code is in the address after the # sign, so the browser does not send it to the page server. The page runs on Cloudflare Pages hosting; like any web server, the host records the IP address, time of visit and browser type in technical logs (for security, for a short period set by the provider). Event data (name, expenses, settlements, payment details) is stored in Supabase in the EU, as for the app. compa:mio never asks for a BLIK code or a bank password.
Who we share data with
No one except the participants of the given event, who see its expenses and settlements, and the hosting provider (Supabase), which acts as a processor. Google, as the sign-in provider, knows that you sign in to compa:mio but receives no data about events or expenses from us. The exception is the optional AI receipt reading (Anthropic, USA), described above, which needs your consent. We do not sell data and do not pass it on for advertising.
How long we keep data
Until the event or account is deleted or the app test ends, whichever comes first. Detailed periods:
- 30-day trash: a deleted expense, repayment or a whole event does not disappear at once. For 30 days it can be restored (an expense or repayment by its author or the organiser, an event by the organiser), and participants can see in the trash who deleted an entry and when. After 30 days we delete it permanently from the database together with the receipt photo.
- Receipt photos in the cloud: 12 months after the event ends (it is locked or its last expense). Then we delete them from our server; the photo stays only on the phone of the person who took it. Expenses, amounts and balances stay unchanged, and the app tells you at the receipt that the photo is no longer in the cloud.
- Photo files that no longer belong to any existing event or expense are deleted from the server.
Deleting data and your rights
- The organiser can delete an event in the app, with its expenses and photos. A deleted event can be restored for 30 days; after that it is permanently deleted, including receipt photos in the cloud.
- You can delete your account right away in the app: ⋮ menu › Settings › Delete account. We delete the account and the payment details. Events you organise are taken over by a person with an account whom you choose; if nobody else has an account, the event goes to the trash and is permanently deleted with its photos after 30 days. Your name and entries stay in the events, unlinked from any account. Details: the “Delete account” page.
- To delete an account without the app, delete guest data or get a copy of your data, write to hello@compamio.app. We will reply within 30 days.
- You have the right of access, rectification, erasure, restriction of processing, data portability and objection. You can also lodge a complaint with the President of the Polish Personal Data Protection Office (uodo.gov.pl) or your local data protection authority.
The legal basis is providing the app that you install and use yourself (Art. 6(1)(b) GDPR), and, for voluntarily given phone and account numbers, your consent (Art. 6(1)(a) GDPR).
Changes
When we change the scope of collected data or the controller, we will update this document and the date at the top.