Claims policy

What every KidsPiggy surface is allowed to say

One canonical record of product status, feature status and prohibited claims. No KidsPiggy subdomain may publish a stronger claim than this page. Last updated 2026-08-04.

Product surfaces and their status

kidspiggy.appLive

Canonical informational and evidence site

Source of truth for every public KidsPiggy claim. All other surfaces must stay within the wording published here.

play.kidspiggy.appPublic beta

Interactive surface for children, used with an adult

Publicly reachable and in active development. Its exact feature set and data flows are NEEDS OWNER CONFIRMATION and are not described as finished here.

adventure.kidspiggy.appPrototype

Longer-form explanation and concept surface

Contains interface concepts and marketing copy that predate this claims policy. Its certification, encryption, offline and non-profit statements are not supported by evidence and are scheduled for removal.

piggy.academyLegacy

Earlier KidsPiggy-related deployment

Not maintained under this claims policy. Anything it states should be checked against this page before being reused.

Claims removed or prohibited

These statements have appeared on KidsPiggy surfaces and are not supported by documentary evidence. They must not be republished, and they must not be replaced with synonyms. Certification badges and compliance seals are prohibited unless the certifying body, report identifier, issue date, validity period, audited scope and evidence URL are all published alongside them.

COPPA Certified / Full COPPA compliance

seen on adventure.kidspiggy.app

Why it is removed: No certification through an FTC-approved COPPA Safe Harbor program exists, and no compliance assessment has been published.

Approved wording: KidsPiggy is designed for minimal data collection and adult involvement. No COPPA Safe Harbor certification has been obtained.

GDPR Certified

seen on adventure.kidspiggy.app

Why it is removed: GDPR has no general certification of this kind, and no certification body or Article 42 mechanism is documented.

Approved wording: Privacy requests can be sent to Free Intelligence Institute LLC. No GDPR certification is held.

kidSAFE Certified

seen on adventure.kidspiggy.app

Why it is removed: No active kidSAFE certification or verifiable public listing exists.

Approved wording: None. Do not mention this at all.

SOC 2 Certified

seen on adventure.kidspiggy.app

Why it is removed: No SOC 2 report exists; no type, scope or audit period can be stated.

Approved wording: None. Do not mention this at all.

Regular third-party security audits

seen on adventure.kidspiggy.app

Why it is removed: No third-party security audit has been commissioned or published.

Approved wording: No independent security audit has been performed. This is an open item.

End-to-End Encryption / bank-level encryption

seen on adventure.kidspiggy.app

Why it is removed: Traffic is served over standard HTTPS/TLS. No end-to-end encrypted architecture has been implemented or verified.

Approved wording: Traffic between your browser and our servers is encrypted in transit using HTTPS.

On-Device Processing / many features work offline

seen on adventure.kidspiggy.app

Why it is removed: AI responses are produced by server-side model providers. No verified offline mode exists.

Approved wording: KidsPiggy requires an internet connection. AI responses are generated on servers, not on your device.

No Data Collection / no data collection at all

seen on adventure.kidspiggy.app

Why it is removed: Incompatible with described features such as profiles, personalization, dashboards, activity reports and conversation processing.

Approved wording: KidsPiggy aims to collect as little as possible. What is actually processed is itemised on the privacy page.

Never shared with third parties

seen on adventure.kidspiggy.app

Why it is removed: Hosting, delivery, analytics and AI model providers necessarily process data.

Approved wording: Data is not sold. It is processed by the infrastructure and AI providers needed to run the service.

100% Non-Profit

seen on adventure.kidspiggy.app, piggy.academy

Why it is removed: KidsPiggy is operated by Free Intelligence Institute LLC, a limited liability company, not a registered nonprofit entity.

Approved wording: KidsPiggy is developed by Free Intelligence Institute LLC as an independently funded educational AI project, without advertising revenue.

100% parent-controlled / full parental control

seen on adventure.kidspiggy.app

Why it is removed: Parent-facing controls are partly interface concepts and are not all operational.

Approved wording: Parent-facing controls are in development. Current status per feature is published on this page.

No tracking (as a blanket statement)

seen on adventure.kidspiggy.app

Why it is removed: Advertising tracking is genuinely absent, but hosting logs and aggregated product analytics exist.

Approved wording: No advertising, no ad networks and no ad tracking. Hosting logs and aggregated analytics are used to keep the site running.

