Magima Kids

Privacy Policy

Ages 6-8 • Kids Category

Last Updated: March 21, 2026

Developer: Magima Kids LLC

Contact: hello@magima.kids

Phone: (323) 366-1535

Website: www.magima.kids

THE SHORT VERSION:

All creations stay on your device. We can't see anything your child creates. We don't collect names, emails, or identifying information.

Our Commitment to Children's Privacy

Magima Kids is designed for children. We take their privacy seriously. This app complies with the Children's Online Privacy Protection Act (COPPA), the Family Educational Rights and Privacy Act (FERPA), and Apple's App Store Guidelines for children's apps (Kids Category).

In plain terms: Today, everything stays on the device. We cannot see, access, or retrieve anything your child creates or does in the app. If we introduce features that change this in the future, they will require separate parental consent before activation.

What Information We Collect

Persistent Identifiers (Internal Operations Only)

The only personal information we collect, as defined under COPPA, is persistent identifiers used solely for internal operations. These are collected and processed by Apple as part of their standard App Analytics service, which provides us with:

  • Number of app sessions (how often the app is opened)
  • Device type and iOS version
  • App crash reports

This data is anonymous and aggregated by Apple before we see it. We cannot identify individual users. We cannot see who is using the app, only aggregate totals (e.g., "the app was opened 500 times this week"). This qualifies for the internal operations exception under 16 CFR 312.5(c)(7), which does not require verifiable parental consent.

On-Device Diagnostic Logging

The app includes local diagnostic logging using Apple's os.log framework. These logs are stored on the device only and are visible only through Xcode or Console.app during development. These logs are NOT transmitted to any server and are NOT visible in Apple App Store Connect. They exist solely for debugging during development.

Local Device Storage

The app stores the following data locally on the device only:

  • User-created artwork, music, and animations (stored in the app's local database)
  • Profile names and avatar selections (e.g., "Player 1" with a star icon). Profile names are chosen freely by the user — the app does not request or require real names. We recommend using nicknames or pseudonyms
  • App preferences and settings
  • Photos and videos saved to the device's Photos library (at the user's direction)

This data is currently stored only on the device. It is not uploaded to any server, cloud service, or third party. Future features such as cloud save or AI-assisted creation may process some data externally; see "Future Features and Consent Tiers" below.

Information We DO NOT Collect

We do not collect, request, or have access to:

  • Names, email addresses, or physical addresses
  • Phone numbers or contact information
  • Photos, videos, or audio from the device's camera or microphone (note: the app processes camera data on-device in real-time for creative effects; photos and videos are saved only to the device's local Photos library at the user's direction and are never transmitted to any server)
  • Location or geolocation data
  • Device identifiers used for cross-app tracking
  • Browsing history or search queries
  • Any data about contacts, calendar, or other apps on the device

How We Use Information

Anonymous, aggregated analytics data from Apple is used exclusively for:

  • Understanding which features are most popular so we can improve them
  • Identifying and fixing app crashes
  • Making informed decisions about future feature development

We do not use any data for:

  • Advertising or marketing to children
  • Building behavioral profiles
  • Selling or sharing with third parties
  • Cross-app tracking
  • Contacting any individual

On-Device Processing (Vision Framework)

The Magic Camera feature uses Apple's on-device Vision framework to:

  • Person segmentation — detect the outline of a person to apply creative background effects
  • Body pose detection — detect body joint positions for real-time creative effects

This processing happens entirely on the device's processor. No biometric templates, facial recognition data, or body measurements are created, stored, or transmitted. The processed data exists only momentarily in device memory during the camera session and is discarded each frame. No AI processing data is saved, logged, or sent anywhere.

Magi Assistant (On-Device Speech Recognition)

The app includes Magi, a kid-safe contextual helper that responds to voice input. Magi is a deterministic, rule-based assistant (not a generative AI or chatbot). It uses keyword matching to provide helpful responses and guide kids through the creative tools.

  • Speech recognition is performed entirely on-device using Apple's Speech framework with requiresOnDeviceRecognition enabled
  • No audio data is transmitted to any server, including Apple's servers
  • Voice input is processed in real-time and discarded after each request
  • No voice recordings are saved, stored, or logged
  • No transcripts are retained beyond the immediate interaction
  • Magi does not generate novel text. All responses are predefined by the developer
  • Magi does not learn from or remember previous interactions across sessions

Speech recognition permission is requested at the time of first use (when the child taps the "Ask Magi" button), not during initial app setup. Microphone permission (granted during setup behind a parental gate) is required for voice input.

Photos, Camera, and Microphone

