myna

myna — Privacy Policy

Last updated: 28 August 2026 · Effective: 28 August 2026

myna is a family-coordination appliance built by Herbert Chan (Singapore). This policy explains what we collect, why, how it's used, and your rights. We follow Singapore's Personal Data Protection Act (PDPA) and apply the same standard everywhere myna ships.

Who we are

What we collect

CategoryExamplesWhy
Account & profile Name, role (parent/kid/helper/relative), avatar, gender, language, household name, optional email, optional birthday, optional Apple/Google Sign-In ID To let family members address each other correctly and personalise Aunty's voice narration.
Messages & tasks Text, voice notes, photos, video notes, calendar events, task titles, completion state The core messaging and household-coordination features.
Voice transcripts Speech-to-text transcripts of voice messages and voice announcements So Aunty can narrate the contents aloud and translate across languages.
Location Precise device coordinates from members who have location sharing switched on — including in the background, and a short recent trail of past points. On iOS we use Apple's location-push mechanism so a position can be refreshed while the app is closed. We also derive an approximate city from your IP address to show local weather. The family map ("where is Laura now?"), arrival and departure alerts for places you define, and weather. Off by default; each member can turn it off at any time in their device settings.
Documents & household knowledge Anything you or Aunty file into your household's records: scanned or photographed documents and the details read out of them. Depending on what you choose to store, this can include health information (allergies, diagnoses, doctors, immunisations), financial information (bank and insurance details), government identifier numbers (NRIC, passport, licence), and — where it appears on a Singapore NRIC — race. Also home address, emergency contacts and phone numbers. So the household has one reliable place for the paperwork it actually needs, and so Aunty can answer questions about it. Identifier numbers and other secrets are encrypted at rest (AES-256-GCM). You choose what to file; none of it is required to use myna.
Camera & microphone Live camera and microphone audio during calls; image captures for avatars and message photos Voice/video calls and message attachments. We never record calls server-side.
Calendar (iOS) Read access to selected iCloud calendars; optional write access to a chosen calendar Two-way sync between myna and your iPhone calendar. Disabled by default.
Push tokens Firebase Cloud Messaging tokens; APNs VoIP tokens (iOS) To deliver call rings, message banners, and Aunty audio to your devices.
Crash & error reports App version, device model, the error itself and a short trail of the actions leading up to it — which can include the web addresses myna called, and those contain your household and account identifiers. Collected automatically whenever the app hits an error, not only when you ask. So crashes get found and fixed. Sent to Sentry. It is not used for advertising or profiling, and we do not use it to track you.
Feature-usage records Which member triggered which AI feature and when, and a record of who called whom To keep the service running within its cost limits and to size features. Never sold, never used for ads.
Subscription state Whether the household has an active subscription, billing status from Apple/Google To gate paid features. We do not store credit-card data — Apple and Google handle payments.

What we do NOT collect

Third-party services we rely on

myna uses these processors strictly to deliver its features. Each is bound by their own privacy terms; we share data with them only as needed to operate the app.

We do not use any advertising, attribution or ad-network service. myna contains no advertising identifier and no ad SDK of any kind.

Google Calendar & Google API Services — Limited Use

When a parent chooses to connect their Google Calendar, myna requests the https://www.googleapis.com/auth/calendar scope to provide two-way sync between the household calendar and the parent's Google Calendar. This connection is optional, off by default, and can be disconnected at any time in myna's settings — which immediately revokes our access and stops all sync.

myna's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, data accessed through Google Calendar is:

How long we keep data

Children's data

myna serves households that include children. We collect only the minimum needed for the app to function: display name, optional avatar, a parent-administered task list, and — where a parent has switched it on for that child's device — precise location, including in the background, which is the point of the family map. On Android, a parent may also see which apps are installed on a child's phone and how long they are used, in order to set time limits; on iOS this is handled by Apple's own Screen Time system and those details never reach us. Children's accounts are administered by parents through the in-app Family settings. We do not show ads, do not enable behavioural profiling, and children cannot interact with anyone outside their own household.

Your rights

You can:

Security

Changes to this policy

We'll update this page when we add or change data practices, and bump the "Last updated" date at the top. Material changes will be surfaced in-app the next time you open myna.

Contact

Questions, requests, complaints — email [email protected]. We aim to respond within 7 business days.