Moderation, Trust & Privacy (GDPR/KVKK)

Overview

ToRun runs automated content moderation through a classifier and backs financial actions with tamper-evident billing audit records. It also provides first-class GDPR/KVKK tooling: data export, erasure, and consent tracking. The goal is safety and compliance that are auditable, not just asserted.

Automated screening

Content is screened automatically by a classifier:

• Images you upload are screened before they are stored and rejected if flagged; categories include sexual content involving minors.
• Text published to a public surface — shared canvas artifacts and community/forum posts — is screened before it goes live.
• Public persona content is gated to an "approved" state before anyone else can see it.

Transparency: this automated screening is a classifier applied to uploaded images and to publicly published text — not a hash-matching database such as PhotoDNA — and it does not screen every private, in-session generation. We are actively expanding coverage.

Prohibited content and reporting

CSAM and other illegal content are strictly prohibited under our Acceptable Use Policy. When we become aware of such content we remove it, terminate the account, and report it to the competent authorities (for example NCMEC or the relevant national body) where the law requires. This is a policy commitment, not an automated reporting pipeline.

Reports, review and appeals

We review abuse reports through human review and enforce proportionately: a warning, a suspension, or permanent termination depending on severity. If a decision goes against you, you can appeal it.

Tamper-evident billing audit

Billing and financial events are written to append-only, hash-chained audit records: each entry's hash incorporates the previous entry's hash, so any later tampering breaks the chain and is detectable. Financial and audit records are not bulk-deletable and follow long retention — integrity over convenience.

Privacy: consent, export, erasure

• Consent — granular consent is recorded per category and version, with revoke history, so you have a clear record of what each user agreed to and when.
• Data export — users can request a copy of their personal data; the platform gathers personal data across modules and returns it.
• Erasure — users can request deletion. Content is hard-deleted; financial and audit data is anonymized and retained (legal/financial records must survive, but with the personal link removed). Data-subject requests are tracked formally end to end.

Tips

• Review your consent settings — they govern what's processed and can be revoked.
• Use the data export/erasure controls for any access or deletion request; both are formal, tracked flows.
• Remember that erasure removes personal content but intentionally keeps anonymized financial/audit records for compliance.