Privacy Policy

OME.UNDFND.EU ("we", "us") is responsible for the personal data described on this page. It covers the website, the dashboard, the browser extension, the phone and guest pages used by OME Link and OME Party, and our Discord server and bot.

It is about two groups of people. Our members, who sign in and use the Service, are covered in sections 02 and 03. The people our members connect to on Ome.tv, and the guests they invite onto a call, never signed up for anything here, and section 04 is written for them.

This page explains what we do with personal data. It is not something you agree to: the choices you can make (cookies, ads, your public profile, notifications, deleting your account) are made in the cookie settings and in your dashboard.

From Discord, when you sign in

• Discord user ID: your account identifier. Your public profile address is built from it
• Username and avatar: shown on your profile, in chat, in the dashboard and in staff tools
• Account locale: picks your language out of the nine the product ships (Czech, Dutch, English, French, German, Latvian, Polish, Romanian and Spanish)
• Account creation date: read from your user ID. It enforces the 90-day minimum account age for signing up and the Welcome Pack's conditions
• Server membership, roles and boost status: checked to confirm you are in our server, to set your role tier and to give server boosters their VIP. We store the tier, not the list of roles

We do not receive your Discord email address, phone number or password.

When you use the website and dashboard

• IP address: recorded with the time at every sign-in, in a security log. It protects accounts. Our servers' technical logs also record the IP address and account of each request
• Where you came from: only if you allow analytics, a random visitor ID in a cookie, with the first page you landed on, the domain of the site that sent you (never the full address), any campaign tags in the link and the partner code if a partner's link brought you. If you sign up, this is attached to your account, which is how we tell which videos and pages bring members in
• Product usage events: a first-party record of named actions (for example "opened a case" or "claimed a season reward") with your account ID and a few counters. A page view also records the page, the kind of device (phone, tablet or desktop) and your browser's language. Events never contain message text, IP addresses or free text
• Browser notifications: if you turn them on, the push address and encryption keys your browser gives us, and your browser's name so the device list can label it

When you generate and use the extension

• Network binding: when the extension sets itself up we store your IP address, and its sign-in then only works from that network. The binding is cleared every day at 06:00 (Polish time). We also keep the last address your extension was set up from on your account, which staff use to see roughly which countries members are in. We do not store a fingerprint of your browser
• Search history: every IP address you look up is stored against your account, together with the location (including approximate coordinates) and network data the lookup returned. This happens on every tier, not only VIP. Browsing that history in the overlay is a VIP feature, but the record is kept either way, so if you have never held VIP, you have a history you cannot currently see. It has no time limit and you cannot clear it yourself: ask us and we will send you a copy or delete it, and deleting your account removes it entirely
• Encounter list: for each address you looked up, how many times, when first and last, and its country and city. It powers "you have met them before" and blocking, and it holds your block list and any private label you gave a connection
• Usage counters: lookups per day, time spent on calls, connections made, and a regular heartbeat that shows the extension is running
• Extension settings: your overlay preferences (theme, accent, panel layout, automation rules) are stored on your account so they follow you between browsers
• Your files in the overlay: the sounds you put on the soundboard, the pictures and videos you pick for your camera and its background, and your Edits deck with the songs you add to it are stored on your account, so every browser you sign in on gets them back. They are private to your account: nobody else can see or download them. You can turn this off, and delete them from your account, in the overlay's Settings, General, Your files
• Meeting another member: when two members are connected to each other on Ome.tv, each overlay recognises the other person as a member from their network binding and shows their Discord username, avatar and role, plus whatever their public profile shows. This happens even if your profile is private, because it is how we keep members safe from people running several accounts. Staff can see these matches too
• What your extension reports about strangers: the lookups, statistics and signals described in section 04 are stored with your account as the member whose extension sent them
• The Chrome Web Store version: before it runs anything, it shows what it uses and asks you to agree. It keeps that you agreed, your sign-in state and your settings in your browser, and sets itself up the first time it runs on Ome.tv with the same network binding described above. You can withdraw from its setup page at any time, and it then stops loading

