Privacy Policy
Last updated: July 15, 2026
Pauzi is an app built with care for parents and children. We take seriously the responsibility of protecting our users’ data. This policy explains what data we collect, why, who we share it with, and your rights.
At a glance
- We never sell data.
- We don’t run ads. Pauzi is ad-free.
- Children do not create accounts or type free-form text in Pauzi. We process child-device usage data only for features configured by the parent.
- Core account and app data is stored in the EU (Frankfurt) via Supabase. Certain limited data is processed by the providers described below, including outside the EU.
- You can delete your account anytime: Settings → Account → Delete account.
- For any data request, write to privacy@pauzi.app.
Who we are
Pauzi is operated by ROCKSOLID MEDIA SRL, Romanian company identification number 38420346, registered office in Bucharest, strada Tincani, no. 4, bl. F7, sc. 1, ap. 12, Romania.
For privacy questions or data requests, contact us at privacy@pauzi.app.
What data we collect
From the parent (you)
- Email and password or Google Sign-In — for authentication. Passwords are managed by Supabase Auth as secure hashes and we never see them in plain text. If you choose Google Sign-In, Google supplies an ID token and identity data associated with the selected account, such as the account identifier and email; Pauzi does not receive your Google password.
- Account settings — your preferences (notifications, language, parental PIN stored as a hash, device timezone).
- Subscription status — whether you have an active Premium subscription and until when (synced from Google Play via RevenueCat).
- Premium email preference — your explicit opt-in/opt-out choice and the times when you changed it.
- Premium email sending and CTA access — for each campaign we may keep the account identifier, recipient address, audience label, sending status and timestamps, provider ID or error, a random tracking token, the CTA access count and its timestamps. The CTA first passes through pauzi.app to record access and then opens the app or Pauzi on Google Play. Sending status and accesses do not prove that the person received or read the message; some email-security systems may automatically access links. Pauzi does not store the IP address in the click log.
About the child (entered by you)
- Name and age — for personalizing sessions and the way Pauzi addresses your child.
- Avatar and preferences — visual and behavior options.
- List of allowed apps — the apps you’ve approved your child to use during a session.
- Custom activities (Premium) — the text you create for your child (e.g., “Davidut, let’s dance with mommy”) and the audio generated for that text.
- Patience Chest (Premium) — star count, target set by you, reward text, generated reward audio and reward claim history.
Session activity (on the child’s device)
- Currently foreground app — to know when to display the Pauzi screen over an app that should no longer be used. In live state and reports we store the package name/label (e.g.,
com.google.android.youtube), not app content. Window metadata processed locally by the Accessibility Service is described below. - Session duration — when it started and ended, whether the child respected the time.
- Session events — messages received from the parent (nudges), suggested follow-up activity.
- Daily quota, cooldown and live progress — remaining/consumed time per day, session state, child-device battery and whether Accessibility permission is active.
On pauzi.app
- Interest/testing-list email — if you voluntarily submit it through the form, we store it with communication status and operational timestamps.
- IP address for form protection — processed transiently in server-instance memory to limit submissions to 5 within a 10-minute window. Vercel may separately process the IP in normal hosting logs, as described under providers.
Technical data (per device)
- Push notification token (FCM) — to send notifications between parent and child.
- Device role (parent/child), local installation identifier and child device link — so Pauzi can distinguish the parent phone from the child phone and sync the right profile.
- App version, device model, Android version — used for error reporting, performance diagnostics (Sentry) and debugging.
- Pairing code — generated temporarily when linking parent-child devices and valid for 10 minutes.
- Device timezone — for correctly scheduling quiet hours. We do NOT collect GPS coordinates or real location.
- Install attribution — after sign-in, we read the raw referrer string from the Google Play Install Referrer service and extract
utm_source,utm_medium,utm_campaign,utm_term,utm_contentandgclidwhen present. We associate them with the account identifier to measure install source and the onboarding funnel. This processing is separate from the Firebase Analytics setting. - Onboarding progress — we keep the account identifier, the milestone reached (for example offer viewed, trial activated, phone type selected, or setup completed), flow version, app version, and a server-generated timestamp. We use this data to identify unclear steps and compare onboarding variants in aggregate; this processing is separate from the Firebase Analytics setting.
▸Detailed — main database fields
In Supabase Auth: account identifier, email, identity data supplied by the authentication method and a password hash when you use password authentication. In users: id, email, language, country, timezone, onboarding status, subscription status, analytics preference. In parent_settings: parental PIN hash, notification preferences and language. In child_profiles: name, age, avatar, tone, default duration, daily quota, cooldown and bedtime schedule. In routines and child_default_activity_prefs: routines and selected default activities. In custom_activities and tts_usage: activity text, TTS audio status/path/hash, voice, TTS errors and generated character counts. In sessions and session_events: session start/end, planned/actual duration, screen_time_seconds, per-app app_usage, end reason, suggested activity, acknowledgements and overlay events. In child_installed_apps and child_allowed_apps: installed and allowed package names/labels. In child_live_state: heartbeat, accessibility_ok, battery, current app, session progress, quota/cooldown. In child_devices and device_tokens: device role, locally generated device_instance_id, FCM token, model, app version, platform and last_seen. In pairing_codes: temporary pairing codes. In subscriptions: provider, product_id, status, start/expiry, renewal, unsubscribe-detection time and RevenueCat webhook payload. In reward_programs and reward_events: stars, target, reward text, TTS audio status/path/hash and reward claim history. Other functional tables keep voice nudges, request throttling, announcement reads and trial-reminder delivery state. In user_acquisition_attribution: raw referrer, UTM, gclid and timestamps associated with the account. In onboarding_conversion_events: account identifier, milestone, flow version, app version and server-side timestamp. In analytics_events: only technical/product analytics events if the option is enabled. In waitlist: email, status, testing track, Premium-pending flag, operational notes (which may include the audit of a replaced address) and timestamps. Operational email campaign logs may keep the recipient address, status, Resend ID and any delivery error.
Sensitive Android permissions
Pauzi uses sensitive permissions on the child’s device to do its job. Here’s exactly which and why:
Accessibility Service
Required on the child device to detect foreground app/window changes, calculate per-app usage time and redirect from disallowed apps. We process the package name, window type and window bounds. On certain devices we use the list of interactive windows; if we detect another app in a floating window while child mode is active, Pauzi may request that it be closed through ACTION_DISMISS (falling back to the global Back action) and redirect to the child launcher. We do NOT traverse the UI tree, read text, chats, passwords or form fields, or record the child’s keystrokes or gestures.
“Display over other apps” (System Alert Window)
Required to display the Pauzi interface over another app (e.g., over YouTube when time’s up).
Foreground Service
Used to keep the session active in the background, even if you temporarily close the Pauzi app. A permanent notification “Pauzi session active” is shown.
Notifications (POST_NOTIFICATIONS)
For the active-session notification, messages from the parent on the child’s device and alerts about the child on the parent’s device. On Android 13+ this permission is requested explicitly; if you deny it, some alerts and the session notification may not appear in the notification drawer.
Audio (Audio Focus)
Used to play Pauzi’s voice and, when the system allows it, temporarily lower other apps’ volume while Pauzi speaks. We do NOT use the microphone and we do NOT record audio.
▸Detailed — all permissions requested by the app
INTERNET and ACCESS_NETWORK_STATE (account and server connectivity), POST_NOTIFICATIONS (active-session and parent-child notifications), FOREGROUND_SERVICE and FOREGROUND_SERVICE_SPECIAL_USE (active session foreground service), SYSTEM_ALERT_WINDOW (Pauzi overlay), BIND_ACCESSIBILITY_SERVICE (declared by the service, manually enabled by the user), RECEIVE_BOOT_COMPLETED (technical observability hook after reboot; the current version only logs the system event), SCHEDULE_EXACT_ALARM (accurate midpoint/warning/end timers), VIBRATE (brief haptic feedback after an incorrect PIN), QUERY_ALL_PACKAGES (show installed apps so the parent can choose allowed apps), KILL_BACKGROUND_PROCESSES (used locally, where Android allows it, to help return the child from blocked apps). These permissions do not give us access to contacts, photos, messages or microphone audio. Accessibility is described separately above, including window metadata and the limited dismiss action.
What we do NOT collect
- We do NOT access contacts, photos, calendar, SMS, or emails.
- We do NOT collect GPS or Wi-Fi location. We only use the device timezone.
- We do NOT read app contents (we do NOT track which YouTube videos your child watches, NOT read messages, NOT record audio).
- In the app we do NOT use tracking cookies. On the website (pauzi.app) we use Google Analytics only if you explicitly accept it from the cookie banner (details under “Who we share data with”).
- We do NOT sell or share data with advertising networks.
- We do NOT ask the child to enter personal data or free-form text. The child interacts with overlays, the child launcher and the Patience Chest; those interactions are saved only as session/reward events.
Why we need this data
- Authentication data: so you can sign in with email/password or Google Sign-In from multiple devices and not lose data when you switch phones.
- Child profile: to personalize sessions — duration appropriate for the age, tone matching the child’s temperament, addressing by name.
- Current foreground app: to display the Pauzi screen at the right moment, over the app the child is using.
- Session history: to show you in Activity whether the child respected the time, on which days / at what hours.
- FCM token: so the parent can send messages to the child’s device (and vice versa — “your child is offline” alerts).
- Stars and rewards: so Pauzi can show the child’s progress, open the chest at the parent-set target and keep reward history.
- TTS text: so OpenAI can normalize the short Romanian text and ElevenLabs can generate voice for the custom activity or parent-approved reward.
- Subscription status: to unlock the Premium features you’ve paid for.
- Install Referrer, UTM and gclid: to measure the source/campaign that led to the install and how users progress through onboarding. This purpose is separate from Firebase Analytics and the “Usage statistics (Firebase)” choice.
- Email submitted on the website: to manage your access/testing request and related operational communications.
- Premium emails and CTA tracking: only if you separately enable marketing emails, we may send Premium or trial messages and measure whether the CTA was accessed to evaluate the campaign. The legal basis is your consent. You may withdraw it at any time in Settings → Premium and trial emails or through the email’s unsubscribe link, without affecting prior lawful processing.
Who we share data with
To make Pauzi work, we use the following service providers and, where applicable, processors/sub-processors:
Supabase (EU — Frankfurt, Germany)
Database, authentication, Edge Functions and storage provider. Stores accounts, child profiles, sessions, live state, custom activities, TTS audio, rewards and technical tokens. Data at rest is encrypted. Supabase Privacy Policy.
Google Sign-In / Credential Manager — optional
If you choose “Continue with Google”, Google processes account selection and supplies Supabase Auth with an ID token and identity data permitted for the selected account, such as its identifier and email. Pauzi does not receive your Google password. Google Privacy Policy.
RevenueCat (USA)
Manages Premium subscriptions. Receives your unique Supabase identifier (UUID, not name/email) and Google Play purchase info. RevenueCat Privacy Policy.
Google Firebase Cloud Messaging (USA, under Google)
Sends push notifications. Google processes the token tied to the Pauzi installation and the payload required for delivery; depending on the alert, this may include the child’s name, app name, duration/minutes or session summary. We do not send the content of other apps’ windows through FCM. Firebase Privacy Policy.
Sentry (USA)
Collects error reports and performance diagnostics so we can fix bugs quickly. Data sent may include: error type, stack trace, app version, device model, Android version, environment, execution timings and sanitized technical messages. It does NOT include email, password, the content of apps used by the child, or TTS texts. We do not intentionally set an account identifier in Sentry, so we cannot reliably locate a report by email address. Contact privacy@pauzi.app with questions or objections about this processing. Sentry Privacy Policy.
OpenAI — Premium text normalization
When you create a custom voice activity or a spoken reward, the short text you entered is first sent to the OpenAI API for conservative correction of Romanian diacritics, punctuation and typos. The normalized result, or the original text if normalization is unavailable, is then sent to ElevenLabs. We do not include your email, password, session history or app list in the OpenAI request, but the text may contain information you choose to write, including the child’s name. OpenAI Privacy Policy.
ElevenLabs (USA) — generated-voice features
After the normalization step described above, the activity or reward text is sent to ElevenLabs for audio generation. The free Premium demo sends a short personalized sentence that may contain the child’s name. The resulting audio is stored in Supabase Storage (EU), and the app plays it to the child or uses it as a parent preview. We do not send ElevenLabs session history, installed/allowed apps, email or password. ElevenLabs Privacy Policy.
Google Play (USA, under Google)
Distributes the app and processes Premium subscription payments. For installed-app icons, our backend may query a Google Play page using the package name, and the phone may load the resulting image from Google Play infrastructure; Google may process the package name, IP address, user agent and asset request. Google Play’s policy applies to these requests and payment transactions.
Google Play Install Referrer
After you sign in, the app attempts to read the referrer made available by Google Play and saves the raw string plus UTM parameters and gclid, when present, in Supabase. After a successful sync, the read is marked locally as completed for that account on that installation. We use this data for install-source attribution and internal funnel analysis. gclid is a campaign click identifier, not the Android Advertising ID. Install Referrer collection is separate from consent for Firebase Analytics.
Resend (USA)
We use Resend for certain operational emails and, only after the separate opt-in, for Premium or trial emails. Resend receives the recipient address, subject, content and web CTA link required for sending; it does not receive the child profile, session history or app list. Sending/status and CTA accesses are logged in Supabase, while the redirect route is hosted by Vercel; these signals are not proof of delivery or reading. Resend Privacy Policy.
Vercel (USA) — hosting for pauzi.app
The pauzi.app website, including this page and the email CTA tracking/redirect route, is hosted on Vercel. When you access the site or a CTA, Vercel processes the web request and normal hosting metadata such as IP address, user agent, timestamp and requested URL, according to the service configuration and retention; Pauzi does not add the IP to the Supabase click log. When you submit the interest-list form, the server-side route hosted on Vercel also processes the email/body transiently before insertion into Supabase. Functional Android-app data is sent directly to the providers described in this policy, not through Vercel. Vercel Privacy Notice.
YouTube — only after you start the video
The video poster is served locally by Pauzi. We do not load YouTube resources merely because you visit the page. If you press Play, we load the youtube-nocookie.com player and Google/YouTube may process the IP address, user agent and playback data under Google’s policy.
Google Analytics and Firebase Analytics (USA, under Google) — only with consent
On pauzi.app we use Google Analytics 4 to understand how the site is used (pages visited, traffic source, Google Play clicks and newsletter signups). We do not load the Google Analytics script or send Google pings before you explicitly accept. You can withdraw your choice at any time using the permanent “Cookie settings” button; on refusal we disable GA, remove accessible first-party GA cookies and reload the page without the script. In the Android app, Firebase Analytics is disabled by default and is enabled only after the parent makes an explicit choice in the post-onboarding card or later through “Usage statistics (Firebase)” in Settings. When enabled, Google/Firebase processes a pseudonymous app-instance identifier, app opens and usage sessions, screen views, technical app/device information, an approximate region derived from the masked IP address and, where applicable, purchase or subscription events. Pauzi explicitly logs the Premium demo-play and trial-CTA interactions with their screen source; we do not set the Pauzi account identifier or email in Firebase and do not send the child’s name, messages, passwords or content from other apps. Google generates the pseudonymous identifier; we do not collect the Android Advertising ID, and ad storage, ad user data and ad personalization remain disabled. Supabase onboarding-step audit, Sentry and Play Install Referrer/UTM/gclid are separate flows not controlled by this choice. Google Privacy Policy. The choice can be changed at any time in Settings.
How long we keep data
- Account + child profiles: until you delete the account.
- Session history + activity: until you delete the account.
- Custom activities, rewards + TTS audio: until you delete them, delete the child profile, or delete the account. Merely disabling a feature does not delete its history or an already generated file.
- Crash reports and diagnostics (Sentry): according to the retention configured in Sentry. We do not intentionally link them to an account/email, so we cannot reliably identify an individual report from the account address.
- FCM tokens: deleted on sign-out or account deletion. After uninstall or token rotation, Google may invalidate the old token; if the device could not remove its record, it may remain in our database until the account is deleted.
- Pairing codes: usable for 10 minutes. Expired records are removed periodically, normally within approximately 30 hours after expiry.
- Install attribution (raw referrer, UTM, gclid): until you delete the account; the database record is linked to the account and deleted with it through cascading deletion.
- Onboarding milestones: until you delete the account; they are linked to the account identifier and deleted with it through cascading deletion.
- Subscription status and technical RevenueCat payload: until you delete the account. Payment documents processed by Google Play follow Google’s policy and legal obligations.
- First-party analytics events: until you delete the account; disabling the setting stops future collection. Retention for data processed by Firebase/Google Analytics follows the service configuration and Google’s policy.
- Interest/testing-list email and recipient-history copies: until you request deletion or withdrawal from the list at privacy@pauzi.app. Our erasure procedure removes both the waitlist row and address copies in recipient logs; data already sent to the email provider follows its controls and retention.
- Marketing consent and Premium campaign history: the preference, sending/status history, token and CTA events linked to the account are kept until account deletion or an earlier justified erasure request. Unsubscribing stops future messages but does not automatically erase the prior log needed for audit and security. Copies already processed by Resend and normal Vercel logs follow those providers’ retention.
Your rights (GDPR)
As an EU user, you have the following rights:
- Access: to know what data we hold about you. Write to privacy@pauzi.app.
- Rectification: to correct incorrect data. Child profile is editable directly in the app.
- Erasure: delete app-account data from Settings → Account → Delete account. For an email submitted separately through the website form or used on the tester list, use the request process on the dedicated page or write to privacy@pauzi.app.
- Portability: to receive a copy of your data in machine-readable format (JSON). Write to privacy@pauzi.app, we respond within 30 days.
- Objection: to object to certain processing (e.g., crash reporting). Write to privacy@pauzi.app.
- Withdraw marketing consent: turn off “Premium and trial emails” in the app or use the unsubscribe link in any such email.
- Complaint to supervisory authority: if you believe we’re violating your rights, you can complain to ANSPDCP (Romanian DPA) or your country’s authority.
Children under 13
Pauzi is designed for parents and legal guardians of children aged 3–8, and the account belongs to the parent (or legal guardian). The child may interact with the Pauzi overlay, the child launcher and the Patience Chest, but cannot create an account and does not type free-form text. Child data is configured by the parent and can be deleted anytime. Consistent with GDPR Article 8, we process children’s data under the parent’s/legal guardian’s authority and choices, as described in this policy.
Security
We use encrypted HTTPS/TLS connections, encrypted storage provided by our vendors and access controls for administrative systems. Passwords are managed and stored as secure hashes by Supabase Auth; Pauzi does not store them in plain text.
If a security incident occurs, we will assess the risk and notify the competent authority and/or affected individuals when required by law, within the applicable timeframes.
Changes to this policy
If we make material changes affecting your rights or how we use data, we will notify you through appropriate channels before they take effect where required by law. The updated version will always be available on this page, with the last modification date visible at the top.
Contact
For any privacy question or to exercise your GDPR rights, write to privacy@pauzi.app. We respond within 30 days (usually much faster).
For general tech support: support@pauzi.app.