Clerk
Provides optional account creation, Google and Apple sign-in, email-code sign-in, sessions, and account identity.
Privacy Policy
Effective 31 July 2026. This policy explains what the LumenApexflow iPhone app and website process, why, and what you can control.
Lumenshore Limited is the controller of personal information processed for LumenApexflow. It is registered in England and Wales under company number 09607326and has its registered office at Windsor House, Troon Way Business Centre, Humberstone Lane, Leicester, England, LE4 9HA.
Privacy and account-deletion requests may be made through the in-app Privacy Center where available. A written request may also be sent to the registered office above. We may need to verify that the requester controls the relevant account before acting.
Apexflow is local-first. The following information is stored on the device so the app can play rituals, remember choices, and work offline:
You can clear eligible local data in the Privacy Center. Removing the app also removes its local container, subject to the device and backup settings you control through Apple.
Google sign-in is optional. If you choose it, Google sends basic identity information to Clerk, our authentication provider, so we can create or recognise your Apexflow account:
We use this information only to authenticate you, protect the account, display its basic identity, and connect the optional account features described below. Apexflow does not request access to Gmail, Google Drive, Google Calendar, contacts, or other Google services, and does not use Google identity information for advertising.
An account is optional for local rituals. When you sign in and use sync, chat, support, or deletion features, the relevant information is sent to Lumenshore's authenticated service:
We process this information to provide the feature you chose, maintain account security, respond to support and deletion requests, prevent abuse, and keep the service reliable. We do not sell personal information or use it for behavioural advertising.
Royal requires a signed-in account so purchase access can follow the right person across devices. Apexflow sends RevenueCat only the opaque Clerk user identifier—not the account email, name, profile image, or other Clerk profile fields. Apple remains the payment processor; Lumenshore receives subscription state and transaction references, not full card details.
We disclose only the information needed for providers to perform services for Apexflow. They process information under their own security and privacy obligations. We may also disclose information where required by law, to protect people or the service, or as part of a corporate transaction subject to appropriate safeguards.
Provides optional account creation, Google and Apple sign-in, email-code sign-in, sessions, and account identity.
Provide identity information only when a person chooses the corresponding social sign-in option.
Provides authenticated account features, including session sync, ratings, chats, support reports, and deletion requests.
Stores private soundscape files delivered through short-lived links issued by the Lumenshore service.
Hosts the website and provides Web Analytics and Speed Insights for aggregate page-view and real-user performance reporting.
Processes the opaque Clerk account identifier plus App Store product, purchase, renewal, entitlement, storefront, and subscription-status data needed to operate and restore Royal. We do not send RevenueCat your email address, name, or Clerk profile details.
Processes Royal purchases, payment, tax, renewal, cancellation, restore, and refund requests under your Apple account. Lumenshore does not receive full payment-card details.
The website uses Vercel Web Analytics to measure page views and Vercel Speed Insights to measure Core Web Vitals and related real-user performance. Web Analytics may process the page path, referrer, approximate location, browser, operating system, and device type. Vercel states that Web Analytics does not use cookies and does not tie these measurements to a person or IP address. We use the resulting aggregate reports to understand site usage and improve reliability, not for advertising or cross-site tracking.
The current native product does not request location, health, contacts, calendar, microphone, or advertising identifiers. It is not designed to infer medical, athletic, productivity, or emotional outcomes. The website contains no account form, waitlist form, subscription checkout, advertising script, or behavioural advertising integration, and it does not collect payment details. Hosting providers may still process ordinary request and security logs.
Local information remains until you clear it, remove the app, or the device removes it. Account identity and synced product data are retained while needed to provide and secure the account, meet legal obligations, resolve disputes, and prevent abuse.
The in-app synced-data request places an authenticated request in the Apexflow privacy queue. Completing it removes the Apexflow product profile and its ritual sessions, ratings, chats, messages, bug reports, local Royal mirror, and identity links to normalized webhook records. Identity-free immutable billing events may remain so Lumenshore can evidence purchases and preserve the integrity of its billing ledger. Before the request is marked complete, an authorised operator must also request deletion of the corresponding RevenueCat customer profile. Apple, RevenueCat, and Lumenshore may retain limited transaction, tax, fraud-prevention, dispute, and legal records where required or permitted by law. The request record keeps a one-way subject digest, limited status, and app-version information so the deletion can be evidenced. This product deletion does not automatically delete the separate Clerk authentication account; request that separately through the contact route above. Residual copies may remain temporarily in protected backups before they are overwritten in the ordinary backup cycle.
Deleting Apexflow data or a Lumenshore account does not cancel an Apple subscription. Manage or cancel Royal separately in Apple's subscription settings to stop future renewal.
You can use Apexflow locally without Google sign-in, sign out at any time, choose Apple or email-code sign-in instead, clear eligible local information, and request deletion of synced Apexflow data. Depending on where you live, you may also have rights to access, correct, restrict, object to, or receive a copy of personal information and to complain to a data-protection authority.
See the Terms of Service for the service rules and the Support page for in-app help routes.