This Privacy Policy explains how the Dribtack iOS application (the “App”) handles information about you. References in this Policy to “we,” “us,” or the “Publisher” refer to the publisher of the App. It is written to be readable. Where we use a defined term, we mean what it says here.
This Policy covers the Dribtack iOS app and any data processed in connection with it. It does not cover websites, services or apps operated by Apple, RevenueCat or other third parties, even if you reach them from inside Dribtack.
For data we determine the purpose of (such as the small set of pseudonymous purchase analytics described in §5), the Publisher acts as the “controller” under EU/UK GDPR. For data that lives only on your device or in your private iCloud database, we do not act as a controller because we do not have access to it.
The vast majority of Dribtack’s data lives on your iPhone and is processed entirely on-device. We do not transmit it to any server we operate (we do not operate a server). This includes:
None of this leaves your device unless you explicitly enable iCloud sync (see §3) or use the share-card feature (see §7).
If you are signed into iCloud and have iCloud Drive enabled for Dribtack, the App synchronises the categories listed in §2 (other than purely device-local flags) to your private CloudKit database. This means:
If you sign out of iCloud, disable iCloud for Dribtack, or delete the App, the on-device copy of your data is removed by iOS in the usual way. The iCloud copy is governed by your iCloud account settings.
Dribtack relies on a number of Apple services. Apple acts as an independent controller of the data it collects through those services. We do not receive identifying information from Apple, but you should be aware that:
NSUbiquitousKeyValueStore. The same iCloud privacy framing applies.To understand sales performance, conversion and renewal rates, the App integrates the RevenueCat SDK. RevenueCat acts as our processor for billing analytics: it observes the StoreKit transactions that occur in the App and provides us with anonymised, aggregate dashboards and webhook events.
| Category | Specific data | Purpose |
|---|---|---|
| Pseudonymous user ID | An anonymous “App User ID” (e.g. $RCAnonymousID:…) generated by the RevenueCat SDK on first launch. We do not call Purchases.logIn with any account identifier, because the App has no account system. |
To group transactions belonging to the same install / Apple ID and avoid double-counting. |
| Device identifier | The iOS Identifier for Vendor (IDFV). | De-duplication and entitlement matching. |
| Network identifier | Your IP address (used by RevenueCat for country-level geolocation, tax handling and fraud detection; not stored long-term in identifiable form). | Geographic analytics, fraud prevention, tax compliance. |
| Transaction metadata | The App Store product identifier of the purchased subscription or one-time in-app purchase, transaction and original-transaction identifiers, purchase and expiration dates, price and currency, country of purchase, trial / introductory-offer status, refund or chargeback events. | Subscription analytics: conversion, retention, churn, LTV, revenue. |
| Environment metadata | App version, OS version, device model, locale, SDK version. | Diagnostics and segmentation. |
Under EU/UK data-protection law, the IP address and device identifier described above are still considered personal data even though they are not directly identifying. We have therefore described them clearly here rather than calling the integration "fully anonymous."
RevenueCat’s own privacy practices are described at revenuecat.com/privacy.
For clarity, the Publisher itself does not:
Because most of your data never leaves your device or your iCloud, “use” in the privacy sense applies to a narrow slice:
If you are in the EU, EEA, UK or Switzerland, our legal bases for processing the limited personal data described in §5 are:
For everything that stays on your device or in your iCloud, no Publisher-side legal basis is required because the Publisher does not process it.
The App may ask for the following iOS permissions:
We share personal data only as described in this Policy:
RevenueCat is based in the United States. Where we transfer personal data of EU/UK/Swiss users to RevenueCat, we rely on the EU Standard Contractual Clauses (and the UK Addendum / Swiss equivalent where relevant) as the lawful transfer mechanism, supplemented by RevenueCat’s technical and organisational measures. Apple operates a global infrastructure and will determine the location of data it processes in accordance with its own policies.
On-device and iCloud data is retained for as long as you keep the App installed and your iCloud account configured. You can permanently delete it at any time using the in-App control: Profile → Manage Data → Delete All Data. This wipes your sessions, logs, sets, measurements, personal records, custom templates, custom exercises, and profile from your device, and propagates the deletion to your iCloud database (and through CloudKit to any other Apple devices signed into the same Apple ID).
RevenueCat retains transaction-level data for as long as it is needed for analytics, fraud prevention and the Publisher’s tax and accounting obligations (which can be up to ten years in some jurisdictions). To request deletion of RevenueCat-side records associated with your install, contact us at the address in §17 with the approximate date of your purchase and your country of purchase — we will use that information to identify the relevant pseudonymous record and ask RevenueCat to delete it, except where a legal obligation requires us to keep it.
Depending on where you live, you may have rights to: access, correct, delete or receive a copy of your personal data; object to or restrict its processing; withdraw consent; or lodge a complaint with your local data-protection authority. Because most of your data lives on your own device and your own iCloud account, you can exercise most of these rights yourself by editing or deleting data in the App, or by managing iCloud settings on your device.
For the limited data described in §5, contact us using §17 and we will respond within the timeframe required by applicable law (typically one month under GDPR).
If you are a California resident, you have rights under the CCPA/CPRA, including the right to know, delete and correct, and the right to opt out of “sale” or “sharing” of personal information. We do not sell or share personal information for cross-context behavioural advertising.
Dribtack is not directed at children under 13, and we do not knowingly collect personal data from anyone under 13. Use of Dribtack by minors above the age of 13 should be supervised by a parent or guardian.
We rely on Apple’s platform security (iOS sandboxing, Keychain, iCloud encryption in transit and at rest) for on-device and iCloud data, and on RevenueCat’s security programme for the analytics data described in §5. No system is perfectly secure; we encourage you to keep your device, OS and Apple ID protected with up-to-date software and a strong passcode or biometric lock.
We may update this Policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, surface the change in the App or on the App Store listing.
For any questions or to get in touch, reach out at:
Asad Nawaz
Email: turretspire@gmail.com