Community and feature data

• Chat: messages you post in the global room or a country room, shown to everyone in that room
• IP Notes: if you write a note about an IP address, we store the subject, the description, any image you attach, and your account as its author. Notes are visible to every member who looks up that address until they expire
• Profiles: notes you leave in other members' guestbooks, the endorsements and reputation you give or receive, and which profiles you view (used only to count unique visitors; the owner sees a number, not your name)
• ISP ratings, reports and location corrections: ratings you give internet providers, content you report, and corrections you submit to a looked-up location
• Pixel canvas: every pixel you place on the community canvas is recorded with your account ID and a timestamp in a permanent, append-only history. The canvas replay and leaderboards are built from it
• Community automations: an automation you share is stored with your account as its author, its name, description and blocks, and how many members installed and rated it. Signed-in members see your Discord name and picture beside it; everyone else, and its page on the website, says only that a member shared it. You can take it down at any time, and deleting your account removes it
• Shared edits: an edit you share in Community is stored with your account as its author, its name and description, the song title you give it, a fingerprint of the song's rhythm around its drop and, when you leave Share the song with it on, the part of your song the edit plays (under a minute, compressed in your browser). Members who add the edit download that part of the song into their own browser. Otherwise the songs you add in Settings, Edits are private to your account (see Your files in the overlay above). You can take a shared edit down at any time, and deleting your account removes it; a song no shared edit uses any more is deleted within a day
• Vouches: if you post in the VIP vouch channel on Discord, the site may show your message with your name hidden
• Cases and rewards: every case you open is logged with its random seed, the roll and the prize, so any opening can be independently re-checked on our fairness verifier, and with the IP address and network it was opened from, to stop free openings being claimed twice. Claims of rewards (sponsor pages, season and streak rewards) are recorded the same way
• Codes and claims: which VIP codes you redeemed and when; if you claim the Welcome Pack, your IP address, your Discord account's age and your talk time at that moment

Payment and billing data

VIP is paid from a top-up balance held on your account. You add funds by sending a transfer: BLIK, PayPal, Revolut, or cryptocurrency (BTC, ETH, LTC, XMR, SOL and DOGE). Crypto top-ups confirm on-chain; the others are checked from a screenshot you upload. We never receive or store your card number, CVC, or bank login, and we don't use a hosted checkout or third-party payment processor. For your balance, top-ups and purchases we keep:

• Recharge orders: the amount, the payment method you chose, the screenshot you upload as proof of the transfer (it may show your name or account details, depending on your bank), the order status, any note from the reviewer, and timestamps
• Crypto deposits: a deposit address derived for your account, and the transaction hash, amount and confirmation state of each deposit. A blockchain is a public, permanent ledger outside our control: we cannot edit or erase what is recorded there, and anyone who knows an address can see its transactions
• Balance and purchases: your current balance and, for each VIP purchase, the plan, the amount (in euro cents), the VIP code issued, whether it was a gift, any affiliate code applied, and timestamps

Affiliate program data

• Referral code: assigned to your account on first sign-in
• Referral clicks: when someone arrives through your link, a daily count per code with the first page they landed on. Their IP address is kept only as a one-way hash
• Referral records: when someone buys VIP with your code, the purchase value (in euro cents), the commission rate locked in at that time, and the commission earned
• Withdrawal requests: the amount, your chosen payment method, and the payment details that go with it: a PayPal email address, a Revolut @tag or, where crypto payouts are enabled, the wallet address you supply and the hash of the transaction that settles it

Discord bot data

Our bot runs in our own community server only. It cannot be added to other servers, and it handles Discord data as follows:

