Start video chat

Legal

Privacy Policy

Last updated: 14 November 2026

This page explains which personal data Ominglo uses, for what, who else gets it, how long we keep it and what you can do about it.

In brief. Video and sound of chats are never recorded. For safety we do keep some single still pictures from cameras, in the cases listed in section 3, and our moderators can view a low-resolution live preview from your camera. Everything else we hold serves accounts, chats, payments or moderation. We do not sell personal data and we show no third-party advertising.

1. Who is responsible for your data

The controller of your personal data is AM SUPPLY sp. z o.o., ul. Sadowa 45, 22-400 Zamość, Poland (KRS 0000886762, NIP 9223068005, REGON 388291844), which runs Ominglo. For anything about your data, write to [email protected].

2. Video and sound are not recorded

A video chat travels between the two browsers over WebRTC and is encrypted on the way. We do not record it, store it or play it back.

Some networks do not allow a direct link between two browsers. Then the encrypted stream goes through a relay server (TURN) that runs on our own server. The relay only passes on encrypted data; it cannot decrypt it and writes nothing to disk.

To find a route between the two browsers, your browser also contacts a public STUN server run by Google. That server sees your IP address, but no picture, sound or text.

3. Still pictures from your camera

By a still frame we mean a single image, with no sound. These are the only cases in which a frame from your camera reaches us:

  • The check in your browser. During a chat, a model that runs inside your browser scores single frames from your camera for content that breaks the rules. For most frames we receive only numbers: the score, how many faces were seen, when in the chat the frame was taken and technical details of the camera and device.
  • Flagged frames. If the browser check marks a frame, typically because the score goes over a fixed limit, the image itself is uploaded and stored for review. The same happens when the camera looks like a virtual (software) camera.
  • A random sample. A small share of frames that were not flagged is also sent at random. We use them to measure how well the check works and to improve it.
  • Regular check frames. In a random chat, roughly twice a minute one frame is uploaded no matter how it scored, since the browser check is not perfect. When the second check (below) finds no problem, we erase that frame at once.
  • Reports. If your chat partner reports you, a recent frame from your camera is attached to the report so a moderator can look at it.
  • Penalty evidence. A moderator who blocks or bans an account can save a frame from its camera to support the decision if you appeal.
  • Live preview. While your camera is on, also before you are paired, every few seconds a tiny, low-resolution image from it goes to the server. The server keeps only the newest one, in memory and briefly, never on disk. Moderators can see it.
  • Live view. A moderator may look at your camera live while checking a case. They see the picture only: no sound reaches our team, and nothing is recorded.

Frames that are sent to us go through a second automated check on a separate computer used for our moderation. Only that check and our moderators see the frames, the preview and the live view.

Decisions made automatically

If the second check is sure that a frame shows nudity, the chat is ended and a penalty applied with no person involved: a short block from random chats, longer with each new violation, and a permanent ban after repeated violations. What counts: the scores from the two checks and when earlier violations happened on the same account or device, and, for short blocks, from the same IP address. This is needed to provide the service under our Terms of Service. You can contest such a decision free of charge from the penalty screen or by e-mail; a person reviews it, and you can give your side.

How long frames are kept

Frames are kept only while they are needed for moderation, for reports and appeals, and to test and tune the automated check, and then they are deleted automatically. Frames tied to a block or ban stay stored no shorter than the penalty itself and any appeal against it. Material that the law obliges us to keep, such as material in cases involving a minor, is kept and passed to the authorities as the law requires. If you want a frame of you deleted, write to [email protected]; we delete it unless the law makes us keep it.

4. What else we collect

  • Account details. Display name, gender, date of birth, country and, if you add one, a profile picture. With an e-mail account: your e-mail address and your password, stored only as a hash we cannot read. With Google sign-in: your e-mail address and Google account identifier. A guest account has a technical identifier instead of an e-mail address.
  • Chat history and friends. Who you were paired with, when and for how long; your friends list; and messages you exchange with friends.
  • Text in a random chat. It is passed to the other person. The server holds the last messages of the current chat in memory only, so that a report can include them. They are written to our database only if someone sends a report; otherwise they are dropped when the chat ends.
  • Reports, penalties and appeals, including the reason, the frame and messages attached, and what was decided.
  • Technical data. IP address, browser and device type, and a device identifier that your browser works out from the features of your browser and device. We use them for security, to keep banned people out and to know your country.
  • Country. We take it from your IP address, usually through Cloudflare. It is used for region filters and pairing.
  • Payments. Your plan, amounts, dates and the payment reference from Stripe. No card numbers.
  • How you found us. If you arrive through a link that carries a campaign name or an ad click code, we store that with your visit and, once you sign in, with your account, to see which campaigns bring sign-ups and purchases. For this we do not store your IP address; a code that changes every day replaces it.
  • Counts. We count events such as button clicks as plain totals, not linked to you.
  • Messages to us through the contact form or by e-mail.

