Privacy Policy
Last updated: October 21, 2026
Kivvie is operated by M2V2 Solutions Pty Ltd, a company registered in Australia, which is the data controller responsible for the personal information described here. We built Kivvie around privacy and child safety. This policy explains what we collect, how we use it, and how we protect it. For a plain-English overview of the app, see our whitelist parental control feature or read about how we remove YouTube Shorts. Our Terms of Service covers the legal agreement between you and Kivvie.
The short version:
We do not sell, rent, or trade your personal information. We only collect what we need to run Kivvie. We share limited data with providers that host the product, process payments, and run product analytics. We may send you service updates and newsletters, which you can opt out of at any time. Our Cookie Notice lists the cookies we set and what each one does.
What we don't do:
Most children's video apps collect data from kids to power recommendations and serve ads. We don't:
- No behavioral profiling. We may collect viewing history and watch duration so parents can see it in the dashboard, but that data never feeds recommendation algorithms or advertising
- No ads in the product. No display ads, no ad identifiers, no frequency capping inside the app or parent dashboard
- No device fingerprinting. We do not collect advertising identifiers or use device information to identify a child across unrelated apps or websites
- No voice data collection. We don't collect or process voice or audio data from children
- No algorithmic recommendations. Parents choose the channels and individual playlist videos. There is no algorithm deciding what kids see next
- No children's data shared with advertisers. Child names, ages, PINs, profile IDs, approved channels, playlists, watch history, and viewing data are never sent to advertising networks, Meta, or data brokers. Our website does not load Meta Pixel or any other ad tracker
- No cross-device tracking. We don't link children's activity across devices to build profiles
1. Information We Collect
1.1 Account Information
When you sign in with Google, we collect:
- Email address - To identify your account, send important service notifications, and newsletters (you can opt out)
- Name - To personalize your experience
- Profile picture - The picture on your Google account, if you have one, shown so you can tell which account you are signed in with
- Birthdate - Used only for age verification during sign-up to comply with COPPA. We verify you are 18+ but do not store your birthdate after verification. If your Google account has only a birth year, we count your birthday as 31 December of that year.
Important: We never see your Google password. Authentication goes through Google's OAuth 2.0 system. We use Google access tokens to search YouTube channels on your behalf. So that you do not have to sign in every hour, we also keep a Google refresh token, which lets us get a new access token. We store it encrypted, never share it, and keep it until you delete your Kivvie account or remove Kivvie's access in your Google Account settings. When you delete your account, we delete the token and ask Google to cancel the access it gave.
Age Verification (COPPA Compliance)
To ensure proper parental consent as required by COPPA, we verify that all users are 18 years or older during the sign-up process. We access your birthdate from your Google account for this one-time verification. Your birthdate is not stored after verification is complete. Users under 18 years of age cannot create accounts or use Kivvie.
1.2 Child Profile Information
For each child profile you create, we may store:
- Child's name or nickname - Stored within your account and not sent to analytics providers
- Age or birthdate - Optional, used only to help parents choose appropriate settings and starter channel ideas
- No photos - We do not ask for or store photos of children. A child profile shows the first letter of its name
- Approved channels - List of approved YouTube channels for each child
- Channel change count - On the free plan, how many channel changes were made for each child in the current month and when that child first reached 5 channels, so we can apply the free plan's limit of 3 channel changes a month. We do not keep a list of which channels were added or removed
- Custom playlists of individual videos - Playlist names, the child profile they belong to, selected YouTube video IDs, video order, and the time each video was added
- Public YouTube metadata - For playlist videos, we may store the title, thumbnail, description, channel ID and name, duration, view count, publication date, and language returned by YouTube. The playlist data Kivvie sends to a child's device leaves out the source channel identity and video description
- Content settings - Preferences for Shorts and comments visibility
- Viewing preferences - Optional settings to personalize the experience
- Watch history and duration - On paid plans only, we record which videos a child watches, keeping one entry per video containing the video title and identifier, the channel it came from, its thumbnail image address, the furthest point watched, the video length, how many times it was opened, and the first and last time it was watched. Views under 10 seconds are not recorded. Rewatching a video updates its existing entry rather than creating a new one, so this is a per-video record and not a session-by-session log. It exists solely to display this information to the parent who owns that profile in the dashboard Activity page. Recording begins when a paid plan starts; we do not record watch history on the free plan. If a paid plan ends, recording stops. Entries that were already recorded are kept until the child profile is deleted or a parent erases them, as section 8 explains. This data is never used for algorithmic recommendations or advertising, and is never shared with anyone outside your account. A parent can turn watch-history recording off for any child at any time in Settings, which stops future recording without affecting other paid features, and can erase a child's existing watch history at any time from the Activity page, on any plan
Important: All child information is controlled entirely by parents and stored securely. We do not sell children's information or share it for advertising.
1.3 Usage Information
We may collect:
- Device and technical information such as platform, operating system, app version, browser type, screen size, and your country, worked out from your IP address. Our analytics provider uses your IP address only to find your country and then discards it. It no longer stores your city, postcode, or map coordinates
- Camera for setup-code pairing only - On a phone or iPad, the child app may use the camera to scan a setup QR from the parent dashboard. Frames are processed on the device to read the code and are not stored or uploaded. You can deny camera permission and type the code instead
- App and website usage statistics such as page views, features used, onboarding steps, channel search result counts, session duration, and playback reliability events
- Error logs, crash reports, and diagnostic events used to improve service stability
- Playback error reports - When a video will not play in the child app because it cannot be played outside YouTube, the app sends us the video ID and the error code. We store each report with a one-way hash of the parent account ID instead of the ID itself, so we can tell when two families hit the same video. We use these reports only to decide when to hide that video for every family. We hide it once YouTube confirms that the video cannot play outside YouTube, or once two families report the same problem
- Product analytics through PostHog, our analytics service provider. On our website, surveys, autocapture, rage-click tracking, and web performance autocapture are turned off, and analytics profiles are created only for signed-in users. Where website analytics is active, we also use PostHog session replay, which records how website pages look and how visitors move through them (page layout, scrolling, mouse movement, and clicks) so we can see where the site breaks or confuses people. Text you type into form fields is always masked. On the dashboard, onboarding, sign-in, support, and email-preference pages, the page content itself (text, images, video, and other elements) is blocked from recordings, so child names and profile details on those pages are not captured. Admin pages and the watch pages children use are never recorded. Network request headers and bodies, console logs, and canvas content are not recorded. Recordings are linked to the same PostHog visitor identifier described in our Cookie Notice, which becomes your parent profile identifier after you sign in. We can switch session replay off or record only a sample of visits through the build configuration of our website. We do not send child names, PINs, raw search text, OAuth tokens, payment credentials, raw child profile IDs, raw channel/video IDs, or hashed channel/video IDs to PostHog. Older versions of the child app sent one-way hashes of channel and video IDs; current versions do not.
- Mobile app analytics - Each time the mobile app starts, it asks kivvie.app whether analytics needs your consent where you are. On devices in the European Economic Area, the United Kingdom, or where we cannot tell the country, or if that check fails, the app sends no analytics at all. Elsewhere it sends the usage, error, and playback reliability events described above
- Child app events - Events from a paired child device, or from the child experience on a parent's phone, use an anonymous device identifier. They are never linked to the parent's analytics profile and never create a profile of their own. We use them only to keep the app working: finding errors, playback failures, and features that break. Under COPPA this is the "support for internal operations" use of a persistent identifier: we never use these events to contact a child, build a profile of a child, or choose ads. Where older versions of the child app still send child viewing and navigation events under the parent's identifier, our analytics pipeline moves them to an anonymous identifier before they are stored. Error reports from those older versions can still carry the parent's identifier until the app is updated
- Your choice in the EEA and the UK - If you visit our website from the European Economic Area or the United Kingdom, or we cannot tell where you are, PostHog analytics, session replay, and Umami load only after you agree in our cookie banner. The banner does not appear on the sign-in page, and analytics still waits for your answer there. If you say no, the website works the same. You can change your choice at any time with the Cookie settings link at the bottom of our website pages and the sign-in page. We work out your region from your IP address on each visit and do not store it
- Website statistics through Umami, which counts page views on our website. Umami does not set cookies. We tell it not to collect the query part of web addresses, and it does not run on signed-in, sign-in, support, email-preference, or watch pages
- Directory badges - The footer of our homepage shows badges from six directories that list Kivvie: DanielLaunches, Fazier, KittyLaunch, ScrollLaunch, Stork and Turbo0. Other pages show no badges. These images load from the directory's own server, so your browser sends that server your IP address and browser details, as it does for any image. We do not send those directories any other information
- Child age band - Child app analytics events may include an age band such as 4-6 or 7-9, never the exact age or birthdate
1.4 Payment and Billing Information
If you subscribe to a paid plan, payments are processed by Airwallex Pty Ltd (ABN 29 609 653 312), a PCI DSS Level 1 certified payment processor. We do not collect, see, or store your full card number, CVV, or other sensitive payment credentials.
What we receive and store:
- Transaction records. Subscription type, amount paid, currency, and payment date
- Subscription status. Your current plan, billing period, and renewal date
- Payment processor identifiers. Customer and subscription IDs used to manage your billing with Airwallex
What we never see or store:
- Your full credit or debit card number
- Your CVV or security code
- Your card PIN
Your card details are entered directly into Airwallex's secure payment form and transmitted to Airwallex via encrypted connections. Airwallex's handling of your payment data is governed by their Privacy Policy.
Children and payments: Payment and billing features are only accessible to parent/guardian accounts. Child profiles cannot access billing information or make purchases.
2. How We Use Your Information
We use collected information to:
- Provide the service - Sign you in, save and sync your choices, check playlist videos, and deliver video content
- Maintain security - Protect your account from unauthorized access
- Improve functionality - Identify and fix bugs, optimize performance
- Communicate with you - Send essential service updates, newsletters, product announcements, and respond to support requests
Marketing Communications: We may send you newsletters and promotional emails. You can opt out at any time. Open the unsubscribe link in any newsletter, tips email, or weekly watch history email and press Unsubscribe, or use the unsubscribe button your mail app shows. One unsubscribe stops all three kinds of email, and it takes effect at once. Service-related emails (e.g., security alerts, account notifications, receipts) cannot be opted out of.
We never sell your data. Children's information is never shared with advertisers or sent to Meta. Our website does not load Meta Pixel or any other ad tracker.
3. YouTube API Services and Google Privacy Policy
Kivvie uses YouTube API Services to search for channels, validate videos selected for playlists of individual videos, retrieve public video metadata, and provide playback. The Google Privacy Policy explains how Google handles information from YouTube and its player.
Important YouTube API disclosures:
- We access YouTube data to search for channels and retrieve metadata for channel videos and specific videos selected by parents
- We store YouTube video IDs and public metadata so we can maintain playlists of individual videos and check whether their videos remain available and eligible for playback
- We do not store YouTube video content on our servers
- Playback uses YouTube's player. YouTube may process device, playback, and usage information under Google's privacy practices
- You can revoke Kivvie's access to your Google account at any time through your Google Account settings
4. Data Storage and Security
Here is how we protect your data:
- Encryption - All data is encrypted in transit (HTTPS) and at rest
- Authentication - OAuth 2.0 through Google. We never see your password
- Access controls - Internal access policies and audit logging
- Security monitoring - We monitor for vulnerabilities on an ongoing basis
Your data is stored securely using Supabase infrastructure with automatic backups and redundancy.
5. Data Sharing and Disclosure
We do not sell, rent, or trade your personal information.
We may share limited information only in these circumstances:
- With your consent - When you explicitly authorize data sharing
- Service providers - Companies that help us run Kivvie, including hosting, authentication, payments, analytics, and diagnostics providers. They are bound by their own terms of service and privacy commitments to us, and may use the data only to provide their service to Kivvie. Section 9 explains where these providers are located and the current state of our transfer safeguards
- Legal requirements - When required by law or to protect rights and safety
6. Children's Privacy
Kivvie is for children, but parents manage it. We build and operate Kivvie with child privacy and online safety laws in mind, including COPPA (Children's Online Privacy Protection Act), the Australian Privacy Act 1988, and Australia's online safety framework. If you are in the European Economic Area or the United Kingdom, section 10 covers how the GDPR applies to children's information.
Our Approach to Children's Privacy:
- Children can't create accounts - All accounts require parental authentication via Google. Children never provide information directly
- Parents control everything - Child profiles are created and managed only by verified parents or legal guardians
- Limited child profile data - From parents, we collect a child's name or nickname, optional age, approved channels, playlist video choices, and content settings
- No tracking for algorithms - We may collect watch history and duration so parents can see it in the dashboard, but we never build behavioral profiles or use it for recommendations or advertising
- No session replay on watch pages - Website session replay is switched off on the watch pages children use, so nothing a child does there is recorded
- No ads - Kivvie does not show advertisements to children
- No advertising sharing. Children's information is never sold or shared with advertisers, data brokers, or Meta
Australian Social Media Age Restrictions:
Kivvie is designed as a parent-controlled filtering and viewing service, not as an age-restricted social media platform under Australia's Social Media Minimum Age obligation. It:
- Does not allow children to create YouTube accounts, social media accounts, or Kivvie parent accounts
- Does not provide public child profiles, messaging, comments, posting, following, friending, or peer-to-peer interaction
- Does not use child viewing data for recommender systems or behavioral ranking
- Provides a video viewing environment where parents control approved channels, individual playlist videos, and child profiles
- Offers optional Channel Packs, which are community-recommended channel bundles, not sponsored or paid
- May disclose limited information to regulators or law enforcement only when the law, a court order, or a valid regulatory notice requires it
Parental Rights:
Parents have full control and can:
- Review all information collected about their children
- Request deletion of child profiles and all associated data at any time
- Refuse further collection or use of their child's information
- Control the approved channels and playlist videos their children can access
7. Your Choices
You may:
- Request your data - Ask for a copy of the information we hold about you
- Correct information - Ask us to update or correct inaccurate data
- Delete your account - Request deletion of your account and associated data, subject to our data retention obligations
- Revoke permissions - Remove Kivvie's access to your Google account through your Google Account settings
We respond to these requests as quickly as we can. We may decline only where the law requires or permits us to, for example where we must retain billing records for tax purposes. If you are in the European Economic Area or the United Kingdom, section 10 sets out additional rights and a binding one-month response deadline that we honour.
8. Data Retention
We retain your information only as long as necessary to provide our service:
- Account data is retained while your account is active
- Playlist names and video selections are retained while the playlist, child profile, or account exists. Deleting a playlist removes its video-selection records and its link to that child. Public YouTube metadata may remain in Kivvie's video records after the playlist is deleted, even if no current playlist uses that video
- Watch history. Recorded on paid plans only. Entries are retained for as long as the child profile exists, so that longer-term summaries of a child's viewing remain available to the parent; there is no automatic expiry. You stay in control of this: deleting a child profile deletes that child's watch history immediately, a parent can erase it manually at any time from the Activity page on any plan, and switching watch-history recording off for a child in Settings stops any further entries being recorded. If a paid plan ends, existing entries are retained but are no longer viewable while the account is on the free plan
- Channel change count - Kept while the child profile exists and deleted with it. We keep only one count per child, for the most recent month with a counted change. It is replaced the next time a change is counted, and a count from an earlier month is never used
- Retired waitlist data. Kivvie no longer operates a pre-launch waitlist. The remaining historical waitlist submissions were deleted on August 19, 2026, and we no longer collect or retain waitlist submission data
- Playback error reports. Kept while your account exists and deleted when you delete your account. The list of hidden videos stays. For each video it holds the video ID, why it was hidden, the first error code, and the date, but nothing that identifies a family
- When you delete your account, personal data is removed, except where we are required or permitted by law to retain it
- Billing records - When you delete your account, we delete our own copy of your subscription and payment history. Airwallex, our payment processor, keeps its own transaction records (amount, date, subscription type) for as long as the law requires it to, which can be up to 7 years
- Service providers - Our providers keep limited records under their own policies. For example, our email provider keeps delivery logs, and Google keeps its own record of the access you gave Kivvie until you remove it in your Google Account settings
- Backups - Deleted data can stay in our database host's encrypted backups until those backups are replaced on their normal schedule
9. International Data Transfers
Kivvie is operated from Australia by M2V2 Solutions Pty Ltd. If you use Kivvie from outside Australia, your information is transferred to and processed in Australia, and in the countries where our service providers operate. Our infrastructure and service providers currently include Supabase (hosting and database), Google Cloud (application hosting), PostHog (product analytics, United States), Umami (cookieless website statistics), Google (authentication and YouTube API services), and Airwallex (payment processing). Directory badge images in our homepage footer load from those directories' servers, as section 1.3 explains.
Australia has not been granted an adequacy decision by the European Commission. Where we transfer personal information out of the European Economic Area or the United Kingdom, we rely on your explicit consent, given when you create an account and accept this policy, and on the necessity of the transfer to perform the service you have asked us to provide.
10. European Economic Area and United Kingdom (GDPR)
If you are in the European Economic Area or the United Kingdom, the General Data Protection Regulation and the UK GDPR give you specific rights. This section explains them and how we handle your information.
Who is responsible for your data
The data controller is M2V2 Solutions Pty Ltd, a company registered in Australia. You can reach us about any privacy matter at admin@kivvie.app.
If you are in the EEA or the UK and need to raise a data protection matter, contact us at the address above and we will handle it directly.
Why we are allowed to process your information
We rely on the following lawful bases:
- Performance of a contract - to create and run your account, store the child profiles, approved channels and playlists you set up, deliver video content, and provide support. Without this we cannot give you the service you signed up for
- Legitimate interests - to keep the service secure, prevent abuse, diagnose faults, and understand how the product is used so we can improve it. We limit what we collect for these purposes. Our analytics redacts known sensitive fields before data leaves your device, and we do not send child names, PINs, or raw child profile identifiers. When you are signed in, your parent profile identifier is sent to our analytics provider so we can count returning users and link errors to an account we can help
- Consent - for website analytics and session replay, which we ask for in our cookie banner, for marketing newsletters, and for transfers of your data outside the EEA and the UK as described in section 9. You can withdraw consent at any time, and withdrawing it does not affect processing that already happened
- Legal obligation - to keep billing and tax records for the periods the law requires
Your rights
You have the right to:
- Access - get a copy of the personal information we hold about you
- Rectification - have inaccurate or incomplete information corrected
- Erasure - have your personal information deleted. You can do this yourself in the Kivvie mobile app: open the menu on the home screen, choose Delete Account, and confirm with your parent PIN. That permanently removes your account, all child profiles, approved channels, playlists and watch history, and cancels any paid subscription. There is no recovery once confirmed. We also ask Google to cancel Kivvie's access to your Google account, and ask our analytics provider, PostHog, to delete your analytics profile, the events linked to it (including child app events), and session recordings. PostHog deletes these within about a week. Account deletion is not available on the website, so if you cannot use the app, email us and we will action it for you. Section 8 explains what our payment processor and other providers keep under their own policies
- Restriction - ask us to limit how we use your information while a concern is being resolved
- Portability - receive the information you gave us in a structured, commonly used, machine-readable format. Kivvie has no self-service export button today, so email us and we will prepare the file and send it to you
- Object - object to processing we carry out on the basis of legitimate interests, and object to direct marketing at any time
- Withdraw consent - withdraw any consent you have given, including for newsletters
- Complain - lodge a complaint with your local supervisory authority. In the UK this is the Information Commissioner's Office. In the EEA it is the data protection authority for your country
To exercise any of these rights, email admin@kivvie.app. We will respond within one month of receiving your request. If your request is complex, we may extend this by a further two months, and we will tell you within the first month if that happens. There is no charge, and using these rights does not affect your account or the service you receive. If a request is clearly unfounded or excessive, the GDPR lets us charge a reasonable fee or refuse it, and we will explain our reasoning if that ever happens.
Because Kivvie accounts are created through Google sign-in, we will normally verify a request by confirming it comes from the email address on the account.
Children in the EEA and the UK
Kivvie accounts are held by parents and guardians, not by children. Only adults aged 18 or over can create an account, and children never provide information to us directly. All information about a child reaches us because a parent or guardian entered it.
Under Article 8 of the GDPR, the age at which a child can consent to online services on their own varies between 13 and 16 depending on the country. This does not change how Kivvie works: we require a parent or guardian to hold the account and provide consent in every country, which meets the strictest of these thresholds. A parent or guardian can review, correct, or delete any information relating to their child at any time, on any plan.
Retention periods are set out in section 8 above.
11. Changes to This Privacy Policy
We may update this policy at any time. Changes are effective when posted. The "Last updated" date at the top of this page reflects the most recent revision. It is your responsibility to review this policy periodically. Continued use of Kivvie after changes are posted constitutes acceptance of the updated policy.
12. Contact Us
Questions about this policy? Email us at admin@kivvie.app. Kivvie is operated by M2V2 Solutions Pty Ltd, Suite 17, 89-97 Jones Street, Ultimo, NSW 2007, Australia, which is the data controller for the information described in this policy.
