Privacy policy

Effective from 18 October 2026 · version 7

Omni (omni.contact) helps groups settle matters: someone asks, the others answer, and in the end there is a settled result. To make that work, we process some of your data. Below we explain in plain words what data that is, why we use it, who can see it, who we share it with and how you can delete it.

In short

We collect what Omni needs to work: the name you enter, the content of conversations, cards and votes, and an email address if you give one or choose to sign in with Google.
We do not sell data or show ads, and we do not store cookies in your browser.
We do not track what you do in the app: we do not record your screen, do not store the order of your clicks and do not use third-party analytics tools. We receive numbers about which screens you use only if you turn on the “Help improve Omni” switch (it is off by default).
Messages are visible to the people in the conversation you belong to. A person with a link to a single card sees only that card.
Messages are not end-to-end encrypted. Day to day, we see only identifiers, dates, numbers and states in the database. Only the owner of Omni, in person, can see content, and only for a reported problem, your request or abuse; every such look is recorded in a register (section 10).
We do not use artificial intelligence to process your messages or letters (section 6).
You can ask for access to your data or for it to be corrected. Write to contact@omni.contact. You can delete your account yourself in the app: You, “Delete account”.

1. Who is responsible for your data

The controller of your data is FUTURE PROOF spółka z ograniczoną odpowiedzialnością (a Polish limited liability company), registered office: ul. Wielicka 40/U1, 02-657 Warsaw, Poland, entered in the National Court Register (KRS) under number 0000996785, tax ID (NIP) 5213987731, REGON 523388798. We run Omni, a messenger available at app.omni.contact.

For personal data matters write to contact@omni.contact.

2. What data we process and why

We give legal bases according to the GDPR (Regulation 2016/679). Article 6(1)(a) is your consent, which you can withdraw at any time. Point (b) means performance of a contract, that is, providing you with the service. Point (f) is our legitimate interest.

Account and entering Omni

Data: The name you enter on joining. Language. For accounts created before 5 October 2026, the date of the earlier AI consent also remains (for AI features we have switched off). A technical account identifier. An email address, if you give one (so that you can return from another device, receive a login code and get reminders about matters). The version number of the Terms of Service and the date you accepted them. Your “Away until…” date, if you set one. Whether you want reminders by email.
Why: To create your account, recognise you on later visits and show your name to the people in a conversation. We record the version and date of the Terms of Service acceptance with your account, so that we know who accepted which version. Email reminders about “silence means yes” matters are on by default; you can turn them off in “You”. Only you set your away date: until that day, your silence in “silence means yes” matters does not count as agreement.
Basis: Article 6(1)(b) GDPR (a contract for the provision of an electronic service, whose terms are set out in the Terms of Service).

Conversations, matters and votes

Data: The text of messages, topics, reactions, attachments and voice messages. Questions in cards, their options, amounts and deadlines. Your answers and votes (with your name) and votes you pass on. Who has read a conversation and when (the “Seen by” line). A trace of reminders about a matter: when a reminder appeared in the app, when an email reminder was accepted for sending and whether sending failed (without content and without an address).
Why: To make conversations, cards, voting, passing your vote and the Ledger of settled matters work. In “silence means yes” matters, silence counts as agreement only when we have proof that a reminder reached you: an email reminder accepted for sending, a visit to Omni after a reminder or reading the card. Without such proof the matter goes back to its author.
Basis: Article 6(1)(b) GDPR.

Mail in Omni (an imie@omni.contact address)

Data: The name of the address you create. Letters that arrive there, including ones forwarded from another mailbox: the sender’s address and name, subject, body, attachments. We store only the text of a letter, without images from other servers; we do not store program or script files (for example .exe) at all. We recognise automatic replies (“out of office”) by the letter’s headers. Your “Mark as spam” and “Not spam” decisions and blocked senders.
Why: To deliver letters to the “Mail” conversation, let you reply and remember your decisions about senders (spam, blocking).
Basis: Towards the owner of the address: Article 6(1)(b). Towards people who write to such an address: point (f) (handling the addressee’s mail and protecting the mailbox from abuse: letter limits and sender blocking).

