This policy explains how the Nadeem mobile messaging service collects and uses information. Nadeem provides account authentication, direct and supported conversation experiences, attachments, device sessions, safety controls, and optional push notifications.
Information we process
- Account identifiers supplied by UsersLife or verified mobile sign-in, plus profile details such as display name, email address, or mobile number when available.
- Device and session information, including install and device identifiers, app/platform version, session activity, and push tokens. Authentication and push tokens are not included in account exports.
- User-generated content (UGC), including messages, replies, conversation membership, and attachments, together with delivery, read, and deletion state.
- Preferences for read receipts, online status, notification categories, and message previews.
- Safety information, including blocks, reports, report categories, and audit records used to investigate abuse.
- Support requests, including the reply email, selected topic, request message, status, and support audit history.
- Security and operational records such as sign-in attempts, connection activity, export/deletion events, and limited delivery diagnostics.
How we use information
We use information to authenticate accounts, deliver and synchronize conversations, send enabled notifications, enforce privacy preferences and blocks, prevent abuse, respond to safety reports, protect accounts, provide support, and meet applicable legal obligations.
Sharing and service providers
Conversation content is shared with the people participating in that conversation. We may use UsersLife for identity, an SMS provider for one-time codes, Firebase Cloud Messaging or Apple push infrastructure for notifications, and contracted hosting/storage providers. These providers process only the information needed to perform their service. We may disclose information where legally required or necessary to protect users and the service.
Your choices
You can control read receipts, online status, message previews, and notification categories in the app. Blocking is enforced for direct messaging, presence, and inbox visibility. You can report a user or message. You may request a portable account-data export from Me → Storage and account data.
Retention and deletion
Me → Delete account lets you remove your profile identity, contact details, login links, recovery credentials, sent message bodies and uploaded file bytes from Nadeem. Delete now starts processing automatically. Where offered, Delete after 7 days signs you out immediately and keeps the account data for a seven-day cancellation period. Cancel before the displayed deadline from the signed-out receipt screen using the private confirmation code and a verified sign-in method linked to the account. Permanent deletion starts automatically when that period ends. Keep the confirmation code to check progress and completion from the receipt screen or status page. Other participants' own messages and the conversation structure remain. Copies already downloaded by recipients and independently managed services are not recalled. Earlier identity-only requests retain their original disclosed scope. The former public username is retained only as an undiscoverable hashed reservation to prevent impersonation.
Support, safety, security and audit records may also remain, as may backups. Earlier requests with a displayed cancellation period keep their existing schedule. Accounts and data held separately by UsersLife or another provider follow that provider's process.
Security and age
We use access controls, token hashing, audit trails, private attachment storage, and transport security. No system can guarantee absolute security. Use Nadeem only if you meet the age and consent requirements that apply in your country and app marketplace.
Contact and changes
For privacy help, use Me → Help and about in Nadeem or submit the secure public support form. Never send a password, one-time code, access token, or private cryptographic key. Material policy changes will use a new version and require consent where appropriate.