Privacy Policy

Information collected on the website

If you apply for the beta, we collect the email address you submit, the source or campaign label attached to the visit when available, and timestamps needed to manage the waitlist and understand which channels are working.

The landing page also uses a random first-party visitor identifier stored in your browser. The server combines that identifier with the UTC day and source into a deduplicated visitor-day record and aggregate counts. It is not intended to identify you by name.

Information collected in the app

Depending on how you use the beta, WakeFlow may store an authentication identifier and email address, alarm settings, routine selection, progress and completion information, app and device diagnostics, and feedback that you choose to send.

You may optionally share research consent and limited demographic information for product research. Research sharing is optional and can be withdrawn by contacting us.

Camera, pose, and face-related data

WakeFlow uses the iPhone camera and Apple’s on-device Vision framework during movement routines to detect a human body pose. This processing temporarily derives pose landmarks, including nose and neck coordinates, which Apple may classify as face-related data. WakeFlow uses these transient coordinates only to determine body positioning and movement progress during the active routine.

Camera frames, photographs, videos, face images, facial geometry, face templates, and raw pose landmarks are not uploaded or transmitted to WakeFlow servers or Firebase, are not shared with third parties, and are not used for identification, authentication, advertising, or profiling.

Camera frames and derived landmarks are processed only in volatile memory on the device. They are overwritten during processing and cleared when the camera session ends. WakeFlow retains no face-related data after the active camera session, so there is no stored face-related data requiring later deletion.

You can control camera access through iOS permissions. If camera access is unavailable, some WakeFlow routines may not work.

How we use information

• Provide, operate, support, and communicate about the beta.
• Confirm device fit and send beta-related email when you request access.
• Save your settings and progress across supported beta sessions.
• Diagnose reliability, improve the product, and understand aggregate usage when permitted.
• Protect the service, prevent abuse, and comply with applicable obligations.

Analytics and service providers

WakeFlow uses Firebase services, including Firebase Authentication, Firestore, and consent-gated Firebase Analytics or related infrastructure, to operate the service and store the information described above. These providers process information on our behalf under their own service terms and privacy practices.

The current beta does not sell personal information. We do not use camera frames for advertising or behavioral profiling.

Retention and deletion

We keep information for as long as reasonably needed to operate the beta, provide support, maintain security, resolve disputes, and understand product performance. We may keep aggregated or de-identified information after individual records are deleted.

Email us to request access, correction, withdrawal of optional research consent, or deletion of information associated with you. We may need to verify the request and may retain limited information where required for security or legal reasons.

Children and third-party links

WakeFlow is not directed to children under 13, and we do not knowingly collect personal information from children under 13. The website may link to third-party services, including Apple or authentication providers. Their policies govern information they process directly.

Changes to this policy

We may update this policy as WakeFlow changes. The effective date above shows when this version was published. If a change is material, we will use a reasonable notice method available to us.