The app includes creative features that use the device's camera and microphone:

  • Camera and microphone access requires a parental gate (a challenge only an adult can complete)
  • Camera data is processed entirely on-device in real-time
  • No photos or videos are captured without user action (tapping the capture button)
  • Video recordings captured in the Magic Camera feature include audio from the device's microphone. Audio is recorded only during active video capture
  • Captured photos and videos are saved only to the device's local Photos library
  • No camera, microphone, or photo data is transmitted to any server or third party

The app uses Apple's PhotosPicker to allow users to select photos as creative backdrops in the Magic Camera feature. The app can only see items the user explicitly selects. It does not have broad access to the photo library and does not scan or index photos.

Screen Recording

The MagiMatic drawing feature includes a screen recording option that uses Apple's ReplayKit to capture the app's screen content. The front-facing camera and microphone are disabled during screen recordings. Recordings are saved to the device's Photos library only at the user's direction. The developer has no access to recordings.

Profile Export and Import

Users can export a profile and all associated creations to a .magimaprofile file, which can be saved to the device's Files app or iCloud Drive. This export is user-initiated and contains the profile name, avatar selection, and creative content (artwork, music, animations). It does not contain device identifiers, analytics data, or any information beyond what the user created within the app. Exported files can be imported on another device to transfer a child's creations. Each export file can only be imported once.

Motion Sensors

Device motion sensors are used for 360° panoramic backgrounds that respond to device orientation. Motion data is processed in real-time on the device and is never stored, logged, or transmitted.

Third-Party Services

Apple App Analytics

Apple provides anonymous, aggregated analytics to developers through App Store Connect. Apple acts as the data processor and aggregates all data before it reaches the developer, preventing individual identification.

Apple App Store Update Check

The app makes a single network request to Apple's iTunes Lookup API to check if a newer version is available. This request contains only the app's bundle identifier (public information) and no user data.

No Other Third Parties (Current)

  • No advertising networks. We do not serve ads to children
  • No third-party analytics SDKs (no Firebase, no Google Analytics, no Mixpanel)
  • No social or community features at this time
  • No third-party crash reporting
  • No external APIs beyond the App Store update check listed above

Future updates may integrate additional services (such as AI content generation or cloud storage). Any such integrations will be disclosed in an updated privacy policy and will require verifiable parental consent before activation. See "Future Features and Consent Tiers" below.

Data Storage and Security

  • All user-created content is currently stored locally on the device using Apple's SwiftData framework
  • No data is currently transmitted to external servers
  • No cloud synchronization is currently enabled
  • Data is protected by the device's built-in iOS encryption and passcode
  • If cloud storage or synchronization is introduced in the future, it will require verifiable parental consent and will be disclosed in an updated privacy policy

Data Retention and Deletion

Data TypeRetention
Profile data (name, avatar, UUID)Until user deletes profile or uninstalls app
Artwork, music, and animation creationsUntil user deletes or uninstalls app
App preferencesUntil app reinstalled
Photos/videos saved to Photos libraryManaged by user in Photos app
Temporary video recordingsDeleted automatically on next app launch
Apple App AnalyticsRetained by Apple per their 25-month rolling deletion policy
On-device diagnostic logsManaged by iOS, not persistent
Person segmentation / body pose dataDiscarded each frame, never stored
Magi voice input / speech recognitionProcessed on-device in real-time, discarded after each request

Parents and teachers can delete profiles and all associated creations directly within the app's Settings screen.

Internal Operations Exception (COPPA 2025)

We collect persistent identifiers solely for the following internal operations as defined under COPPA (16 CFR 312.2):

  1. Maintaining and analyzing the functioning of the app — anonymous usage metrics help us understand which features are used and identify crashes
  2. Protecting the security and integrity of the app — crash reports help us fix issues promptly

These identifiers are processed by Apple in anonymous, aggregated form. We ensure they are not used to contact any individual, for behavioral advertising, to build profiles on individuals, or for any other purpose, through the following safeguards:

  1. No third-party SDKs have access to any identifiers
  2. Apple's processing aggregates all data before it reaches the developer, preventing individual identification
  3. No user-level data export capability exists
  4. No advertising or profiling systems are present in the app
  5. The developer cannot link any analytics data to any specific user or device

Children's Privacy (COPPA Compliance)

Magima Kids is designed and intended for use by children under 13 and is published in Apple's Kids Category.

  • We collect persistent identifiers under the internal operations exception (16 CFR 312.5(c)(7)), which does not require verifiable parental consent
  • The app currently does not require account creation, login, or registration. If accounts are introduced in the future (e.g., for cloud save or parent/teacher portals), they will require verifiable parental consent
  • We do not currently contact children or enable children to publicly share personal information
  • We do not use any data for behavioral advertising or profiling
  • Camera, microphone, and photo library access require a parental gate within the app
  • All creative content stays on the device and is never transmitted

School and Classroom Use (FERPA Compliance)

