Child Safety Standards

Last updated: 13.08.2026

This document sets out the standards AURCAM applies against child sexual abuse and exploitation (CSAE) and child sexual abuse material (CSAM). The policy can be summarised in two words: zero tolerance. This page is public, requires no account and cannot be edited by users. These standards apply alongside our Community Guidelines, Terms of Service and Privacy Policy.

In short: the five things to know

Zero tolerance

Any content or conduct that contains, depicts, promotes or facilitates the sexual abuse of children is strictly prohibited on AURCAM. Detected content is removed immediately, the account is permanently closed, the records are preserved as evidence and the incident is reported to the competent authorities. No appeal process applies in this category.

Prohibited: sharing, requesting or searching for CSAM; sexualising minors; sexual communication with a child (grooming); sextortion. It makes no difference whether the material is real, drawn or generated by artificial intelligence.
Reporting: report a post from its ⋯ menu, or a person from their profile or chat screen, and pick child safety as the reason. For anything else write to safety@aurcam.com — the email channel covers every surface. Reports are anonymous.
Minimum age: AURCAM is not available to anyone under 13; where your country sets a higher limit, that limit applies. Accounts found to be below the minimum age are removed and their data deleted.
Legal compliance: we report confirmed CSAM to the competent authorities in Turkey and in the user's own jurisdiction, and we respond to properly made law enforcement requests.
Contact point: safety@aurcam.com for any child safety matter. To report an account belonging to someone under 13, write to privacy@aurcam.com.

1. Our commitment and definitions

AURCAM treats the protection of children online not as a feature to be marketed but as a condition of the product existing at all. The following terms are used in this document with these meanings:

Child: Any person under 18. Where local legislation provides a broader definition, that definition applies.
CSAE: Child sexual abuse and exploitation — any sexually motivated conduct, approach, threat, encouragement or organisation directed at a child.
CSAM: Child sexual abuse material — any photo, video, audio, drawing, animation or artificially generated material that depicts a child in a sexual manner.
Grooming: Attempting to build a relationship of trust with a child in preparation for sexual abuse.
Sextortion: Threatening or blackmailing a child by obtaining, or claiming to have obtained, intimate imagery of them.

These standards apply across every surface of AURCAM: the iOS and Android apps, the macOS and Windows desktop apps and the aurcam.com web interface, including posts, stories, reels, comments, direct messages, audio and video rooms, audio/video calls, profile fields and usernames.

2. Content and conduct that is strictly prohibited

Sharing, resharing, requesting, searching for, selling or linking to child sexual abuse material (CSAM).
Sexualising minors — whether the material is a real image, a drawing, an animation, a composite or generated by artificial intelligence.
Attempting sexual communication with a child (grooming); sending sexual messages to a child whose age you know or should know.
Requesting intimate imagery from a child, sharing a child's intimate imagery, or using such imagery for blackmail (sextortion).
Content that normalises, praises or defends child trafficking, child prostitution or child abuse.
Communities, groups, coded language or hashtags used to bring child abusers together.
Creating an account on behalf of anyone under 13, or under the higher limit that applies in your country.
Creating a new account in order to evade an enforcement action taken in this category.

No appeal, no gradual ladder

For other violations we follow a graduated path: warning, content removal, feature restriction, temporary suspension, permanent ban. For child safety violations those steps are skipped: the first violation leads directly to permanent closure of the account, and the appeal process under the Community Guidelines does not run for this category.

3. Minimum age and underage accounts

The minimum age is 13. AURCAM is not directed at anyone under 13 and we do not knowingly collect their data.
Where the local limit is higher, it applies. In some countries the minimum age for data processing is 14, 15 or 16; in those countries the local limit governs.
A date of birth is required at registration. It is requested when the account is created and the age gate is enforced server-side; applicants below the limit cannot create an account.
Accounts below the minimum age are removed. If we learn that an account holder is below the age limit, we close the account and delete its data.
Misstating your age is a violation. Entering a false date of birth to pass the age gate breaches the Terms of Service.

How do I report an account belonging to someone under 13?

Send the username to privacy@aurcam.com. We review it and, once confirmed, close the account and delete its data. The same address handles data requests about your own child's account; the detailed guide written for parents is on the Parents' Guide page.

4. How to report a child safety concern

Anyone can raise a child safety concern with us, with or without an account. The in-app reporting route exists on every surface:

Post: The post's ⋯ menu → Report → choose Child safety from the reason list.
Person (account): The ⋯ on the profile screen → Report; or, in an open conversation, the Security section of the chat profile → Report. You can block from the same screen.
Comment, message, story, reel or room: These surfaces do not have a separate report button yet. Report the person who posted it as described above, or write to safety@aurcam.com; email reports enter the same priority queue.
Account under 13: Write to privacy@aurcam.com with the username.
Email (public): safety@aurcam.com — use this if you have no account or the situation is urgent. Write URGENT in the subject line.
Account belonging to someone under 13: privacy@aurcam.com

