Skip to content
Home

Sparky AI · Legal & help

Privacy Policy

This policy describes parent accounts and family use when available. We minimize children’s data, use no advertising trackers and do not sell personal information.

Draft updated: November 2, 2026

1. Controller and contact

The controller and provider is Binoron, LLC, 1111B S Governors Ave # 47095, Dover, DE 19904, United States. General contact: support@littleaiminds.com. Privacy and security: security@binoron.com.

Sparky is offered to families in multiple countries. Mandatory rights where a family lives remain unaffected.

2. Children and parental consent

Sparky is intended for children ages 6–12. Child use requires expressly enabled protected family access approved for the relevant country; anonymous or public child access is not offered.

Where registration is offered, a parent registers their own protected account without an invitation and confirms their email. The new usage path creates no child account or child profile and requires no nickname, gender or profile image. Language and answer level are temporary choices for current use, not saved facts about an individual child.

Usage access starts only after its own parental consent for this path and the current notice has been verified. Previous child-profile consent or adult QA attestation cannot replace it. Parents can withdraw it at any time in the protected parent area, immediately blocking the associated usage sessions. When family access is offered, it requires separate, explicit parental checkboxes for the current data-processing notice and a successfully completed, verified qualifying credit-card payment with a notification mechanism to the primary cardholder. A checkbox, adult or email login, or an arbitrary successful payment alone is insufficient. The payment obligation and withdrawable parental consent are separate declarations. No signed document or document upload is required. Each family needs its own current verified consent; previous child-profile consent or adult testing does not replace it. Parents can withdraw consent in the parent area, immediately blocking the associated usage sessions.

3. Data we process

  • Question and answer content: deliberately typed or recorded open questions, generated answers, and the temporarily selected language and answer level. These choices shape the explanation without collecting a child’s age, gender or identity. No learning progress or chat history is saved. Voluntary questions, recordings and answers may themselves contain personal information; removing profiles does not remove that processing.
  • Microphone use starts deliberately; an active voice conversation may then capture short turns automatically after pauses. It must be possible to stop or interrupt it; there is no background listening outside a started conversation. Open typed questions remain an equally available input. Recording and a technical session identifier do not create a child profile.
  • Session data: random technical session identifiers, usage counts, error categories, and limited device or browser information for safety and operations.
  • Visual coverage: the new usage path finds relevant images without saving the question or answer as a visual-gap report. Separate editorial paths may store minimized general visual topics and counts without a raw child question, answer or direct network identifier.
  • Parent and access data: email in Supabase Auth, short-lived registration and session credentials, parental consent evidence and status, an isolated usage session, technical usage counts and export, correction, deletion, withdrawal and cancellation-request status. Existing older child-profile and consent records remain for parent rights and the documented deletion process; the new usage path does not use them as a profile.
  • When parent payments are offered, Stripe processes payment and billing details on its protected pages. Sparky receives adult account, customer, checkout, subscription, price, invoice and status identifiers, paid periods, plan-change and cancellation status and minimal security evidence. No child name or profile is sent; Sparky stores neither full card data nor raw payment webhooks.
  • Support data: an adult’s email address and voluntary message content when contacting us.

4. Purposes and legal bases

We process data to provide a requested answer, produce speech, retrieve relevant visuals, limit abuse and cost, fix errors, apply safety rules, and answer support requests. For EU/EEA users, the legal basis depends on the activity and may include a contract or pre-contract steps with the parent, legitimate interests in a safe and functional service, legal obligations, and explicit parental consent where required.

We do not sell personal information, use behavioral advertising or build marketing profiles about children. The prepared model route requires providers not to collect request data for training; voluntary input/output logging or product-improvement use is not intended to be enabled. This routing rule is not an independent audit of all provider systems and does not eliminate their safety, metadata or legal processing.

5. Recipients and service providers

  • Vercel for hosting, delivery, and technical operational logs.
  • OpenRouter: receives the current text question, limited conversation context, language and explanation level and routes them only to Microsoft Azure in the United States for the OpenAI GPT-5.5 model. Answers return through the same route; the family path does not use direct OpenAI speech services or fallback model providers.
  • Microsoft Azure Speech, EastUS (United States): receives short microphone audio for transcription when enabled; checked answer text is processed for synthetic speech using the prebuilt Brian voice. Audio and text pass through Sparky’s server. Brian is an AI voice, not a real conversation partner or a clone of a child’s voice. Microsoft describes no retention of audio, input text or output audio for the selected real-time STT/prebuilt TTS features; general operational metadata and differently configured features are separate.
  • Supabase for the EU-hosted visual library, parent authentication and self-registration, private consent, account, rights and admin data, isolated usage sessions, short-lived rate limiting and minimized editorial visual-coverage data. Older profile records remain for parent rights; the new path creates no child profiles.
  • HeyGen for a technically available optional avatar/video feature in the separate adult QA path. The new protected usage path does not use it. Where deliberately and permissibly used, only a scrubbed Sparky answer, not the raw question, is sent.
  • Stripe only if parent payments are later enabled, for checkout, subscription, and payment management.
  • Authorities or advisers only when legally required or necessary to protect rights, safety, and prevent abuse.
  • Resend for transactional parent sign-in, confirmation and recovery emails, using email addresses, message content or one-time codes and delivery, error and technical logs. Where Resend is used for voluntary adult support emails, it may also process those messages and voluntary attachments. No child newsletter or marketing delivery is provided through this path.

