Document · draft

Privacy policy

Version of October 18, 2026. Describes Evensies version 1.0. This is a translation; the Polish version prevails.

1. In short

  • Evensies is for sharing the costs of trips. We only process the data needed for that.
  • No ads, no tracking, no analytics, no selling of data. The app doesn’t send crash reports.
  • The sync server, database, receipt photos, backups, email and this website all run on one server in the European Union, operated by the app’s publisher.
  • You don’t need an account. The app runs on an anonymous device identity; you only give us an email address if you choose to sign in.
  • You can download your data, export a trip (CSV, JSON) and delete your account at any time — in the app or at evensies.com/delete-account.

2. Data controller

The data controller is the publisher of the Evensies app: Special services Sebastian Drożdż, to be completed: address, tax ID (NIP) to be completed.

For anything about your personal data, write to hello@evensies.com — in English or Polish.

3. What data, why and for how long

We process data to perform the contract for using the app (Art. 6(1)(b) GDPR), for our legitimate interest in keeping the service secure and running (Art. 6(1)(f)), and to meet legal obligations, such as handling complaints (Art. 6(1)(c)). We don’t rely on consent, because we don’t collect anything beyond what the service needs to work.

DataPurposeBasisRetention
Trip content: names, amounts, members, people, notes, display namerunning the appcontractuntil the trip is deleted; a trip with no users left — 90 days
Receipt photosrunning the appcontractas the trip; a photo removed from an entry — 30 days
Payment details (e.g. account number, BLIK phone number)helping you settle upcontractuntil changed or removed; deleted with the account
Email address (only if you sign in)account, sign-in codes, account messagescontractuntil the account is deleted
Sessions and devices: device name and platform, app version, last usedsign-in, device list; security and abuse prevention (recognizing a signed-out installation and refusing it access)contract; security — legitimate interestsaccount sessions: until sign-out, account deletion or 400 days of inactivity; guest sessions: until the guest is deleted (24 months without activity); revoked sessions and device data: 30 days — with the caveat below
In-app notifications (e.g. new entries, payments marked as paid, reminders — with names of people in the trip)telling you about changes in your tripscontract90 days after the notification last changed; sooner if the trip or account is deleted
Trip change historytransparency and restoringcontractfor the life of the trip
IP addresssecurity, rate limitslegitimate interestscounters 24 hours; app and website logs — to be completed (goal: 7 days, section 9)
Trace of a permanently deleted triptelling former members the trip was deletedlegitimate interestslist of former members 180 days; the trip ID with dates, without personal data — indefinitely
“Download my data” packageaccess to and portability of your datalegal obligation72 hours after it’s prepared
Email sending queue (recipient address, sign-in code)delivering messagescontractthe address and code are removed from the queue right after sending
Mail server log (recipient address, delivery time and result)delivering email, detecting abuselegitimate intereststo be completed (goal: 7 days, section 9)
Backupsdisaster recoverylegitimate interests35 days

Caveat about sessions. Thirty days after a session is revoked, we delete its token, device name and app version. If changes to trips were sent from that device, an empty technical row with the session ID and platform (iPhone, Android or browser) remains, because the stored changes point to it. That row can’t be used to sign in and contains no device name or app version. It stays linked to the account, and the retained hash of the installation key lets the server recognize that old installation and refuse it access.

Providing data is voluntary. Without an email address you can’t create an account, but you can use the app as a guest. We don’t make automated decisions or profile you.

4. Data others enter about you

A trip is shared. Whoever creates or runs it may enter your name or your family’s name, the expenses you take part in, amounts and — if you let them (terms, section 5) — your payment details. So the source of this data is the trip’s members. Everyone in the trip can see it, and we process it so the trip can be settled (Art. 14 GDPR). You have the same rights over it as over data you enter yourself — ask the trip admin to change it, or write to us.

If your access to a trip is removed, the app deletes that trip’s data from your device at the next sync. Copies made earlier — for example while a device was offline — can’t be recalled remotely.

