MilnaZaroor is currently a free, Google Play-only beta. No paid checkout or subscription is offered during this beta.
Last updated: September 8, 2026
Purpose
This notice explains how Milnazaroor protects personal information handled through the transparent, consent-first social and real-world meeting network. It should be read together with the Privacy Policy and Terms of Service.
Core protection approach
Milnazaroor is designed around minimum necessary disclosure, authenticated access, explicit sharing state, and server-side authorization.
Our protection approach focuses on:
- keeping ordinary discovery on coarse city/area context rather than precise live location;
- separating compatibility from consent, availability, connection, and meetup authorization;
- limiting private messages and meetup information to authorized participants;
- enforcing block/report boundaries across discovery and contact paths;
- preventing secrets, bearer material, signing credentials, or private moderation evidence from entering public client configuration, ordinary analytics, URLs, or routine logs;
- preserving auditable state changes and recoverable durable state where the product promises them;
- using least-privilege access for operational and moderation roles.
Information requiring additional care
Contextually sensitive information may include:
- phone numbers and account/session identifiers;
- profile visibility settings and private profile fields;
- explicit interests, tastes, locality, and availability choices;
- private conversations and messages;
- precise meetup details when shared with authorized participants;
- blocks, reports, moderation records, and evidence references;
- payment, refund, and contribution-economics records;
- export/portability bundles and optional portable-identity records;
- device, fraud-prevention, security, and incident-response signals.
Compatibility results are derived from documented eligible inputs and do not create permission to access another person's private information.
Authentication and authorization
Milnazaroor uses authenticated sessions and server-side authorization intended to keep account-linked data within the correct user and role boundaries.
Authorization rules should be enforced independently of UI state. Sensitive operations must not rely on hidden buttons or client-side checks as their security boundary.
Production authentication must fail closed: development OTP/test bypasses are not permitted in production, and production verification state must not silently fall back to process-local test behavior.
Location and meeting-data protection
Location is intentionally bounded.
- Ordinary discovery uses coarse locality by default.
- Precise live coordinates are not required for canonical discovery.
- Compatibility does not unlock contact or meetup details.
- More specific meetup information is disclosed only when the relevant connection, event, RSVP, meet-plan, or authorization state allows it.
- Availability and location visibility should be reversible through product controls where supported.
Messaging and realtime delivery
Durable message storage is authoritative. Realtime transport, where enabled, is a delivery hint rather than a second message store.
Realtime events should carry only the minimum routing/state information required. Message bodies should not be copied into the realtime fanout plane when the client can recover authoritative content from the durable message API.
Blocks, reports, and moderation
Active blocks are intended to prevent future discovery/contact paths according to the safety policy. Report evidence and internal moderation state are restricted to authorized review purposes.
Safety records may require longer retention than ordinary profile content where reasonably necessary to investigate abuse, prevent repeated harm, comply with law, or maintain platform integrity.
Exports and portability
Export and portability tools should return the requesting user's eligible data without leaking another user's private fields, secrets, internal security material, or restricted moderation data.
Shared relationship records may be represented only to the extent necessary to explain the requesting user's own connection, community, event, or meetup state.
Storage, backups, and retention
Data is retained according to service, safety, accounting, legal, migration, backup, and recovery needs. Retention periods vary by data class.
Deletion from active product state may not immediately remove every bounded backup or legally required record. Retained backup copies should not be restored into ordinary active use except for legitimate recovery, legal, security, or safety purposes.
Schema changes and product migrations should preserve established account identifiers and verified identity links unless an explicitly tested migration requires otherwise.
Security measures
Milnazaroor may use measures including:
- encrypted network transport;
- secure session handling;
- server-side authorization and rate limiting;
- secret-management systems;
- restricted production access;
- bounded operational logging and audit trails;
- abuse detection and moderation controls;
- database migrations and backup/recovery procedures;
- serverless or metered infrastructure where appropriate to reduce unnecessary persistent attack surface and idle systems.
No online service can promise absolute security. Users should protect their devices, phone or identity account, and active sessions.
Service providers
Milnazaroor may rely on infrastructure, communications, identity, payment, monitoring, security, and professional service providers. Information should be limited to what the provider reasonably needs for the specific service being performed.
Canonical discovery and mutual connection do not require model-provider credentials.
User requests
Users may contact contact@amretra.com regarding:
- access to account-linked information;
- correction of inaccurate information;
- profile/social export or portability where available;
- account deletion, subject to documented legal and safety retention boundaries;
- privacy or data-protection concerns.
International processing
Some providers may operate in different regions, so information may be processed outside the user's state or country as part of legitimate infrastructure, security, communications, or payment operations, subject to applicable law and provider safeguards.
Contact
Data-protection questions may be sent to contact@amretra.com.
© 2026 Amretra Dynamics. All rights reserved.