People outside Omni who are sent an email from Omni

Data: Email address, name (if someone entered it), the text of the email, the recipient’s reply and the facts that they opted out of such emails, that an email bounced or that it was reported as unwanted. We receive the address from the person who writes to you from Omni: they send a question, a settled result or an invitation.
Why: To deliver an email someone wanted to send you and to respect your opt-out. Every such email contains an unsubscribe link; once you click it we keep your address on a suppression list so that nobody can send you another email from Omni.
Basis: Article 6(1)(f) GDPR (delivering an email the sender wanted to send you).

Guests (people with a link to a card)

Data: The name entered when voting and the vote itself.
Why: To accept the vote and show it to the people in the project (section 3).
Basis: Article 6(1)(f) GDPR (letting you answer a card you were invited to by link).

Security and abuse prevention

Data: IP address and time of failed login attempts (for example a wrong code). Technical logs kept by our providers: IP address, time, type of request. Numbers of emails sent, bounces and complaints in the last hour and day, counted from the records described in the article on people outside Omni.
Why: To protect Omni from code guessing and abuse, and to fix outages. When someone reports an email from Omni as unwanted or emails bounce too often, Omni itself pauses sending cards and invitations to people outside Omni. An account that sent an email reported as unwanted, or from which three emails bounced within a week, cannot send cards or invitations to people outside Omni until we have looked into it. When we have sent 800 emails within a day, emails that can wait (cards, invitations and reminders) wait, while login codes still go out.
Basis: Article 6(1)(f) GDPR.

Aggregate statistics

Data: Numbers calculated in the database from the data described above, for example how many accounts were created in a given week, how many matters were settled and how many people used Omni. Test accounts are left out of these numbers. To count openings of card links without repeats, we keep a hash of the link (a string from which the link cannot be recovered) for a few days (at most 5), without the person and without an IP address. From Cloudflare we fetch daily totals of traffic to Omni’s pages: the number of requests, page views, an approximate number of distinct visitors and the number of blocked threats, without IP addresses and without people. The number of visits to the page omni.contact/en/from-a-card, which the prompt under a card sent from Omni links to, we read from Cloudflare’s server statistics for that address: that is how we know how many people came from a card. It is only a count of visits to that address: we leave nothing on your device and do not link it to people.
Why: To know whether Omni works and who finds it useful, and to decide what to improve. The Omni owner’s dashboard shows only numbers: no names, content or addresses. It does not show numbers about a group of fewer than 10 people (it only says that such a group exists), except for totals across everyone in the beta.
Basis: Article 6(1)(f) GDPR (running and developing the service).

“Help improve Omni” (only if you turn it on)

Data: The switch is in “You” and is off by default. When you turn it on, the app counts on your device how many times each screen was opened and a few actions from a public list were taken on a given day. It stores numbers only, with no order, no times and no content. Once a day it sends us the numbers for completed days and deletes them from the device. The database adds them to shared daily totals for everyone and does not store the package itself anywhere. So that one day is not counted twice, for 7 days we remember only that numbers for a given day came from a given account.
Counted: Visits to screens: Chats, Waiting, Chat, Matter, Write, Sent, Ended, Drafts, Deleted, To read, Mail, New senders, People, Ledger and You. Actions: card with a matter sent, answer to a card (after the time to undo it has passed), message sent, search used, invitation sent by email or a new invitation link, vote delegated, decision recorded. The app shows the same list next to the switch.
Why: To see which parts of Omni people really use, and to improve what is difficult or unused. The panel shows the numbers for a given day only when at least 10 people sent them. For a day when fewer people sent them, it shows only how many people that was, and its numbers are not added to totals for longer periods.
Basis: Article 6(1)(a) GDPR (your consent) and Article 399 of the Polish Electronic Communications Law (storing counters on your device with consent). Turning the switch on is your consent; we remember it only on that device. You can turn it off at any time in “You”, and any numbers not yet sent are then deleted.