Statements that are accurate

KidsPiggy is developed and operated by Free Intelligence Institute LLC as an independently funded educational AI project.
KidsPiggy does not sell personal data.
KidsPiggy carries no advertising, no ad networks and no ad targeting.
KidsPiggy is designed to support — not replace — parents, teachers or human judgment.
Free access is currently available.
Traffic is encrypted in transit using HTTPS.
No independent audit, certification or peer-reviewed evaluation of KidsPiggy has been published.

Feature verification record

A feature is only described as working if it is currently functional and testable. Everything else is labelled as an interface concept, a planned feature, or unverified.

Guided conversation with Piggy

Unverified — needs owner confirmation

Surface:: play.kidspiggy.app
Data processed:: Conversation content sent to a server-side AI model provider.
Allowed wording:: Children can talk with Piggy in a guided, age-aware way.
Limitations:: Exact model provider, retention and logging are not confirmed for publication.

Parent Dashboard

Interface concept — functionality in development

Surface:: adventure.kidspiggy.app
Data processed:: None in the displayed concept; the numbers shown are illustrative.
Allowed wording:: Interface concept — functionality in development.
Limitations:: Must be labelled as a demonstration. Sample values such as 'Today: 45m' must not imply a real account.

Screen time limits

Planned feature

Surface:: adventure.kidspiggy.app
Data processed:: None today.
Allowed wording:: Planned feature.
Limitations:: No enforcement mechanism is implemented.

Activity reports

Planned feature

Surface:: adventure.kidspiggy.app
Data processed:: None today.
Allowed wording:: Planned feature.
Limitations:: No report generation exists.

Real-time alerts

Planned feature

Surface:: adventure.kidspiggy.app
Data processed:: None today.
Allowed wording:: Planned feature.
Limitations:: No alerting pipeline exists; must not be described as a safety net.

Content filters

Unverified — needs owner confirmation

Surface:: play.kidspiggy.app
Data processed:: Conversation content evaluated during generation.
Allowed wording:: Age-aware interaction boundaries are applied. No filter catches everything.
Limitations:: Not independently red-teamed, audited or certified.

Multi-child support

Planned feature

Surface:: adventure.kidspiggy.app
Data processed:: None today.
Allowed wording:: Planned feature.
Limitations:: No profile system is confirmed as operational.

Remote management

Planned feature

Surface:: adventure.kidspiggy.app
Data processed:: None today.
Allowed wording:: Planned feature.
Limitations:: No remote control capability exists.

Offline / on-device processing

Planned feature

Surface:: All surfaces
Data processed:: Not applicable.
Allowed wording:: KidsPiggy requires an internet connection; responses are generated on servers.
Limitations:: Must not be described as offline or on-device.

Personalization and adaptive learning

Unverified — needs owner confirmation

Surface:: play.kidspiggy.app
Data processed:: Would require storing per-child interaction history.
Allowed wording:: Interaction is age-aware. Any persistent personalization is not confirmed for publication.
Limitations:: Cannot be advertised alongside a 'no data collection' claim.

Encryption

Implemented and operational

Surface:: All surfaces
Data processed:: All traffic.
Allowed wording:: Traffic is encrypted in transit using HTTPS.
Limitations:: Not end-to-end encryption and not 'bank-level' anything.

Crisis handling

Unverified — needs owner confirmation

Surface:: play.kidspiggy.app
Data processed:: Conversation content.
Allowed wording:: KidsPiggy is not a crisis service. In an emergency, contact local emergency services.
Limitations:: No verified escalation or human-review pathway is published.

Sample values in any mock interface — for example a "Today: 45m" screen-time figure — are illustrative only and must be labelled as a demonstration, never presented as a live account.

Unresolved data-flow questions

Until these are answered by the operator, no surface may publish a precise privacy promise beyond what the privacy page already states.

Which AI model or API providers serve play.kidspiggy.app responses?
Are child profiles, conversations or drawings stored, and for how long?
Which analytics and error-logging services run on each surface?
Which hosting, CDN and database providers process data, and in which regions?
Is any account or parent/guardian consent flow implemented today?
Is any content used for model training, and with which provider settings?
What is the deletion procedure and its turnaround time?

Machine-readable

/claims.json · /llms-full.txt · Evidence and validation