We do not keep your browsing history or your exact location.

5. Why we use your data, and on what legal basis

  • To provide the service you asked for (performance of a contract, Article 6(1)(b) GDPR): accounts, pairing, video and text chat, friends, history, paid plans and automated penalties for clear nudity.
  • To meet legal duties (Article 6(1)(c)): keeping minors out, accounting and tax records, answering lawful requests from authorities and reporting where the law requires it.
  • For our legitimate interests (Article 6(1)(f)): keeping the service safe through moderation, reports, appeals and blocks by account, device and IP address; preventing fraud and misuse; measuring and improving the automated check; finding out which of our campaigns work.
  • With your consent (Article 6(1)(a)): optional cookies, if we use any (section 9). You can withdraw consent at any time without affecting what was done before.

6. Who receives your data

We use a small number of providers, each for a set task and under a contract with us:

  • OVHcloud: hosts our server, which is in France (EU).
  • Cloudflare: network and security services; traffic to our site, including frames sent to us, passes through it.
  • Stripe: payments and subscriptions. Stripe receives your e-mail address and payment details.
  • Resend: sends e-mails such as sign-in links and receipts; it receives your e-mail address and the message.
  • Google: sign-in, only if you choose Google sign-in; and the public STUN server described in section 2.
  • IP location services (ip-api.com, ipwho.is, ipapi.co): asked for the country of an IP address only when Cloudflare cannot tell it. They receive the IP address alone.
  • Authorities, where the law requires it, in particular in cases involving minors.

We do not sell personal data, and we do not share it for advertising.

Some of these providers may process data outside the European Economic Area, mainly in the United States. Where that happens, the transfer relies on the EU–US Data Privacy Framework or on the standard contractual clauses approved by the European Commission.

7. How long we keep your data

  • Account details, chat history and friends list: until you delete your account.
  • Messages between friends: until one of the two accounts is deleted; then they are erased for both sides.
  • Random-chat text: only during the chat, unless it is attached to a report.
  • Frames: as described in section 3. The live preview is never saved.
  • Reports, penalties and appeals: as long as the case, any appeal and keeping banned people out require. After a permanent ban the device stays blocked for one year.
  • Payment records: for as long as tax and accounting law requires.
  • Backups of our database are kept for a few days, so deleted data disappears from them shortly after.
  • Server logs, which include IP addresses, are rotated and deleted automatically after a limited time.

When you delete your account

You can delete your account in Profile. We then remove your e-mail address, password, name, gender, date of birth, country, profile picture and Google link, delete your own chat history and the messages between you and your friends, and end your sign-in. What remains is an empty record marked “Deleted account” that keeps any penalty on it, so that a ban cannot be avoided by signing up again. We also keep report evidence and payment records the law requires us to keep. People you were paired with still see in their own history that they talked to a deleted account. Deleting the account does not cancel a subscription: cancel it in Premium first (see the Terms of Service).

8. Your rights

Under the GDPR you have the right to:

  • get a copy of your data and information about how we use it;
  • have wrong data corrected;
  • have your data erased;
  • restrict how we use it;
  • receive data you gave us in a portable format;
  • object to uses based on our legitimate interests;
  • withdraw a consent at any time;
  • have an automated decision reviewed by a person and give your point of view.

Write to [email protected]. We answer within one month. We may ask for something that shows the account is yours before acting.

You can also lodge a complaint with the Polish supervisory authority: the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, Poland, uodo.gov.pl, or with the authority in the EU country where you live or work.

9. Cookies and browser storage

We use one cookie that the service needs: token, which keeps your guest account or your account signed in, for up to 30 days. Cloudflare may also set its own short-lived security cookie that protects the site from abusive traffic.

The site also saves a few settings in your browser’s local and session storage: your device identifier, theme, language, cookie choice, camera mirror settings, interest tags, the campaign details described in section 4, and the name and e-mail you entered, so you do not need to type them again. They stay in your browser and are used only by Ominglo.

We use no analytics and no advertising cookies at the moment. If we ever add analytics, it will run only after you allow it in the cookie banner, and this policy will name the provider first.

10. Adults only

Ominglo is only for people aged 18 or over. If it turns out that the person behind an account is younger, we close the account and delete its data, apart from material the law obliges us to keep and report. Reports that involve minors are handled first.

11. Changes to this policy

When this policy changes, we update the date at the top. If a change is important, we also tell you in the service and, if you have an account, by e-mail before it applies.