Skip to content

Privacy Policy for WakeGate

This privacy policy applies specifically to the product WakeGate.

1. Data controller and contact

The controller for the WakeGate app is Tom Silas Helmke, c/o Online-Impressum #4746, Europaring 90, 53757 Sankt Augustin, Germany. Contact: tshfm78@gmail.com.

2. Scope

This policy describes processing by the WakeGate app. Processing when visiting tommsel.com, including hosting and any website services, is described in the general tommsel.com privacy policy.

3. Local first and no account

WakeGate is locally oriented. The app uses no user account, no custom backend, no custom server database, and no custom cloud synchronization.

4. App data stored locally

WakeGate stores data on the device including alarm times, alarm names, repeat rules, snooze settings, alarm-sound selection, mission and exercise settings, NFC configurations, wake history, and app settings. WakeGate does not transmit this data to its own servers.

5. Camera and exercise missions

The camera is used only during an Exercise Mission. WakeGate processes camera images or frames with AVFoundation and Apple Vision Human Body Pose Detection on the device to count or assess movement needed for the mission. Images and frames are not stored, uploaded, sent to custom servers, or used for advertising. WakeGate does not use facial recognition, identify people, or perform medical or fitness diagnosis.

6. NFC and NDEF data

WakeGate uses CoreNFC for NFC missions. It writes a WakeGate NDEF record with a randomly generated WakeGate token to compatible tags. Only the SHA-256 hash of that token is stored locally for assignment. A hardware UID is not used as an identity, and no location data is automatically obtained from a tag. Optional tag names, such as Kitchen, are assigned locally by the user. Existing writable tags are overwritten only after explicit confirmation; the NDEF area can be cleared only on user action. This is not a factory reset or deletion of all physical tag memory.

7. AlarmKit, widgets, and system functions

WakeGate uses Apple’s AlarmKit to schedule alarms through the system alarm infrastructure. Widgets, Live Activities, a Control Center control, and the current system media-volume status may be used for app functions. WakeGate cannot set system media volume to a fixed value. Processing by iOS and Apple system services is separate from WakeGate’s own processing.

8. StoreKit and purchases

WakeGate uses Apple StoreKit 2 for optional Pro subscriptions. Purchases, payments, price and currency display, management, and restoration are handled through Apple and the Apple ID. WakeGate does not process payment data itself. Apple’s processing is governed by Apple’s privacy information.

9. No analytics, advertising, or tracking

WakeGate uses no app analytics, tracking, or advertising.

10. Data sources not used

WakeGate uses no microphone, location collection, contacts, photo library, or HealthKit. This statement must be checked again against the final app code before release.

11. Deleting data

Local data can be deleted through app functions and settings and by removing the app from the device. Available iOS options can differ.

12. Your rights and right to lodge a complaint

Where the legal requirements are met, you have rights of access, rectification, erasure, restriction of processing, data portability, and objection. You can contact tshfm78@gmail.com and have the right to lodge a complaint with a data-protection supervisory authority.

13. Effective date

Last updated: September 2026. This policy will be updated if WakeGate features or data processing change.

Last updated: September 2026