• Message content: messages posted in the server are checked against automated moderation rules as they arrive. Content is not stored outside Discord, is never used for analytics or profiling, and is never used to train machine learning or AI models. Moderation-log entries stay in staff channels on Discord and are removed on request.
• Ticket transcripts: when a support ticket is closed, a plain-text transcript is generated, sent to the ticket owner and archived in a staff channel on Discord. Both copies live on Discord and are removed on request.
• Presence: used only to produce an aggregate online count shown in the bot status, the extension widget and the site statistics. No per-member presence is stored and no history is kept; members who appear offline are simply not counted.
• Direct messages: the bot messages you for things like your welcome steps and the VIP codes you buy or win.
• Staff logs: private staff channels in our server receive notices of account events (sign-ins, refused sign-ins, extension setup, codes, cases, account deletion requests), a short summary of each lookup (your name and the approximate city and provider of the person you looked up), members meeting each other, and a copy of each IP Note with its picture so it can be moderated. These never contain an IP address: addresses stay in our own database. Images in the server are also checked against a list of known scam pictures, by fingerprint only.

The page is addressed by your Discord user ID, so the ID is visible to anyone who opens it. Depending on which sections are left on, it can show your username and avatar, your level and XP, badges and achievements, cases you have opened, the countries you have connected to, your activity heatmap, your pixel-canvas contributions, your reputation score and endorsements, your bio, and the guestbook notes other members have left you.

Public profiles are also listed in the member directory and may be indexed by search engines. To change any of this, open Account, then Privacy in your dashboard: the master switch takes the whole page offline, and the per-section toggles carve individual blocks out of an otherwise public page. New accounts are asked to make this choice during onboarding.

This section is about someone other than our members: the stranger on the other end of an Ome.tv connection, and anyone a member brings onto a call. They are not our users, they have not agreed to these terms, and we think it is only fair to be plain about what the product does with their data.

The lookup

• Their IP address, and the location and network data it resolves to. This is the core of the service. The address is sent to our IP data providers to be resolved, the answer is cached, and the lookup is recorded in the member's search history and encounter list (see Data Retention)
• An estimated age and gender, for statistics. This estimate is computed in the member's browser from the video on screen. For these statistics, what reaches us is one verdict per connection, folded immediately into a daily total per member, never linked to an IP address
• Bot-detection signals: short one-way hashes that describe the video content (a looping sequence or a frozen frame), not the person in it. A verdict is only ever produced when many members independently report the same content, and the link between a signal and an IP address is deleted after one week
• How the call went, for Crowd Pulse: when a call ends, the member's extension sends how long it lasted, who ended it, and whether the other person typed in the chat, kept their camera off for most of it, or was caught by an explicit-camera check. Other members only ever see this as counts and percentages about that address for the past week, never who reported what, and only once at least two other members met it. Each record is deleted after 8 days

Faces stay in the member's browser

The extension's Face Analyze panel finds the faces in the video and estimates age and gender in the member's browser. The face pictures it shows, the optional on-device sharpening, and a picture the member copies with the Copy button all stay on the member's own device. None of them is sent to us.

Replay recordings stay on the member's computer

A member can turn on Replay, which keeps the last minutes of their calls, the other person's picture and voice included, in the member's own browser so they can save a clip as a video file on their computer. None of it is sent to us: nothing is uploaded, and turning Replay off or closing the tab clears it. A stranger whose camera the explicit-camera check flags is never kept. What a member saves and shares is their own responsibility, and recording people without their permission is against the law in some places.

Notes written by members

Members can write an IP Note about an address, optionally with a frame captured from the video. This is the place where the product publishes what one person says about another. Notes are member-written, so they can be wrong, unfair, or about whoever holds an address next. IP Notes expire on their own (one day for mobile addresses, otherwise 7 to 30 days), are moderated, and can be reported and removed. A copy of the note and its picture, without the address, goes to a private staff channel on Discord for moderation and stays there until staff remove it. Notes that identify, target or harass someone are not allowed and cost the author the feature.

Calls through OME Party and OME Spectator

A Party guest joins a member's call from a link, on their own phone or computer, with or without an account here. Their camera and microphone go to the member and, depending on the member's settings, on to the stranger on the member's call. OME Spectator (VIP) connects the strangers in two of a member's browsers to each other, so each stranger's picture and voice reach the other. The member's browser checks the relayed picture for nudity and skips it.