Invitation requests on omni.contact

Data: Your email address, the few sentences about yourself you type in (who you are and why you want to use or test Omni), the page language and the time of sending.
Why: To decide on inviting you to Omni and to reply by email. We don’t send newsletters or ads to this address.
Basis: Article 6(1)(b) GDPR (steps taken at your request before entering into a contract).

Problem reports and error reports

Data: When you send “Report a problem” in “You”: the description you type in. When you choose “Send report” after an app error: the error message. In both cases, technical data: the app version, the screen name, the page address in the app with link codes hidden, the browser family and system (for example “Safari, iOS”), the language and whether the report was sent from an account with an email address (only yes or no, without saying which one). Before sending, the app shows which technical data it attaches. We do not attach your name, email address, account identifier or the content of conversations.
Why: To find and fix bugs. A report is anonymous, so we cannot reply to it; if you want a reply, write to contact@omni.contact. Please do not paste the content of conversations into the description.
Basis: Article 6(1)(f) GDPR (fixing errors in the service).

Contacting us

Data: Your email address and the text of your message to us.
Why: To reply and resolve your matter.
Basis: Article 6(1)(f) GDPR.

3. Who can see your data in Omni

People in a conversation see your name, your messages, reactions and votes (with your name), and who has read the conversation. People you share a conversation with also see your “Away until…” date, if you set one.
A guest sees only the card they were given a link to. Their name and vote are visible to the people in the project.
A person outside the project who was given someone’s vote on a single matter sees only that one matter: the question, the amount and the votes with names. They do not see the rest of the project.
The email address of a person outside Omni who was sent a question or an invitation is seen only by the author who sent it. Other members of the project see their name and the note “outside Omni”.
If the author of an invitation sent by email has an address in Omni Mail (imie@omni.contact), the invited person sees that address, because their reply goes to a conversation with the author.
We do not show the email address of your account to other people.
Mail in Omni is visible only to the owner of the address.
The owner of Omni sees only aggregate numbers in the dashboard, without names, content or addresses. They can see content only in exceptional situations, and every such look is recorded in a register (section 10).

4. Who we share data with

We use several providers. The first two process data on our behalf, only to provide us with their services.

Supabase Inc. (USA): Database, login, file storage and server functions. The data sits in a data centre in Frankfurt (EU). Supabase’s data processing agreement contains the European Commission’s standard contractual clauses.
Cloudflare, Inc. (USA): Serves the app, runs the omni.contact domain, receives mail for imie@omni.contact addresses and sends emails from Omni: login codes, cards with questions, invitations and reminders. All requests to the app pass through its network. It also counts daily traffic totals for us, which we fetch without IP addresses and without people (section 2, “Aggregate statistics”). Cloudflare is certified under the EU-U.S. Data Privacy Framework and uses standard contractual clauses.
Google (only if you choose “Continue with Google”): See section 5.
UptimeRobot s. r. o. (Bratislava, Slovakia): Every few minutes it checks whether Omni is up, that is whether its addresses respond: the app, the omni.contact site and the database’s check address, which answers only “working” or with one sentence about an outage. It receives no data about the people who use Omni.
Anthropic PBC (USA): An AI programming assistant (Claude) used when working on Omni’s code; it sees only a view of the database without content (identifiers, dates, numbers, states).

We do not share data with advertisers or data brokers. We may disclose it to public authorities if the law requires.

5. Signing in with Google

If you choose “Continue with Google”, Google passes to Omni the email address of your Google account, your name and the address of your profile picture. We do not ask for access to your Gmail, contacts, calendar, files or any other data in your Google account.

We use this data only to create your Omni account or sign you in to it, so that you can return to your conversations from any device. We do not display the Google picture in Omni; its address is stored only by the login system (Supabase). We do not use this data for advertising, do not sell it, do not share it with anyone other than the providers in section 4 and do not train artificial intelligence models on it.

