1. Who is responsible
is operated by Andreas Mondo, who carries out activities for the service in Australia and Italy. He is responsible for personal information handled for the service and is the controller where the GDPR applies. Andreas Mondo, ABN 40 907 562 679. Business address: Suite 17, 89-97 Jones Street, Ultimo NSW 2007, Australia. Postal correspondence: GPO Box 320, Sydney NSW 2001, Australia. Email: strenqo-support@strenqo.eu.
This policy covers the app, its connected services and this website. Australian privacy protections apply to the relevant Australian activities; the GDPR applies to processing carried out in the context of the Italian establishment and in other cases within its scope. Additional rights in the place where you live continue to apply; moving the operator to Australia does not remove those rights.
2. Information and sources
We receive information you enter, information from connections you authorise, and technical information produced when the service runs. Depending on the features you use, this includes:
- Account and profile: email, account identifier, sign-in provider, credentials handled by the authentication service, profile image, goals, preferences, country, language, units, subscription status and age-verification information. The exact birth date is checked by the server and may be kept locally on your device. Cloud records retain a verified age band, birth year where supplied, market, threshold and acceptance time; the current consent record does not retain a hash of the full birth date.
- Training and body: plans, exercises, sets, repetitions, load, timers, completed sessions, perceived intensity, weight, body measurements, optional body photos and notes.
- Nutrition: meals, food queries and barcodes, photos you submit, portion sizes, recipes, calorie and macro targets, water, dietary preferences, allergies or intolerances you disclose, and supplement schedules.
- Health and devices: authorised heart rate, HRV, intervals between heartbeats and Night HRV recordings, resting heart rate, sleep and stages, steps, distance, energy, oxygen saturation, temperature and supported body measurements, menstrual flow and inferred cycle context where available. Availability varies by device, platform and permission. We also process derived scores, source identifiers, timestamps and time-zone information.
- Location: outdoor route coordinates when you use GPS recording, including while an active outdoor session continues in the background. Optional GPS clipping hides route endpoints in supported displays and exports; it does not erase the underlying stored route.
- AI: messages, selected files or photos, relevant fitness context, generated results and memory preferences or summaries where enabled.
- Community: participation consent, handle, profile visibility, follow relationships, team roles and membership, invitations, chosen posts and aggregate metrics, compliments, reports and blocks.
- Creator codes and existing rewards records: code claims, offer eligibility, referral or purchase references and, for existing creator programme participants, application and verification records, campaign submissions, payout account references, ledger entries and security/review signals. A payout provider may collect identity and bank details directly.
- Operations: device and app version, push tokens, connection tokens, network and server logs, security events, support correspondence, requests and consent records. The website host receives ordinary request information such as IP address, time and requested resource.
- AI choices and reports: where the updated controls are available, we record the consent notice version, choice and time, and any report description, relevant feature, language, submission time and review status. Reports are private support/moderation records, not public posts or prompts sent for AI generation. Do not include unnecessary health information or another person’s private details.
3. Why information is used
Information is used to provide the features you request, keep your account and devices in sync, maintain security, manage purchases, respond to support and rights requests, and meet legal obligations. We do not sell personal information or use health data for advertising.
| Use | Relevant basis where the GDPR applies |
|---|---|
| Account, saved plans, requested features and billing | Performance of the contract; health information also requires an Article 9 condition, normally explicit consent. |
| Optional health connections and AI processing of sensitive context | Specific consent and, for special-category data, explicit consent; an OS permission alone does not replace every legal consent requirement. |
| Voluntary public posts and shared fitness aggregates | Your requested Community participation and sharing choices; explicit consent where special-category data is involved. |
| Security and abuse prevention | Legitimate interests in protecting users and the service, balanced against their rights. |
| Records required by law and regulatory requests | Compliance with a legal obligation. |
4. Health, AI and sharing controls
Health connections are optional. Choose categories in Apple Health or Health Connect and connect or disconnect supported cloud accounts in Settings. Imported or derived information used for saved workouts, daily snapshots and trends can be stored in your account; health data is not necessarily confined to your phone.
In the planned release, onboarding presents Terms/Privacy and explicit health-data consent on consecutive pages. The first Continue accepts Terms and acknowledges Privacy; the next Continue confirms the separate statement for workout, body, nutrition and connected-health processing before personalisation. After sign-in, the age check records the health choice on the server separately from optional AI. Returning users do not repeat registration or receive a routine date-of-birth prompt. AI requests, server push and protected wearable uploads still require the applicable valid server eligibility and health-consent records. You can withdraw it in Profile → Settings → Privacy, data, and support; AI requests, server push and protected wearable uploads stop after the server confirms withdrawal; cloud wearable connections are disconnected and you are signed out. Another device that is offline may still show cached information until it reconnects, but the server will refuse new uploads. You may reconnect a provider after a new active choice. Existing saved data is not automatically erased; request deletion separately. An offline withdrawal cannot be confirmed and must be retried when connected.
In the planned release, the AI option is initially selected. “AI on · Manage” opens a separate panel with the processing notice and a choice you can turn off. If the selected option has not been confirmed, creating an account opens that panel and requires an explicit confirmation before registration proceeds. You can deselect AI and register without it. Initial selection, opening the panel or closing it does not by itself authorise AI processing. New AI requests require registration, server-confirmed eligible age, separate health-data consent and a recorded AI choice. Existing accounts keep their recorded choice; you can change it in Settings. We record the account, notice version, time, confirmation action and selection state, including that the option was initially selected and that the panel choice was confirmed. The record describes actions taken and does not prove that the notice was read.
Withdrawing AI consent blocks new AI requests on that device. If the device is offline, the withdrawal is saved locally and retried when connectivity returns; server tasks and other devices can reflect it only after the server receives it. Requests already sent may have been processed. Withdrawal does not automatically delete earlier conversations or data: use the separate deletion controls or contact support.
The updated consent flow and in-app AI reporting are prepared for the next app release; availability depends on the installed version. A preselected AI preference is not itself consent. The planned registration flow requires confirmation of the separate panel choice; publishing this policy does not create consent or replace that confirmation. Check your settings and update the app when the new controls become available.
Community requires separate acceptance. The initial profile is private, not discoverable and excluded from global leaderboards. You choose supported sharing metrics and posts. Other users can see content according to the audience you select and may copy public content.
You can use this website without creating an account. Account-based features require enough information to identify your account; anonymous use of those features is not practical. Withholding an optional permission prevents the related feature, rather than granting that permission implicitly.
5. Providers and overseas processing
The service-provider register explains the services used and the information involved. Providers include Supabase, Cloudflare Workers AI, RevenueCat, Resend, Apple, Google, Expo and the wearable or food services relevant to your choices. Some are processors; others act independently for their own platform services.
Operating from Australia does not mean all information is stored in Australia. Processing may involve Australia, the European Union and the United States, depending on the service and its infrastructure. An overseas recipient must be assessed under applicable Australian requirements; European transfers require a valid Chapter V mechanism, such as applicable contractual safeguards or an adequacy decision. Ask us for the safeguards relevant to your information. This policy does not represent an unverified provider contract or certification as already completed.
6. Retention and deletion
Account records, saved activity, content and preferences are generally kept while needed to provide your account. Delete individual records where supported or request account deletion. Connected-provider tokens are kept while required for the connection; disconnecting does not necessarily delete historical workouts or derived trends already saved.
Limited audit events become eligible for removal after 90 days; completed, failed or cancelled privacy requests after 30 days. Daily scheduled cleanup applies these periods, so actual removal can occur at the next scheduled run. Export confirmation links expire after 24 hours and deletion confirmation links after one hour. Unfinished requests may remain while being resolved. These periods are distinct from legally required purchase, dispute or fraud records.
Deleted information may remain temporarily in restricted backups until overwritten under the hosting provider’s retention cycle. Provider-side logs and store transaction records follow their applicable retention rules. We do not promise instant erasure from every backup or every independent provider.
Account deletion can finish before all private stored files and the linked subscription-service customer record have been removed. Cleanup is recorded and retried if a provider is temporarily unavailable. A limited pending-cleanup record contains the account identifier and technical processing status, rather than a copy of your health records or uploaded files, and is removed after successful cleanup. Store billing records and legal retention obligations are separate.
Notifications and background information
Server notifications pass through Expo Push Service and the Apple/Google delivery services. Tokens, title/body and data payload may include personalised fitness or briefing context. Manage notifications in Settings and the operating system, including what appears on a lock screen. Disabling AI does not by itself revoke all non-AI reminders.
Bluetooth/Night HRV may process intervals between heartbeats, and supported recovery functions can use cycle-related context. These remain sensitive wellness information. Background location is associated with an active outdoor session; GPS clipping affects supported displays/exports, not the stored source route.
AI photos and shared illustrations
Cloudflare Workers AI hosts Gemma 4 for Intelligence, text and selected image/document requests. Meal and exercise illustration generation sends descriptive text; generated output may be cached and reused across accounts. Free-text labels may still contain personal information, so omitting an account ID does not prove anonymisation. See the photo and AI-image notice.
Generic non-personal artwork may remain in the shared catalogue after account deletion. Personal source files and records follow the normal deletion rules; no shared-cache exception permits unlawful retention of identifiable information.
7. Access, correction, export and complaints
Settings → Privacy, data and support provides account export. Supported sections include profile and activity records, Community records and account-specific custom exercise-name associations; health and AI consent receipts and AI reports are included when the updated controls are available. Exports may not include every conversation or the full binary contents of attachments; media may be represented by storage references. Contact support for missing categories, additional personal information or help obtaining files.
You may request access and correction, withdraw consent and seek deletion. Depending on your region you may also have rights to portability, restriction, objection or review of certain automated decisions. See account deletion and the regional notices. We verify identity proportionately and do not ask for your password or tax file number.
Send requests or complaints to strenqo-support@strenqo.eu or our postal address. We aim to respond within 30 days; GDPR requests are answered without undue delay and normally within one calendar month, with any permitted extension explained. Where Australian law applies, you can complain to the OAIC after first giving us a reasonable opportunity to respond. You can also contact your local privacy regulator.
8. Automated processing and AI
calculates fitness estimates and trends and uses AI for replies, plans, photo estimates and briefings. These features support personal fitness decisions; they are not intended to make decisions about employment, insurance, credit, healthcare eligibility or legal rights. Subscription access, rate limits and security controls also use automated rules. Contact us to challenge an incorrect account restriction or result. See AI transparency.
9. Age and younger users
is available from age 16 in AT, AU, BE, CA, DE, ES, FR, GB, IE, IT, NL, PT and US. Distribution through the UK App Store is not planned for launch; this is separate from access while travelling and does not waive applicable privacy rights. Switzerland and other markets remain 18+. Teen use remains subject to applicable consent and contract rules. The birth date is sent to the server for the age check; the account database does not keep the full birth date, but records the verified age band, market, accepted Terms/Privacy versions and time, and may retain birth-year age-proof metadata. The current cloud consent record does not retain a hash of the full birth date. Accounts without age confirmation are blocked from server AI requests and server push notifications. Local reminders already scheduled by older installed versions may continue until the updated app opens and cancels them. An account holder, parent or guardian may contact us about information or deletion for a previously registered minor.
10. Security and policy changes
The service uses access controls, encrypted transport and security checks appropriate to its functions. No service can guarantee complete security. Security incidents are assessed and notified to affected people and authorities when required by applicable law, including the Australian Notifiable Data Breaches scheme where applicable.
Material changes will be communicated through appropriate in-app or direct notices where required. A revised policy does not retroactively create consent for a new purpose. The date above identifies this document version.