Reports are anonymous: the person you report does not see who reported them.
Child safety reports go into a priority queue and are reviewed ahead of other reports.
When reporting, do not download, save or forward the material; in many countries that is itself a criminal offence. Reporting the link or the username is enough.
If a child is in imminent and genuine danger, call your local emergency number first; in Turkey that is 112.

5. What we do when we receive a report

CSAE reports are reviewed by an authorised human moderator, not by whoever received the report. The process has the following steps:

Priority review. The report enters the child safety queue and is handled first, regardless of the order it arrived in.
Restricting access to the content. Where there is serious suspicion, the content is made invisible before the review is complete.
Closing the account. On a confirmed violation the account is permanently closed and the user's other accounts are also reviewed.
Preserving the evidence. The content, account records, session records and moderation records are preserved as evidence. Moderation records are kept for at least 2 years, and longer where an investigation is ongoing. Taking enforcement action does not erase those records.
Reporting to the authorities. Confirmed CSAM incidents are reported to the competent authorities (see section 7).
Escalation. Anything indicating that a child is in imminent danger is passed to law enforcement without delay.

Access to the admin panel is role-based and every administrator action is written to an audit log, so it is traceable which moderator saw which record and when. We publish aggregate statistics on content removals and authority requests on the Transparency Report page.

False reports

Abusing the reporting system — deliberately filing a false child safety report to silence someone — is itself a serious violation and is enforced against. This does not cover reports made in good faith that ultimately could not be confirmed.

6. What the product does to reduce the risk

Reporting and enforcement come into play after the event. Before that, the tools that make unwanted contact harder are already built into the product:

Blocking: Profile → ⋯ → Block. A blocked person cannot see your profile, message you or reach your content.
Private account: Settings → Privacy → Private account. Only people you approve see your content.
Who can message you: Settings → Privacy → Who can message you → Friends only. This cuts off most unsolicited first contact from strangers.
Comment and tagging limits: Settings → Privacy. Commenting and tagging can be restricted to friends.
Location off by default: Location sharing is off and works only with explicit permission; ghost mode hides you from the map with one tap. Details: Privacy Policy — Location.
Online status and footprint: Both can be switched off; the footprint is off by default.
Two-step verification: Settings → Security. It makes it harder for an account to be taken over and turned into a route to a child.

The set of settings we recommend for younger users is explained step by step on the Parents' Guide page. Settings belong to the account: a change made on one device applies instantly to every other session.

7. Legal compliance and cooperation with law enforcement

AURCAM complies with the child safety legislation of the countries in which it operates. For Turkey this covers, in particular, the provisions of the Turkish Criminal Code no. 5237 on the sexual abuse of children and Law no. 5651, together with related regulations.
We report confirmed CSAM incidents to the competent authorities: in Turkey to the Public Prosecutor's Office and the relevant agencies; and, to the extent local legislation requires, to the competent authority in the user's own country.
We respond to law enforcement requests. We act on properly made, written and legally binding requests. Where there is an emergency involving a risk to life, we use the emergency disclosure route to the extent the law permits.
Our data protection obligations are unaffected. This reporting and cooperation does not conflict with our obligations under KVKK and the GDPR: a legal obligation is a lawful basis for processing personal data.
We publish the aggregate number of authority requests we receive on the Transparency Report page.

The status of this page

This document is the public policy published to meet Google Play's child safety standards requirement and Apple App Review expectations. It requires no account, is accessible worldwide and is updated only by AURCAM. The current version always lives at aurcam.com/child-safety.

8. Child safety contact point

Child safety (published contact point): safety@aurcam.com
Reporting an under-13 account and parental data requests: privacy@aurcam.com
Law enforcement and legal requests: legal@aurcam.com
General support: support@aurcam.com

We treat child safety reports as priority. In an emergency write URGENT in the subject line. These addresses also work for people who have no access to the app.

9. Where else you can turn, besides reporting to us

Reporting to AURCAM is not a substitute for going to the authorities. You can do both:

Emergency (Turkey): 112 — the emergency call centre. If a child is in imminent danger, call this first.
İhbar Web (Turkey): ihbarweb.org.tr — the official line for reporting unlawful content encountered online, including child abuse.
Social Support Line (Turkey): 183 — the support line of the Ministry of Family and Social Services.
Other countries: Contact your country's child protection line or the police. For international reporting, the INHOPE member hotlines and the NCMEC CyberTipline can be used.

10. Updates

We update these standards in line with changes in legislation and in the product. The last updated date at the top of the page always shows the version in force. Material changes are announced together with updates to the Community Guidelines.

Language

This English text is a translation provided for information. The binding version is the Turkish text at /child-safety; in the event of any conflict, the Turkish text prevails.

Questions? support@aurcam.com · Contact page