6. International transfers

Binoron, LLC is based in the United States. The prepared OpenRouter→Azure model route processes data in the United States; Azure Speech uses EastUS. The Supabase database in Frankfurt does not make those flows EU-only. Providers may use other countries for operational data and subprocessors. Provider-specific processing contracts and applicable transfer safeguards, such as Standard Contractual Clauses or an actually applicable adequacy/DPF arrangement, are distinct from technical retention and routing controls. Information about recipients and applicable safeguards can be requested through our privacy contact. We do not promise end-to-end EU data residency.

7. Retention and deletion

  • Questions, answers, microphone and replay audio are processed temporarily in the browser and server memory for current use; Sparky keeps no permanent raw-question, answer or audio history in its own database. A new topic, exit or language/level change discards conversation context. Technical cost and security metadata are separate.
  • OpenRouter retains request metadata such as token counts and latency and describes sampled categorization. Even where a model request asks for Zero Data Retention (ZDR), content suspected to be child sexual abuse material (CSAM) may be retained for human review, legal reporting and required preservation. The fixed model route requests ZDR routing without provider fallback. Microsoft also describes temporary derived prompt caches, up to 24 hours for GPT-5.5; we have not independently inspected the upstream Azure configuration. We promise neither immediate erasure by every provider nor unconditionally storage-free processing.
  • Short-lived rate-limit and visual-gap session keys expire automatically. Aggregated visual topics may remain for catalog review and quality planning, but do not contain a raw question or direct identifier.
  • Existing technical cleanup rules cover short-lived usage and playback records: playback tickets last at most 90 seconds and become eligible one hour after expiry, turn metadata 24 hours after expiry and session records seven days after expiry or revocation. Rejected, withdrawn or superseded consent evidence becomes eligible after 30 days unless still necessary. A non-directly identifying rights-request receipt and access audit records provide for up to 365 days. These are technical eligibility rules, not a promise of immediate complete erasure; bounded batches, outages and unresolved new data flows must be considered.
  • Our support-mailbox policy is deletion 90 days after a case closes, unless a specific unresolved matter or legal duty requires preservation. This is an operational policy, not automatic app-database deletion.
  • Prepared defaults are 90 days after a closed cost period, 12 months after account or consent evidence is superseded, and 18 months after billing references become terminal and resolved. Current authorization, unresolved costs, disputes and required legal records remain protected. Minimal replay-prevention digests may remain while needed to reject old operations; they contain no conversation text or card details. Specific preservation holds are reviewed every 30 days and remain protective until expressly released.
  • Selective database cleanup for these categories has been installed and tested. The stated periods determine when records become eligible; they do not prove that every record has already been deleted. We review valid deletion requests and explain retained categories and reasons. Backup recovery copies and providers follow their respective arrangements; we do not promise immediate erasure from every copy.

8. Parent and individual rights

Parents and other adult account holders can request export, correction, deletion, and withdrawal of parental consent in the protected account. Withdrawal immediately blocks the associated usage sessions. Depending on location, additional rights may include access, restriction, objection, portability, and a complaint to a supervisory authority. Requests can also be sent to security@binoron.com; we may reasonably verify identity and parental authority.

US state laws may provide additional access, deletion, correction, and opt-out rights. Sparky does not sell or share data for targeted advertising, so a sale/share opt-out is not needed for that practice; relevant preference signals are still respected. Parents may refuse further collection and use, request access and a copy, and use available export, correction, deletion and consent-withdrawal controls in the parent area. Withdrawing parental consent blocks use but does not cancel a billing contract. Account deletion, privacy withdrawal and subscription cancellation are separate actions. We do not promise erasure at every provider without statutory exceptions.

9. Security and automated decisions

We use server-side credentials, access controls, private admin areas, rate limits, content rules, and data minimization. No online service is risk-free; incidents are assessed and notified as required by applicable law.

Sparky produces answers automatically but does not make legal or similarly significant decisions about children. There is no advertising profiling.

10. Changes

We update this policy before materially changing family access or payment processing, adding providers or introducing materially different data flows. Material changes will be shown clearly and, where required, require renewed parental consent.

Parent journey and current availability

Availability of parent registration, sign-in options, family access and subscriptions is shown in the parent area. A paid subscription requires separate confirmation of the displayed offer and payment obligation. Sign-in alone makes no charge and does not authorize child use.

When family access is offered, it requires separate, explicit parental checkboxes for the current data-processing notice and a successfully completed, verified qualifying credit-card payment with a notification mechanism to the primary cardholder. A checkbox, adult or email login, or an arbitrary successful payment alone is insufficient. The payment obligation and withdrawable parental consent are separate declarations. No signed document or document upload is required. Each family needs its own current verified consent; previous child-profile consent or adult testing does not replace it. Parents can withdraw consent in the parent area, immediately blocking the associated usage sessions.

Family access is offered only where the app confirms availability. EU/EEA countries and excluded territories, the United Kingdom, mainland China, Russia, Cuba, Iran, North Korea, Syria, Connecticut in the United States, and Crimea, Sevastopol, Donetsk and Luhansk are outside the supported scope. The parent’s declared residence and approximate current country/region are checked separately; a US state or Ukrainian region is required where relevant. Missing, unresolved or ineligible information blocks access. Do not evade these checks. This is no promise of availability in every other country.

Optional sign-in with Google or Apple

When this option is offered and you choose it, Sparky redirects you to Google or Apple. Supabase Auth processes the provider identifier and verified email address, which may be an Apple private relay address. Profile details supplied by the provider, such as name or profile image, may form part of the Auth account; Sparky does not need contacts, calendars, files or additional Google services.

This sign-in is for parents and does not replace verified parental consent. A necessary cookie lasting up to ten minutes binds the sign-in attempt to your browser. Google/Apple access tokens are not retained in the Sparky browser session. The providers process sign-in under their own privacy notices, potentially outside the EU. You can revoke the connection with the provider and request deletion of your Sparky account in the parent area; these are separate steps.

Family allowance emails

Where usage notices are offered and enabled in the parent settings, they notify the confirmed parent email at 75% and 90% of the shared family allowance. They use the plan, paid period, limited cost counters, language preferences and dispatch status; individual children, questions and voice recordings do not appear in these emails.

Parents can opt out of usage notices. Higher-plan suggestions also require a separate setting that is off by default. These choices are separate from revocable parental consent and subscription cancellation. Delivery uses Resend. Dispatch identifiers and status prevent duplicate notices.

For notices finalized as sent or suppressed, minimized queue and status metadata becomes eligible for cleanup 90 days after the relevant paid billing period ends. Active, pending or uncertain processing and preservation holds remain protected. Required payment and legal evidence follows its separate retention schedule. This eligibility does not promise immediate or already completed deletion.

Residence and availability checks

After parent sign-in, the new parent journey collects the country of residence and, for the United States or Ukraine, the state or region. It also records the declaration and parental-notice version and digest, selected language, confirmation, server timestamp and technical receipt identifiers. This does not collect a particular child’s residence, age or profile. These checks alone do not enable family access.

Current availability also uses the hosting service’s approximate country and region. Binoron does not store an IP address, city or raw network headers in this check’s receipt. Geolocation can be inaccurate and does not prove residence. A new declaration replaces the previous eligibility decision, revokes existing usage sessions and cancels unconsumed payment-consent intents. Sign-in, access requests, withdrawal and cancellation remain separate.

The current residence receipt is needed for the parent account. Under the prepared deletion contract, superseded receipts become eligible for selective cleanup 12 months after replacement; specific preservation holds and necessary evidence remain protected. Account closure follows the verified deletion process and remaining legal duties.

Parent contact phone

+13027700232

Telephone notice updated: November 21, 2026

Binoron, LLC uses Twilio for adult telephone support and voicemail. We process the caller number when available, call time and duration, and any message you choose to leave to handle support requests and operate this contact channel. Twilio processes the call details and stores voicemail messages for us. This contact channel is separate from children's use of Sparky.

This telephone support is for adults. The announcement is in English. After the beep, you may choose to leave a voicemail of up to 60 seconds. To avoid leaving a recording, hang up before the beep and email support@littleaiminds.com. Please do not leave children's names or questions, payment details or other sensitive information.

We do not transcribe these messages or analyze their content with AI. Access to recordings is protected by authentication and restricted to authorized support personnel. We delete recordings within 30 days after the support case closes, unless a specific legal preservation obligation requires longer retention. Email support correspondence remains subject to the separate deletion period of 90 days after case closure. Privacy and deletion requests may be sent to security@binoron.com.