Get It Done Son Privacy Policy

Effective: 6 September 2026 · Last updated: 12 September 2026

This Privacy Policy explains how GOBIAS LTD (“GOBIAS”, “we”, “us” or “our”) handles personal information when you use the Get It Done Son mobile application (the “App”) or contact us about it. GOBIAS LTD is the controller of personal information we receive through the App and support enquiries.

1. Information you create

Depending on how you use the App, you may create:

• life aspects, roles and role descriptions;
• habits and vices, including their names, details, frequency and tracking history;
• goals, subgoals, target dates and links between goals and habits;
• daily tracking entries, completions, occurrences, avoidances and reflections;
• category selections, ordering, rankings, challenges and reminder preferences; and
• feedback or support information you choose to email to us.

We do not ask for contacts, photos or precise location, the App does not request GPS or other device-location access, and the App does not access HealthKit. The free text you choose to enter could nevertheless reveal personal or sensitive information. Please do not enter information about another person without the right to do so, or highly sensitive information that is not needed to use the App.

2. Local storage and platform differences

iOS

App content is stored in a local Realm database. Guest progress uses a separate guest store. Each Firebase account uses its own account-specific local store. Signing out keeps the most recently used account’s progress available on that device for offline use, and that progress remains owned by the original account. Offline changes sync only when the same account signs back in. Signing into another account opens that account’s separate progress; data from different accounts is never combined automatically. Local content may be included in Apple device or iCloud backups according to your device and Apple backup settings.

Android

The Android App currently has no account, Firebase Authentication or Firestore sync. Roles, habits, goals, reflections and tracking history stay in its local Realm database. That database is excluded from Google cloud backup. It may be included in a direct device-to-device transfer when Android transfers the App’s data to a new device. Less sensitive configuration, such as reminder preferences and onboarding state, may be included in Android backup according to the device’s settings.

3. iOS accounts and cloud sync

On iOS, you may use Sign in with Apple to create or access an account. Apple provides an authentication credential to Firebase Authentication. We receive a Firebase user ID and, depending on what Apple provides and the choices you make, may receive a name or email address, including an Apple private relay address. We do not receive your Apple password.

While you are signed in, account-owned App content syncs through Cloud Firestore so that it can be restored and reconciled across signed-in devices. Synced content includes life aspects, roles, habits, goals, daily trackers, saved Coach plans, reflections, related progress and account preferences. The App also uses Firebase Functions for account preparation and deletion. Firebase Remote Config may provide feature configuration on iOS.

Signing in does not automatically import guest progress. After signing in, you may explicitly choose to move guest progress into that account. The original guest records remain on the device until cloud confirmation and verification of the transferred content have succeeded.

Sync is designed to keep guest and account data separate. It is not a backup guarantee: interrupted connections, conflicting edits, service outages or unsupported App versions can delay or prevent synchronization.

4. Analytics and diagnostics

Optional Firebase Analytics stays off unless and until you consent by choosing “Share Analytics” or turning on Settings → Privacy → Share Usage Analytics. Firebase Crashlytics and optional crash or session reporting covered by that choice are also disabled by default. You can turn sharing off again at any time; the App then disables future optional collection and resets locally held Firebase Analytics data.

If you opt in, Google may process:

• usage events such as app opens, onboarding, feature interactions, paywall and purchase-flow events, reminder changes and sync outcomes;
• coarse event details such as feature source, habit type, success status or counts;
• device model, operating-system version, App version, locale, app or device identifiers and approximate location derived from the device’s IP address; and
• crash stack traces and diagnostic information needed to understand a failure.

Custom analytics events are not designed to include habit names, goal titles, role descriptions or reflection text. On iOS, analytics may be linked to the signed-in account: if analytics is enabled when you sign in, the Firebase user ID may be used as a pseudonymous analytics user identifier. Approximate location is inferred from network information; the App does not request GPS access. We do not use analytics for advertising or tracking across other companies’ apps or websites.

Separately, Firebase services may generate operational diagnostics needed to receive and secure service requests even when optional analytics is off. These can include App, operating-system and Firebase SDK versions, network metadata such as IP address, request timing and status, and service logs. This operational processing is distinct from optional Firebase Analytics, Crashlytics and session reporting; it does not mean those optional features have been enabled.

5. Subscriptions and payment information

RevenueCat manages subscription status and premium entitlements. It may process a RevenueCat App user identifier, product and transaction identifiers, purchase and renewal events, subscription status and related device or technical information. RevenueCat uses a guest identifier when you use the App without an account and may use the Firebase user ID while you are signed in. These identifiers and purchase records are used to provide and restore subscription access and should not be understood as universally anonymous.

Apple processes App Store payments and Google processes Google Play payments. GOBIAS LTD does not receive your full payment-card details. Store and subscription providers may keep transaction records under their own legal obligations and privacy policies.

6. Reminders and support

App reminders are scheduled locally on your device after you grant notification permission. The App does not use remote push notifications for these reminders. If you contact us, we and the email providers involved receive the address, message and attachments you choose to send. Please do not send unnecessary habit, goal or reflection content in a support request.

