Photognome Safety Center | Reporting, policies, appeals, and status

Page 21: Safety Center

Clear rules, easy reporting, and realistic safety promises.

Photognome gives creators visible guidance for community behavior, verification, blocking, report submission, report status, staff triage, consent, adult/minor safety, scams, and appeals without claiming outcomes beyond platform control.

Report an issue Check report status

Escalation guide

Use the right channel

Immediate danger: emergency services.
Threats, minor safety, coercion: high severity report and preserve evidence.
Scams, harassment, content rights: structured report for moderator triage.

Community guidelines

Respect collaborators, disclose expectations, do not harass, impersonate, spam, pressure people off-platform, or post illegal/prohibited content.

Verification

Badges should explain what was checked. Verification improves trust signals, but it is not a guarantee of safety, quality, or background screening.

Meeting safety checklist

Meet in public or professional spaces first, share plans with a trusted person, keep booking terms in writing, and leave if conditions change.

Adult and minor safety

Adult/sensitive content must be age-gated and opt-in. Minors, if allowed, need stricter discovery, messaging, guardian consent, and adult-content exclusions.

Scams and payments

Beware advance-fee requests, overpayment/refund tricks, off-platform pressure, vague usage rights, unsafe travel demands, and unverified payment claims.

Blocking guide

Blocking should stop new messages and future interaction paths. Use a report too when there is harassment, threats, scams, or safety evidence staff should review.

Appeals

Users should be able to appeal moderation actions with context and evidence. Appeals are reviewed separately from the original action where possible.

Structured reporting

Report a profile, message, media item, casting call, listing, group, or safety issue.

Reports are stored locally in this non-production build using the same shape expected by the reports/moderation/audit database work: reporter, target type/id, reason, severity, description, evidence, status, assignment, and timestamps.

Reporter email or username Your role Target type Target ID or URL Reason Severity

What happened? Evidence links, message IDs, or notes

Preserve related content for staff review where policy allows. Support may contact me about this report.

Report status

Check local report status

Production should back this with authenticated report-status APIs. This demo lets a reporter or staff member verify the structured record was created.