These connections run directly between browsers. When a direct connection is not possible, the encrypted audio and video pass through a relay server we run, which cannot read them and records none of it. Our server passes the setup messages between the devices and keeps no record of the call. Nothing about these calls is recorded.

Our basis, and your rights if this is you

For the lookup, the statistics, bot detection and Crowd Pulse we rely on legitimate interests: letting people see who they are about to talk to on an anonymous video platform, and filtering out bots and abuse. That telemetry is aggregated, hashed or expiring by design. We do not sell any of the data in this section.

If you were on the other end of a connection, or a guest on a call, and want to know what is held about an address or a face, have a note or your face data removed, or object to this processing, email us at [email protected]. Tell us whatever helps us find it, such as the date, time and country of the call or the IP address you were using. You do not need an account with us to ask, and we will act on it the same as any other request under Your Rights.

• Running the Service: signing you in, checking your access level, serving your dashboard and the extension, answering lookups, keeping your search history and settings
• VIP, balance and payments: checking top-ups, debiting your balance for VIP and case openings, issuing codes, keeping your billing history, syncing your Discord role
• Community features: running chat, profiles, guestbooks, endorsements, badges, seasons, notes, the pixel canvas and shared automations, and moderating them
• Security and abuse prevention: spotting suspicious sign-ins, account sharing, several accounts run by one person, VPN use on free accounts, and repeat claims of free allowances
• Understanding the product: which features are used, and which videos and pages bring members in
• Affiliate program: crediting commissions and processing payouts
• Support: staff can see which members are online on the extension, in chat and on calls, and can send your overlay simple commands (for example skip, stop, reload or a message) or ask it for a diagnostic report, which you can switch off in the overlay's settings
• Communication: Discord announcements, direct messages from our bot, and browser notifications if you turn them on. We do not send email

Our legal bases, where EU law applies: running your account, VIP, balance, cases and the affiliate program is performance of our contract with you; keeping payment records is a legal obligation; security, abuse prevention, product statistics and the lookup are our legitimate interests; Google Analytics, visit and referral attribution, advertising and browser notifications run on your consent, which you can withdraw at any time.

OME.UNDFND's use of information received through its Chrome extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

We do not sell your data and we do not target ads with it. The ads and sponsor pages are chosen by Google and Ad-Maven from what their own scripts and pages see. We decide only where a free account is offered a sponsor page: before copying the script once a day, before a free case, and on the Rewards tab.

We do not sell, rent, or trade personal data. It reaches the following, and nobody else unless the law requires it:

• Other members: what you publish (profile, chat, notes, endorsements, canvas)
• Discord: sign-in, server roles, our bot, and the private staff channels described in section 02 (which never receive IP addresses). Discord Privacy Policy
• Cloudflare: every request to our site passes through Cloudflare's network, which protects and speeds it up and sees your IP address and browser details to do so. Its Turnstile check runs on sign-in, case openings and the Welcome Pack, and its web analytics beacon counts page loads. Cloudflare Privacy Policy
• IP data providers: every address looked up through the extension is sent to our IP data provider to be resolved, and to ipinfo.io when that provider is unavailable
• Google Analytics: traffic analytics, only if you accept it (see Cookies & Browser Storage). Google Privacy Policy
• Google AdSense: ads on our pages, only if you allow advertising and do not have VIP. Its script receives your IP address, browser details and the page you are on. How Google uses data in ads
• Ad-Maven: the pop-under script on our pages, only if you allow advertising and do not have VIP, and the sponsor pages free accounts can open. Its script and pages receive your IP address, browser details and the page you are on. A Rewards link also carries a one-time code for our site, which does not contain your Discord ID
• Google STUN servers: when OME Link, OME Party or OME Spectator connects, your browser asks Google's STUN servers for its public address, which shows them your IP address
• Browser push services: if you turn on notifications, your browser's own push service (from Google, Mozilla, Apple or Microsoft) carries our encrypted messages to you
• Map, flag and font providers: the overlay and dashboard maps load tiles from CARTO (street and dark styles) and Esri/ArcGIS (satellite); flag images come from flagcdn.com; the overlay loads its fonts from Google Fonts. Each request shows that provider your IP address, and a map tile or a flag also shows the area or country you are looking at
• Addresses your automations call: an automation you build can send the data you pick (for example the location of a lookup) to a web address you enter, such as a Discord webhook. That request goes from your browser straight to that address. We do not see it, and what the receiver does with it is up to them
• Payment services you choose: your bank, PayPal or Revolut process your transfer under their own policies
• Blockchain networks: a crypto top-up or payout is recorded on a public ledger (Bitcoin, Litecoin, Ethereum, Base, Polygon, Solana or Dogecoin) that we neither control nor can erase. Monero is the exception: it publishes no balance and no counterparty anyone can look up
• Legal obligations: we may disclose data if required by law or court order, or to protect the rights, safety or property of OME.UNDFND.EU or others

