Privacy Policy
CRITICAL ANTI-PHISHING & DATA PRIVACY ADVISORY
onetest and its creators will NEVER, under any circumstance, ask for your personal details, passwords, account information, email credentials, or phone numbers.
Kindly DO NOT share any personal data or credentials with anyone — even if someone claims to be us, impersonates Raheman, or asks on our behalf. onetest has no accounts, no sign-up requirements, and no user databases.
1. Fundamental Privacy Philosophy
At onetest, your privacy is not merely a policy — it is the foundational architectural pillar of our software. Traditional online hardware diagnostic websites often inject tracking scripts, ad pixels, and data harvesting backends.
onetest was intentionally built to be the exact opposite: a 100% client-side, zero-knowledge hardware testing workstation. All diagnostic computation occurs entirely inside your web browser's temporary memory (RAM).
2. Zero Personal Data Collected
We do not collect, process, sell, rent, or store any personal information. Specifically:
- No Account Information: You do not need to register, log in, or provide any identity to test your hardware.
- No Keystroke Logging: Every keystroke you type on the Keyboard Tester is captured purely by standard browser DOM events (
KeyboardEvent) to colorize the keycap on your display and measure latency. Keystrokes are never recorded, saved to a file, or transmitted over any network socket. - No Audio or Voice Storage: Microphone and sound testing utilize the browser's native Web Audio API (
AudioContext). Audio streams are visualized locally as waveforms and FFT frequency bars and are immediately discarded from memory. - No Camera Frames or Video Recordings: Camera testing utilizes the native WebRTC pipeline (
getUserMedia) to draw a local real-time feed directly to an HTML5 video canvas. No video stream or screenshot is ever captured, encoded, or sent to any server. - No Pointer or Touch Tracking: Mouse clicks, scroll intervals, and touchscreen finger coordinates are processed locally to test sensor health and digitizer matrix response.
3. Volatile In-Memory Lifecycle
All hardware diagnostic telemetry, input timestamps, and test counts exist exclusively in your browser's volatile JavaScript memory for the current session:
Instant RAM Purge: Pressing Refresh (F5 or Ctrl+R) or closing your browser tab permanently purges 100% of temporary testing states from system memory.
4. Local Storage & Cookies
We do not use tracking cookies, marketing cookies, or profiling identifiers. The only browser storage used is standard HTML5 localStorage, strictly reserved for non-identifiable client settings:
onetest-theme: Remembers your selected display theme preference (darkorlight).onetest-sound-mute: Remembers whether you have typing switch sound effects enabled or muted.
This data stays exclusively on your device and is never synchronized to an external database.
5. Camera & Microphone Permissions
When utilizing the Camera or Microphone diagnostic tools, your browser will prompt for permission via standard security dialogs:
- Permissions are used solely for the duration of the active test.
- You can revoke permissions at any moment through your browser's site settings or by toggling off the camera/mic switches inside onetest.
6. Infrastructure & Security
onetest is pre-rendered as a static Multi-Page Application (MPA). Static assets (HTML, CSS, JS, fonts) are delivered over secure, encrypted HTTPS. Standard web server access logs (such as IP address and user-agent requested by web servers to deliver files over TCP/IP) are maintained strictly for network routing, DDoS mitigation, and system availability.
7. Questions & Verification
onetest is an open-source-minded diagnostic project engineered by Raheman. If you have any inquiries regarding our privacy standards or wish to audit our client-side architecture, please reach out directly: