GlassForty
Privacy Policy
GlassForty is designed around data minimization: scoring works without an account, ads or a network connection. The website support form is a separate, optional service.
Governing law: Mandatory consumer law and the Apple Standard EULA apply; no statutory rights are waived.
Contact: Open secure support
Privacy contact: Open secure support
Website host: Railway Corporation
Host privacy information: https://railway.com/legal/privacy
Website log retention: Railway may retain infrastructure logs under its current Privacy Policy; GlassForty runs no web analytics.
Diagnostics retention: Optional app diagnostics follow the configured provider policy and exclude Health data, player names and point-by-point scores.
Support retention: Support requests are deleted after 365 days unless you request earlier deletion or law requires a longer period.
1. Scope
This policy covers the GlassForty iPhone app, Apple Watch app, complications and this website. It explains the categories of data the product may process and the boundaries enforced by the product design.
The publication details identify the verified publisher and privacy contact responsible for this policy.
2. Data processed
GlassForty may process the following data when you choose to use the related feature:
- Match data: rules, score events, timestamps, server/side state, correction timeline and completed result.
- Optional preferences: scoring presets and accessibility choices.
- Optional Health data: workout duration, heart rate and active energy processed under HealthKit permission. When you choose Save, GlassForty writes the workout and GlassForty/match identifier metadata to your Apple Health store.
- Purchase state: StoreKit transaction and entitlement information plus an anonymous Adapty profile identifier needed to show products, complete or restore purchases and unlock Pro. GlassForty sends no customer user ID or custom profile attributes.
- Limited operational diagnostics: app version, device/OS class, a pseudonymous non-advertising device identifier, crash/performance state and low-cardinality reliability events that exclude score, names and Health data.
- Support data you choose to submit: reply email, issue category, message and optional app/device versions. Do not include Health data, player names or payment details.
3. Why data is used
- Run, save, recover and synchronize matches between your own Watch and iPhone.
- Show local history, recap, optional workout metrics and Pro insights.
- Restore purchases and keep entitlement state available offline.
- Diagnose crashes and aggregate reliability without profiling individual matches.
4. Storage and synchronization
Active Watch match state is stored locally with a backup and a durable completion queue. iPhone history can use your private iCloud/CloudKit container when enabled.
HealthKit-derived heart rate, energy and fitness values are processed by the app and Apple Health. They are not written to GlassForty CloudKit or sent to Adapty, Sentry or product analytics. Apple may synchronize Health data under your Apple Account and system settings; that is separate from GlassForty private CloudKit history.
5. Service providers
The release build may use narrowly scoped providers for these functions:
- Apple: app distribution, StoreKit purchases, HealthKit and private iCloud synchronization.
- Adapty: subscription entitlement and paywall configuration on iPhone only.
- Sentry: filtered crash and release-health diagnostics.
- TelemetryDeck: privacy-focused aggregate product and operational events.
- Railway: HTTPS hosting and a persistent SQLite volume for the website documents and optional support requests.
6. Website privacy
This website ships no analytics script, advertising pixel, cookie banner or account system and does not write cookies or browser storage. Privacy and Terms revisions are stored in the site SQLite database.
If you send the support form, GlassForty stores the fields you submit in SQLite. Raw IP addresses and User-Agent strings are not stored there; keyed one-way fingerprints are used only for abuse limits. Railway may separately process infrastructure logs under its own policy.
7. Retention and deletion
Active-match files and local history stay in the app container until you replace them through normal use, delete the app or erase its data. Private CloudKit history stays in your Apple-managed iCloud account until you remove the app’s iCloud data using Apple system controls.
Saved workouts stay in Apple Health until you delete them there. Revoking Health permission stops future access but does not itself delete an existing workout. Limited provider diagnostics and purchase records follow the configured retention period and Apple’s transaction-retention requirements shown in the publication details.
Support requests are deleted after the support-retention period shown above unless you ask for earlier deletion or a legal obligation requires longer retention.
8. Your controls
- You can deny or revoke Health access in Apple system settings without losing scoring.
- You can disable iCloud for the app and continue with local history.
- You can manage or restore App Store purchases from Settings.
- GlassForty v1 has no account to close and no in-app delete-all portal. Use Apple Health/iCloud controls for Apple-managed data, delete the app for its local container, or use the secure support form for access/deletion questions about a support request or provider-held diagnostics.
9. Changes
Material changes will be reflected by a new date and, where required, an in-app notice. Health data will never be repurposed for advertising, marketing profiles or data brokerage.