Everything else runs on servers we rent. The extension's code libraries, map renderer and camera models are served from our own domain or shipped inside the Chrome Web Store version, never from a public CDN, so no third-party script host sees you use the extension.

Several of these providers, including Discord, Google and Cloudflare, are based in the United States or process data there and in other countries outside the EU.

Necessary

__Host-omeu.sid keeps you signed in. It stays while you are active and expires after 30 days without activity, or when you sign out.

__Host-omeu.trial holds a random ID for this browser, set the first time the extension connects to your account and kept for up to 400 days. Your cookie choice itself is kept in your browser's local storage. It is not linked to your account. We use it only so the one-time welcome lookups are given once per browser, not again to every account that signs in on the same browser (see section 08).

Referral and visit tracking (optional)

Set only if you allow analytics, and removed when you withdraw it:

• omeu.ref: set for 30 days when you arrive through a partner's link, so the partner is credited if you sign up
• omeu.vid: a random visitor ID, kept for a year, that ties together the first page you saw, the site that sent you and your sign-up (see section 02)

Analytics (optional)

With your consent, Google Analytics sets _ga cookies to measure how visitors use the site: pages visited, session length and approximate region. You can accept or withdraw at any time from the cookie preferences link in the footer; withdrawing stops it and deletes those cookies.

Advertising (optional)

If you allow advertising and do not have VIP, our pages load Google AdSense and Ad-Maven's script, which can show pop-under ads. Both may set their own cookies or similar identifiers under their own policies. Nothing loads until you allow it, and VIP accounts load no ad code at all. Payment pages never show ads.

The free tier is paid for by these ads. If you decline them, they stay off everywhere, and a signed-in account without VIP is asked, on its dashboard, to allow ads or take VIP before using the free tools. Your account settings, privacy controls, data export, account deletion and wallet stay open either way. You can change your choice at any time from the cookie preferences link in the footer.

Free accounts are also offered sponsor pages run by Ad-Maven: once a day before copying the script, before a free case, and on the Rewards tab, where finishing them earns lookups, cases or VIP time. Those open only when you press the button, as their own pages. VIP accounts are never asked to open a sponsor page.

Browser storage

The site and the extension keep preferences in your browser's local storage: your cookie choice, the chat room you last used, and your overlay settings. The overlay also keeps your files (sounds, camera pictures and videos, songs) in your browser's storage, and a copy on your account as described above. Faces you save for Face Swap are stored in your browser only and never sent to us. The Chrome extension also keeps a random install ID, created when you install it and removed with it, which it sends with its sign-in check for the same once-per-browser rule as the cookie above.

How long we keep things

