Mitu Privacy Policy
Effective Date: September 9, 2026
This Policy describes the personal information handled when you use Mitu, why it is processed, when it is shared, and how you can exercise control over it. It covers both planned conversations started from the home page and spontaneous connections through random video matching.
1.1 Who we are. This Privacy Policy explains how Mitu, the operator of the Mitu mobile application ("Mitu," "we," "us," or "our"), handles personal information in connection with its one-to-one video social services. Mitu is responsible for determining the purposes and means of the processing described here, except where an independent third party determines its own processing.
1.2 Services covered. This Policy applies to account registration, profiles, home-page discovery, direct video calls, random video matching, virtual gifts, following, text conversations, and related support and safety operations. It also applies to Mitu pages or forms that expressly link to this Policy. Separate services operated by third parties are governed by their own notices.
1.3 How to reach us. Our privacy contact is service@mitu.zone. You may use this address for privacy questions, rights requests, account deletion, and concerns about the handling of your information. This Policy explains our practices; it does not treat your use of Mitu as consent to every form of processing.
2.1 Information you provide. We collect information you submit when creating or editing an account, communicating with another user, sending a gift, making a purchase, reporting a concern, or contacting support. The information collected depends on the features you use and the fields you choose to complete.
2.2 Information generated by use. We collect technical and interaction information when you access Mitu, including connection logs, feature activity, communication metadata, and diagnostic events. Other users can also provide information about you through messages, gifts, reports, or support submissions. We limit our use of this information to the purposes explained in this Policy.
2.3 Required and optional information. Information needed to establish an account, verify eligibility, route communications, or protect the service may be required for the relevant activity. Optional profile details and permission-dependent features are your choice. Declining optional information can limit the associated feature without making that information necessary for unrelated functions.
3.1 Account credentials. Depending on the sign-in method you select, account information can include an email address or telephone number, an account identifier, authentication tokens, and protected credential records. If a third-party sign-in option is offered and you select it, we receive the identifiers and profile fields authorized through that provider, rather than your password for that provider.
3.2 Profile details. We process your username, display name, profile photograph, age or date of birth, and any optional biography, gender, country, language, or interests you provide. Age information supports our adult-only eligibility rule. Profile information supports discovery and helps other users understand who they are communicating with.
3.3 Profile visibility. Your display name, photograph, and other fields identified as visible in the profile interface can be shown to other users. We do not display account credentials, private contact details, or your full date of birth as public profile fields. Avoid placing information you want to keep private in a visible biography or image.
4.1 Home-page activity. We process profile views, interaction selections, call initiation events, and related timestamps to display users, respond to your actions, diagnose errors, and understand how discovery features are used. A profile view or call request does not guarantee that another person is available or will respond.
4.2 Random video matching. When you use random video matching, we process your participation request, session identifier, availability, and connection outcome. Matching can also account for operational constraints such as connectivity, eligibility, and safety restrictions. Random matching involves meeting an unfamiliar participant; it does not mean that your identity or activity is anonymous to Mitu.
4.3 Following and communication history. We keep records of following relationships, messages exchanged, calls initiated or received, and gift interactions to support continuity between conversations. Block and restriction records, where applicable, help prevent prohibited interactions and protect users. These operational records are separate from the audiovisual content of a live call.
5.1 Content collected. User-generated content ("UGC") includes text messages, profile text, photographs, and any other media you upload through an available feature. We process the content itself and associated information such as sender and recipient identifiers, upload or delivery time, file type, and delivery status. Available upload formats depend on the feature you use.
5.2 Storage and delivery. We store messages and uploaded content as necessary to deliver them, display conversation history or profiles, support access across sessions, handle user requests, and investigate reported violations. Infrastructure providers can process this content on our behalf. Content is subject to the retention and deletion rules in Sections 19 and 20.
5.3 Private conversations. Text conversations are intended for the participating users. Authorized personnel or contracted reviewers may access relevant content when necessary to investigate a report, provide requested support, address a security incident, or meet a legal obligation. We limit such access by purpose and role. This Policy does not promise end-to-end encryption.
5.4 Information about others. Only submit information about another person when you have an appropriate right or permission to do so. Messages or images can reveal sensitive facts about you or someone else. You should avoid sharing identification documents, payment credentials, home addresses, or other unnecessary sensitive information through conversations.
6.1 Real-time processing. Video calls require access to your camera and microphone when you activate the relevant functions. We and our communication infrastructure providers process and transmit live video and audio so that participants can see and hear each other. Network buffering and routing necessary to deliver a call are distinct from maintaining a stored recording.
6.2 Call records and recordings. We retain call metadata, such as participant identifiers, start and end times, duration, connection status, and technical quality information, for service delivery, troubleshooting, safety, and any applicable billing. Routine video calling does not create a stored recording of the complete call for Mitu. Any separate recording feature or retained moderation capture will be explained before collection, including its purpose, access, and retention.
6.3 Faces and biometric processing. A profile photograph or video stream can contain an image of your face. Processing that image to display it is different from extracting a biometric template to identify a person. Ordinary video calling does not require biometric identification. If a separate age or identity verification feature processes identification documents, facial templates, or liveness information, we will provide a specific notice and obtain consent where required before that processing begins.
6.4 Other participants. Another participant may independently capture or disclose what appears in a conversation, including through another device. We cannot guarantee control over those copies. Do not record or redistribute another person's conversation without an appropriate legal basis and any permission required by applicable law. Report suspected misuse through the available reporting tools or service@mitu.zone.
7.1 Technical information. We process information such as device model, operating system and version, app version, language, time zone, IP address, network type, and app-generated identifiers. Session and authentication information supports login continuity and abuse prevention. Push notification tokens are processed when notifications are enabled.
7.2 Performance information. Diagnostic information can include crash reports, error codes, loading times, connection failures, and video or audio quality measurements. We use this information to identify faulty releases, improve reliability, and resolve problems. Diagnostic collection should avoid unnecessary message content, credentials, or unrelated files.
7.3 Identifier limits. Identifiers are used for disclosed operational purposes and subject to platform restrictions. We do not require access to your telephone contact list, SMS messages, ordinary cellular call history, or inventory of installed apps to provide the described video social features. Any additional sensitive access requires a justified feature, clear disclosure, and applicable permission.
8.1 Approximate location. We may derive an approximate country or region from your IP address, network information, or the country you enter in your profile. This information can support language and regional settings, service availability, security checks, and relevant discovery. An IP-derived location can be inaccurate and is not a reliable indication of your precise whereabouts.
8.2 Precise location. The core features described in this Policy do not require continuous GPS tracking. If an optional feature requests precise device location, its permission prompt and accompanying notice will explain the purpose, whether processing is on the device or off the device, the recipients, and any retention. We obtain permission before accessing location protected by the operating system.
8.3 Your controls. You can manage location permission in your device settings and edit any self-declared location through available profile controls. Turning off location permission does not prevent approximate location from being inferred from an IP address used to connect to the service. Avoid revealing your address or exact location in visible content.
9.1 Transaction information. Sending or receiving a virtual gift generates records such as gift type, quantity or value, sender and recipient identifiers, and time. Where paid calls, virtual currency, gift purchases, or other paid features are offered, we also process the product identifier, order reference, purchase status, currency, amount, and relevant balance or entitlement changes.
9.2 Payment processing. Purchases made through Google Play are processed by Google under its own terms and privacy policy. Mitu receives the purchase information needed to validate transactions, deliver purchased items, and handle support or fraud concerns. We do not receive your complete payment card number or card security code from Google Play billing.
9.3 Transaction purposes and visibility. We use transaction records to maintain balances, deliver gifts, reconcile purchases, investigate disputed activity, and satisfy accounting obligations. The recipient can see information needed to identify and display a gift. Full payment credentials and private purchase receipts are not shared with other users. Financial records may require retention after account deletion as explained in Section 19.
10.1 Support requests. When you contact us, we collect your contact details, account identifier, description of the issue, correspondence, and any supporting attachments you choose to send. We use this information to investigate and respond. Send only the information needed for the request, and do not send passwords or complete payment card details.
10.2 Safety reports. Reports can include the reporting and reported account identifiers, selected messages or content, incident times, report reasons, and investigation outcomes. We use these records to review conduct, protect users, prevent repeat abuse, and handle appeals. Relevant material may be preserved where needed for an active investigation or legal reporting obligation.
10.3 External information. Where relevant to your use of Mitu, we receive authentication results from sign-in providers, transaction confirmations from payment platforms, and security or abuse indicators from service providers or lawful sources. We assess the relevance and reliability of such information before relying on it and do not treat an allegation as proof of misconduct.
11.1 Device permissions. Camera and microphone permissions support video calling. Photo or media access supports selecting a profile image or an upload when offered, and notification permission supports incoming communication and service alerts. We request permission in connection with the relevant feature and use limited system access, such as a photo picker, where appropriate.
11.2 Local storage. Mitu uses local storage, cached files, and similar app technologies to maintain sessions, remember preferences, and improve performance. Related web pages may use cookies for comparable purposes. Clearing these items can sign you out or reset preferences. Local deletion does not automatically remove information held on our systems.
11.3 Additional disclosures. A device permission is not blanket consent for unrelated processing. Where personal or sensitive information is used in a way that is not reasonably expected, we provide a prominent explanation within the app and obtain affirmative consent when required before accessing or collecting it. Optional tracking technologies are subject to available consent controls and applicable law.
12.1 Providing the service. We use account information to authenticate users; profile and interaction data to support discovery and following; communication data to route calls and deliver messages; and gift or purchase records to provide requested transactions. We also use contact details and support history to answer questions and communicate service-related information.
12.2 Improvement and personalization. We analyze device, diagnostic, and feature-use information to resolve technical faults, assess feature performance, improve usability, and tailor parts of the experience. Profile fields and interaction signals can help select relevant profiles or communication suggestions as described in Section 14. We favor aggregate results where individual identification is unnecessary.
12.3 Safety and compliance. We use relevant account, content, transaction, and technical information to enforce eligibility rules, investigate misconduct, protect accounts, detect fraud, respond to rights requests, and meet legal obligations. Access to information for these activities is limited to what is appropriate for the purpose. A new incompatible use requires an appropriate legal basis and any additional notice or consent required by law.
13.1 Contract and requested services. Where applicable data protection law requires a legal basis, we rely on contractual necessity for processing objectively needed to provide services you request, such as account access, message delivery, video connections, and gift transactions. Optional processing that is not needed to perform those services is not automatically covered by this basis.
13.2 Legitimate interests and legal duties. We may rely on legitimate interests for proportionate service security, fraud prevention, reliability analysis, and protection of legal claims, after considering your rights and reasonable expectations. We rely on legal obligations where processing is required by applicable law, including certain financial records and lawful reporting or disclosure duties.
13.3 Consent and sensitive information. We rely on consent where required for optional technologies, permission-dependent uses, or specific sensitive processing. You may withdraw consent as described in Section 22. Where information is subject to additional legal protection, such as biometric identification data, we must also satisfy the additional conditions that apply. Merely uploading or displaying an image is not consent to unrelated sensitive profiling.
14.1 Relevant signals. Home-page discovery and suggestions may use profile information you provide, language, approximate region, activity, following relationships, and previous interactions. Operational and safety restrictions can affect which users are shown or connected. These signals support relevance and service operation; they do not establish compatibility or guarantee any particular social outcome.
14.2 Random matching limits. Random matching selects from users eligible to participate at the relevant time and can be constrained by availability, blocked relationships, and connection conditions. Participation and matching records support operation and abuse prevention. A random match does not grant the other participant access to nonpublic account data or permission to reuse your content.
14.3 Automated safety tools and review. Automated tools may help flag suspicious account activity, payment abuse, or potentially prohibited content for action or review. You may contact service@mitu.zone to question a restriction and request review. Where a solely automated decision produces legal or similarly significant effects and local law provides safeguards, we provide the applicable explanation, opportunity to express your views, and human review.
15.1 Profiles and interactions. Other users receive the profile fields displayed by Mitu and information associated with interactions you initiate, such as your identity as a caller, message sender, follower, or gift sender. Your video and audio are delivered to the participant in your call. Visibility can vary by feature and any privacy controls offered.
15.2 Audience choices. Before submitting content, consider its intended audience and the information it reveals. Choosing to send information to another user makes that information available to the recipient. A recipient may retain a copy outside Mitu. We do not describe messages or video calls as confidential against all recipients, service providers, or lawful access.
15.3 Protecting private account information. We do not make login credentials, private support correspondence, or full payment information visible as part of ordinary social interactions. We limit disclosure of a reporter's identity where practicable, although facts in a report or a legal process may reveal it. Blocking or ending a conversation does not retrieve copies already made by another person.
16.1 Provider categories. We use providers for hosting and storage, video and audio transmission, message delivery, authentication, notifications, payment validation, diagnostics, customer support, and safety operations. Depending on their task, providers process account identifiers, contact information, content, live media, technical logs, or transaction records. They receive only the information relevant to the service they perform.
16.2 Provider responsibilities. When a provider processes information on our behalf, we require appropriate confidentiality, security, purpose limitations, and deletion or return arrangements. We assess third-party software development kits (SDKs) as part of our data handling responsibilities. Integrating an SDK does not exempt Mitu from explaining the information it collects or shares.
16.3 Independent providers. App stores, payment platforms, and third-party sign-in services can also act independently for their own account administration, fraud prevention, and legal duties. Their policies explain those separate practices. You can ask service@mitu.zone for information about relevant recipient categories or providers handling your data, subject to lawful security and confidentiality limits.
17.1 Legal requests and protection. We may disclose relevant information when required by applicable law, a valid legal process, or a binding authority request. We may also disclose information when legally permitted and necessary to address fraud, protect rights, investigate serious abuse, or respond to an imminent threat to a person. We assess the request and limit disclosure to its legitimate scope.
17.2 Business changes. Information may be disclosed to professional advisers and a prospective or actual successor during a merger, acquisition, financing, restructuring, or asset transfer, subject to appropriate confidentiality and data protection safeguards. If a transaction changes the controller or materially changes how your information will be used, we provide notice and any choices required by law.
17.3 Your instructions and data sales. We share information when you direct us to do so, including when you send a message or gift to another user. We do not sell personal and sensitive user data for money. Any activity that falls within a broader local legal definition of sale, sharing, or targeted advertising must be disclosed and subject to the applicable rights before it takes place.
17.4 Aggregate information. We may use or share aggregate statistics that do not identify an individual, such as overall connection success rates. Removing a name alone does not make information anonymous. Where information can reasonably be linked back to a person, we continue to treat it as personal information and apply this Policy.
18.1 Processing locations. Mitu serves users in different countries, and information can be stored or processed where we or our service providers operate. Communicating with a user in another country also makes the information you share available there. The country in a profile does not determine the location of our servers.
18.2 Transfer safeguards. Where a transfer is subject to data protection restrictions, we use an applicable lawful mechanism, such as an adequacy decision or approved contractual safeguards, and assess whether supplementary measures are necessary. We do not rely on your acceptance of this Policy alone as authorization for every international transfer.
18.3 Further information. You may contact service@mitu.zone to ask about the processing locations and safeguards relevant to your information and to request a copy or description of applicable transfer protections. We may redact confidential commercial or security details while providing the information required by law. Applicable local storage restrictions take precedence where they apply.
19.1 Account and content retention. We retain account and profile information while it is needed to maintain your account. Messages, uploads, following records, and gift history are retained for the associated service functions, subject to deletion requests and justified exceptions. We assess continued need by the purpose, account status, user choices, and applicable obligations, rather than treating all information as permanently necessary.
19.2 Technical and communication records. Operational logs, call metadata, and diagnostics are retained for the period needed to investigate faults, protect the service, resolve billing issues where relevant, and establish system reliability. Live media transmitted for an ordinary call is not retained as a complete call recording. Separately disclosed safety evidence is assessed according to the incident and any legal preservation duty.
19.3 Financial and safety exceptions. We retain transaction records for applicable tax, accounting, fraud, and dispute requirements. Complaint files, enforcement records, and limited identifiers can be retained where necessary to investigate serious abuse, enforce a justified restriction, or establish or defend legal claims. Retention must remain proportionate; an exception does not justify keeping an entire deleted profile or unrelated conversations.
19.4 Deletion and backups. When information is no longer needed, we delete it or render it irreversibly anonymous. Backup copies are removed through the applicable backup lifecycle and are restricted from ordinary use pending removal. If a backup is restored, relevant deletion instructions must be reapplied. We explain material retention exceptions when responding to a deletion request, unless disclosure is legally prohibited.
20.1 How to request deletion. You can initiate account deletion using the account deletion option in Mitu. You can also request deletion without using or reinstalling the app by emailing service@mitu.zone with the subject "Mitu Account Deletion" and providing your Mitu user ID or registered contact detail. These email instructions can be used independently of access to your account.
20.2 Identity checks. We may ask for proportionate information to confirm that you control the account and protect it from unauthorized deletion. We do not request your password or require unrelated information to exercise this right. If you cannot access your registered contact method, tell us so that we can consider an appropriate alternative verification method.
20.3 What deletion does. After a verified request, we delete the account and associated personal information, subject to the limited lawful retention grounds in Section 19. Deletion is not merely account suspension or deactivation. We notify relevant processors of required deletion and respond within the period required by applicable law, explaining any lawful extension or reason a particular record must be retained.
20.4 Related effects. Uninstalling Mitu does not delete your account. Account deletion does not automatically cancel a subscription managed by Google Play, if you have one. Copies independently retained by other users are outside our direct control; this does not remove our duties regarding data we control. Before deleting your account, you may request access to information you wish to keep.
21.1 Access correction and portability. Depending on the law that applies to you, you may request confirmation of processing, access to personal information, correction of inaccurate information, or a portable copy of eligible information. Available profile controls let you update certain details directly. If a field cannot be changed in the app, contact service@mitu.zone.
21.2 Deletion restriction and objection. You may request deletion, restriction of processing, or object to processing based on legitimate interests where applicable. You may object to direct marketing at any time. Where local law grants additional rights relating to sensitive information, targeted advertising, sale, or sharing, we will provide the applicable controls and honor requests and legally recognized preference signals that apply to our processing.
21.3 Requests and representation. Send requests to service@mitu.zone, identifying the right you want to exercise and the account concerned. An authorized representative may act for you where permitted by law, subject to appropriate verification of authority. We use request verification information for handling the request and protecting accounts, and avoid collecting more than necessary.
21.4 Responses and complaints. We respond within applicable legal deadlines and generally do not charge for a request. If a lawful exception, extension, or permitted fee applies, we explain it. We will not unlawfully discriminate against you for exercising your rights. You may ask us to review a refusal, appeal where local law provides that right, or complain to the competent data protection authority, including in your place of residence where applicable.
22.1 Withdrawing consent. Where processing is based on consent, you may withdraw it through the relevant app or device control or by contacting service@mitu.zone. Withdrawal does not affect the lawfulness of processing already carried out. We explain if the affected feature cannot continue without the information or permission concerned.
22.2 Permission controls. You can revoke camera, microphone, location, media, or notification permissions through your device settings. Revocation stops future access covered by that permission but does not automatically erase previously processed information. Use the rights or deletion process to request removal of information already held by Mitu.
22.3 Messages from Mitu. We use available contact channels for account security, support, transaction, and material service notices. Where promotional communications are offered, they are subject to applicable consent rules and include an appropriate opt-out method. Opting out of promotions does not prevent necessary account or safety notices. Notification previews may reveal message information to anyone who can view your device screen.
23.1 Protective measures. We apply technical and organizational safeguards appropriate to the information and risks, including encrypted transmission, access restrictions, authentication controls, and measures to protect stored information. Access by personnel and providers is limited according to their responsibilities. We review safeguards as services, threats, and legal requirements evolve.
23.2 Your role. Protect your login methods and device, avoid sharing verification codes, and contact us if you suspect unauthorized account activity. No internet service or storage system can be guaranteed completely secure. A security statement in this Policy should not be read as a guarantee that another participant cannot capture or misuse information you share.
23.3 Incidents. If we identify a personal information security incident, we investigate, take appropriate containment and remediation measures, and assess the risks to affected individuals. We notify relevant authorities and affected users when required by applicable law, using appropriate channels and providing the information needed to understand the incident and protective steps.
24.1 Adults only. Mitu is intended exclusively for people aged 18 or older. Individuals under 18 may not create accounts or use the service, even with parental permission. We use eligibility information and appropriate safety processes to enforce this restriction. A higher local minimum age applies where required by law.
24.2 Underage information. If we learn that an account belongs to a person under 18, we take steps to restrict access and remove the account and associated personal information. Limited information may be preserved only where necessary for a legal obligation, child protection investigation, or proportionate prevention of repeated abuse. Age-check information must be limited to the purpose and protected from unrelated use.
24.3 Child Sexual Abuse and Exploitation (CSAE). Mitu prohibits Child Sexual Abuse and Exploitation (CSAE), including grooming, sexual solicitation involving minors, sexual extortion, trafficking for sexual purposes, and the creation, possession, promotion, or distribution of child sexual abuse material (CSAM). This prohibition applies to profiles, messages, video calls, gifts used to facilitate exploitation, and all other conduct through the service.
24.4 Reports and protective action. Users can report suspected underage use or exploitation through available in-app reporting tools or by contacting service@mitu.zone. Do not download, reproduce, or attach suspected CSAM to an ordinary support email. Provide the relevant account identifier and incident details instead. We assess reports, remove identified prohibited material, restrict offending accounts, and report confirmed CSAM to the appropriate authority as required by applicable law.
24.5 Child safety contact. Child safety concerns can be directed to service@mitu.zone with the subject "Mitu Child Safety" for routing to the responsible contact. Necessary evidence is handled with restricted access and retained only for the relevant protective or legal purpose. We cooperate with competent authorities and do not disclose information to an alleged guardian without appropriate verification and a lawful basis.
25.1 Using your content. You retain your rights in content you create, subject to the applicable Terms of Service. We process and make operational copies of UGC to host it, transmit it to the audience you select, display profiles or conversations, provide support, and protect the service. This Privacy Policy does not transfer ownership of your content or grant unrestricted permission for unrelated promotional use.
25.2 Prohibited content and review. Users must not upload or communicate unlawful content, sexual exploitation material, harassment, threats, fraud, non-consensual intimate material, or content that infringes another person's privacy or intellectual property. Reports and relevant content may be reviewed by authorized personnel and appropriate automated systems. We may remove content or restrict an account under the applicable rules while preserving limited evidence where justified.
25.3 Copyright and privacy complaints. To report suspected infringement or misuse of your personal information, contact service@mitu.zone and identify the material, the account or location involved, your relationship to the rights at issue, and a reliable reply address. We may seek further information to assess the request. Necessary complaint details may be shared with the affected user or a competent authority where required or appropriate, subject to protection of sensitive information.
25.4 Review and removal limits. You may ask us to review an enforcement decision through the support contact. We consider relevant context and corrections and explain the outcome to the extent permitted by law and safety needs. Removing content from ordinary display does not require destruction of evidence that must lawfully be preserved, and does not guarantee removal of independent copies held by recipients.
26.1 Changes to this Policy. We may update this Policy when our features, processing practices, or legal obligations change. We publish the revised version with an updated effective date. Material changes will be brought to your attention through an appropriate in-app notice, email, or other suitable channel before they take effect when required by law.
26.2 New uses and consent. If a change introduces a new purpose or sensitive processing that requires consent or another specific safeguard, we obtain that consent or implement the required safeguard before the new processing begins. Continued use alone does not replace legally required affirmative consent. Feature-specific notices supplement this Policy and should clearly explain the processing concerned.
26.3 Contact details. For privacy inquiries, access or deletion requests, objections, complaints, or questions about this Policy, contact Mitu at service@mitu.zone. Include your Mitu user ID or registered contact detail where needed to identify the relevant account, and describe your request. Do not include passwords, complete payment credentials, or unnecessary sensitive attachments.