Privacy policy
App: Wakey Wakey (iOS) Document version: 1.0 Effective date: 21 August 2026
In short
Wakey Wakey collects no personal data.
The app has no user account, no server, no usage analytics, no advertising and no trackers. It has no network connection at all: everything you enter — your alarms — stays in your iPhone's memory and never leaves it. The publisher has no technical means of accessing it.
The rest of this document details how that works, along with the system permissions the app requests and exactly what each one allows.
1. Data controller
| Publisher | Romain Caille — natural person, publishing in a non-professional capacity |
| Contact | hello@romain-caille.fr |
| Data Protection Officer (DPO) | Not appointed — an appointment is not required, as the app carries out no processing of personal data on the publisher's behalf. |
2. Data handled by the app
All data below is stored locally, in the app's private container on your device (the
alarms.json file in the Application Support directory, protected by iOS storage
encryption). None of it is transmitted to the publisher or to any third party.
| Data | Source | Purpose | Retention |
|---|---|---|---|
| Alarm hour and minute | Entered by you | Trigger the alarm at the intended time | Until the alarm or the app is deleted |
| Repeat days | Entered by you | Schedule recurring alarms | Same |
| Mission type and difficulty | Entered by you | Know which challenge to present on waking | Same |
| Contents of the reference QR / barcode | Scanned by you during setup | Check, on waking, that the right code was scanned | Same |
| Alarm enabled/disabled state | Entered by you | Enable or suspend an alarm | Same |
| Internal technical identifiers (UUIDs) | Generated by the app | Match an alarm to the iOS system timer | Same |
None of this information identifies you in itself. It is not analysed, not profiled, and not cross-referenced with anything.
No usage data is recorded: no actual wake-up times, no count of dismissals, no mission durations, no statistics, and no crash logs transmitted to the publisher.
3. System permissions requested
3.1 Alarms (AlarmKit)
The app requests permission to schedule system alarms so that the sound can ring through Silent mode, through Focus modes, and while the app is closed. Alarm times are then entrusted to the iOS alarm service, a component of your device's operating system. That processing happens entirely on the device, under Apple's control, and is governed by Apple's privacy policy: https://www.apple.com/legal/privacy/.
3.2 Camera
Camera access is requested only if you choose the "QR / barcode" mission. The video stream is analysed in real time and exclusively on the device (Apple's VisionKit framework) to detect a code.
No photo, no video and no image is ever saved — neither on the device nor anywhere else. Only the character string contained in the code (a barcode number, for instance) is stored locally, and only when you set your alarm's reference code.
You can revoke this permission at any time in Settings ▸ Wakey Wakey ▸ Camera. The "QR / barcode" mission then stops working; the other missions are unaffected.
3.3 Motion sensors
The "Shake" mission reads the device's accelerometer for the duration of the mission, in order to detect shaking. The readings are processed in memory, in real time, and are neither stored nor transmitted. This requires no iOS permission and involves neither location, nor physical activity, nor health data.
3.4 Notifications and Live Activities
The app displays a countdown ("Live Activity") before the alarm rings. That display is rendered locally by the system; it involves no remote notification server and no push token.
4. What the app does not do
- ❌ No account, no sign-up, no email address requested
- ❌ No internet connection, no server, no remote API
- ❌ No audience measurement or analytics tooling (Firebase, Google Analytics, etc.)
- ❌ No advertising SDK, no advertising identifier (IDFA), no cross-app tracking (App Tracking Transparency does not apply)
- ❌ No cookies, no trackers
- ❌ No iCloud sync, no backup to the publisher's servers
- ❌ No sale, rental or disclosure of data to third parties
- ❌ No transfer of data outside the European Union
5. Processors and recipients
The publisher uses no processor within the meaning of article 28 GDPR, since no data is transmitted to them.
One third party is nevertheless involved in distributing the app: Apple. When you download Wakey Wakey from the App Store, Apple processes data tied to your Apple Account (the download, any purchases, and crash reports if you have allowed them in your device settings). That processing is Apple's sole responsibility and is governed by Apple's privacy policy, over which the publisher has no control. If you have enabled sharing analytics with developers in Settings ▸ Privacy & Security ▸ Analytics & Improvements, Apple may pass on to the publisher aggregated and anonymous crash reports, containing no identifying data.
6. iCloud and device backups
If you have enabled iCloud Backup or an encrypted computer backup, the app's container — and therefore your list of alarms — may be included in that backup, as with any iOS app. The backup is performed by Apple, under your control and according to your settings; the publisher has no access to it. You can exclude the app in Settings ▸ [your name] ▸ iCloud ▸ Backup.
7. Legal basis
To the extent that the information you enter remains on your device and is neither collected nor consulted by the publisher, the GDPR does not apply to any processing carried out by the publisher.
For the technical access performed locally by the app, the legal basis is performance of the contract (article 6(1)(b) GDPR): without an alarm time, the app cannot deliver the requested service. Camera access additionally rests on your consent (article 6(1)(a)), given through the iOS dialog and revocable at any time.
8. Retention
Data remains on your device for as long as you keep the app. It is erased:
- immediately, when you delete an alarm in the app;
- entirely and permanently, when you uninstall the app — iOS then destroys its whole container, including the alarms file.
No copy remains with the publisher, who never received one.
9. Security
Data is protected by the iOS security mechanisms: app sandboxing, storage encryption tied to the device passcode, and the complete absence of network attack surface, since the app opens no connection.
10. Your rights
The GDPR (articles 15 to 22) grants you rights of access, rectification, erasure, restriction, objection and portability. Given the app's architecture, you exercise them directly and without an intermediary:
- Access and rectification: all your data is visible and editable in each alarm's edit screen.
- Erasure: delete the alarm in question, or uninstall the app.
- Portability: the
alarms.jsonfile can be extracted through a local device backup.
Since the publisher holds no data about you, they are not in a position to answer an access or erasure request concerning content they do not possess. For any question, write to hello@romain-caille.fr.
You also have the right to lodge a complaint with the French data protection authority, the CNIL: 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France — https://www.cnil.fr. If you reside in another EU country, you may lodge your complaint with your own national supervisory authority.
11. Minors
The app is not specifically aimed at children and collects no data, whatever the user's age. The age rating applied on the App Store is shown on the app's page.
12. Changes to this policy
This policy may be updated, in particular if the app's features change. Any amended version is published at this same address, with a new effective date. Should a change ever entail data collection — which is not the case today — you would be informed in the app before it takes effect, and your consent would be obtained where the law requires it.
13. Contact
For any question about this policy: hello@romain-caille.fr.
Language. This document is a translation provided for convenience. The French version is the reference text.