• Account data (Discord ID, username, avatar, settings): until you delete your account
• Search history: until you delete your account. It is not age-limited and you cannot clear it yourself, but anyone can ask us to clear it
• Encounter list: 180 days after your last lookup of that address. Addresses you blocked stay on your block list until you unblock them
• Network binding: until the next 06:00 (Polish time) daily reset. The last address your extension was set up from stays on your account until you delete it
• Security log of sign-ins and staff actions: kept, including the IP addresses in it, and not removed when you delete your account
• Case openings and reward claims, with the IP address they came from: until you delete your account
• Payment screenshots: until you delete your account, when they are blanked
• Staff log copies on Discord: until staff remove them. They contain no IP addresses
• Product usage events: 90 days, then deleted automatically
• Visit tracking: 90 days if you never sign up; with your account if you do
• Chat messages: until moderation removes them or your account is deleted
• Notifications: 60 days
• Your files in the overlay: 90 days after your overlay last signed in. Every sign-in keeps them another 90 days. Files you delete, or delete from your account in Settings, are removed from our server within a day
• Profile activity heatmap: daily activity cells age out after roughly 400 days
• IP Notes: expire on their own, after one day for mobile addresses and otherwise 7 to 30 days as chosen by the author. Expired notes stop being served immediately and are deleted by a daily sweep
• Cached IP answers: never written to our database. They are held in memory for at most 12 hours and in our cache server for at most 30 days from the first lookup of that address, then deleted
• Bot-detection signals: the link between a signal and an IP address is deleted after 7 days, so a verdict can never outlive the address's current occupant
• Crowd Pulse records: 8 days, then deleted automatically. The numbers members see only ever cover the past week
• Camera capture statistics: kept only as per-day totals per account; no individual connection is ever stored, so there is nothing narrower to delete
• Pixel-canvas history: permanent. The canvas replay, timelines and leaderboards are all derived from this append-only log
• Free-allowance IP checks: a one-way hash of your IP address, 30 days
• Free-allowance browser checks: a keyed one-way hash of the browser ID cookie and of the extension install ID, 90 days
• Billing and payment records: kept for financial and tax record-keeping, including after account deletion, to the extent the law requires
• Staff review copies: when staff need to look into an account (a dispute, a hijacked account), they may take a copy of its data. Every copy is deleted after 7 days, even if the account itself was deleted in the meantime
• Session cookie: 30 days after your last activity

Deleting your account

You can delete your account yourself from Account, then Privacy, in your dashboard. Deletion runs after a 30-day grace period, so you can cancel if you change your mind. It then removes your account, search history, encounter list, chat messages, IP Notes and your votes on them, ISP ratings, achievements and badges, notifications, browser notification registrations, case history, your vouch, your own affiliate ledger, the files your overlay kept on your account, your overlay automations, your camera statistics, your activity heatmap, your guestbook reactions and your canvas bookmarks and missions. Where you were the buyer in another partner's ledger, only the link to you is removed, and your visit tracking is unlinked from you in the same way. Payment screenshots are blanked.

These survive deletion:

• Billing and payment records, and settled withdrawal records, which we are required to keep
• The security log of sign-ins and staff actions, including the IP addresses in it
• Your Welcome Pack claim, if you made one
• Your pixel-canvas placements, which stay in the canvas history under your Discord user ID, with no username or profile behind it any more
• Guestbook notes you left, endorsements, reputation and profile views
• The free-allowance record explained below
• Records of rewards you claimed (season, streak and case missions) and any spending limit you set, so they cannot be claimed or reset twice
• Your canvas player record, location corrections you submitted and content reports you made
• Product usage events, until they age out after 90 days
• Staff log copies on Discord about your account

Apart from the billing records, the security log and the free-allowance record, ask us and we will remove any of these by hand.

One exception, stated plainly. Every account receives a one-time allowance of free lookups. To stop the same person collecting it over and over by deleting and re-creating their account, we keep a record that a given Discord account has already had its allowance, and that record is not deleted when you delete your account. It contains no username, no IP address and no usable identifier: only a keyed one-way hash of the Discord ID, which we can compare against but cannot reverse, and which is meaningless to anyone who does not hold our server-side key. We keep it under our legitimate interest in preventing fraud and abuse of a free service. If you delete your account and later sign up again with the same Discord account, this is the reason the free allowance is not granted a second time. For the same reason we keep, for 90 days, a keyed one-way hash of the random browser ID and extension install ID that received an allowance, with no account attached, so a second account set up in the same browser does not receive it again.

