Submit a report
Email contact@egomonk.com with the subject "Ultra abuse report". Include:
- the category of harm, approximate UTC time, and a concise factual description;
- whether anyone faces immediate danger;
- your preferred contact address and, where relevant, your authority or relationship to the affected work.
Do not send a share URL or any share, transfer, target, or capability ID. Ultra does not yet expose a non-authorizing report reference; after the secure intake workflow is operational, the reviewer will arrange an approved identification step.
Intended review process
The following workflow is the pre-release operating target and is not yet an exercised response SLA:
- Verify that the identifier belongs to the service and create a redacted case reference.
- Contain immediate safety or integrity risk at the narrowest effective scope.
- Preserve only bounded evidence needed for the decision.
- When appropriate and lawful, notify the affected account and provide an appeal route.
- Apply account or capability restrictions after repeated substantiated abuse.
Removal is not a finding of criminal or civil liability. Legal requests require verification and escalation; ordinary support email is not treated as valid legal process. Until the mailbox and case workflow are exercised, reports are acknowledged on a best-effort basis.
E2EE and inspection limits
On browser-E2EE paths, Ultra generally cannot inspect plaintext payloads. Safety action may rely on reports, public metadata, bounded operational signals, capability revocation, account controls, and valid legal requirements. Ultra does not claim automated scanning of opaque E2EE payloads.
Intended appeal route
After the case workflow is operational, a reporter or affected account may reply with the case reference, the decision being challenged, and concise supporting facts. A reviewer other than the original decision-maker should assess the appeal where staffing permits. Provider mailbox operation and response targets remain pre-launch verification items.