7. How and why we use information

We use information to:

• provide local App functionality and, on iOS, requested account and sync services;
• authenticate users and keep different account and guest stores separate;
• verify subscription entitlements, process restorations and provide premium features;
• operate optional analytics and crash reporting when you consent;
• secure, maintain and troubleshoot the App and connected services;
• respond to support and privacy requests; and
• comply with legal obligations and establish or defend legal claims.

Where UK GDPR or EU GDPR applies, we rely on performance of our contract with you for requested App, account, sync and subscription functions; consent for optional analytics and crash reporting; legitimate interests in proportionately securing and maintaining the service and responding to enquiries; and legal obligations where applicable. The App is not intended as a repository for special-category information. If content you enter may reveal health or other sensitive information, it is handled as part of the content service you request and can be removed using the controls described below.

8. Service providers

• Google Firebase: Authentication, Cloud Firestore, Functions and Remote Config on iOS, plus optional Analytics and Crashlytics on iOS and Android.
• RevenueCat: subscription status, purchase restoration and entitlements.
• Apple: Sign in with Apple, App Store distribution, payments and Apple-platform subscriptions.
• Google: Google Play distribution, payments and Android subscriptions.
• Email providers: support and feedback messages that you choose to send.

These providers process information under applicable agreements and their own privacy terms. We do not sell or rent personal information and do not use third-party advertising networks in the App.

9. International processing

Google, RevenueCat, Apple and their systems may process information outside the country where you live, including in the United States. Where data-protection law requires it, we use applicable safeguards such as adequacy regulations or approved contractual clauses.

10. Retention and deletion

• Local content: remains until you delete it, remove the App, or it is removed through account-deletion or device-management controls. Content successfully preserved in guest mode before account deletion remains on the device. Existing device backups may retain earlier copies according to your Apple or Android backup settings.
• iOS account content: remains in Firestore while the account exists unless you delete individual content sooner.
• Authentication: Firebase account information remains until account deletion or another applicable deletion request is completed.
• Recovered guest copies: conflicting guest records and their linked history may be retained as read-only recovered copies on the device. They are separate from Firestore sync and may be included in normal Apple device or iCloud backups.
• Optional analytics, crash and session reports: if enabled, are retained according to the Firebase settings we maintain and Google’s applicable retention practices, then deleted or aggregated when no longer reasonably needed.
• Operational diagnostics: Firebase and other service providers may retain service and network records according to their applicable practices and operational or legal requirements.
• Subscription and transaction records: are retained by RevenueCat and the relevant store for their operational, fraud-prevention, accounting and legal requirements.
• Support messages: are kept only as long as reasonably needed to respond, maintain an appropriate record and meet legal obligations.

11. Account deletion on iOS

A signed-in iOS user can select Settings → Account → Delete Account and reauthenticate with Apple. Before requesting cloud deletion, you can choose to preserve progress in guest mode. If you do, the App refreshes the account content, saves a local guest copy and verifies that copy. Safe changes are combined. If guest records conflict, the account version remains the active copy while the original guest version and its linked history are retained as a read-only recovered copy available in guest Settings. Recovered copies stay on the device and are not part of Firestore synchronization. Normal Apple device or iCloud backups may include these App documents.

If preservation or verification fails, the App stops before requesting deletion. If cloud deletion is interrupted after preservation, the saved guest copy remains on the device. Without the preserve-progress choice, deletion removes that account’s local progress. Existing separate guest progress remains in either case.

Successful deletion removes the Firebase account, account-owned Firestore content and settings, and the account-specific local Realm store. It also revokes the Apple authorization used by the App and resets the App’s RevenueCat identity. Account deletion does not delete your Apple ID, cancel an Apple subscription or necessarily erase billing, transaction or subscription records retained by Apple, RevenueCat, Google or another provider. Manage or cancel a subscription separately through the relevant App Store or Google Play account.

12. Your choices and privacy rights

• Keep analytics and crash reporting off, or withdraw consent in Settings.
• Use guest mode on iOS instead of creating an account.
• Delete individual content using the App’s controls.
• Delete an iOS account using the in-App account-deletion control.
• Manage device backups through Apple or Android settings.
• Manage or cancel subscriptions through the relevant store account.

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing; receive portable information; and withdraw consent. Rights may be subject to legal limits and may not apply to information held only on your device, which GOBIAS LTD cannot access. You may complain to your local data-protection authority. In the UK, this is the Information Commissioner’s Office.

13. Security

We use reasonable technical and organisational measures designed to protect information against unauthorised access, loss, misuse or alteration. No device, transmission or storage system is completely secure, and we cannot guarantee absolute security. Keep your device, Apple or Google account and App access protected.

14. Children

The App is not directed at children under 13. Where local law requires a higher age for a person to consent to online data processing, a parent or guardian should provide any required authorisation. If you believe a child has provided account information to us without appropriate authorisation, contact us.

15. Changes to this policy

We may update this policy to reflect changes to the App, providers, law or our practices. We will publish the updated version at this URL with a revised date and provide additional notice where required.

16. Contact