We implement reasonable technical and organizational measures to protect your data against unauthorized access, disclosure, alteration, or destruction. These include:

• HTTPS encryption for all data in transit
• Server-side session management with cryptographically signed cookies
• Rate limiting on authentication and API endpoints, and a human check on sign-in
• An extension bound to the network it was set up on, with a token you can replace and devices you can sign out from the dashboard
• Discord OAuth2 authentication (we never handle your Discord password)
• A log of staff actions on accounts, including every look at a review copy
• No IP addresses in the staff channels on Discord

No method of transmission over the internet or electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your data, we cannot guarantee its absolute security.

Depending on your location, you may have certain rights regarding your personal data under applicable law (including GDPR for users in the EU/EEA):

• Right of access: you can request a copy of the personal data we hold about you. Members can download most of it themselves from Account, then Privacy
• Right to rectification: you can request correction of inaccurate data (most account data updates automatically on next login)
• Right to erasure: you can request deletion of your account and associated personal data. What survives, and why, is listed under Data Retention
• Right to restriction: you can request that we limit processing of your data in certain circumstances
• Right to data portability: you can request your data in a structured, machine-readable format
• Right to object: you can object to processing based on legitimate interests
• Right to withdraw consent: you can withdraw consent for analytics, attribution and advertising at any time via cookie preferences, and turn browser notifications off

The quickest route for erasure is the self-service account deletion in your dashboard. For anything else, email [email protected] or contact us via Discord. We will respond within 30 days. We may need to verify your identity before processing requests.

You do not need an account to exercise these rights. If you believe you appear in our data as someone else's connection (see People You Connect To), write to the same address.

If you are in the EU/EEA and are unhappy with how we handled your request, you have the right to lodge a complaint with your national data protection authority.

California residents

If you live in California, the CCPA (as amended by the CPRA) gives you the rights above under different names, and they apply to you the same way: to know what personal information we collect and why (see Data We Collect About You), to delete it, to correct it, and to opt out of its sale or sharing.

We do not sell personal information for money. If you allow advertising, our pages load Google AdSense and Ad-Maven's script for accounts without VIP, and they and Ad-Maven's sponsor pages collect information from your browser for advertising, which California law may treat as sharing for cross-context behavioural advertising. Declining advertising in the cookie preferences opts you out. VIP accounts never load them. See Who Receives Data for everyone who receives data and why.

Exercise any of these at the address above. We will not discriminate against you for doing so: your account, your balance and your VIP time are unaffected by a privacy request. An authorized agent may make a request on your behalf, in which case we will ask for proof of their authorization and verify your identity directly.

Other US states

Several other states now have comprehensive privacy laws granting substantially the same rights: to know, to delete, to correct, to a portable copy, and to opt out of the sale of personal data or its use for targeted advertising. If you live in one of them, those rights apply to you here on the same terms and through the same address. We do not sell personal data for money, the advertising described above is the only targeted advertising on our pages, and we do not profile anyone in a way that produces legal or similarly significant effects. If your state gives you a right to appeal a refused request, write to the same address and say so, and a human who did not handle the original request will answer.

OME.UNDFND.EU is an 18+ service. It is built for use alongside an adult video-chat platform and it sells paid digital items, so it is not directed at children and we do not knowingly collect personal data from anyone under 18.

Ome.tv is meant for adults too, but a member's extension cannot tell a stranger's age for certain: the estimate in section 04 is a guess. If you are under 18, or the parent or guardian of someone who is, and believe their account, face or other data is held here, contact us at [email protected] and we will close any account and delete the data promptly.

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. Material changes may be announced via our Discord server.

For privacy questions, data access or deletion requests, or complaints, write to [email protected]. This address is monitored and does not require a Discord account. Use it for anything you want on record.

For quick, informal questions our Discord server is faster: open a ticket in #open-ticket and a staff member will pick it up.