We keep the Google data for as long as your Omni account exists. You can revoke access in your Google account settings (myaccount.google.com/permissions); your Omni account remains until we delete it at your request.

Omni’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

6. Artificial intelligence

Omni does not pass the content of conversations or letters to any external artificial intelligence model. We removed the former “Count this as…” suggestions and switched off automatic spam rating in Mail on 4 October 2026. You always cast your vote yourself, with a button, and you mark spam by hand.

This also applies to fixing bugs: when a problem is reported, the content of conversations and letters can be seen only by a human, the owner of Omni, and not by any program or artificial intelligence model (section 10). An AI programming assistant (Claude, by Anthropic; section 4) helps us work on Omni’s code, but it sees only a view of the database without content.

If we ever introduce an artificial intelligence feature in the app that processes the content of conversations or letters, we will first change this policy and sign a data processing agreement with the provider, and we will ask for your consent where the law requires it.

7. How long we keep data

Account, conversations, matters and votes: as long as you have an account. When you delete your account, personal data and Mail are removed, while settled matters, messages and votes stay without your name (see below).
Your away date: as long as you have an account. The trace of reminders about a matter: as long as the card or your account exists.
Letters in Mail, including ones from people outside Omni, and their attachments: until deleted by the user, that is the owner of the address, or until the account is deleted. A deleted letter from a person outside Omni, or a conversation with them, first goes to “Deleted”: it can be restored for 30 days, after which it disappears for good together with its attachments. You can also ask us to delete a letter.
A deleted message: its text is erased immediately and a trace remains that a message existed. Attachments of a deleted message are erased from file storage together with it.
Leaving a conversation ends your participation, but your earlier messages stay in it for the other people until you delete them or ask us to.
Failed login attempts (IP address and time): about a day.
An address that opted out of emails from Omni, or to which emails bounced twice or an email was reported as unwanted: on the suppression list for as long as we run Omni, so that an unwanted email is not sent again. The record of the bounce or complaint (address, time, sender’s account) is kept for as long.
Aggregate statistics and daily totals from “Help improve Omni”: without a time limit, because they are numbers only and cannot be linked to a person. Hashes of opened links: at most 5 days. The note that numbers for a given day came from a given account: 7 days. Numbers on your device: until sent, at most a few days, or until you turn the switch off.
Problem reports and error reports: 12 months from sending, then we delete them automatically.
The register of looks at content (section 10): for as long as we run Omni, so that every look can be checked.
We make database backups to restore the service after an outage. Deleted data may remain in backups for some time.
Invitation request: until we decide on the invitation and for at most 12 months after that, or shorter if you ask us to delete it.
Correspondence with us: until the matter is resolved.
Technical logs kept by providers: according to their rules.

8. Your rights

You have the right to access your data and receive a copy, to have it corrected, deleted, restricted and ported. You can object to processing based on our legitimate interest. You can withdraw your consent to “Help improve Omni” at any time by turning off the switch in “You”; this does not affect the lawfulness of what was sent before. Numbers already added to the daily totals cannot be separated out, because they are not linked to any person.

Write to contact@omni.contact. We reply without undue delay and at the latest within a month.

In the app you can delete your own message, leave a conversation, mark the sender of a letter as spam, turn off email reminders and delete your account (You, “Delete account”). When you delete your account we delete your name, email address, sign-in data, your Mail address with its letters and attachments, reminders and their trace. Settled matters, your messages (with attachments) and votes stay in conversations and Ledgers without your name, as “Deleted person”, because other people need them; your open matters are closed. If you want us to delete your messages too, write to contact@omni.contact and we will delete them on request.

Giving your name is a condition of entering Omni. Your email address is optional.

We do not make decisions about you based solely on automated processing that would have legal effects or similarly significantly affect you. The “silence means yes” rule in a matter is chosen by its author and is shown on the card. Silence counts as agreement only once a reminder has reached you, and never while you are away by your own setting.

