Security is a continuous practice, not a promise that any online service can be risk-free. This page describes the safeguards and the limits that matter most to members.
Aware uses Firebase Authentication for account sessions and requires verified email for sensitive actions. Use a unique password, secure the email account connected to Aware, and sign out on shared devices. Google sign-in confirms the Google account email; it does not by itself grant an Aware verified badge.
Private bank/authority-report proof, verification documents, Aadhaar processing material, selfies, and verification videos are handled through restricted server and storage paths. Public profile, report, and asset-lookup views use curated fields rather than raw verification records. Never upload passwords, OTPs, card details, or an unmasked Aadhaar.
Fraud reports, social-post limits, protected-asset actions, ownership claims, verification approval, review decisions, scoring, and administrator actions are checked by server-side functions. Browser-visible buttons are not the source of authorization. A successful document upload or a client-side field change cannot create a verified badge or unlock verified features.
Where an Aware offer requires payment, use only the official payment flow and identified provider. Aware will never ask for a card number, UPI PIN, OTP, document, or payment in a direct message, call, or email. A browser message alone never activates a verified badge.
The service applies server-side rate limits and validation to selected registrations, uploads, searches, reports, and verification steps. We may suspend access, preserve relevant activity, or require review where we detect abuse, duplicate submissions, manipulation, or behavior that risks another member’s privacy or safety.
Last updated: September 8, 2026 · See also Privacy Policy.