Privacy Policy — ChildLock for iPhone
Last updated: October 13, 2026
1. Introduction
ChildLock is a parental-control app for iPhone and iPad operated by EpowerX Labs Private Limited ("EpowerX", "we", "us"). A parent blocks the apps their child shouldn't open and approves the video channels their child may watch. This policy covers the ChildLock iOS app and the childlock.xyz website. Using ChildLock on Android? Read the Android privacy policy. The short version: no account, no ads, no data sales, and your child's name, watch history, and the apps you block stay on your device.
2. Data we do not collect
- We do not require an account, login, email, or phone number.
- We do not collect your name or your child's name, contacts, precise GPS location, photos, or messages.
- We do not collect the names or identities of the apps you block — Apple's frameworks hand ChildLock only opaque tokens.
- We do not collect browsing history outside childlock.xyz.
- We do not show ads, we do not use the advertising identifier (IDFA), and we do not track you across other companies' apps or websites.
- We do not sell data to anyone.
- We do not receive your payment-card or bank-account details. Apple processes those details directly.
If you contact support, we receive the email address and information you choose to include in your message so that we can respond.
3. On your iPhone
ChildLock uses Apple's Screen Time technology (the FamilyControls, Managed Settings, and Device Activity frameworks) to shield apps you have not approved. The apps you select are represented by opaque tokens that Apple's frameworks process entirely on-device — ChildLock never sees or transmits app names. Your child's name, the list of approved channels, watch history, and session state are stored on the phone and are deleted when you delete the app. Face ID is handled by iOS; ChildLock never receives your face data.
4. What the app sends
- Channel catalog — the curated channel list is fetched from
api.childlock.xyzwithout any per-user identifier. - Channel search — when you search for a channel, the search text is sent to our channel-search service (
api.regainapp.ai, operated by EpowerX) to find matching YouTube channels. It is not linked to any identifier. - Videos — video lists and thumbnails are loaded from YouTube's public feeds, and videos play through YouTube's embedded player. YouTube (Google) receives these requests under Google's privacy policy.
- App analytics — to find bugs and see which features help families, the app sends usage events to our own self-hosted analytics server (
analytics.regainapp.ai): which screens were opened and buttons tapped, permission results, onboarding steps, session minutes, the public YouTube IDs of channels and videos involved, the child age you selected, and counts (for example how many children or channels are set up). Events carry Apple's identifier for vendor and a random install ID, plus device model, iOS version, app version, and language. They never include your child's name (only its length), search text, or blocked apps, and they are not used for advertising or shared with any third party.
5. Website analytics
When you visit childlock.xyz, the site records one website_page_viewed event for the page load. When you select an App Store or Google Play button, it records a website_app_store_clicked event with which store you chose. These events include only: the page path and title, the button location and store, the referring domain (not the full referring URL), and any utm_source, utm_medium, utm_campaign, utm_content, or utm_term campaign values in the landing URL.
The site creates a random pseudonymous identifier in memory for each page load so that a store click can be associated with the page view that preceded it. The identifier is discarded when the page closes or reloads. We do not use analytics cookies, local storage, session storage, or tracking pixels. Our server necessarily receives your IP address while handling the request; the analytics pipeline uses only a temporary, process-specific one-way hash of that address for abuse rate limiting — the raw address is never stored in the analytics event, and the hash salt regenerates every server restart. Global Privacy Control and browser Do Not Track signals disable this collection entirely.
Separately from analytics, our web server keeps standard operational access logs — source IP address, browser user agent, request path, and timestamp — used only for security, abuse prevention, and troubleshooting. These logs are retained for 30 days and then deleted; they are never joined to analytics events, used for profiling, or shared with third parties.
6. Purchases
The current version of ChildLock for iPhone has no in-app purchases. Subscriptions bought in an earlier version are billed and managed by Apple through the App Store; we never see your payment-card or bank details. Manage or cancel at apps.apple.com/account/subscriptions.
7. Children's privacy (COPPA and Apple kids-category rules)
ChildLock is built for children to use under a parent's control, and we take COPPA and Apple's guideline 5.1.4 obligations seriously. The parent sets ChildLock up and is the only person we transact with. Your child's name, watch history, and profile stay on the phone. The analytics described in section 4 contain no name, contact details, or advertising identifier, and are used only to operate and improve ChildLock. We do not knowingly collect personal information from children, we show no ads to children, and there are no third-party analytics or tracking beacons in the child-facing experience.
8. Third parties
- Apple — processes payments and runs the on-device Screen Time / FamilyControls frameworks. See Apple's privacy policy.
- YouTube (Google) — hosts the videos and public feeds ChildLock shows. See Google's privacy policy.
- Jitsu / OpenPanel (self-hosted) — our own first-party analytics infrastructure that receives the app events in section 4 and the website events in section 5. No third-party analytics service receives your data.
9. Your rights
Email privacy@childlock.xyz for access, correction, or deletion requests. Under the GDPR you have the rights of access, rectification, erasure, restriction of processing, data portability, and objection. Under the CCPA you have the right to know, the right to delete, and the right to opt out of the sale of personal information — the last is inapplicable because we do not sell data. Because ChildLock has no accounts, tell us roughly when you used the app and on which device so we can locate and delete the matching analytics; deleting the app removes everything stored on the phone.
10. Data retention
Website analytics events are retained for at most 12 months in our self-hosted OpenPanel. App analytics events are kept only as long as they are needed to operate and improve ChildLock, and are deleted on request (section 9). Web-server access logs (section 5) are retained for 30 days. Data on your iPhone is deleted when you delete the app. Apple retains purchase records under its own policies and applicable legal obligations.
11. Changes to this policy
If we change this policy, we will post the updated version on this page and update the "Last updated" date above. If a change is material and the app is installed, we will surface it via an in-app notice.
12. Contact
Privacy, GDPR, CCPA, copyright, and DMCA notices: privacy@childlock.xyz
EpowerX Labs Private Limited
Plot No. 77, JBR Tech Park, 6th Rd
Whitefield, EPIP Zone
Bangalore, Karnataka 560066
India
13. Summary of what leaves your device
Catalog fetches (no per-user ID), channel searches (no ID), video requests to YouTube, the pseudonymous usage analytics in section 4, and — only if you browse childlock.xyz — the website events in section 5. Your child's name, watch history, and the apps you block stay on-device.
