SickSense← Back to home

Privacy Policy

Effective date: 8 July 2026 · Last updated: 8 July 2026

Who we are

SickSense ("the app", "we", "us") is developed by Three Eyed Emu, based in Perth, Western Australia, reachable at support@sicksense.tech. The app is operated by parents and guardians ("you") on behalf of children riding in vehicles ("passengers"). Children do not create accounts and do not interact with the app directly.

What this policy covers

This policy explains what data the SickSense Android app processes, where it goes, how long it is kept, and what choices you have. It applies to the SickSense Android app (com.motionsentry.app) and the backend services that support it.

What we collect

Account information

  • Email address — used to sign in. Provided by you when you create an account through Supabase Auth.
  • User identifier (UUID) — generated by Supabase when you sign up. Used internally to link your data together.
  • Display name — optional. Provided by you in app settings.
  • Sharing consent flag — whether you have opted in to share anonymised trip features for research (off by default).

Passenger profiles (about your children or other passengers)

  • Name — entered by you for each passenger. Can be a real name or a nickname.
  • Age band — one of under 5, 5–10, 11–15, or adult. We do not collect dates of birth.
  • Baseline sensitivity — your subjective rating of how prone the passenger is to motion sickness, 1–10.
  • Personalisation model parameters — derived numbers (gain, time constant) computed in a future release from this passenger's reported sickness history. Not used in V1.

Trip records

  • Start and end timestamps of each trip.
  • Seat position, windows-open, screen-use flags — entered by you per trip if you record them.
  • Driver label (always "self" in V1).
  • Calibration quality — clean, drifted, failed, or uncalibrated. Indicates whether the phone's mount was stable enough during the trip for the motion analysis to be reliable.
  • App version, device model, OS version — for debugging and compatibility tracking. Some of these fields are not yet populated in V1.

Motion analysis data

The phone's accelerometer and gyroscope produce raw data many times per second. We do not store or upload that raw stream. We compute summary features over rolling 10-second windows and store only:

  • Window feature snapshots at the moment a rule fires (e.g. average jerk, sway power, yaw rate variance).
  • Periodic diagnostic summaries (peak feature values per ~30 seconds) — see "App diagnostics" below.

We do not collect GPS coordinates (latitude/longitude). We collect GPS speed only (a single number in metres per second), which is used by the stop-and-go and sustained-driving rules.

Sickness reports

When you press "I FEEL QUEASY" or use the equivalent voice command for a passenger, we store:

  • The passenger ID, timestamp, and severity (queasy, unwell, or vomited).
  • An optional free-text note if you add one.

This is health-adjacent information about the passenger.

App diagnostics

The structured logger writes events to an error-log table to help us diagnose problems:

  • Event timestamp, scope (e.g. engine, sensor, voice, db), level (info / warn / error), and message.
  • Free-form context (e.g. feature values being computed, error details).
  • App version and your device's user-agent string (browser/WebView identifier, including device model on Android).
  • The trip ID the event relates to, if any.

These logs help us see why an alert did or did not fire on a real drive. They are gated by Supabase Row-Level Security to your account only.

Voice commands and microphone

The app supports hands-free operation while driving. You can say "stop", "mark this", "queasy", or a passenger's name to control the app.

The app does not record, store, or transmit audio. Audio is captured and transcribed by your device's system speech recognition service (on Android, this is normally Google Speech Services). Depending on your device, its operating-system version, and your account settings, that system service may process the audio on-device or upload it to its operator's servers for cloud transcription. The app only receives the resulting text and discards anything that doesn't match a known command. We have no access to the audio buffer.

If you do not wish to use the system speech recognition service, you can revoke the microphone permission in Android Settings → Apps → SickSense → Permissions. The app will continue to work using touch controls.

What we don't collect

For clarity:

  • We do not collect GPS coordinates (latitude/longitude). Only speed.
  • We do not record or store audio.
  • We do not access your contacts, calendar, photos, files, or other apps.
  • We do not use third-party analytics, ad networks, or trackers.
  • We do not collect biometric identifiers, health records, or government IDs.
  • We do not collect data about children directly — only the limited passenger profile fields you enter on their behalf.

