Tester Privacy Policy
Specific Diagnostic Data Governance for Authorized Beta Testers • Last Revised: September 2026
1. Scope of This Tester Privacy Notice
This Tester Privacy Policy specifically supplements the general CoachingsNearMe Privacy Policy. It applies to individuals authorized to participate in our closed testing, staging builds, and pre-release Android APK evaluations.
Due to the experimental nature of beta software, our builds contain diagnostic instrumentation designed to pinpoint software anomalies, measure UI render latency, and track backend throughput.
2. Diagnostic Telemetry Collected During Testing
When running pre-release testing builds, the application may transmit the following diagnostic information:
💥Crash Reports & Stack Traces
Detailed Dart/Flutter stack traces, unhandled exceptions, thread states, and memory allocation snapshots at the time of an unexpected crash.
📱 Device Hardware Specifications
Device model (e.g., Pixel, Samsung Galaxy), Android OS version, SDK level, screen DPI, viewport height/width, and available system RAM.
⏱️API Performance & Network Logs
Fastify backend endpoint response times, HTTP status codes, network timeout occurrences, and payload parsing latency.
🧭 UX Session Breadcrumbs
Sequence of route navigations (e.g. from `/tester-welcome` to `/tester-info` to `/login`) to assist engineers in reproducing UI anomalies.
3. Tester Whitelist Authorization Data
To safeguard our pre-release environment from unauthorized public access, we maintain a secure whitelist containing:
- Authorized Indian mobile numbers permitted to request OTP codes during closed testing.
- Authorized Google OAuth emails permitted to authenticate.
- Designated tester roles (Internal Developer, QA Specialist, Pilot Student, Pilot Institute Owner).
This whitelist is stored securely in our in-memory access control layer and encrypted database, accessible only to our core engineering team.
🛡️4. Security Threat Monitoring & Telegram Alerts
Our backend runs an active threat-detector monitoring all incoming network calls. If a client attempts to execute vulnerability scans, sensitive path probes (e.g., /.env), or high-frequency 404 flooding:
- The calling IP is automatically placed in quarantine and throttled with HTTP 429.
- A real-time security alert card is dispatched to our engineering Telegram security channel detailing the threat category and payload.
5. Retention & Data Purging
Diagnostic logs and crash telemetry collected during test cycles are retained only for as long as necessary to debug and stabilize software builds (typically 30 to 90 days). Once an issue is remediated and verified in production, associated diagnostic logs are systematically purged.
Questions on Tester Telemetry?
If you have questions regarding diagnostic data collection or wish to remove your account from the testing whitelist, email us at: support@coachingsnearme.in.