Child safety standards

1. Audience and age eligibility

Whytype is an AI writing and meeting assistant, not a service designed for children. The audited app and website materials do not establish a product-specific minimum age or an implemented age-verification process. Users must meet the minimum age required by the laws and app-store terms that apply to them. The operator must set and publish one consistent product age rule before release. This statement is a standard, not a claim that Whytype can verify age or enforce an age gate.

2. Prohibited child sexual abuse and exploitation

Whytype prohibits child sexual abuse material (CSAM) and any conduct that sexually exploits, abuses, endangers or solicits a minor. This includes:

• creating, requesting, uploading, storing or sharing CSAM;
• grooming, sexual solicitation or attempts to move a minor into sexual contact;
• sextortion, sexual exploitation or trafficking of a child;
• sexualized depictions or descriptions of minors, including synthetic material; and
• using Whytype to facilitate contact, abuse, coercion or harm involving a child.

Do not submit, forward or attach suspected CSAM to a report. Provide only a concise description and the minimum account or content details needed to identify a concern. Do not download or redistribute suspected illegal material.

3. Reporting a concern

The audited app has no dedicated child-safety report button or reporting queue. As an interim public route, use the DizByte contact form and clearly title the message “Whytype child safety concern.” Include the relevant account or feature, approximate date/time, and a short explanation. Do not include passwords, authentication tokens, unnecessary personal details or suspected CSAM attachments. The current form is a general contact channel; it is not an in-app report mechanism or a dedicated monitored child-safety channel.

If a child is in immediate danger, contact local emergency services or the appropriate child-protection/law-enforcement authority first. You may also report harmful app content to the relevant app store using its reporting process.

4. Review, escalation and enforcement

Reports received through the general contact form require human review through the current contact process. The audited project does not show dedicated child-safety staffing, a moderation queue, automated CSAM detection, 24/7 monitoring, a guaranteed response time or tooling to restrict accounts from this page. Do not assume a report has been seen until the operator confirms receipt through a verified channel.

Where the operator can act and has sufficient information, it may review the report, preserve relevant records where lawful, restrict access or take other account action consistent with law and platform obligations. The operator must establish and staff these procedures before claiming that enforcement is operational. Information may be escalated to appropriate authorities when required by law or necessary to protect a child, subject to applicable legal requirements.

Reports are sensitive. Submit the minimum necessary information; access should be limited to people who need it to assess and handle the concern. The project audit did not verify an internal access/retention procedure for child-safety reports, so that process must be established before publication.

5. Current safety controls and release requirements

The repository audit did not establish implemented age verification, parental controls, automated moderation, in-app reporting or continuous monitoring. This page publishes standards only; it does not represent those controls as available.

Apple App Review Guideline 1.2 requires filtering, reporting with timely response, blocking and published contact information for apps it treats as user-generated-content apps, including AI content-generation experiences. The operator must assess whether Whytype's private AI generation and user-captured content fall within that guideline and implement any applicable controls before submission.

Google Play's Child Safety Standards policy currently applies to anonymous/random chat apps and apps declared in the Social or Dating categories. It requires published standards, an in-app feedback mechanism, a process for CSAM, compliance with child-safety laws and a designated child-safety point of contact. Whytype's Play category and policy scope must be confirmed in Play Console. If in scope, the audited app currently lacks several required operational controls and must not be represented as compliant until they are implemented.

Official references: Apple App Review Guideline 1.2 and Google Play Child Safety Standards.

6. Related information

Read the Whytype Privacy Policy or visit Account deletion. These pages do not replace a dedicated child-safety reporting and response system.