Privacy choices in plain language
Understand your data choices
Your data choices depend on the account, device and regional rights that apply to you. Use browser settings for media permissions, review the privacy policy for service-side handling, and prepare a specific request through the available support or reporting route.
This page explains available choices. It does not promise that every request can erase information that must be retained for safety, fraud prevention, transactions or legal obligations.
Privacy choices in plain language
Review camera and microphone access in your browser settings.
Identify the account and information involved instead of sending a vague demand.
Read the privacy policy for collection, use, retention and processing details.
Start with the information and setting involved
A useful privacy request identifies what you want to change. Account details, a message, a transaction record, a browser permission and a marketing preference are different kinds of information or settings. The available action can differ for each one. Begin by naming the exact item and the account or device it belongs to.
Keep sign-in secrets, one-time codes and complete card details out of every support message. A UID, approximate date and concise description are usually more useful than unrelated screenshots. The contact preparation guide explains how to organize those details without exposing additional sensitive information.
Browser permissions remain under your control
Camera and microphone access begins with a browser choice when the selected conversation format needs it. You can decline a prompt, end a conversation or revisit the browser’s site settings to change device access. Choosing text is another way to reduce the information shared through a camera view or background sound.
A browser permission is separate from service-side records. Changing device access does not by itself alter information already processed during an earlier session. For that distinction, review the privacy policy and identify any specific request you want to make.
Available requests depend on the applicable rights
Depending on your region and account situation, available privacy rights may include asking for access, correction or deletion of certain personal information, or objecting to particular processing. These rights are not identical everywhere. Exceptions may apply to records needed for security, abuse prevention, payment history or a legal obligation.
Use the available reporting or support route with a clear request and the information needed to locate the account. Verification may be necessary before an account-specific request can be answered. Do not send more identity material than the actual process requests. The safety guide also explains how to limit disclosure during ordinary conversations.
Separate privacy requests from safety reports
A privacy request concerns personal information or data rights. A safety report concerns another user’s conduct. Pressure from a match calls for an immediate exit, followed by the available blocking and reporting controls. Waiting for a separate privacy request should not delay the immediate safety action.
For conduct reports, keep factual details such as the UID, approximate time and what happened. For data requests, focus on the information and choice involved. Keeping the two requests distinct helps avoid confusion and unnecessary disclosure.
One person is enough
Make a specific, informed choice
Review the policy, adjust device permissions deliberately and identify the exact information or setting your request concerns.