Your child's face never leaves your iPhone or iPad.

1Who we are

ChewView is an iOS app developed and operated by Esprizzle Inc. ("Esprizzle", "we", "us", "our"). This Privacy Policy describes our practices with respect to information we may handle when you use the ChewView app and the chewview.esprizzle.com website.

You can contact us at any time about this policy at contact@esprizzle.com.

2What we don't collect

We have designed ChewView so that the question of "what we collect" mostly does not apply. Specifically, ChewView does NOT send any of the following off your device, there is no ChewView server for us to send anything to:

• Your name, email address, phone number, or any other contact information.
• Your location, IP address, or device identifiers (other than the Apple-provided receipt confirming your $0.99 unlock).
• Camera frames, photos or videos of your child, or face images. Nothing from the camera ever leaves your device; the only image stored at all is the optional profile picture you may choose to set, which stays on your device (see Section 3).
• Audio recordings, voice samples, or the optional voice prompts you record in-app.
• The videos you choose to play, including titles, URLs, or YouTube channel data.
• Usage analytics, crash logs, app open events, or feature engagement data.
• Third-party tracking identifiers, advertising IDs, or attribution data.

Apple's App Store privacy nutrition label confirms this with the line "Data Not Collected." That status reflects the truth: there is no ChewView backend, no analytics pipeline, no log server, no marketing database.

3What stays on your device

The data ChewView needs to function lives entirely on your iPhone or iPad. It is never transmitted off-device by the app.

Face detection data

ChewView uses Apple's ARKit framework to detect facial landmarks (mouth open, jaw movement) for chewing detection. The raw camera frames are processed in real time on-device and are immediately discarded, they are never written to disk, uploaded, or otherwise saved. ChewView does not photograph or video-record your child through the camera.

Face profile (face embedding)

For identity matching (so a sibling sitting in front of the camera does not unlock the playing video), ChewView stores a small mathematical embedding, computed on-device using Apple's Vision framework, derived from the enrolled child's face (typically five samples). This embedding is a set of numbers, not a photo, and cannot be reconstructed into a recognizable image. It is saved only in ChewView's private on-device storage, which only ChewView can read. A coarse 3D face-size measurement (from ARKit) is stored alongside it to help distinguish an adult from a child.

You can delete a child's face data at any time from within the app: on the "Who's watching?" screen, press and hold the child's card and choose Delete to remove the whole profile, or Re-scan to replace the stored samples. Deleting the ChewView app removes everything as well.

Profile photo (optional)

You can optionally give each child a profile picture so their card is easy to recognise in the picker. If you choose one, ChewView stores a small, downscaled copy of the image you pick, on your device only, alongside your other settings. It is never uploaded or shared, you can change or remove it at any time, and it is not used for face recognition (recognition uses only the numerical embedding above).

Settings and preferences

