Phone Sign-in and Contacts

Effective 17 October 2026. This supplement forms part of the FNF Privacy Policy and describes these features where enabled.

FNF is operated by Indian Networks, K-142, Shivalik Nagar, Haridwar, Uttarakhand, India. Contact our verified privacy-request form or fnf@fnfmeet.com.

Account setup

We process your mobile number and its verification status, name, username, nickname, stated age and optional photo to operate your account. Your age is used to check eligibility and is not included in public profiles or contact-search results. Your nickname, username and chosen photo identify you to other users.

PIN, fingerprints and new devices

The six-digit sign-in PIN is separate from the optional four-digit app safety lock. The server stores a protected password hash, not your PIN. Trusted devices hold random sign-in credentials in protected local storage. Android fingerprint sign-in uses a device-held signing key unlocked through Android's biometric prompt. FNF does not receive fingerprint images or biometric templates; the server holds the corresponding public key.

A new device requires verification. A five-minute new-device sign-in code is first made available inside an eligible approved FNF device. If you request another delivery option, the same code is sent to your verified email, where available, then by SMS on a further request. Registration and PIN recovery may require SMS directly. Only approve requests you initiated. Approving and showing a code on an approved encryption device authorizes the exact new encryption identity presented by that sign-in attempt. SMS verification alone does not provide an existing device's encryption approval or recover lost encrypted history. Approved devices can transfer available saved history using encrypted transfers, while an existing device holding that history is online. Resetting your sign-in PIN ends existing sign-in sessions and invalidates trusted sign-in credentials; it does not give FNF your private encryption keys.

We process request times, device identifiers, public keys, approval signatures, sessions and security events to protect accounts. Codes expire, have attempt limits and cannot be reused after verification. Push notifications contain no code. The configured SMS provider, currently 2Factor, processes the destination number and verification message. Generic alerts may use the notification providers described in the main policy.

Suggested country

The calling-code selector can suggest a country from your public IP address using country.is, which receives that IP address. The suggestion is approximate and changeable; it does not prove location or identity.

Finding friends

Contact discovery runs after you choose to share contacts and grant any required device permission. FNF processes normalized phone numbers to match registered accounts. Address-book names stay on your device. Submitted numbers are used for matching and are not saved as a server address book. Account phone numbers remain part of their owners' account records. Matches exclude blocked and unavailable accounts. Turn off being found by number under Phone number privacy.

Invitations open personalized SMS drafts in your messaging app. You decide whether to send them; FNF does not send invitations automatically. Carrier charges may apply. You can decline contact access and continue using FNF.

Administrators may provision an account with optional initial phone verification. A temporary PIN must be replaced during setup. An unverified number is not marked verified or used for contact discovery. Additional-device encryption approval remains required.