If you believe we process data unlawfully, you can lodge a complaint with the President of the Personal Data Protection Office in Poland (ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl) or with the data protection authority in your country.

9. Browser storage instead of cookies

Omni does not store cookies, does not show ads, does not use third-party analytics tools and does not load scripts or fonts from other servers. To work, the app saves essentials in your browser’s storage (localStorage and sessionStorage): your login session, your language and appearance, the conversation you opened last, messages waiting to be sent (when there is no connection), which notifications were already shown, the fact that the request for an email was dismissed, the page to return to after signing in with Google, a trace of a matter made from a letter, and which cards you left unanswered. They are used only to run the app. If you turn on “Help improve Omni”, the app also stores there the state of the switch, the numbers for days not yet sent and the time of the last sending attempt (section 2). You can remove all of this by clearing the site’s data in your browser; Omni will then sign you out and the switch will go back to off.

10. Security

Connections to Omni are encrypted (HTTPS). The database makes sure each person sees only the conversations they belong to. The number of login attempts is limited. Messages are not end-to-end encrypted, so we also limit our own access to the database.

Day to day, to keep Omni running, we use a view of the database that shows only identifiers, dates, numbers and states, without content, names or addresses. When working on Omni’s code we are helped by an AI programming assistant (Claude, by Anthropic). It uses only this view, so it sees identifiers, dates, numbers and states, never content, names or addresses, and it has no access that opens them. Content, names and addresses are opened by a separate access that only the owner of Omni uses, in person, and only to fix a reported bug, answer your request or investigate abuse. Every such look is recorded in a register: when, why and which query was run. The owner of Omni sees the register in the dashboard. That access cannot change or delete the record, and the view expires after an hour. No artificial intelligence model reads the content of conversations or letters.

11. Changes to this policy

When we change the policy, we will also change the date and version number at the top of the page. We will tell you about significant changes in Omni: the first time you open it after a change, we will show a bar with a link to a description of the changes. A change to the policy does not require you to accept it again. For new kinds of data that need your consent, we will ask separately, and without it we do not collect them.

Version 2 (5 October 2026): we removed the description of artificial intelligence features and of the provider TypeSafe, because Omni no longer uses them, and the AI consent from the sign-in screen.

Version 3 (6 October 2026): we added invitation requests from omni.contact (sections 2 and 7).

Version 4 (7 October 2026): we described that a person outside the project who was given a vote sees only one matter, and that the email address of a person outside Omni is seen only by the author of the question or invitation sent to them (section 3). We added the recording of the version and date of the Terms of Service acceptance (section 2). We changed the contact address to contact@omni.contact.

Version 5 (9 October 2026): we described that letters in Mail, including ones from people outside Omni, and their attachments are kept until deleted by the user, that attachments of a deleted message are erased together with it, and that we record bounces and complaints about emails sent from Omni (sections 3 and 7).

Version 6 (13 October 2026): emails from Omni, that is login codes, cards with questions and invitations, are now sent by Cloudflare instead of Amazon Web Services; Amazon no longer processes any Omni data (section 4).

Version 7 (18 October 2026): we added aggregate statistics, the “Help improve Omni” switch (by consent only, off by default) and problem and error reports (section 2). We described email reminders and when silence counts as agreement, “Away until…”, “Deleted” with erasure after 30 days, pausing sending after bounces and complaints, and what we store from letters from people outside Omni (sections 2, 3, 7 and 8). We described that day to day we see only identifiers, dates, numbers and states in the database, that content can be seen only by the owner of Omni, with a record in a register, and that no artificial intelligence model reads content (summary and sections 3, 6 and 10). We added Anthropic (an AI programming assistant that sees only a view without content), UptimeRobot and traffic statistics from Cloudflare (section 4). We rewrote the sentences about tracking and analytics (summary and section 9).

12. Contact

FUTURE PROOF sp. z o.o., ul. Wielicka 40/U1, 02-657 Warsaw, Poland. Email: contact@omni.contact.