Your settings (idle threshold, voice prompt preferences, kid names, the list of videos you've saved) are stored in standard iOS UserDefaults inside the app's sandbox.

Saved videos library

The list of YouTube URLs you save is stored locally. The videos themselves play directly from YouTube's servers using the standard YouTube IFrame Player; ChewView does not host video content.

Recorded voice prompts

If you record voice prompts inside the app ("One more bite!"), the audio files are stored locally inside the app's sandbox in standard M4A-AAC format. They never leave the device.

4Camera, microphone, and Files access

Camera

ChewView requests camera access to run on-device chewing detection and identity matching. The camera feed is processed frame-by-frame on-device by Apple's ARKit and Vision frameworks inside the app's process. No frame is ever saved, screenshotted, exported, or transmitted. The camera is active only while a chewing session is running.

Microphone

The microphone is requested only when you choose to record a voice prompt. The recording starts only after you tap the in-app Record button. Audio is saved to the app's local sandbox.

Files and Photos

When you choose to import a video file (e.g., a homemade MP4), ChewView uses the standard iOS document picker. We only access the specific files you select. We do not browse your wider Photos library, file system, or iCloud Drive.

5YouTube playback

ChewView plays YouTube videos using the standard YouTube IFrame Player. You build your child's library yourself by pasting YouTube links (or importing your own video files). There is no YouTube account linking, no Google sign-in, and no OAuth of any kind. ChewView never asks for, receives, or stores credentials, tokens, or any other access to your Google or YouTube account.

When you play a YouTube video, your device streams it directly from YouTube's servers, the same way it would in a web browser. There is no intermediate ChewView server in the request path. That playback is governed by the YouTube Terms of Service and the Google Privacy Policy.

When you paste a YouTube link, the app fetches the video's publicly available title and thumbnail directly from YouTube (no sign-in required) so it can display the entry in your library. That information is stored locally inside the app's sandbox, alongside the URL you pasted.

6Payments

ChewView is offered with a free 7-day trial and a one-time $0.99 unlock. Payments are processed entirely by Apple through standard In-App Purchase. We never see or store your credit card number, billing address, or other payment details. The only purchase-related data ChewView's app reads is the Apple-signed receipt verifying that you have completed the unlock; this receipt is processed on-device and is not transmitted to us.

Refunds for App Store purchases are handled directly by Apple at reportaproblem.apple.com.

7Children's privacy (COPPA)

ChewView is designed for parents to use during their child's mealtime. The app is set up so that:

• Children do not log in, create accounts, or provide any personal information. Neither do parents, the app has no accounts or sign-ins at all.
• The face profile we keep locally is a small numerical embedding that cannot be reverse-engineered into an identifiable image of the child.
• No information about the child (face data, any profile photo, voice prompts, video selections) ever leaves the device.

ChewView complies with the United States Children's Online Privacy Protection Act (COPPA), 15 U.S.C. §§ 6501–6506, by design: because we do not collect any personal information from any user (child or adult), we never collect personal information from a child under 13.

If you believe a child has somehow provided personal information to ChewView, please contact us at contact@esprizzle.com so we can investigate.

8European Union (GDPR and GDPR-K)

Because we collect no personal data, the legal bases under Article 6 of the General Data Protection Regulation (GDPR) do not generally apply to ChewView. Where data is processed on your device for the purpose of running the app's features, the legal basis is your consent (given by installing the app and granting iOS permissions for camera, microphone, etc.).

The on-device face embedding (generated on-device by Apple's Vision framework) could be considered biometric data under Article 9 GDPR. We process it on-device only, do not transmit it, and use it strictly for the purpose of preventing the child's video from being unpaused by an unenrolled person. You can delete it at any time. We do not rely on this embedding for any decision that produces legal effects or similarly significant effects.

If you are an EU resident, you may exercise the following rights to the extent any personal data is held by us (which, by design, is normally none): access, rectification, erasure, restriction, portability, objection. Contact contact@esprizzle.com.

9Other jurisdictions

ChewView is compliant by design with the Australian Privacy Act 1988, the California Consumer Privacy Act (CCPA) as amended by the CPRA, the UK Data Protection Act 2018, Brazil's LGPD, Canada's PIPEDA, and equivalent frameworks. Because we do not collect personal information, the substantive disclosure, opt-out, and access-request obligations of these statutes have no underlying data to apply to. We will respond to any verifiable consumer request within the applicable timeframes.

10Third-party services

ChewView intentionally avoids third-party SDKs that perform tracking, analytics, advertising, or crash reporting. The third-party services ChewView does interact with, and the limited purposes of each, are:

11Data retention

The data ChewView creates and uses lives only on your device. Its retention is therefore controlled by you:

• Face data (the numerical embedding and the 3D face-size measurement): kept until you remove the child's profile, or Re-scan it, on the "Who's watching?" screen, or delete the app.
• Profile photos (optional): kept until you change or remove them in the app, or delete the app.
• Voice prompts: kept until you delete the recording in Settings or delete the app.
• Saved YouTube library entries: kept until you remove them in Manage or delete the app.
• Apple In-App Purchase receipt: kept by iOS in association with your Apple ID; we do not control or retain a separate copy.

12Security

Because we operate no server, store no personal data off-device, and require no accounts or sign-ins, the principal security boundary for ChewView is the iOS app sandbox itself. We rely on iOS's standard sandboxing for all app data. ChewView holds no user credentials, OAuth tokens, API secrets, or cryptographic keys, there are none to store.

No internet-connected system is perfectly secure. If we ever experience a security incident that could affect users, we will notify affected users by email (where available through Apple App Store reviews or support tickets) and post a notice at chewview.esprizzle.com.

13International data transfers

Because ChewView operates no servers and stores no personal data off your device, there are no international data transfers performed by us. When you play a YouTube video, your device communicates directly with Google's servers in accordance with Google's own data-handling practices.

14Changes to this policy

We will update this Privacy Policy when our practices change. The "Last updated" date at the top of this page will reflect the most recent change. For material changes that affect how the app handles data, we will post a prominent notice in the app and on chewview.esprizzle.com at least 14 days before the change takes effect, so you have time to review.

15Contact us

For any privacy-related question, request, or concern, please reach out at:

Esprizzle Inc.
Email: contact@esprizzle.com
Web: www.esprizzle.com
Subject line: "ChewView Privacy"

We aim to acknowledge privacy emails within one business day.