GOALIFY
Privacy Policy
1. Controller and scope
Goalify Technologies LLC, based in the United States, operates Goalify’s web, mobile and connected watch services and is responsible for the processing described here. Send privacy inquiries and rights requests to support@goalify.club.
This policy explains processing and your choices. Acknowledging it does not constitute blanket consent. We rely on a basis appropriate to the purpose and applicable law, such as providing the requested contract, lawful operations and security, legal obligations, or consent. Sensitive health data and optional external AI have separate notices and consent.
2. Data and purposes
- Account and authentication: name, email, authentication-provider identifiers and supplied name/profile information, language, verification status, signup, terms and age-confirmation timestamps and consent versions. Supabase Auth handles email-password authentication. Date of birth and identity documents are not ordinary signup fields. Providers differ, for example Apple private relay email.
- Teams, leagues and matches: memberships, roles, player profiles and photos, schedules, locations, attendance, results, statistics, votes and invitation/sharing settings, for collaboration and access control.
- Communications and support: chat, posts, attachments, reports, support requests and responses, for requested delivery, safety and resolving inquiries.
- Accounting: dues, money movements, amounts owed, expenses, approvals and settlements, linked member identifiers and receipt images or PDFs. Documents may contain names, addresses and financial details. We process these for records, review and settlement, without requiring bank-login or card-payment credentials.
- Device and security: push tokens, device, browser and platform information, IP addresses and other service logs, session, error and security records, for notifications, service delivery and abuse prevention.
- Health, workout and location: only as described separately below and permitted by device permissions.
Without required information we may be unable to provide an account or the relevant feature. Declining optional photos, health sharing, external AI or translation does not prevent unrelated ordinary features.
3. Health and workout data
⚕️ Health Data Collection — Requires Your Explicit Consent
If you choose to use our workout analysis feature, we may collect health and fitness data with your explicit, prior consent. We will never access your health data without your permission. The data we read differs by platform, and is limited to what the workout summary actually displays.
Apple Watch and iPhone (Apple HealthKit)
When you opt in, we read the following data types from Apple HealthKit:
- Heart Rate: Heart rate recorded during the workout, used for the session average and heart rate zone chart
- Activity Data: Step count, walking/running distance, and active energy (calories burned)
- Workout Sessions: the duration and summary of workouts Goalify saved to Apple Health, read on iPhone only to check a synced workout against its record
We also write the workouts you record in Goalify back to Apple HealthKit (workout, route, active energy, and distance) so that they appear in the Apple Health app.
Wear OS Watch and Android Phone
Goalify does not integrate with Google Health Connect. When you press Start workout, the Wear OS app requests android.permission.health.READ_HEART_RATE on Wear OS 6 and later for live heart-rate sensing during that workout. This permission name is also used by Health Connect, but Goalify does not read or write Health Connect records or historical health data stored by other Android apps.
On a Wear OS watch, workout metrics are measured live by the watch's own sensors through Wear OS Health Services, only while a workout you started is running:
- Heart Rate: Live heart rate from the watch's optical sensor, shown on the watch and averaged for the session. Available when the watch supports the sensor and you grant heart-rate permission
- Activity Data: Step count, distance, speed/pace, and calories burned
- Location: GPS route and distance, only in Outdoor mode and only with your location permission
- Motion Sensors: Accelerometer and gyroscope readings, used to detect cadence and sprints
Heart rate uses BODY_SENSORS through Wear OS 5.1 and android.permission.health.READ_HEART_RATE on Wear OS 6 (Android 16) and later. You can deny heart-rate access and record other supported workout metrics. Measurements run during a workout you start, with a foreground workout service, and stop when it ends. If all permissions needed to run that service are denied, the watch asks you to enable an appropriate permission before starting. We do not request continuous background health monitoring.
We do not collect VO₂ Max, resting heart rate, heart rate variability (HRV), blood oxygen saturation (SpO₂), respiratory rate, sleep, or body weight on any platform.
How We Use Health Data
Your health data is used solely for the following purposes:
- Displaying workout analysis and performance metrics linked to your match participation
- Generating heart rate zone distribution, sprint detection, and performance scores
- Allowing you to optionally share workout summaries with your teammates
How Health Data Is Stored
- Health data is stored in our secure database (Supabase) with Row Level Security (RLS) enforced — ordinary members can access only their own private health records; authorized operators may access records when necessary to provide the service, protect security or handle rights requests
- Data is encrypted in transit (HTTPS/TLS) and at rest
- Raw health snapshots are never exposed to other users; shared data contains only aggregated summaries (e.g., average heart rate, total distance)
Health Data Sharing
- Health data is private by default. You control whether to share workout summaries with your team
- When you enable sharing, only aggregated statistics (not raw biometric data) are visible to teammates
- You can revoke sharing at any time, and shared data will be removed from teammates' views
Health Data Deletion
- You can delete your health data for any match at any time through the app
- You can revoke health data consent entirely, which will prevent further data collection
- Account deletion removes health records held by the service, subject to the retention and backup rules below. Manage separate originals in Apple Health or on your device through that app or device.
Apple HealthKit Disclosure
We integrate with Apple HealthKit to read health and fitness data. In accordance with Apple's requirements:
- Data obtained from HealthKit is not used for advertising, marketing, or sale to data brokers
- HealthKit data is not shared with third parties without your explicit consent
- We do not use HealthKit data to build user profiles for purposes unrelated to health and fitness
- We do not disclose HealthKit data to third parties for their own marketing or advertising purposes
Android and Wear OS Disclosure
On Android, Goalify does not read or write the Google Health Connect record store. Workout metrics come only from the sensors on your own Wear OS watch, measured through Wear OS Health Services:
- Sensors are read only while a workout you started is in progress, and stop the moment it ends
- We request only the minimum permissions necessary for the workout analysis feature
- Live heart rate requires your permission:
BODY_SENSORSthrough Wear OS 5.1, orandroid.permission.health.READ_HEART_RATEon Wear OS 6 and later - Sensor data is used solely to provide the app's health and fitness features, never for advertising or non-health-related purposes
4. Help AI and paid Gemini
Local quick answers and queries over match, player, performance and fee records can run on-device. When external interpretation is needed, with separate consent we send your question and relevant text conversation to the Google Gemini API. Help AI does not also receive player lists, original match records, health records or accounting ledgers to calculate the answer.
We mask recognizable patterns such as emails, phone numbers, links and long numbers before transmission. This cannot reliably remove names or every piece of personal information; do not enter sensitive content. Our policy retains masked questions for 90 days for help improvement and troubleshooting, accessible to authorized operators, not ordinary team administrators.
We use a paid Gemini API project with billing enabled. Under Google’s paid-service terms, inputs and outputs are not used to improve Google’s products or models. Limited logging for service delivery, safety and abuse prevention and international processing may still occur; this is not a zero-retention or no-review promise. See the Google Gemini API terms. You may withdraw consent in Settings; prior lawful processing and records with a retention basis follow the retention rules.
5. AI classification of questions, support and reports
When the relevant server classification feature is enabled, text may be sent to TypeSafe AI, Inc. (Jev). Help-topic classification sends a pattern-masked question and common app guidance. Support classification may send submitted user inquiry text; report classification may send the report reason/details and text excerpts of the reported content. We do not guarantee that all free text in support and reports is anonymized.
This assists classification of topics, urgency and need for review, distinct from generating help answers or sending actual match, health or accounting ledgers. A classification alone does not make payments or final enforcement decisions. Model-training use and log retention follow the TypeSafe Privacy Policy and applicable agreements, rather than Google’s terms. Zero retention is not promised; logs may be retained under the applicable agreement. Avoid unnecessary personal information in inquiries/reports and send rights requests to our contact address.
6. Receipt/accounting AI and translation
Accounting AI sends different data from help AI. For an eligible user with team enablement and individual consent, a requested receipt extraction sends the original selected image or PDF to Google Gemini. Accounting question text needing interpretation may also be sent. Report assistance sends only boolean review signals, not actual ledger entries, amounts or the entire ledger. Supported local queries do not require external interpretation.
Original receipts may contain names, addresses and financial details. Select only documents you are authorized to transmit and remove unnecessary personal information first. Users review AI suggestions; they do not automatically approve, post, pay or notify anyone. Declining or withdrawing consent leaves manual entry and local summaries available. The paid Gemini data-use terms above also apply.
When you request translation, the selected text may be sent to Microsoft Azure Translator or DeepL. This does not continuously send every chat, and translation is not required to read the original.
8. External services and processors
- Supabase: authentication, database/access control, server functions and some file storage, processing the relevant account, team, match, accounting and permitted health data. Privacy and contact details.
- Vercel: web hosting, request delivery and operational logs, which may include IP, browser and request information. Privacy and contact details.
- Cloudflare R2: storage and delivery of uploaded media and attachments. Public media and restricted accounting evidence have different access scopes. Privacy and contact details.
- Google: the optional paid Gemini processing described above and FCM push delivery. FCM receives push tokens and information needed for notifications. Privacy and contact details.
- Apple: iOS APNs push delivery and Apple sign-in when selected. HealthKit is a device-permission integration; using it alone does not mean we instruct an upload of all original workouts to a separate Apple server. Privacy and contact details.
- Microsoft and DeepL: receiving/sending support email and requested Azure Translator or DeepL translations. The relevant service receives email/inquiry content or selected translation text. Microsoft and DeepL privacy and contact details.
- TypeSafe AI, Inc. (Jev): the text described above for enabled help/support/report classification. Privacy and contact details.
- Sentry: error/performance information and error-session replay when configured in production. Text is masked, media blocked and default email/IP attachment disabled. A portion of the in-app user ID may be sent as a pseudonymous identifier. These measures do not guarantee removal of personal data from every error message. Privacy and contact details.
- Open-Meteo and BigDataCloud: weather/place lookups process place names, coordinates, match dates and related query information. Direct device requests may expose the network IP. Open-Meteo and BigDataCloud.
- Google, Apple and Kakao sign-in: authentication exchanges with the provider you select; that provider’s policy applies to its own accounts and services. Kakao privacy and contact details.
We send only data needed for the function and require applicable contractual and access protections. Also review settings and policies for services a provider operates independently.
9. International processing and choices
We operate from the United States. The current primary Supabase project database is in Oregon, United States (us-west-2). Account, team, match, permitted health and accounting data are transmitted over encrypted networks and stored as you use the service. This does not mean every copy at every provider is in that region.
Vercel/Cloudflare delivery and storage, Google AI/push, Apple push, Microsoft email/translation and DeepL may process in the United States and other countries according to their configuration and international infrastructure. Paid Gemini terms also describe storage or transient processing in countries where Google or its agents have facilities. Processing locations and subprocessors are described in Vercel’s processor information, R2 data-location documentation and the providers’ privacy/contract documents. A provider’s headquarters are not necessarily the storage country.
TypeSafe AI classification, Sentry error reporting and weather/place lookups may also be processed on those providers’ infrastructure.
Transfers occur when you use accounts/features, receive notifications, request optional AI/translation or contact support. Data and purposes are described above; our retention is below. Provider safety or legal logs may follow their contracts. We arrange a transfer basis and safeguards required by applicable law, and provide additional notice or consent before processing where required. Necessary contracted processing/storage is distinguished from optional consent-based transfers.
You can decline or withdraw optional AI, translation, health-sharing or push permissions, which may limit the relevant feature. Declining essential authentication/storage can prevent provision of an account. Ask support@goalify.club about transfers, rights and alternatives.
10. Retention and deletion
- Account and collaboration records: retained while needed for active accounts/teams and requested features, with prompt deletion when their purpose ends or a valid request applies. For shared match history or lawful accounting evidence in another person’s team, continuity, rights and applicable law determine deletion, unlinking or minimization of identifying data.
- Operational audit logs: our retention policy is 90 days for security and deletion traceability. They can include user ID, email, deletion outcome and operational metadata; deleting an account does not immediately erase every audit record.
- Raw usage events and masked help-AI questions: each has a 90-day retention policy.
- Chat media: scheduled cleanup uses 30 days after sending; processing time until a cleanup run may be additional. We cannot directly erase copies recipients have already saved.
- Health records: retained for the permitted feature and consent scope; relevant service records are deleted when you request deletion or withdraw with deletion. You can also choose withdrawal while retaining existing records. Manage separate device/Apple Health originals there.
- Accounting/support material: retained as needed for team books, evidence and inquiry resolution. Specific legal obligations or dispute holds are limited to the relevant basis, scope and period and separated from ordinary use. Where lawful retention applies, we explain its basis and period when handling a rights request.
Deletion removes accessible service copies and account links and performs file cleanup. Failed file deletions may require further operator cleanup. Disaster-recovery backups or provider security logs may not support immediate per-record erasure and follow their retention/expiry procedures and access restrictions. We therefore do not promise that every copy disappears within a single fixed number of days. We explain applicable exceptions and request status when asked.
11. Account deletion and owned teams
Request permanent deletion through My Settings → Permanently Delete Account. Owned teams and linked records can also be deleted; transfer ownership first for teams that should continue. In teams owned by others, memberships and links are removed but not necessarily every shared record. Contact us for review of personal information remaining in others’ records.
You may export or request needed personal information before deletion. We request only the minimum identity information needed to handle a request, without disclosing others’ private data. Apple Health/device originals, content saved by others and lawfully retained material are managed separately.
12. Device storage, measurement and security
We use app/browser storage for sessions, language, display settings, recent sign-in method and consent choices. Native sessions use iOS Keychain/Android Keystore-backed storage; web authentication uses browser storage. Protect devices containing sign-in information with an up-to-date operating system and device lock.
Usage measurement includes random device/browser and session identifiers, account ID when signed in, screens, platforms and selected actions. It does not send chat bodies, invitation links, health values, accounting ledgers or full page URLs as usage events. There is currently no dedicated in-app usage-measurement opt-out switch. Contact us to object or request restriction. Blocking or clearing browser storage may limit some measurement but can also affect sign-in and preferences; it does not replace a request to erase server records.
We apply transport encryption, storage safeguards, role-based access and operational least privilege. No system is absolutely secure; breaches requiring notification are handled under applicable procedures. Health information is not used for advertising targeting or sale.
13. Your rights and children
Depending on applicable law, you may request access, a copy, correction, deletion, restriction, objection, portability and withdrawal of consent. Use relevant app settings or contact support@goalify.club. We respond within applicable statutory timelines and explain grounds and review options for any limitation or refusal. Withdrawal does not retroactively invalidate prior lawful processing.
Your right to complain to a supervisory authority or seek statutory remedies is preserved, including Korea’s Personal Information Protection Commission/Personal Information Dispute Mediation Committee, or your EEA supervisory authority where applicable.
Our account policy is 14+. We do not offer guardian-consent signup for children under 14; contact us if you believe their information was collected. Additional requirements may apply by residence and optional feature. Provider terms restrict offering Google Gemini-based external AI to people under 18.
14. Updates and previous versions
This policy’s revision version is 2026-10-19. Material changes to purposes, data, recipients or choices will be notified through appropriate app/web channels with their effective date before taking effect; separate consent will be obtained where required. Editing this document does not create new consent records for existing accounts.
The Korean and English documents cover the same scope; other app languages may display English. Read the previous Privacy Policy (2026-08-14) and Terms of Service. Contact: support@goalify.club.