RemoWake — Privacy Policy

Last updated: 29 September 2026 Controller: FaceyIT FZ-LLC, United Arab Emirates (operator of RemoWake) Contact: privacy@remowake.app

In one paragraph

RemoWake lets one person set time-anchored reminders on another person's phone, with that person's agreement. To do that we store a device identifier, the reminders themselves, the answers the recipient gives to each one, the organiser's subscription status as reported by Apple, and technical records needed to deliver them. We do not collect location, contacts, photos, health data, or the content of anything else on either phone. Our servers are in Malaysia.

1. Two roles, two different sets of data

RemoWake is one app used in two ways. What we hold depends on which.

The organiser (the person who sets reminders)

Data	Why	Kept
A random device identifier generated on the phone	To link the two phones to each other	Until the account is deleted
Device model, iOS version, time zone	To deliver correctly and to diagnose failures	Until deletion
The reminders they compose — title, time, day, type	This is the service	Until deleted or the pairing ends
A name they give a paired phone, e.g. "Mum"	Shown only to them	Until deletion
The name they give themselves, e.g. "Steve"	Shown on the recipient's phone next to every reminder they set ("Steve reminds you…") and in invitations	Until deletion
Subscription records from Apple — see section 1a	To know which plan is active, count connections, and reconnect a new phone or iPad	Until deletion

The recipient (the person the reminders are for)

Data	Why	Kept
A random device identifier generated on the phone	To receive the right reminders	Until unpaired or deleted
An Apple Push Notification token	So a change can reach the phone	Until it rotates or is deleted
Device model, iOS version, time zone, chosen language	To show the right time in the right language	Until deletion
The recipient's answer to each reminder — accepted, declined, or unanswered, with the time of the answer	The organiser is shown what they decided. This is what makes the app agreed care rather than remote control	Until deleted or the pairing ends
Which reminders the recipient has ticked off, with the date	So the organiser can see the day is going	Until deleted on request
Technical events: app opened, reminder scheduled, reminder dismissed, delivery received	To detect that a reminder silently failed to arrive	Until deleted on request

1a. Subscription records (organisers only)

The recipient never pays and nothing about money is ever stored for their phone. For the organiser, Apple sends us signed records that we verify before using:

Data	Why	Kept
Apple's app-transaction identifier — one per Apple ID for this app, the same on every device signed in to it	To count connections across all your devices, and to recognise you on a new phone or iPad so the people you already help reappear there	Until deletion
When the app first contacted us under your Apple ID, and the date Apple says it was first downloaded	The 14-day free period is counted from the first of these	Until deletion
For a purchase: Apple's original transaction identifier, the plan, and when it renews, lapses or was refunded	To know which plan is active	Until deletion
Notices Apple sends when a subscription renews, changes, lapses or is refunded	So the plan we see stays correct without the app being opened	Until deletion

We never receive card or bank details, or the name or email of your Apple ID. Payment is handled entirely by Apple.

1b. When a second organiser is invited

An organiser can invite another person to help the same recipient. We store the name of the person inviting, the name of the person invited, the recipient's answer and when it was given. Nothing changes on the recipient's phone until the recipient accepts.

2. What we never collect

This list is a commitment, not a description of the current version.

Location. Not at any accuracy, not in the background, never.
Contacts, photos, calendar, mail, messages, health or fitness data.
What either person does in any other app, or how the phone is used outside RemoWake.
Audio or the microphone.
Medication names, dosages, prescriptions, or any record of doses taken or missed. Reminder text is free text written by a family member; we neither interpret it nor build a health record from it. RemoWake is not a medical device and makes no clinical claim.
Advertising identifiers. There is no advertising in RemoWake and no third-party tracking SDK of any kind.

3. The reminder text itself

Titles are written by the organiser and shown to the recipient. We store them so they can be delivered, and we do not read them, analyse them, translate them, or use them to train anything.

Because the organiser is free to type whatever they wish, they should not put medical, financial or other sensitive detail into a reminder title. "Time for your tablets" is a reminder; the name of a drug is a medical record, and RemoWake is not built to hold one.

4. Consent is part of the product, not a checkbox

Nothing appears on the recipient's phone without them seeing it and answering. An unaccepted reminder is never scheduled. A declined reminder is not scheduled, and the organiser cannot override that decision — they can only ask again.

The recipient can end any reminder at any time from their own screen, and unpair the phone without the organiser's permission or knowledge.

The app always shows on the recipient's device who it is paired with.

5. Legal basis (EU/EEA — GDPR)

Purpose	Basis
Delivering the reminders both people asked for	Contract, Art. 6(1)(b)
Push delivery and technical failure diagnosis	Legitimate interests, Art. 6(1)(f) — a reminder that silently fails to arrive is the harm the service exists to prevent
Storing the recipient's answers to each reminder	Contract, and their explicit act of answering
Checking the organiser's subscription and counting connections	Contract, Art. 6(1)(b)

We do not process special-category data under Art. 9. Reminder text is not solicited as health information and is not treated as such.

6. Where the data is, and who else sees it

Servers: Malaysia. Our server is a virtual machine rented from a hosting provider (Hostinger); the provider stores it but does not access its contents.
Apple delivers push notifications on our behalf and receives the push token and the fact that a message was sent. Apple does not receive reminder text in a silent update. Apple also processes every payment and tells us, in signed records, which plan an organiser has; it does not tell us who they are.
No advertising networks, no analytics vendors, no data brokers. We sell nothing and share nothing for marketing.

7. Your rights

Either person may, at any time and without asking the other:

see what we hold about their device,
correct it,
end a pairing from the app at any time, with no email required,
have everything we hold erased, by writing to privacy@remowake.app,
take their data in a machine-readable form,
object to processing, or withdraw agreement.

Ending a pairing from the app takes effect immediately: the two phones stop exchanging anything, and reminders from that organiser stop being sent. It does not erase the records already written — see below.

We say the next part plainly because it is unusual. Our server keeps an append-only record — every change is written once and nothing is overwritten. That is what makes it possible to establish afterwards whether a reminder was actually delivered. It also means ending a pairing in the app does not by itself erase what has already been written.

Erasure of that record is done on request: write to privacy@remowake.app and every entry naming the device is removed within 30 days, backups included within a further 60. There is no automatic expiry today.

We would rather describe this than promise an automatic deletion the system does not perform.

Requests we cannot satisfy in the app: privacy@remowake.app. EU/EEA residents may complain to their national data protection authority.

8. Children

RemoWake is not directed at children and we do not knowingly hold data about anyone under 16. If a paired device belongs to a child, contact us and we will delete the records.

9. Security

TLS in transit. Access restricted to named operators. Push tokens are stored only for as long as they are valid and are replaced when Apple rotates them.

We do not claim to be unbreakable. We do claim that the amount of data we hold is small on purpose — the strongest privacy measure available to us is not collecting things, and it is the one we have used.

10. Changes

Material changes are announced in the app before they take effect. The date at the top of this document always reflects the current version.