At QualityTime, we believe that private personal communications belong exclusively to the people having them. Unlike conventional communication apps that process, inspect, or archive your conversations on corporate servers, QualityTime is engineered upon a peer-to-peer (P2P) architecture where your audio and video streams never pass through an intermediary media storage vault.
1. The Peer-to-Peer Architectural Model
QualityTime leverages the WebRTC (Web Real-Time Communication) standard. When you initiate a call:
- A lightweight signaling handshake occurs to exchange connection coordinates (IP/port ICE candidates).
- Once established, media streams (microphone voice and camera video) are encrypted end-to-end via DTLS-SRTP (Datagram Transport Layer Security - Secure Real-time Transport Protocol).
- Your media flows directly from your device to the peer device without stopping at or being recorded by any QualityTime database or media server.
2. What Information We Do NOT Collect
- Call Content: We do not record, transcribe, listen to, or save any voice, video, screen share, or animated reaction data.
- Media Attachments: Photos, PDF documents, and audio voice notes exchanged during active peer sessions are delivered directly and stored locally on your device.
- Local Customizations: Custom wallpapers, custom ringtones, volume settings, and backdrop blur adjustments remain 100% on your device's local file storage and are never uploaded.
3. Information Used Solely to Facilitate Service
- Signaling & Authentication: To route incoming calls and friend invitations, a random unique identifier (UID) or authenticated phone token is used by our signaling layer to notify the recipient that you are ringing them.
- Push Notifications (FCM): We use Firebase Cloud Messaging to send an encrypted wake-up signal to your phone when an incoming call arrives while the app is in the background or locked. No call content is included in notifications.
- Update Checks: The app periodically queries our public GitHub manifest (
update.json) to notify you of newer releases. No personal identifiers or telemetry are sent during this version check.
4. Device Permissions & Why They Are Required
To function as a high-performance communication tool, QualityTime requests the following Android permissions:
- Camera (
android.permission.CAMERA): Required to capture local video for 1080p and video calling. Activated strictly during active video calls or photo selection.
- Microphone (
android.permission.RECORD_AUDIO): Required to transmit audio through the Opus codec during calls and voice messages.
- Notifications & Full-Screen Intent: Required to ring your device on lockscreen when someone calls you.
- Storage / Media: Required only when you explicitly select a custom wallpaper or custom ringtone audio file from your device storage.
5. Security & Encryption Standards
All real-time streams utilize DTLS-SRTP encryption with modern cipher suites. Session encryption keys are generated randomly in volatile RAM for each call and are irreversibly purged when the call disconnects.
6. Third-Party Services
QualityTime uses open-source WebRTC libraries, Supabase for minimal authentication and signaling coordination, and Google Firebase for waking up Android devices upon incoming rings. We do not integrate third-party ad networks, tracking SDKs, or data brokers.
7. Contact & Security Reports
For security vulnerability disclosures, privacy inquiries, or developer questions, please open an inquiry on our official GitHub repository:
GitHub Repository: https://github.com/Sankha07x/qualitytime-releases
