CSAM and child safety
Reports involving child sexual abuse material, exploitation or grooming are treated as urgent safety matters and may be escalated to appropriate authorities or reporting channels where required by law.
Abuse prevention
Safety protocols for a privacy-first ecosystem.
Ackaia builds products around confidentiality, but private infrastructure must never become a safe harbor for abuse. This page explains how we respond to harmful activity across Ackaia One, Ackaia ID and future Ackaia services while preserving the zero-knowledge boundaries that protect legitimate users.
△
Public share reportedObject signature, report category and link context queued for review.
Intake◇
Zero-knowledge boundary preservedNo employee receives user encryption keys or bulk access to private content.
Privacy↯
Abuse action availableDisable sharing, restrict account behavior, preserve evidence or escalate.
ResponseWhat we act on
Abuse categories that can trigger review, restriction or removal.
Ackaia reviews reports involving illegal, harmful or policy-violating activity. The exact response depends on the product, available evidence, jurisdiction, user history and severity of harm.
Malware and unsafe files
Public links, files or account behavior associated with trojans, ransomware, credential theft, malicious executables or harmful scripts may be blocked, rate-limited or escalated for technical review.
Copyright and piracy
Ackaia processes notices involving unauthorized distribution of protected works, piracy, circumvention tools or repeated infringement under applicable law and internal evidence-handling rules.
Phishing and fraud
Impersonation, fake downloads, deceptive public links, credential capture and financial scams are treated as platform abuse and may lead to link disabling or account restrictions.
Illegal or severe abuse
Content or behavior connected to violent threats, exploitation, severe harassment, non-consensual exposure or other illegal activity can trigger preservation and escalation protocols.
Spam and service misuse
Automated abuse, mass distribution, evasion attempts, infrastructure misuse and attempts to degrade Ackaia services can lead to throttling, suspension or access limitations.
Internal protocol
How an abuse report moves through Ackaia.
Our process is built around proportional action. We collect only what is necessary to evaluate the report, preserve operational integrity and respect the encryption boundaries of the service.
Step 01Intake and classification
Reports are categorized by harm type, urgency, product, object identifier, public link context and available technical signals. CSAM, malware and imminent harm receive priority handling.
Step 02Scoped evidence review
Review focuses on report details, object-level signatures, account behavior, public share metadata, abuse history and legal requirements. Private file contents remain protected by the platform architecture.
Step 03Risk Assessment Engine
Ackaia One Storage uses a Risk Assessment Engine to evaluate signals such as public-link behavior, report patterns, repeated object signatures, abnormal distribution, account trust and policy severity.
Step 04Product-level action
Depending on severity, Ackaia may disable a public share, restrict sharing capabilities, suspend an account, preserve relevant records, request more information or reject unsupported reports.
Step 05Legal escalation
Valid legal requests, child safety reports, copyright claims and severe abuse are routed according to our legal repository, applicable law and internal documentation requirements.
Zero-knowledge first
The Risk Assessment Engine does not override encryption.
Ackaia can fight abuse without making private user files generally visible to employees. The zero-knowledge boundary remains the supreme architectural principle of Ackaia One Storage.
No bulk content surveillance
The platform is not designed around generalized scanning of private user files. Abuse review relies on reports, public-share context, object signatures and operational metadata.
No access to local keys
Ackaia employees do not receive a user's local encryption key as part of abuse review. Reports may include object-level signatures generated by the client without exposing the user's key material.
Proportional intervention
Actions are scoped to the suspected abuse: public links can be disabled, account behavior can be restricted and legal preservation can be applied without weakening the encryption model for everyone.
Documented limitations
Ackaia publishes legal and security documentation so users, reporters and authorities can understand what the company can review, what it cannot review and how requests should be submitted.
Legal repository
Public policies define how Ackaia handles reports and requests.
For binding terms, data handling rules, responsible disclosure and product-specific limitations, use the official legal repository. This abuse page is an institutional overview and should be read together with those documents.
Open all legal documents →Report abuse
Help keep private infrastructure safe.
Send reports with the public link, suspected violation, relevant context and any legal ownership details when applicable. Do not include unnecessary sensitive personal data.