TIWA app

Privacy Policy

Effective date: 16 November 2026
Applies to the TIWA Android application (package com.loopbugs.tiwa).

1. Who we are

TIWA is a wellbeing companion built for a perinatal depression research study involving adolescent girls who are pregnant or caring for babies, associated with the University of Ibadan College of Medicine.

Loopbugs LTD (company number 16341224), Office 4, Second Floor Park Lorne, 111 Park Road, London NW8 7JL, United Kingdom, develops and operates the TIWA software as a processor / developer on behalf of the study team.

The research study team is expected to act as the [TO CONFIRM: data controller identity — University of Ibadan College of Medicine / named principal investigator] for study-related personal data. This policy describes what the TIWA app itself collects and where that information goes, based on the current app source code.

2. Who this policy covers

TIWA is intended only for people enrolled in the research study. It is not aimed at the general public. Access requires consent in the app and a personal PIN on the device.

TIWA does not ask for your real name, phone number, contacts, or location as part of app use. Clinic contact numbers shown in the Support screen are study-configured; dialling them uses your phone’s normal calling features and is not logged by TIWA.

3. What we collect and why

Collection is consent-gated. After you agree in the app, TIWA can create an anonymous install account and sync limited research and operational data when the device is online. If you are offline, some items are queued on the device until a connection is available.

3.1 Synced to the study backend (Supabase)

The app uses Supabase (PostgreSQL with row-level security, anonymous authentication, and private object storage). The following leave the device when consent has been given:

  • Anonymous install identifier — a random UUID from Supabase anonymous sign-in, used as the install record and to keep each participant’s rows separate (RLS). Stored with consent flag, consent time, app version, creation time, and (if you reset the PIN) a reset timestamp.
  • Usage events currently sent by the app — video_started and video_completed (with video id); todo_added (opaque client id and whether a voice note exists, not the audio itself); and todo_completed (opaque client id). Events include timestamps. Metadata is size-limited.
  • To-do metadata only — opaque client id, completed / deleted flags, and related timestamps. Task titles, written notes, and voice recordings are not uploaded.
  • Study video content downloads — educational clips and a manifest may be fetched from a private Supabase Storage bucket via short-lived signed URLs. This is study content, not participant-uploaded media.

The backend schema also allows additional event types (app_opened, app_backgrounded, video_paused, mood_check_in, progress_viewed). As of the code reviewed for this policy (tiwa-app main, November 2026), those types are allow-listed for future use but are not currently emitted by the running app screens. Mood check-ins remain on-device only (see below).

3.2 Kept only on your device

  • PIN — a 4-digit PIN is hashed with PBKDF2-SHA256 (100,000 iterations) and stored in the device secure store. The plain PIN is never sent to the server.
  • Mood check-ins — mood level and optional feeling tags are saved locally for your use in the app. They are not queued for sync in the current code.
  • To-do text and voice notes — task titles/bodies live in the on-device encrypted database. Voice notes are encrypted (AES-GCM) and stored in the app’s private file area, not in your phone gallery.
  • Streaks and trophies — progress, freezes, and earned trophies are stored only in the on-device encrypted database and are not synced.
  • Video watch position / completion — playback progress for downloaded videos is stored locally; completion is also reflected in synced events when you finish a video.
  • Offline study videos — downloaded clips stay in app-private storage (not the shared media library). Android backup of app data is disabled (allowBackup: false).
  • Language preference and local “days opened” counters for the progress UI.
  • Auth session tokens — the anonymous Supabase session token is stored on the device (via AsyncStorage) and used locally to authenticate requests to Supabase when syncing. The token itself is not a separate research dataset uploaded to the backend.

3.3 Permissions

  • Microphone — requested only so you can record voice notes for clinic to-dos. Recordings stay encrypted on the device.
  • The app checks network connectivity to know when it can sync; it does not use location services for that.
  • Screenshots and screen recording are blocked on native Android builds to reduce accidental exposure of sensitive screens.

