FNF MEET Terms of Use

Effective 15 October 2026. Version 1.2.

These Terms govern your use of FNF MEET, operated by Indian Networks, K-142, Shivalik Nagar, Haridwar, Uttarakhand, India. Read them with the Privacy Policy and Security and Moderation notice. Contact fnf@fnfmeet.com or use the verified privacy-request form at /privacy-request.

Service and eligibility

FNF MEET provides messaging, groups, attachments, voice notes and calls on Android and the web. Preview releases may change, fail or become temporarily unavailable. Features are described as they actually operate; a planned feature is not a guarantee that it is currently available.

Independent users must be at least 13, or the higher age required in their location. Where parental/guardian authorization is required, it must be valid and verifiable. Do not create an account below the applicable minimum. FNF does not currently provide a verified parental-authorization process. If that process is required for your use, do not register or continue using the service until it is available.

Use accurate registration information, protect your password and authenticator/recovery material, and notify us of suspected account compromise. Do not sell accounts, impersonate others or share access in a way that defeats security controls. You are responsible for activity you authorize, subject to applicable law and our responsibility for our own systems.

Acceptable use

Do not use FNF for unlawful content or conduct, child exploitation, credible threats, harassment, discriminatory abuse, scams, unauthorized intimate material, impersonation, malicious files or infringement of others’ rights. Do not send unwanted bulk communications, bypass access restrictions, probe other accounts without permission, defeat consent notices, or interfere with service operation.

You must have appropriate rights and lawful authority to upload or share material. Obtain any separate permission required before recording or redistributing a conversation. Do not assume that another participant’s acceptance of FNF moderation permits your own recording, public publication or unrelated reuse.

Content and privacy

You retain your rights in your content. You grant Indian Networks the limited permissions necessary to host, route, display, deliver and otherwise process that content for the features you use, subject to the Privacy Policy and applicable law. This is not a transfer of ownership or unrestricted permission to sell your private content.

Participants can retain copies independently of FNF. Group administrators and other participants may affect membership and visibility. Think carefully before sharing confidential information. FNF calling is not an emergency-service replacement.

Encryption and device verification

FNF supports E2EE conversations for approved accounts, including device security codes, ratcheted messages, encrypted media, device approval/revocation and signed call negotiation. This availability is currently limited to approved accounts. Conversations outside the E2EE mode remain server-readable. Existing ordinary history is not retroactively encrypted. A security code must be independently compared to verify the intended person; first use alone does not verify identity. Calls outside the authenticated E2EE mode use WebRTC transport encryption. Limited Android/browser integration tests have passed; broader validation and an independent FNF integration audit remain pending. This is not a general production security guarantee. A compromised device or lost archive/recovery key can defeat protection or prevent recovery. See the Security and Moderation notice for the applicable mode.

In an E2EE mode, devices hold private decryption material. Verify a contact’s security code or QR code through a trusted channel when that feature is available. A new or changed identity requires renewed verification. Password recovery may restore account access without restoring encrypted history. Lost keys, a device compromise or an insecure backup can defeat confidentiality. We will not claim server-side recovery of keys that the server does not possess.

Screening, flags and disclosed moderation

Staff may assess reports, serious allegations, safety incidents and legally reviewed obligations. We may restrict accounts or flag them for screening. A flag is not a conviction or a statement that a reported allegation has been proved. Legal demands are assessed for validity and scope; a flag is not an automatic authorization for surveillance.

When an interaction is moderated, the interface identifies flagged participants and explains the applicable security mode. Each call participant must accept the recording notice before connection. Video moderation can include periodic front-camera images at the disclosed interval; call audio may be recorded. Moderated messages and voice notes can be accessible to authorized staff following the applicable disclosure and consent.

You may decline the moderated interaction and choose not to use that feature. You may end a call to stop further capture. Previously captured evidence may finish uploading and be retained under the disclosed policy or a reasoned preservation hold. Choosing to use FNF generally does not replace specific recording consent or authorize hidden decryption. Existing E2EE history must not be silently converted into server-readable content.

Reports, restrictions and appeals

Use the reporting features or support/privacy contact routes to raise concerns. Do not knowingly submit false reports or use screening mechanisms to harass others. We may investigate, restrict a feature, suspend access or preserve relevant evidence where proportionate and lawful. We will provide available reasons and a review route unless doing so would be unlawful or create a material safety risk.

Staff actions and evidence access are logged. Evidence holds require an explicit preservation reason. An administrator’s arbitrary preference or a user’s blanket acceptance is not a substitute for a valid legal basis.

Retention, closure and changes

The Privacy Policy explains retention. The current call-evidence period is 90 days after call end, configurable by the super administrator, with reasoned holds excluded. Not every category of information follows this period. Account deactivation is different from a complete erasure request; we assess requests and any preservation duties separately.

We may improve, update or discontinue features. Material changes affecting privacy, consent or encryption will be communicated and require additional acceptance where applicable. Continuing to use a feature after valid notice may have the effect permitted by applicable law; it does not waive mandatory rights.

Responsibility and disputes

We do not guarantee uninterrupted availability or protection against every attack. Reasonable limitations are subject to applicable consumer and data-protection law. Nothing in these Terms excludes liability that cannot lawfully be excluded, or excuses intentional wrongdoing or our statutory duties.

Indian law governs to the extent permitted, without removing mandatory protections or competent forums available in your jurisdiction. Contact Indian Networks first to seek resolution where practical. Privacy grievances can be submitted through /privacy-request, by email to fnf@fnfmeet.com or by post to Indian Networks at the address above. We assess and respond within the timeframe required by applicable law. These Terms do not impose a blanket waiver of legal remedies or compulsory arbitration on all international users.

Feature availability and attachments

The attachment button may be hidden pending release decisions. This does not erase earlier attachments. Current attachments use FNF hosting; personal cloud-drive linking and receiver-owned cloud copies are proposed features and are not available in this release. Device and service storage limits apply. Neither an attachment link nor a thumbnail guarantees permanent access. Do not use FNF as your only copy of an important file.

Mobile sign-in and service settings

If mobile SMS authentication is available, use a number you control and keep that number secure and current. Codes expire and repeated requests are limited. A verification code must not be shared with another person. SMS sign-in is separate from device identity verification for encrypted conversations; a successful sign-in does not automatically approve access to encrypted history. Available registration, sign-in and recovery methods may change through service settings; the interface identifies available backup methods.