Ringwake privacy policy
Last updated October 16, 2026
Effective 16 October 2026. This policy covers the app Ringwake (com.tudiapps.ringwake), published by Gurmehub under the TudiApps brand. Our general privacy policy covers the website and our other apps.
In short: Ringwake is a phone app for your company’s own FreePBX phone system. Your calls, the company directory and your extension live on your company’s PBX, so your employer decides how that data is used. We only run a small relay that wakes the app when a call comes in; the caller’s details in that notification are end-to-end encrypted, so neither we nor Google can read them. There are no ads, no analytics and no account with us.
Who is responsible
Ringwake works only with a PBX that has the Ringwake module installed by your company. Your employer is the data controller for calls, call records, the directory and your extension settings. Gurmehub acts as a processor only for the push relay described below. Questions about your calls or the directory should go to your company’s administrator first.
What stays on your phone
- Your extension settings (server address, extension, password): stored only on the phone, encrypted with the Android Keystore, and sent only to your company’s PBX.
- Recent calls and favourites: stored only on the phone.
- Company directory: downloaded from your company’s PBX and kept on the phone so you can search it offline. Ringwake does not read your phone’s own contacts.
- Microphone: used only during a call. Your voice is sent to your company’s PBX encrypted with SRTP and is never recorded by the app.
- Camera: used only to scan the setup QR code your administrator gives you. The image is not stored or sent anywhere.
Waking the app for calls
Ringwake does not keep a connection open in the background, to save battery. When a call arrives, your company’s PBX asks our relay to send a push notification through Google Firebase Cloud Messaging, which wakes the app so it can ring.
- Your phone’s push token is registered with your company’s PBX. The PBX includes it in each wake-up request so the relay can deliver it; the relay does not store the token.
- The caller’s number and name are encrypted on the PBX with a key that only your phone holds. The relay and Google pass the encrypted message on without being able to read it.
- The relay keeps only technical records: which PBX and which device received a push, and when. These records are used to check the company’s licence and are deleted after 30 days without a push.
What leaves the phone, and where
| What | Where to | Why |
|---|---|---|
| Your voice during calls, call signalling, extension sign-in | Your company’s PBX (encrypted with TLS and SRTP) | To make and receive calls |
| Push token, device ID, phone model, app version | Your company’s PBX | To register the phone and wake it for calls |
| Encrypted wake-up message | Our push relay, then Google Firebase Cloud Messaging (Google LLC) | To deliver incoming calls; neither can read the caller’s details |
| PBX ID, device ID, time of the last push | Our push relay | Licence and seat checks; deleted after 30 days |
Ringwake contains no advertising, analytics or crash-reporting SDKs. We never sell your data or use it for advertising.
Deleting your data
- Sign out in the app’s settings removes your extension, recent calls, favourites and the cached directory from the phone. Uninstalling the app does the same.
- Your company’s administrator can remove your phone from the PBX at any time; it then stops receiving calls.
- Relay records are deleted automatically 30 days after the last push. To have them removed sooner, write to [email protected] with your company name; we act on requests within 30 days. You can also use our data deletion page.
- Call records and the directory on your company’s PBX are managed by your employer; ask your administrator.
Children
Ringwake is a business app for employees and is not directed to children.
Your rights
Depending on where you live (including under the GDPR and KVKK), you can ask to access, correct or delete your data and object to its use. For data on your company’s PBX, contact your employer as the controller. For the push relay, write to [email protected].
Changes
When this policy changes we update this page and the date at the top.