🇬🇧 EN
Tracking and Third-Party SDKs
Current publication-ready legal information for the Strenqo mobile app.
Version: 1.1.1
Last updated: 2026-07-11
Controller: Andreas Mondo, Via Pianezza 16, 10040 Givoletto (TO), Italy — email strenqo-support@strenqo.eu — PEC andreasmondo@ultracert.it.
1. Foreword
Strenqo is a native mobile app for iOS and Android. It does not use cookies for app functionality, does not include advertising SDKs, does not include attribution/mobile measurement SDKs and does not use cross-context behavioral profiling services.
This document explains which platform SDKs and services are present, which data may leave the device, and which choices you can change.
2. Telemetry and diagnostics SDKs
2.1 No Sentry or third-party crash-reporting SDK
The current Strenqo build does not initialize Sentry and does not include a third-party crash-reporting SDK. services/errorTracking.ts is a local shim used to avoid application errors and support development logging; it does not send events to Sentry or another vendor.
This means:
- there is no "Diagnostics and crash report" toggle that sends data to Sentry;
- stack traces, breadcrumbs and user identifiers are not transmitted to a crash-reporting provider by Strenqo;
- crash reports generated by the operating system or app stores are governed by the user's Apple/Google settings and their policies, not by a Strenqo SDK.
2.2 Internal diagnostics
Strenqo records on its servers only technical events strictly necessary for security, audit and service operation, such as rate limits, export/deletion outcomes, subscription webhooks and operational Edge Function logs. These records are hosted on Supabase in the EU and are not used for advertising or behavioral analytics.
3. SDKs not present
Strenqo does not include:
| Category | SDKs not present (non-exhaustive) |
|---|---|
| Third-party analytics | Google Analytics for Firebase, Mixpanel, Amplitude, PostHog, Heap |
| Attribution / mobile measurement | AppsFlyer, Adjust, Branch, Singular |
| Advertising SDKs | Google AdMob, Meta Audience Network, Unity Ads, AppLovin, IronSource |
| Behavioral trackers | Facebook SDK, TikTok SDK |
| Web cookies | None for the native app |
Accordingly:
- Strenqo does not read IDFA on iOS and does not show the App Tracking Transparency prompt;
- Strenqo does not read the Android Advertising ID;
- Strenqo does not share advertising identifiers with third parties;
- Strenqo does not profile users for cross-context marketing.
4. Platform SDKs and services
To provide native app functionality, Strenqo uses platform SDKs and services:
- Apple HealthKit and Google Health Connect: health and fitness read/write only with explicit OS permission. Derived or associated data may be saved on Strenqo servers for workouts, recovery, trends and daily snapshots.
- Apple Push Notification service / Firebase Cloud Messaging: local and push notifications when enabled by the user. Some notifications may be AI-personalized if AI consent is enabled.
- Google Maps SDK Android: map tile rendering for outdoor cardio routes, only when GPS route functionality is used.
- RevenueCat: Pro subscription and entitlement management.
5. Optional connected services
Data transmitted to third-party processors is never used for advertising or marketing profiling.
- Google Gemini: AI Coach, food-photo analysis, plan generation and personalized notifications/briefings when AI data consent is enabled.
- WHOOP, Oura and Garmin only after approval/availability and user connection: if you voluntarily connect one of these accounts, Strenqo uses OAuth to sync wearable data on the backend, including scheduled server-side sync while the app is closed. Tokens are encrypted at rest. Garmin cloud import remains inactive until Garmin Health API access is approved/available and the user completes the connection.
- OpenFoodFacts: food/barcode search without user identifiers.
- Resend: transactional email only.
See the Privacy Policy and Subprocessor List for details.
6. User choices
You can change available choices at any time in Profile -> Support, privacy and legal and in OS settings:
- AI data consent;
- AI Coach memory, where available;
- notifications and reminders;
- HealthKit / Health Connect permissions;
- location, camera, photo and Bluetooth permissions;
- WHOOP/Oura disconnection, plus Garmin disconnection if available and connected, from wearable settings.
Revoking an OS permission prevents new reads/writes from that point forward. To delete data already saved in your Strenqo account, use export/account deletion or write to strenqo-support@strenqo.eu.
7. Contact
- Email: strenqo-support@strenqo.eu
- PEC: andreasmondo@ultracert.it
End of document.