Child Safety Policy

Our commitment

Angyal Group has zero tolerance for child sexual abuse and exploitation (CSAE). No content, conduct or feature that sexualises, endangers or exploits a child has any place in an Angyal app, and we will act on any report of it without waiting to be compelled.

This page is the child safety standards policy that Angyal (OPC) Private Limited publishes for its apps. It sets out how our apps are built, what we do about child safety, how anyone can raise a concern with us, and what we do when they do.

Which apps this covers

These standards apply to every mobile app published under the Angyal Group developer account on Google Play and the Apple App Store — currently Merge and Orbyx. Each app's own privacy policy describes what that app stores and transmits, and account and data deletion sets out how to erase everything an app has put on a device.

Why our apps carry no CSAE risk

CSAE material reaches users through features that let one person send content to another. Our apps have none of those features. In every app we publish:

• There are no accounts and no sign-in, so there is no identity to impersonate and no profile to target.
• There is no user-generated content of any kind. Nothing a player creates, types or uploads can be seen by anyone else, because nothing is uploaded at all.
• There is no chat, messaging, comments, usernames, avatars, or any other user-to-user communication — direct or indirect.
• There is no access to the camera, microphone, photo library or contacts.
• All content is fixed in the app at build time. Nothing is fetched from other players, and no player can change what another player sees.

Taken together, our apps provide no mechanism by which CSAE material could be created, uploaded, stored, shared or discovered, and no mechanism by which an adult could contact a child. This is a deliberate design decision, not an omission.

Age ratings and advertising

Our apps are rated for all ages, and none of them is enrolled in Google Play's Designed for Families programme. Where an app shows advertising, that advertising is served under restricted data processing and its content is capped at Google's “G” rating, so ads shown in our apps are non-personalised and age-appropriate. The details for each app, including which apps show ads at all, are in that app's privacy policy.

Reporting a concern

If you believe anything in one of our apps puts a child at risk, tell us. Write to grievance@angyal.in with the app name and enough detail to find what you saw — a screenshot is ideal. There is nothing you need to sign in to, and you do not have to identify yourself.

You can also report an app to the store it came from, using the report links on its Google Play or App Store listing. Store reports reach us as well, and they reach Google or Apple independently of us.

If you have seen child sexual abuse material anywhere — in our apps or outside them — please also report it directly to the authorities, who can act in ways we cannot:

• India — the National Cyber Crime Reporting Portal, which takes reports of child sexual abuse material, or the National Commission for Protection of Child Rights, which runs the POCSO e-Box.
• Internationally — the NCMEC CyberTipline.
• Anywhere — your local police. If a child is in immediate danger, contact emergency services first.

Why there is no report button inside the app

Google Play asks developers to provide an in-app mechanism for reporting CSAE where one applies. Ours have nothing for it to point at: with no accounts, no user-generated content and no user-to-user communication, there is no message, post, profile or upload for a player to flag. A report button in these apps would open onto an empty list.

The routes above are therefore the reporting mechanism, and they are set out on this page — linked from every app's privacy policy and from the site footer — so that they are easy to find without one. If an app of ours ever gains accounts, user content or player-to-player contact, it will ship with in-app reporting built in, and this page will say so before that build is submitted.

How we respond

Reports to grievance@angyal.in are read by a person, not a queue, and we aim to acknowledge one within 1–2 business days. A report that concerns a child's safety is looked at ahead of anything else in the inbox.

When we receive one, we:

• investigate what was reported and confirm what the app actually does;
• preserve the report and anything we are given with it, so that it is available to law enforcement;
• remove or disable anything that should not be there, and ship a corrected build as an expedited release;
• report the matter to the relevant authority where the law requires it, or where we judge it right to;
• cooperate fully with any law-enforcement or regulatory request that follows;
• and tell the person who reported it what came of it, where we have a way to reach them.

Legal compliance

Angyal (OPC) Private Limited is incorporated in India and complies with the Protection of Children from Sexual Offences Act, 2012 (POCSO), the Information Technology Act, 2000 and the rules made under it, together with the applicable child-safety laws of the markets our apps are distributed in. Where the law requires suspected child sexual abuse material to be reported to a designated authority, we report it.

We also comply with the child safety standards required by Google Play and the Apple App Store as a condition of distribution, and with their requests in relation to a child safety concern.

Our point of contact

The designated contact for child safety matters at Angyal (OPC) Private Limited is the Grievance and Data Protection Officer, reachable at grievance@angyal.in. Written correspondence can be sent to H:434 W:14, Mylapore, Umayanallor P.O., Kollam, Kerala, 691589, India.

That is the same person named on our grievance and data protection contact page, which sets out our response times in full and where to escalate if our answer does not satisfy you. A child safety report is the one thing that jumps the queue ahead of everything else in that inbox.

Keeping this current

We review these standards at least once a year, and whenever an app changes in a way that touches them. Because this policy rests on our apps having no accounts, no user-generated content and no user-to-user communication, any app that adds such a feature requires this page and that app's store disclosures to be updated before that build is submitted, not after it ships.