Why we use the data

  • Account info: to sign you in and link your data together.
  • Passenger profiles: to personalise alerts to each passenger's sensitivity.
  • Trip records and motion features: to evaluate motion-sickness risk during the drive and to record what happened.
  • Sickness reports: to refine future suggestions and (with your consent) contribute anonymised data to research.
  • Diagnostics: to identify and fix bugs.
  • Voice control: to let you operate the app without taking your hands off the wheel.

We do not use your data for advertising, profiling, or sale.

Where the data is stored

All data is stored in Supabase (Postgres + Object Storage), region [SET REGION — Supabase dashboard → Project Settings → Infrastructure]. Data is encrypted in transit (HTTPS) and at rest. Row-Level Security policies in the database ensure that your data is only readable and writable by your authenticated account.

Sharing

In V1, we do not share your data with any third party.

If you opt in (off by default) by enabling "share anonymised trip features for research" in app settings, we will derive anonymised features from your trips — passenger age band, trip duration, RMS jerk values, sway power, alert counts, sickness counts — strip every identifier (your account ID, the passenger's name, the trip ID), and write them to a separate research table. No personal identifiers, names, GPS coordinates, or device identifiers are included in these anonymised features.

Supabase is our data processor — they store and serve the data on our behalf under their published security and compliance terms. They are not a third-party recipient in the sense of selling or repurposing your data.

The system speech recognition service (for voice commands) is provided by your device's operating system and the company that supplies it (typically Google on Android). The app does not send audio to that service; your device does, as part of its built-in functionality. We are not a party to that data flow.

Children's information

This app is designed for parents and guardians. Children do not interact with the app and do not have accounts.

You, the parent or guardian, may create "passenger" profiles that describe a child:

  • A name or nickname you choose.
  • An age band (no birth date).
  • Your own subjective sensitivity rating.
  • Reports about the child's sickness episodes during your trips.

By creating a passenger profile, you confirm that you have the authority to provide this information about that child, and you consent to us processing it for the purposes described in this policy.

We collect the minimum information needed to provide alerts personalised for each passenger. We do not target children with marketing, ads, or features designed to encourage their direct use of the app.

Under COPPA (US), GDPR-K (UK/EU), and similar laws, parental consent is required for collecting information about children under 13 (or 16 in some jurisdictions). The act of you, as a parent or guardian, voluntarily entering a passenger profile in the app constitutes that consent. You can withdraw consent at any time by deleting the passenger or deleting your account.

How long we keep data

We retain account, trip, and sickness data for as long as your account is active. Diagnostic logs are retained for up to 90 days.

You can delete individual passengers, trips, or sickness records inside the app. To delete your entire account and all associated data, email support@sicksense.tech from the email address you signed up with, using the subject "Delete my account" (full instructions at sicksense.tech/delete-account). We action deletion requests within 30 days. An in-app deletion option is planned. Account deletion cascades to remove all your trips, passengers, sickness records, and diagnostic logs from our database.

Your rights

Depending on where you live, you have some or all of these rights:

  • Access — see what data we hold about you. Most of this is visible directly in the app.
  • Correction — fix data that is wrong. You can edit passenger details and trip metadata in the app.
  • Deletion — delete your data. See "How long we keep data" above.
  • Portability — export your data in a machine-readable format. Currently manual — email support@sicksense.tech.
  • Withdraw consent — turn off the "share anonymised features for research" setting at any time.

To exercise any of these rights, contact us at support@sicksense.tech. We will respond within 30 days.

Security

We use Supabase's managed Postgres with Row-Level Security enabled on every table. Every row is gated by a policy that requires the authenticated account to match the row's owner, so even if the database is accessed, no user can read another user's data. All connections use HTTPS / TLS. We do not maintain a separate server-side cache of your data.

No system is perfectly secure. If we become aware of a breach involving your personal data, we will notify you and the relevant authorities as required by law.

Changes to this policy

We may update this policy as the app evolves. The "Last updated" date at the top of this document will change. Material changes will be flagged in the app on your next launch after publication.

Contact

Questions, requests, or concerns: support@sicksense.tech

If you are in the EU or UK and you believe we have not adequately addressed your concerns, you may lodge a complaint with your local data protection authority.