3.4 What we do not collect via the app

  • Name, email address, phone number, contacts, or precise location as app profile fields
  • Advertising identifiers for ads (TIWA has no ads)
  • Third-party analytics or crash-reporting SDKs such as Firebase Analytics, Crashlytics, Sentry, Amplitude, or similar — none are present in the app dependencies reviewed for this policy

Optional over-the-air updates may be delivered through Expo’s update service (configured in the app build). Google Play may process install and update data under Google’s own terms when you install TIWA from Play.

4. How information is stored and secured

  • On device: participant content uses an encrypted SQLite database (SQLCipher via Expo SQLite), with the database key and voice encryption key held in the platform secure store. Voice files are encrypted at rest in app-private storage.
  • In transit / cloud: consented sync uses HTTPS to Supabase. Database row-level security limits each anonymous account to its own install, events, and to-do metadata rows.
  • Hosting region: Supabase project hosted on AWS in the EU (Paris, France — region eu-west-3), within the EU/EEA.
  • Forgot PIN: resetting the PIN wipes local app data (database, keys, voice files, video cache, local preferences) and, when online, marks the server install as reset. It does not by itself delete historical server rows already stored for the study — [TO CONFIRM: whether the study team deletes or retains historical server events/todos after a device reset].

5. Sharing, selling, and advertising

We do not sell your data. TIWA does not show advertising or share data with advertisers.

Information may be accessed by:

  • The research study team, for the purposes described in the study consent materials and ethics approval
  • Loopbugs LTD staff acting as developers/processors, only as needed to build, host configuration, and support the app
  • Infrastructure providers that process data on our instructions — principally Supabase for backend storage and auth, and Expo for app updates/builds. Google Play processes distribution-related data when you use Play

We do not share participant app data with other third parties for their own marketing. Legal disclosure would only occur if required by applicable law.

6. Children and adolescents

TIWA is designed for adolescent participants in a supervised research study (pregnant adolescents and adolescent mothers), not for unsupervised general use by children. Enrolment and consent follow the study’s ethics-approved procedures [TO CONFIRM: age range covered by the ethics approval and any parent/guardian consent requirements].

Because the app may process health-related wellbeing information about adolescents, extra care is taken to minimise what leaves the device and to avoid collecting unnecessary identifiers.

7. Retention and deletion

On your device: you can wipe local TIWA data by using Forgot PIN / reset in the app, or by clearing/uninstalling the app. Uninstalling removes on-device storage; it may not remove data already synced to the study backend.

On the study backend: retention of install records, events, and to-do metadata follows the research protocol and ethics approval — [TO CONFIRM: retention period for server-side study data after the study ends]. Soft-deleted to-do metadata may be retained for research integrity rather than hard-deleted immediately.

To request deletion of server-side data linked to your install, contact the study team using the details below. We will need enough information for the study team to locate the relevant records [TO CONFIRM: process for linking a device install to a participant for deletion requests].

8. Your rights

Depending on where you live and how the study is organised, you may have rights under the UK GDPR and/or the Nigeria Data Protection Act 2023. These can include rights to be informed, to access, to rectification, to erasure, to restrict processing, to data portability (where applicable), and to object or withdraw consent where processing is based on consent.

Because Loopbugs LTD processes app data on behalf of the study, rights requests should usually go to the study team / controller first. You may also contact Loopbugs at privacy@loopbugs.com and we will help route your request.

You may also have the right to complain to a supervisory authority, such as the UK Information Commissioner’s Office (ICO) or the relevant Nigerian data protection authority, if you believe your rights have been infringed.

9. Contact

Privacy and data-rights questions about TIWA: privacy@loopbugs.com.

Developer (Loopbugs LTD): Office 4, Second Floor Park Lorne, 111 Park Road, London NW8 7JL, United Kingdom.

Study / research team contact: Dr Lola Kola, TIWA project, Department of Psychiatry, College of Medicine, University of Ibadan, Ibadan, Nigeria. For privacy and data-rights email, write to privacy@loopbugs.com and we will route your request.

10. Changes to this policy

We may update this privacy policy when the app’s data practices or legal requirements change. The effective date at the top of this page will be revised when that happens. Material changes will be communicated via an in-app notice and by the study team.