Security Practices
How No2Wait protects account access, passwords, OTPs, uploads, admin access, moderation, and production operations.
Last updated August 15, 2026Account Protection
Passwords are stored as hashes and are not stored as readable text. Users should choose strong passwords, keep OTPs private, and sign out from shared devices.
Email OTPs, password reset flows, and Google sign-in are used to reduce account takeover risk. No2Wait may rate-limit suspicious signup, sign-in, OTP, upload, itinerary, and location verification activity.
Admin And Support Controls
Admin access is limited to approved No2Wait operators through backend access rules. Admin actions may be logged for accountability and platform safety.
Support and itinerary workflows may use account, event, location, and ticket details only as needed to resolve requests, show in-app itineraries, or handle safety reports.
Uploads And User-Generated Content
No2Wait may validate uploaded files by type, size, and safety rules before storage or display. Unsafe, illegal, abusive, misleading, spammy, or harmful content may be removed or restricted.
Users can report posts or contact support when they see unsafe content, impersonation, harassment, fraud, or policy violations.
Production Monitoring
Production services may use logs, diagnostics, and crash/error reporting to protect reliability, detect abuse, troubleshoot issues, and improve platform security.
No digital service can guarantee complete security. Users should report suspected account misuse, suspicious messages, or security concerns to support as soon as possible.
Contact
For security concerns, contact support@no2wait.in.