5. Where data lives and who processes it

  • Server. The sync server (api.evensies.com), database, receipt photos, backups and this website run on one server in the European Union, operated by the publisher. We rent the server from Hostinger, which provides the infrastructure as our processor. The data center is in the European Union: to be completed: country.
  • Email. Emails (sign-in codes, new-device sign-in alerts, account deletion confirmations, data package links) are sent by a mail server on the same machine, from no-reply@evensies.com. We don’t use outside email delivery companies. The message goes to your own email provider.
  • Exchange rates. The server itself downloads the European Central Bank and National Bank of Poland rate tables and fills gaps with the Frankfurter service running on the same machine. No user data leaves the server when rates are fetched.
  • App stores. You download the app from the App Store (Apple) or Google Play (Google). These stores process data under their own terms, as separate controllers.

We don’t use analytics, advertising, crash reporting or content delivery networks. We don’t transfer data outside the European Economic Area. Backups are currently kept only on the same server. Before any data goes to a new recipient — for example a backup with another provider or a notification service — we’ll update this policy.

Evensies doesn’t receive, hold or send money and doesn’t connect to banks. Payment buttons open your bank or payment app — what happens there is governed by that provider’s terms.

6. Invite links

An invitation looks like this: evensies.com/j#code. The code comes after the # sign, and browsers never send that part of an address to any server — so it doesn’t end up in logs or the Referer header. That’s why link previews in messengers are generic and don’t show the trip name.

Anyone with the link can join the trip. The trip admin can renew or disable the link and remove access.

7. Device storage and cookies

The app stores trips on your device so it works offline. On iOS and Android this storage is encrypted, and the session token is kept in the system key store (Keychain, Keystore). The web app (app.evensies.com) stores trips in browser storage and uses one strictly necessary session cookie from our server. We don’t use advertising or analytics cookies, so there is no consent banner.

8. Your rights

You have the right to access, rectify and erase your data, to restrict processing, to data portability, and to object to processing based on legitimate interests. You can exercise most of them yourself in the app:

  • access and portability — Account → “Download my data”: a JSON package with your account data, devices, memberships and the payment details you added (with an account, the link arrives by email); download a whole trip in its settings: Export → “Full copy (JSON)” or CSV;
  • rectification — correct your name, entries and payment details directly in the app;
  • erasure — Account → “Delete account,” or without an account: “Delete my data”; you can also delete your account at evensies.com/delete-account: enter your account’s address, type the code from your email and confirm.

For your other rights, including objection and restriction, write to hello@evensies.com. We’ll reply within one month.

When you delete your account:

  • its sessions, email address, payment details and the receipt photos added from it are removed right away;
  • entries in shared trips stay, to the extent the other members need them to settle up, signed as “Deleted user”;
  • trips with no other users are deleted;
  • backups containing this data expire within 35 days.

You can also lodge a complaint with a supervisory authority — in Poland, the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw.

9. Security

Connections are encrypted (TLS). Session tokens and sign-in codes are stored only as hashes, and invite codes are encrypted with a separate key. Backups are accessible only to the service account on the server and contain no encryption keys. Application logs contain no trip content, codes or payment details, and record email addresses only as hashes. The exception is the mail server log: like any mail server, it records the recipient address and the delivery result. Retention of the server’s technical logs — app, website and mail server: to be completed; our goal is 7 days. If a personal data breach occurs, we’ll notify the President of UODO within 72 hours and, if it is likely to seriously affect your rights, tell you without undue delay.

To report a security vulnerability, follow the rules in our terms (also in security.txt).

10. Children

Evensies is a general-audience app, not intended for children. Adults can add children as people in a family to split costs fairly. Names are optional — “Child 1” is enough.

11. This website

evensies.com uses no cookies, no analytics and no third-party scripts, and loads nothing from other servers. The exception is the account deletion page: it connects only to our own server (api.evensies.com), receives one strictly necessary session cookie from it and keeps only a security token for that session in the browser, until the account is deleted. The website runs on the same server as the app. The server records the IP address and the requested page in technical logs to protect the site from abuse; retention of these logs: to be completed (goal: 7 days, section 9).

12. Changes and contact

We’ll announce significant changes to this policy in the app before they take effect. Push notifications, Evensies Plus and AI receipt reading will come in later versions — we’ll describe them here before they go live. Privacy questions: hello@evensies.com.