About this update
Arch is provided by Wayne Hsu Ltd., United Kingdom. This update supplements our 27 November 2025 privacy policy. The subscription analytics update below applies to existing Arch billing records, regardless of which app version you use. The updated-app sections describe the My Plan app, version 1.1.0 and later. On 9 October 2026 we revised the Meta advertising measurement and Your choices sections for version 1.1.1. The next app update adds the confirmed onboarding choices, session outcomes and Contact us form described below. For the legacy app's PostHog and optional CloudKit features, the earlier policy remains available below. This update supersedes its analytics, storage and advertising descriptions only where the changes below apply.
Analytics in the earlier App Store app
The earlier App Store version (1.0) uses PostHog for app and screen activity, onboarding choices (including foot-health goals and toe-lift ability), training targets, routine starts and names, session completion and duration, pauses and skips, and subscription interactions. Routine names can include names you enter. Purchase interactions can include product, price and transaction references; technical failures can include error descriptions. Analytics uses persistent, randomly generated identifiers and technical app/device information. PostHog can derive approximate location from network information. These analytics records are separate from the local workout database and qualify the earlier policy’s statements about information staying on the device. The My Plan app replaces this PostHog flow with the narrower Appbase collection described below.
Subscription analytics across app versions
From 6 October 2026, we use Appbase to analyze RevenueCat subscription records, including available historical customer, subscription and transaction records. This helps us understand subscriptions and improve Arch. These records use RevenueCat customer identifiers and purchase information. The imported records also include country-level information and tracking-permission status supplied by RevenueCat. Incoming billing-event records can retain additional provider fields; the fields depend on the event received. An Arch account is not required. Apple processes App Store payments, and RevenueCat validates subscriptions and restores paid access. We do not receive your payment-card details.
Local records in the updated My Plan app
Assessment answers, exercise selections, your saved plan and detailed workout history are stored locally. Confirmed onboarding choices and coarse session outcomes are also sent to Appbase as described below. The updated app does not use an Arch account or CloudKit synchronization. Depending on your settings, your operating system may back up or transfer app data; that is separate from app-managed synchronization. Downloadable exercise media can be downloaded again and is excluded from backup. A new installation without restored app data does not recover local workout history, and restoring a subscription does not restore that history.
Product analytics in the updated app
In released version 1.1.0, Appbase receives app opens, screens and onboarding progress; selected daily training time, reminder choice and discovery source; membership and checkout interactions; and one signal when you start a real training session. The training signal lets us count starts and understand how often you start training; it does not report which exercises you perform, session duration, intervals, completion or early finish. We do not send plan-edit events or plan exercise counts. Events include timestamps, app version, platform and randomly generated installation/analytics identifiers. We link these identifiers to the existing RevenueCat customer identifier to understand subscription results. They are pseudonymous, not a guarantee of anonymity.
The next app update replaces general screen views with onboarding progress and paywall presentations. It also records each confirmed onboarding choice: training goals, toe control, bunions, leg alignment, daily training time, age group, sex, reminder decision and discovery source. Age is grouped into bands; exact typed age and reminder clock times are not sent. It records a training start and one outcome: full completion of every interval, or an early/partial end. These signals do not include exercise identifiers, detailed workout entries, durations or plan-edit data. Earlier My Plan builds do not send the additional assessment/demographic choices or session outcomes. Free text is not included in product analytics events.
Contact us in the next app update lets you send a message and optional reply email to our Appbase feedback inbox. App/platform/version context and, when analytics is enabled, your analytics identifier accompany it so we can understand and respond to your request. If SDK analytics is disabled, contact omits the analytics identifier. Messages and email are stored separately from activity events and are not sent to Meta. We show a sent confirmation only after server acknowledgement. Drafts remain in the form during a failed attempt but do not survive closing and discarding the form or ending the app process. Providers also receive network information, such as IP addresses, when handling requests; service request logs may retain this information. The updated app does not send PostHog events. Product analytics is separate from Apple's tracking permission: declining tracking does not disable Appbase or the subscription service.
Meta advertising measurement
From version 1.1.1 on iOS, Arch starts Meta's SDK when the app opens so we can measure our Meta ads, including for people who do not allow tracking. Meta receives installation and app-open signals, a Meta-generated identifier, technical information about the app and device, your Apple tracking-permission status, and network information such as IP addresses. The SDK also requests configuration information and may collect technical diagnostics such as crash reports. If you do not allow tracking, the SDK does not share your device's advertising identifier, and Meta states that it restricts its use of these events and removes or combines information using privacy-preserving methods such as Aggregated Event Measurement. If you allow tracking, Meta also receives your device's advertising identifier and can combine Arch's events with information it holds to measure our ads more precisely. Version 1.1.0 started Meta's SDK only after you allowed tracking. Measurement can include activity from people who did not arrive through an ad; every installation is not an ad-attributed install.
Arch also uses Apple's SKAdNetwork ad attribution. When the app first opens, and when a trial or paid subscription starts, Arch updates an Apple conversion value representing installation, trial or subscription. If you installed Arch from an ad, Apple sends that ad network a delayed report with the value; Apple designs these reports so they do not identify you or your device.
Our RevenueCat connection sends confirmed trial starts and subscription purchases, conversions and renewals to Meta, with product identifiers, transaction references and revenue information. Matching can use the Meta-generated identifier, device identifiers and a hashed RevenueCat customer identifier; your advertising identifier is included only if you allowed tracking. From 9 October 2026 this connection can also send these events when tracking is not allowed, together with your permission status, so Meta can apply its restricted measurement. Later subscription events can be reported while Arch is closed. We do not send health assessments, exercise selections or workout details to Meta.
Your choices
Declining tracking does not change subscription access. You can change tracking permission in iOS Settings; the app's Ad tracking setting links there. Declining or revoking tracking stops sharing of your advertising identifier, and when Arch next observes the change it asks RevenueCat to remove a previously stored advertising identifier. Meta's restricted measurement and Apple's attribution reports described above do not depend on tracking permission and continue while you use the app. A server cannot learn a changed device permission until it is synchronized. Revocation does not erase information already received or recall requests already in progress.
Retention and deletion
Local records remain until removed from the device; operating-system backups have separate controls. Analytics records support product analysis, while subscription records support paid access, restoration, accounting and other applicable obligations. Provider records are separate from local data: deleting the app does not automatically delete them, remove backup copies or cancel an App Store subscription. To request access to or deletion of information we hold, contact waynedev9598@gmail.com. We may need limited information to locate pseudonymous records, and will explain what can be deleted and any records that must be retained. Do not send passwords or payment-card details.
Earlier policy
The original policy remains below for the legacy app. The update above supersedes its analytics, storage and advertising descriptions where the changes apply.
27 November 2025Original privacy policy
Arch – Privacy Policy
Last updated: 27 November 2025
This Privacy Policy explains how Wayne Hsu Ltd. (“we”, “us”, “our”) collects, uses, and protects your information when you use the Arch mobile application (the “App”).
We are committed to keeping things simple and privacy-friendly: Arch is designed to work primarily on your device, with no central app database managed by us.
By using Arch, you agree to the collection and use of information in accordance with this Privacy Policy.
1. Who We Are
Controller:
Wayne Hsu Ltd.
Registered in the United Kingdom
If you have any questions about this Privacy Policy or your data, you can contact us at:
📧 waynedev9598@gmail.com
2. What Data We Collect
2.1 Data Stored Locally on Your Device
Arch is designed so that your core data stays on your device by default. This includes:
Your exercise routines and preferences
Your completed sessions and progress (e.g., which exercises you did, duration, streaks)
In-app settings (e.g., reminder preferences, notification settings)
This information is stored locally using Apple’s device storage technologies (e.g. SwiftData).
We do not upload this content to our own servers.
2.2 Optional Cloud Sync via iCloud / CloudKit (Apple)
If you choose to enable iCloud sync on your device, Arch may synchronize your app data using Apple’s CloudKit/iCloud infrastructure. This allows your data to be shared across your Apple devices.
Data that may sync: routines, settings, progress, and similar app data.
This data is associated with your Apple ID inside Apple’s systems, but we do not have access to your Apple ID, name, or email via CloudKit.
CloudKit storage is managed by Apple under Apple’s own terms and privacy policy.
You can control iCloud sync through your device’s iOS Settings.
2.3 Usage Analytics (PostHog)
To understand how Arch is used and to improve the product, we use PostHog Cloud for analytics.
We aim to keep analytics minimal and non-personal. The information we may collect includes:
App events (e.g. “routine started”, “session completed”, feature usage)
Basic technical information (e.g. app version, device type, operating system version)
Pseudonymous identifiers (e.g. a random ID to distinguish one device from another)
We do not intentionally send your name, email address, or obvious personal identifiers to PostHog.
Analytics are used only to:
Understand which features are used and where users drop off
Improve app design, performance, and reliability
Debug errors and problems in aggregate
We do not sell your data and do not use analytics data for third-party advertising.
Note: PostHog may process limited metadata (such as IP address) as part of transmitting analytics. This is handled under PostHog’s own privacy and security practices.
2.4 Payments and Subscriptions (RevenueCat & App Store)
Arch uses RevenueCat to manage subscriptions and in-app purchases.
We use anonymous identifiers with RevenueCat; we do not directly send your name or email to RevenueCat.
RevenueCat helps us:
Verify your purchase status (free, trial, or paid)
Restore purchases across devices
Manage subscription states (active, expired, cancelled)
All actual payment transactions (e.g., your card or Apple Pay details) are handled by Apple’s App Store / StoreKit, not by us. We never see or store your full payment details.
Apple’s own terms and privacy policy apply to the payment process.
3. How We Use Your Information
We use the information described above for the following purposes:
To provide the core functionality of Arch
Store your routines, sessions, and settings
Show your progress and history
Sync your data between devices if you choose iCloud sync
To improve the App (PostHog analytics)
Understand which features are helpful or confusing
Prioritize new features and improvements
Identify bugs, crashes, and performance issues
To manage subscriptions and access (RevenueCat)
Check whether you have an active subscription or trial
Allow access to paid features where applicable
Restore purchases after reinstalling or changing devices
We do not use your data for behavioral advertising, and we do not sell your data.
4. Legal Basis for Processing (UK & EU/EEA Users)
If you are located in the UK or the European Economic Area (EEA), we rely on the following legal bases to process your data under the UK GDPR/EU GDPR:
Performance of a contract:
To provide the App’s core functionality, store your routines, show your progress, and manage your subscription status.
Legitimate interests:
For product analytics (via PostHog) to improve the App, as long as such interests are not overridden by your rights and interests.
Consent:
Where required (for example, enabling iCloud/CloudKit sync via your device settings), we may rely on your consent.
5. Data Sharing and Third Parties
We do not sell your personal data.
We may share or allow access to data only with:
Apple (iCloud / CloudKit / App Store / StoreKit)
For optional iCloud sync of your data
For handling purchases and subscriptions via the App Store
PostHog (Analytics)
To collect anonymized or pseudonymous usage data for product improvement
RevenueCat (Subscriptions & Entitlements)
To manage and validate subscription status
These third parties act as processors or independent controllers under their own privacy terms. We encourage you to review their privacy policies for more details on their processing.
We may also disclose information if required by law or to protect our legal rights (e.g., in response to a lawful request from authorities).
6. International Data Transfers
Our third-party service providers (such as PostHog and RevenueCat) may process data on servers located outside the UK/EEA, including in the United States.
Where such transfers occur, we aim to ensure that appropriate safeguards are in place, such as:
Standard Contractual Clauses (SCCs), or
Other mechanisms recognized by applicable data protection laws.
7. Data Retention
On Your Device / iCloud
On-device data (routines, sessions, settings) is stored for as long as you keep the App installed, unless you delete the App data or the App itself.
If you use iCloud/CloudKit, your data is retained in your iCloud account until you remove it or change your iCloud settings. This storage is controlled by Apple, not us.
Analytics (PostHog)
Analytics events are retained by PostHog according to their default or configured retention settings (which may change over time). We keep analytics only as long as reasonably necessary for product improvement and debugging.
Subscription Data (RevenueCat)
Subscription and entitlement records are kept for as long as needed to manage your access to paid features, comply with App Store rules, and meet our legal/accounting obligations.
8. Security
We take reasonable technical and organizational measures to protect your information, including:
Storing app content primarily on your device
Using reputable third-party providers with robust security practices (Apple, PostHog, RevenueCat)
Limiting the personal and identifying data we collect
However, no system can be 100% secure. You are responsible for:
Keeping your device secure
Managing your iCloud and Apple account settings
Using a strong passcode and enabling features like Face ID/Touch ID where available
9. Your Rights (UK & EU/EEA Users)
If you are in the UK or EEA, you may have the following rights under data protection laws:
Right of access – to know what personal data we hold about you
Right to rectification – to correct inaccurate or incomplete data
Right to erasure – to request deletion of your data in certain circumstances
Right to restriction of processing
Right to data portability – to receive your data in a machine-readable format in certain cases
Right to object – to certain types of processing, including analytics based on legitimate interests
Right to lodge a complaint with your local data protection authority
Because we intentionally minimize personal data and do not run a central app database for your routines/progress, some rights (like access and deletion) may mostly be exercised by:
Deleting the app from your device
Clearing app data from your device’s settings
Managing your iCloud data via Apple ID / iCloud settings
For analytics or subscription-related data, you can reach out to us at waynedev9598@gmail.com, and we’ll do our best to assist.
10. Children’s Privacy
Arch is not directed at children under 16 and is intended for adults or individuals under proper supervision.
We do not knowingly collect personal information from children under 16. If you believe a child has provided us with personal data, please contact us, and we will take steps to delete such information where appropriate.
11. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect:
Changes in the App’s functionality
Changes in our data practices
Changes in applicable laws or regulations
When we make material changes, we will update the “Last updated” date at the top of this page. In some cases, we may notify you in the App (for example, via an in-app message).
12. Contact Us
If you have any questions, concerns, or requests related to this Privacy Policy or your personal data, you can contact us at:
📧 waynedev9598@gmail.com
Wayne Hsu Ltd.
United Kingdom