Magima Kids is suitable for use in educational settings:

  • No student records are created or maintained — the app does not generate education records as defined by FERPA
  • No student data is transmitted — all creations and profiles stay on the local device
  • No cloud accounts currently required — the app works entirely offline at this time
  • Teacher/administrator control — profiles can be created, managed, and deleted directly on the device
  • No data sharing — we cannot access, view, or retrieve any data from school devices

Note: If an educator directs students to create work within the app and associates those creations with specific students (e.g., through named profiles), the creations may constitute education records under FERPA. In such cases, the school — not Magima Kids LLC — maintains custody and responsibility for those records, as all data remains on the school-controlled device.

Recommendation for schools: Create profiles with pseudonymous labels (e.g., "Station 1", "Blue Team", generic avatars) rather than students' real names to minimize personally identifiable information on shared devices.

iCloud Photos warning: When photos or videos are saved to the device's Photos library, they may sync to iCloud if enabled on the device. Schools deploying Magima Kids on managed devices should ensure iCloud Photos is disabled via MDM profile to prevent student-created content from syncing to iCloud.

Schools and districts can deploy Magima Kids via Apple School Manager or Apple Configurator with confidence that no student data leaves the device.

Parental Rights

Parents and guardians have the right to:

  • Review all data stored by the app on the device (profiles, creations, and settings are accessible within the app)
  • Delete any or all data by removing profiles in Settings or uninstalling the app
  • Contact us with questions or concerns at hello@magima.kids

Future Features and Consent Tiers

Magima Kids may introduce new capabilities over time. We use a tiered consent model so that new features never activate without appropriate permission. Each tier builds on the previous one.

Tier 1 — Offline Creative Tools (Current, No Additional Consent)

This is the app today. All creative tools work offline with no accounts, no servers, and no data leaving the device. The only data collection is anonymous Apple App Analytics under the COPPA internal operations exception.

Tier 2 — Cloud and AI Features (Verifiable Parental Consent Required)

Future updates may include features such as:

  • Cloud save and cross-device synchronization of creations
  • AI-assisted content generation (e.g., AI-generated backgrounds, music, or characters) using external AI services
  • These features would require sending limited creative data (such as prompts or artwork) to external servers for processing
  • Only the minimum data necessary to perform the requested function will be sent — no personal information (names, photos of children, or identifying data), only creative content the child chooses to process
  • Any third-party AI service provider will be contractually required to process data solely for the requested task, not retain children's creative content beyond the duration of the request, and not use it for training, profiling, or any other purpose
  • All Tier 2 features will be disabled by default and will require verifiable parental consent (VPC) before activation
  • A child using only Tier 1 features does not have data sent to any external service

Tier 3 — Social and Community Features (Separate Verifiable Parental Consent Required)

Future updates may include features such as:

  • Sharing creations with other Magima Kids users
  • Collaborative creative spaces
  • Community galleries
  • All Tier 3 features will be disabled by default and will require separate verifiable parental consent beyond any Tier 2 consent already granted
  • Content moderation and safety measures will be in place before any social features are launched
  • Any data collected for social features will be fully disclosed at that time

Parent and Teacher Portals (Adult Accounts, Not Subject to COPPA)

We may introduce optional web-based portals for parents and teachers to:

  • View and manage their child's or student's app activity and creations
  • Manage consent preferences and privacy settings
  • Coordinate classroom use across multiple devices

Parent and teacher accounts are adult accounts and do not collect children's personal information directly — they provide a management layer over the child's on-device experience. In school settings, the school may provide consent on behalf of parents for the collection of student information for educational use, as permitted under COPPA (16 CFR 312.5(c)(1)) and the FERPA school official exception. Such consent applies only to educational use within the school context.

For All Future Features:

  • Each tier is independent — consenting to one does not activate another
  • Consent can be withdrawn at any time, which will disable the corresponding features and delete any associated server-side data
  • We will update this privacy policy and provide prominent in-app notice before launching any new tier
  • No feature will ever collect more data than is necessary for its stated purpose (data minimization)
  • All future features will maintain compliance with Apple's Kids Category guidelines, COPPA, and FERPA
  • Any third-party service providers will be contractually bound to handle children's data in accordance with COPPA requirements

Changes to This Privacy Policy

If we make material changes to how we handle children's information, we will provide prominent notice within the app and, where required by law, obtain any necessary parental consent before implementing the changes.

Contact Us

If you have questions about this Privacy Policy, our data practices, or your child's privacy, please contact us at:

Magima Kids LLC

Email: hello@magima.kids

Phone: (323) 366-1535

Website: www.magima.kids

Mailing Address: 415 W. Ave 42, Los Angeles, CA 90065

This privacy policy is effective as of March 21, 2026.

Questions?

Have questions about this privacy policy?

Get in Touch