MilnaZaroor is currently a free, Google Play-only beta. No paid checkout or subscription is offered during this beta.
Last updated: September 8, 2026
Overview
Milnazaroor is a transparent, consent-first social and real-world meeting network. Privacy controls are part of the product model: users choose profile visibility, discovery participation, explicit interests and tastes, locality scope, availability, connections, and other sharing states.
This Privacy Policy explains what information Milnazaroor may handle, why it is used, how sharing is bounded, and what choices users have.
Milnazaroor is designed and operated by Amretra Dynamics, Sole Proprietorship, Musrif Abhinav, Mahbubnagar, Telangana – 509001, India.
Contact: contact@amretra.com
Information Milnazaroor may collect
Depending on the features you use, Milnazaroor may handle:
- phone number and authentication/session information;
- profile information such as name, age, city, coarse area, bio, languages, and visibility choices;
- interests and TasteSync values you explicitly submit, such as music, movies, fashion, beauty/presentation, travel, and activities;
- compatibility weights and deterministic compatibility results derived from eligible explicit inputs;
- coarse locality scope, distance/radius settings, and availability windows you choose to provide;
- connection requests, connection state, conversations, and messages;
- communities, memberships, posts, events, RSVPs, organizer announcements, attendance state, and meet plans;
- safety settings, blocks, reports, moderation actions, and evidence references submitted through safety tools;
- portability/export requests and optional user-owned identity or credential records where supported;
- payment orders, entitlement state, refunds, and contribution-economics records for paid features;
- device, browser, session, network, abuse-prevention, diagnostics, and service reliability signals;
- support requests and communications with Milnazaroor.
Milnazaroor should not require precise live location for ordinary discovery. Where a feature uses more specific meetup information, access is intended to be limited to the relevant authorized participants and product state.
Why information is used
Milnazaroor may process information to:
- create, authenticate, secure, and recover accounts and sessions;
- store and display profile information according to visibility settings;
- compute explainable compatibility using documented deterministic factors;
- support mutual connection requests and messaging;
- operate communities, events, RSVPs, meet plans, and organizer tools;
- enforce locality, availability, consent, block, report, and moderation rules;
- create account-linked exports and portability bundles without exposing another user's private fields;
- operate paid entitlements, payment reconciliation, refunds, and unit-economics accounting;
- prevent fraud, abuse, unauthorized access, spam, and safety violations;
- maintain backups, migrations, auditability, reliability, and incident response;
- comply with legal obligations and enforce applicable terms.
Explainable compatibility
Canonical Milnazaroor discovery is designed to use explicit stored profile, interest, taste, and documented rule inputs rather than hidden engagement ranking.
Compatibility values do not create consent, availability, or a connection. A compatibility result is product context based on eligible inputs; it is not a prediction or guarantee about another person.
Milnazaroor does not use protected or sensitive-trait inference as a required basis for canonical discovery.
Messages and social content
Messages and other social content are processed so the intended participants can use the relevant feature and so Milnazaroor can enforce authorization, safety, abuse prevention, recovery, and retention rules.
Realtime delivery hints are not intended to replace durable message records. Where realtime infrastructure is used, delivery events should carry only the minimum routing/state information required and should not expose message bodies unnecessarily.
Community and event content may be visible to different audiences depending on the object's visibility and the viewer's membership, RSVP, organizer, moderation, or other authorized state.
Location and meetup information
Milnazaroor is designed around minimum necessary location disclosure.
- Discovery should use coarse city/area scope rather than precise live coordinates by default.
- Availability is an explicit user action and is separate from compatibility.
- Precise meetup details should not become broadly discoverable merely because two users have similar interests or tastes.
- More specific meetup information may be shown only where the relevant connection, event, meet-plan, or authorization state permits it.
- Users may change or revoke applicable visibility and availability settings through product controls where supported.
Blocking, reporting, and safety records
Blocking is intended to restrict future discovery/contact paths according to the product's safety policy. Reports may contain reason codes, user-supplied detail, and evidence references.
Report evidence and internal moderation information are restricted to authorized purposes and are not ordinary profile data. Milnazaroor may retain some safety records after other account data is deleted where reasonably necessary to prevent abuse, investigate incidents, comply with law, or enforce platform safety.
Portability and exports
Milnazaroor may allow users to export eligible data associated with their own account.
Exports are designed not to include another person's private profile fields, secrets, internal security material, or moderation information that the requesting user is not authorized to access. Some shared records may be represented only to the extent necessary to explain the requesting user's own relationship or activity state.
Payments and paid features
If you use a paid feature such as Organizer Plus, Milnazaroor and its payment processor may handle order identifiers, payment status, payment-provider references, plan information, amounts, refunds, and related accounting records.
Milnazaroor's internal contribution-economics records may store observed processor fees and measured variable service costs linked to a payment order. These records are used for operational accounting and do not create additional social-profile ranking signals.
Do not send full card or bank credentials directly to Milnazaroor unless a product flow explicitly requires it; supported payment providers should handle payment credentials through their approved interfaces.
Service providers and sharing
Milnazaroor may use service providers where reasonably necessary for functions such as:
- cloud infrastructure, databases, storage, content delivery, queues, monitoring, and backups;
- authentication, phone/SMS verification, or identity services;
- payment processing;
- email, SMS, or other communications explicitly used by a product flow;
- security, abuse prevention, diagnostics, and incident response;
- professional, accounting, or legal services.
Information should be limited to what the provider needs for the relevant purpose. Milnazaroor does not sell user data to advertisers and is not designed around ad-targeting or engagement-ranking economics.
Canonical discovery and mutual connection do not require model-provider credentials. Historical compatibility code may remain isolated during migration, but it is not the source of truth for the forward social product.
Cookies, sessions, and device storage
Milnazaroor may use cookies, secure session records, device identifiers, and local application storage to:
- keep users authenticated;
- maintain product-session state;
- protect account integrity;
- recover durable application state;
- support device-specific preferences and bounded offline/retry behavior.
Authentication secrets and bearer material should not be exposed through ordinary logs, analytics, URLs, or public client configuration.
Data retention
Retention varies by data type and purpose. Milnazaroor aims to keep information only for as long as reasonably necessary for:
- active service operation and account continuity;
- user-requested exports, portability, or recovery;
- safety, fraud, moderation, and abuse prevention;
- payment, accounting, tax, or refund records;
- backups, migration verification, and incident recovery;
- disputes, legal claims, and applicable legal obligations.
Deletion from the active product may not immediately remove every copy from bounded backups or legally required records. Such retained copies should not be restored into ordinary active use except for legitimate recovery, legal, security, or safety purposes.
Security
Milnazaroor uses technical and organizational controls intended to protect personal information, including authenticated sessions, authorization checks, encrypted transport, secret-management practices, bounded logging, abuse controls, migrations, and restricted operational access.
No online service can promise absolute security. Users should protect their devices, phone or identity account, and session access and should report suspected unauthorized access.
International processing
Service providers may operate in different regions. As a result, some information may be processed outside the user's state or country as part of infrastructure, security, communications, or payment operations, subject to applicable law and provider safeguards.
Your controls and requests
Product controls may allow users to:
- update profile information, interests, tastes, visibility, and discovery participation;
- manage locality/availability and applicable safety settings;
- accept, decline, withdraw, or otherwise manage connection state;
- block or report users;
- manage community/event participation;
- request profile/social exports or portability where available;
- request account deletion or closure, subject to documented retention boundaries.
For privacy questions, access/correction/deletion requests, or support, contact contact@amretra.com.
Children
Milnazaroor is not intended for anyone under 18. If we reasonably learn that an underage person has created an account, we may restrict or remove the account and associated access subject to applicable safety and legal requirements.
Changes to this policy
We may update this Privacy Policy to reflect product, infrastructure, legal, or safety changes. Material changes will be reflected in the updated date and, where appropriate, communicated through the product or website.
Contact
For privacy questions or requests, contact contact@amretra.com.
© 2026 Amretra Dynamics. All rights reserved.