Privacy Policy
Only share details that would still be safe if copied into a public forum. Error diagnosis rarely needs OTP, complete phone numbers, identity documents or wallet screenshots.
1. Basic technical signals
- Browser type, referrer, screen size, request time and visited route may be visible in server logs.
- Outbound clicks may be counted to identify broken paths, confusing redirects and unsafe navigation patterns.
- Comment fields may store the text you choose to enter in your browser or on the site.
2. Private data to exclude
Do not enter OTP, password, PAN/Aadhaar details, full phone number, account ID, wallet balance, QR code, payment proof or recovery code into public areas.
3. How route data is useful
Aggregate traffic and click behavior can show which app routes fail, which pages create repeated errors and where users may need clearer safety warnings.
4. After leaving the site
External destinations control their own data handling. Check the destination domain, app identity and policy before logging in, downloading APKs or entering payment details.
5. Safer screenshot habits
- Crop phone number, OTP, wallet, KYC and QR areas before sharing an error image.
- Use device model, Android version, APK filename and exact error text instead of private identifiers.
- For account-specific recovery, use the verified app route rather than public discussion.