Family privacy
Your family’s information.
OkayTu is operated by Mindset Cyber Pty Ltd. This policy explains the OkayTu family communication app and this parent-facing website. Contact us at hello@okaytu.com about privacy, access, correction or deletion.
Last updated 14 November 2026.
Family accounts and children
OkayTu is intended to be set up and managed by a parent or guardian. New parents sign in with Apple. Existing OkayTu accounts may also sign in with their email address and password, which Supabase processes for authentication. Neither sign-in method by itself verifies adulthood or parental authority. We process the account identifier and email supplied by Apple or used for an existing email account, family and member identifiers, display names, chosen relationship labels, device registrations, approved contacts and settings to connect the right people.
A child’s Watch joins through parent-controlled pairing. There is no public family directory or public child profile. Parents should explain to children how messages, location and Help work, choose suitable contacts and keep account access secure. Do not add a child or another person without the authority to manage that relationship.
Voice, messages and delivery state
OkayTu processes live audio, saved voice recordings and fixed quick messages for family communication. Voice and quick-message content are encrypted on the sending device for authorized recipient devices before transfer. Our services route and store encrypted content along with information needed for delivery, such as family, sender, recipient, message and device identifiers, timestamps, message type and delivery receipts. Selected fixed notification previews are described below.
Encryption does not hide all service metadata, stop a recipient from replaying or recording a message, or protect an unlocked device that someone else can access. A Delivered receipt is not proof that someone listened. Heard is a separate playback receipt. Read/unread controls available in supported app versions manage the inbox without pretending that a recording was heard.
Location, Find, Help and battery
Location features use device permission and depend on an internet connection. Location coordinates, accuracy, capture times and exact battery reports are encrypted for approved recipient devices before upload. Services also process sharing-session, reporting-setting, request and device-status metadata.
After location setup, an authorized parent can request a child’s location without a new tap of approval from the child each time. A child can ask to find a parent. Sharing the parent’s position uses the parent’s Find flow and permission. Optional routine reporting and background location have their own setup controls. The 15, 30 and 60-minute choices are reporting targets, not guaranteed wakeups.
Deliberately asking for Help alerts approved family members and can request faster location updates while that Help incident is active. Resolving Help is a shared family action in supported versions; it ends that incident’s faster updates, not separately enabled routine reporting. Receiving a Help alert does not guarantee that a parent saw it or can respond.
The reporting service keeps the latest encrypted report instead of a location trail. Find uses short-lived encrypted position samples. Disabling a reporting source removes the retained opaque report because the service cannot selectively remove a field inside ciphertext. Deletion from active services is not a claim of immediate removal from every backup.
Profile photos
Parents may choose, crop and upload a profile photo. The app prepares a smaller JPEG and removes source metadata before upload. Photos are held in private storage with access checks and temporary download links. They are not end-to-end encrypted. Preset avatars do not upload a personal photo. Only choose pictures you have permission to use.
What a notification reveals
Apple’s notification service receives routing information, the sender’s family display name, the message type and selected fixed previews, such as “I’m OK”, Help, a Find request or a low-battery threshold. These fixed previews are intentionally available before message decryption and are not end-to-end encrypted. They may appear on a lock screen according to the recipient’s settings.
Voice recordings, location coordinates and exact battery readings are not included in notification payloads. Notification permission and previews can be changed in system settings. Turning off previews does not remove service routing metadata.
Service providers and security
OkayTu uses Supabase for account authentication, the application database, private storage and server functions; Cloudflare for website hosting, routing and live communication infrastructure; Apple for Sign in with Apple, app distribution through the App Store and TestFlight, notifications and subscription payments when purchasing is available; Sentry and PostHog US Cloud for limited operational diagnostics in supported release builds; and Resend for account service emails and website contact delivery. Support email uses our Microsoft 365 mailbox. If you enable optional parent iPhone analytics, limited usage events go to PostHog US Cloud as explained below. These services process the information needed to provide their part of OkayTu and may operate in countries other than yours.
We use access controls, encrypted content, protected device storage and limited diagnostic information to operate and protect the service. Security and abuse-prevention records may include request outcomes, device and account identifiers, network information and a one-way hash of source addresses used for pairing abuse prevention. No system can promise absolute security.
The native iPhone and Watch apps do not include Google Analytics, Microsoft Clarity or advertising SDKs. Optional iPhone analytics and the separate technical PostHog reports use explicit requests without a PostHog SDK. The apps separately include Sentry's diagnostic SDK, as described below. We do not use family messages or location for advertising.
Inviting another parent
A parent can choose to email an OkayTu invitation or open Messages with a prepared invitation to send. Email invitations use the address entered by the inviting parent, a private invitation link and code, an expiry time and delivery information. Resend processes that information to send the invitation. The message does not include child names, locations, recordings or photos. For SMS, the Messages app and its delivery provider handle the recipient and message; OkayTu does not upload the phone number entered in Messages.
An invitation grants parent access to manage the family only after the recipient signs in and confirms joining. Approval to communicate with each child is separate. Invitations expire after 24 hours, can be revoked earlier and are for one parent. Keep the link and code private. Opening a link or receiving an email does not join a family automatically.
The invitation landing page does not load browser analytics. The app keeps a pending invitation in protected device storage so it can continue after an interrupted sign-in. Our invitation email queue removes the recipient address and message body through routine cleanup after the invitation expires, while opaque delivery and abuse-prevention records are kept for up to 30 days. These cleanup limits apply to our service, not to copies in a recipient mailbox or provider backups. Invitation email is separate from automatic account lifecycle notices.
Account service emails
We send service emails to verified parent account addresses: welcome messages, verified subscription-status changes, deletion updates and inactivity notices. These are operational messages, not a marketing subscription. Apple manages payment receipts and billing. An OkayTu email about renewal being turned off does not itself cancel a subscription or mean the account has been deleted.
Resend processes the recipient email address, the service-message text, an opaque message identifier and delivery information to send these messages. We do not include child names, private recordings, photos or location. Delivery, bounce and complaint events help us retry safely and prevent automatic inactivity deletion when a warning has not been delivered. Provider acceptance or a delivered event does not prove that a person read the email. If you use Apple Hide My Email, forwarding and Apple’s private relay settings also affect delivery.
Our email queue removes recipient addresses and message bodies through routine cleanup after 30 days for ordinary account notices and after 90 days for inactivity notices. Delivery-event records expire after 90 days. These are service-side cleanup limits, not a promise that a recipient mailbox, Resend or a provider backup immediately removes every copy. A deletion-completion notice may retain the minimum address needed to send that final update within the ordinary 30-day limit.
Subscriptions and billing
Subscribe in the OkayTu iPhone app through Apple. No subscription is sold through this website. Opening Subscription in supported parent iPhone builds lets RevenueCat process an account-linked identifier and available App Store subscription information to show plans, restore purchases and check subscription status. This can include the product, transaction, purchase date, renewal and expiry status. Apple processes any subscription payment. RevenueCat also provides subscription reporting. This billing processing is separate from optional parent usage analytics.
Our server uses verified billing information to associate one subscription with the correct OkayTu family and its approved caregivers. We do not send family messages, photos, child names or location to RevenueCat for billing, and we do not set subscriber email or other profile attributes. Billing requests still expose normal network information to the receiving service. Read RevenueCat’s privacy policy and Apple’s privacy policy for their processing.
Account deletion queues a request to remove the associated RevenueCat customer record. An unavailable provider can delay that separate cleanup. Apple may retain transaction information, and records that must be retained for legal or security obligations have separate limits. Deleting an account, the app or a RevenueCat record does not cancel Apple billing. Use Manage Apple subscriptions to cancel renewal; account deletion can still be requested before the subscription expires.
Retention, access and deletion
Accounts, family settings and saved message records are retained to provide the family service until they are deleted. Saved voice recordings do not currently have an automatic age-based expiry. Replacing a photo does not instantly delete all copies or previously downloaded versions. Short-lived Find samples and the latest-report model have separate limits described above.
Supported app versions provide account-deletion and family-access controls. Where available, signing in with Apple again lets OkayTu revoke the Apple connection as part of deletion. When you sign in with Apple, the app attempts to send a one-time Apple authorization code to our server. After verifying the account, the server stores the resulting revocation credential encrypted and bound to that account. This credential is used to revoke the Apple connection during eligible deletion; it is not used to read Apple mail, contacts or other apps. The one-time code is not retained, and the stored credential is removed after confirmed revocation or account cleanup. If verification is unavailable, supported versions let you continue the saved deletion request and remove that Apple connection separately. If you are the only active parent, deleting the account also requires a decision about the family it manages. If other parents remain, their family and child profiles are preserved. A deletion request is not complete until the service confirms it; do not assume signing out, removing the app or disabling a contact deletes the account. When stored uploads need to be removed, deletion can remain pending for just over two hours while existing upload links expire. Cleanup retries or a service interruption can take longer.
If your version does not show these controls, or a request does not complete, contact hello@okaytu.com. We may need to verify that you own the account or are authorized to manage the child’s information. Ask us to explain the scope and progress before deleting a shared family. Do not email passwords, pairing codes or a child’s location.
Deletion from active systems does not instantly remove provider backups, copies already received by another family device or information that must be retained for security or applicable legal obligations. Contact us for the retention information relevant to your request. We do not promise an unverified backup-deletion deadline.
Cleanup of inactive accounts
Automatic inactivity cleanup applies only when the whole connected family has been inactive and no account in that family is protected by an active paid subscription, trial or billing grace period. It does not delete a quiet parent’s account while another family member is still using OkayTu. A pending purchase, uncertain billing status or an unresolved Apple revocation requirement holds the process for review.
We send the first warning after 45 days of inactivity, followed by a reminder from day 82. The earliest normal deletion date is day 90. Each notice shows an exact earliest date. Deletion also requires at least 30 days after the first warning is positively delivered and at least seven days after the reminder is positively delivered. Late delivery moves the deletion date later; missing delivery stops automatic deletion.
Open OkayTu and sign in to keep the account. We check activity across the family and verified subscription status again before removal. Service interruptions and the existing upload-link expiry and cleanup process can delay completion. This automatic policy does not restrict your right to request account deletion yourself, even while a paid subscription is active.
Operational app diagnostics
Supported release builds use Sentry and, as updated versions become available, PostHog US Cloud to help identify and fix technical failures. This is separate from optional usage analytics and is not controlled by the analytics switch. The iPhone can report fatal crashes and a fixed startup-failure code. The Watch can report fixed startup or connection-setup failure codes; automatic Watch crash reporting is not supported.
As updated releases become available, both apps send a limited sample of technical outcomes to Sentry and PostHog for sending encrypted messages, receiving and playing messages, connecting live audio, requesting Find updates, scheduling Watch background refreshes and submitting encrypted device reports. These technical reports are on by default and remain separate from optional usage analytics. Newer versions also report fixed outcomes for startup, sign-in restoration, Watch connection setup, pairing and access checks. Detailed startup-failure codes and crash reports go only to Sentry. The fixed outcomes are succeeded, failed, unavailable and recovered. Each supported technical stage can report an outcome once per app process, with a maximum of 36 operation reports to each provider. Acceptance of a background refresh request does not prove that the operating system ran it. Acceptance of a device report does not prove that it contains a fresh location. These reports contain no operation duration, message kind, Help status, family role or account identity. They help distinguish a technical fault from an unavailable connection or access condition. They are not a complete activity record, a count of every attempt or proof that another person received or heard a message. Older installed builds do not gain this reporting until updated. Support enquiries are handled separately through our contact form or email.
Before transmission to Sentry, OkayTu reconstructs each allowed report to retain technical information such as the report time, app version and build, platform, operating-system name/version/build, CPU architecture, a fixed failure code or technical stage and outcome. Crash reports may also include program stack addresses and compiled-binary identifiers. Operation reports do not include stacks or exception details. A queued crash may retain its original app version so we can match the correct software. Binary identifiers describe the app software, not a family or device identity. Reports do not include a hardware model or owner/device name, family names or identifiers, message content, audio, photos, location, arbitrary error text, request details, user or installation identifiers, local file paths, breadcrumbs or memory variables. We disable session replay, performance tracing, profiling, logs, screenshots, view-hierarchy collection and session tracking in this integration.
PostHog technical reports contain the fixed technical stage and outcome, app version, build, platform and schema version, plus a random report identifier. Newer versions also include a random identifier that stays the same for that app installation across launches and foreground sessions. It is stored in the app’s private storage, excluded from backups and separate from account, family, service-device and advertising identifiers. The phone and Watch each have their own identifier. It links reports from the same installation so we can investigate reliability and count reporting installations. The first report is not proof of a new download, and these counts do not identify people or families. If optional usage analytics is enabled on the iPhone, its events share that installation identifier. Signing out or turning optional analytics off does not reset it. Removing the app’s data removes the local identifier, but does not delete events already received by PostHog. The payload requests no person-profile processing or IP-based location enrichment. This is pseudonymous data linked by installation, not a guarantee of anonymity. There is no PostHog SDK, session replay, automatic screen capture, persistent report queue or automatic retry. PostHog still receives normal network information, including the connection’s IP address and receipt time. Our last recorded provider settings check found IP discard enabled; this is not a promise of anonymity or a fresh verification of provider processing.
The Sentry SDK may first store local crash records and queue events for later transmission or retry. Removing information before network transmission does not mean the original local crash record was already scrubbed. This diagnostic storage is separate from the optional analytics event flow. Sentry receives allowed reports through its US ingestion endpoint, and its network providers necessarily receive the connection’s IP address. We instruct the SDK not to infer a user IP address, but cannot promise anonymity or the absence of network processing.
Operational reports are not joined to family accounts. Turning off optional analytics does not stop operational diagnostics or delete reports already received. Deleting an OkayTu account does not automatically identify these reports for deletion. Contact hello@okaytu.com for help with diagnostic-data access, retention or deletion, and read Sentry’s privacy policy and PostHog’s privacy policy for their processing. We do not promise an unverified retention deadline or a single-country location for all provider systems and backups.
Optional parent iPhone analytics
Supported iPhone builds offer a separate optional analytics choice in Account and privacy. It is off by default, applies only to that iPhone and is not required to use OkayTu. Allowing website analytics does not enable it. Neither child nor parent Watches send these analytics events.
If you opt in, existing iPhone versions send three types of opening event to PostHog US Cloud: the parent app opened, settings opened and inbox opened. As updated versions become available, an explained optional choice also covers selected setup, pairing, first-conversation, plan-viewing, subscription and restore outcomes, feedback-form opening and email preparation, and your reported results from an alert check. A parent who previously allowed only opening events must choose Allow updated analytics before those additional events are sent. An alert-check result records what the parent reported, not automatic proof of delivery. Feedback comments and experience answers are not included in analytics. These selected events help us understand where setup or purchasing becomes difficult; they are not a complete record of every action. Each event contains the app version, build, platform, analytics schema version and a temporary foreground-session identifier. Newer versions also include the same random installation identifier used for PostHog technical reports. The session identifier changes each foreground session and each opt-in, while the installation identifier persists across launches. This lets us group opted-in usage and technical reports from that installation without linking them to family records. It is not an account, hardware or advertising identifier.
Beyond the random installation identifier, we do not send service-device identifiers, names, account or family identifiers, contacts, message identifiers or content, voice recordings, photos, location, Help status or check-in answers in these events. There is no automatic screen capture, session replay, crash capture or feature-flag collection in this PostHog integration. Separate operational diagnostics, including the technical PostHog reports, are described above and are not controlled by this optional analytics choice. IP-based location enrichment is disabled, but PostHog and its network providers still receive the connection’s IP address and event receipt times. Limited collection is not a guarantee of anonymity.
You can turn this choice off in Account and privacy. The app stores your choice locally, does not save analytics events in an on-disk queue and does not automatically retry them. Opting out, leaving the app or signing out cancels pending analytics requests. Cancellation cannot recall a request already received by PostHog. Turning analytics off or deleting an OkayTu account does not automatically erase events already received by the provider. Contact hello@okaytu.com about analytics retention or deletion, and read PostHog’s privacy policy for information about its processing.
Contacting us and sharing feedback
Updated iPhone versions can offer a short, optional parent feedback form after some use, as well as a Send feedback action. You can postpone the invitation or choose not to be asked again. The app keeps communication dates and dismissal preferences locally for this invitation. It does not send those dates as part of feedback. Comments stay in memory while you prepare them. You choose whether to include the app version, operating-system version and device class, then review the email before sending it. Without Mail, you can copy your feedback into our website form. We do not attach family identifiers, recordings, messages or coordinates automatically. Sending feedback is separate from allowing analytics.
The contact form asks for your email address, topic and message, with an optional name. We use these details to answer your enquiry. Sending a message does not subscribe you to marketing. Please do not include a child’s location, private recordings, passwords or pairing codes. Support is not an emergency service.
Cloudflare hosts the form and checks for abuse using Turnstile and a short-term request limit. Turnstile processes browser and network information for its security check. After that check, our server sends your enquiry through Resend to our Microsoft 365 support mailbox at hello@okaytu.com. The message uses your address as the reply address so we can answer you. These providers may process information outside your country.
We do not load Google Analytics or Microsoft Clarity on the contact page, even if you allow analytics elsewhere. Form contents are not saved in browser local storage, and our contact handler does not log message text, email addresses or security tokens. This does not mean that email providers or hosting services keep no operational records. We retain support correspondence as needed to respond and manage the enquiry, subject to security and legal requirements. Contact us to request access, correction or deletion. Direct email links remain available if you prefer your own email app.
See Cloudflare’s privacy policy, Resend’s privacy policy and Microsoft’s privacy statement for their processing.
Server-side website traffic statistics
Cloudflare already processes normal hosting requests to serve and secure this website. It provides aggregate statistics about requests, response status, approximate country and referring website host. We use these statistics to understand overall traffic and service reliability, independently of your optional Google Analytics and Microsoft Clarity choice. Request totals include images, scripts and bots, not just page visits, and are not a verified count of people.
This baseline uses existing server-side request statistics, not an additional JavaScript beacon, analytics cookies, browser fingerprinting or cross-site identifiers. Cloudflare still receives normal network information, including your IP address, when serving a request. Aggregate reporting does not mean no personal information reaches the hosting provider. Read Cloudflare’s privacy policy for its processing.
Optional website analytics and browser storage
The website works without optional analytics. Google Analytics measures visits and device/browser information to help us understand which pages are useful and improve this website. Microsoft Clarity processes page interactions for heatmaps and session recordings. These tools have separate choices in Privacy choices. Clarity always needs your explicit permission, wherever you are. Neither tool loads on contact or invitation pages, pages excluded from search indexing, or non-production previews.
Google Analytics starts automatically for visitors detected in Australia or New Zealand who have not opted out. This includes analytics cookies used to distinguish visits. In all other regions, we ask before starting Google Analytics. Permission remains the default for unreviewed regions or when the region cannot be determined. A saved refusal keeps the corresponding tool off regardless of region. Global Privacy Control or Do Not Track keeps both tools off. Expired or unreadable saved choices do not become permission for automatic collection.
Our regional policy check uses the approximate country already supplied by Cloudflare from your network connection. It returns the applicable analytics policy, not your country or IP address. Our policy handler does not store either value or send it to another location service, and does not request precise device location. Network location can be wrong and does not establish where you live. Cloudflare still receives normal network information when serving the request.
Use Privacy choices in the footer to allow or turn off each tool separately. An earlier combined Allow analytics or No thanks choice is carried forward for both tools. We remember an acceptance in this browser for up to 180 days before asking again. A refusal remains until you change it or clear the browser storage that holds it. Browser or device changes can also mean a saved choice is unavailable. Turning a tool off clears its accessible first-party analytics cookies and reloads the page without its script. It does not erase data already received by the provider.
The providers may receive network identifiers such as an IP address. Our Google configuration omits URL query strings and fragments, uses only the referring origin and leaves advertising consent off. Clarity is not loaded on entry URLs or referrers with query strings or fragments, and guide-search input is masked. These limits are not a guarantee of anonymity. Read Google’s partner-site explanation and Microsoft’s privacy statement for their processing and choices.
Our Google Analytics account has additional data sharing enabled for Google product and service improvement, aggregated modelling and business insights, technical support, and recommendations to our business. This means Google may use shared data for its own product improvement, including improving advertising tools, not only to produce our website reports. Advertising consent being off does not turn off this account-level sharing. See Google’s data-sharing explanation.
Google and Microsoft may process analytics information overseas, including in the United States. We use their published data-protection terms and security measures and remain responsible for our own collection and disclosures. Google’s additional uses are covered by its controller terms, separately from processing performed on our behalf. These arrangements are not a guarantee that every country provides identical legal protection. Contact hello@okaytu.com about access, correction, deletion or a privacy concern. You can use the website without these optional tools.
The website also remembers a mascot animation preference and any pricing currency you choose in this browser. Choosing Automatic clears your saved currency choice. These local settings do not identify a child. Cloudflare supplies an approximate country from your network connection to suggest a pricing currency. Our separate pricing endpoint returns only the country code, does not store it or send it to another lookup service, and does not request precise device location. Your detected country can differ from your App Store country or region. Normal hosting requests still reach our hosting provider so it can serve and secure the site.
Questions, complaints and policy changes
Contact hello@okaytu.com if you want access to or correction of your information, have a privacy concern, or believe a child’s information was added without proper authority. Tell us enough to identify the account without sending sensitive family content. We will respond after checking identity and the scope of the request. Your rights and available complaint channels depend on where you live.
We will update this page when the service’s data practices change and show the revision date. Material new uses or optional permissions will need an appropriate explanation or choice. Review this policy alongside the terms of use.