Pre-launch draft — not approved for public launch. Operator details, contact channels and described workflows require verification. This page does not submit a complaint or security report.

Grievance Redressal and Complaint Tracking

Formal grievance and complaint process for marketplace, account, privacy, payment, content, and security issues.

1. Complaint Categories

Users should be able to submit order complaints, booking complaints, creator complaints, refund complaints, payment complaints, content complaints, privacy complaints, account/security complaints, IP complaints, and moderation appeals.

2. Tracking Requirements

Each complaint should generate a ticket ID, category, created date, status, assigned team, timeline, user-visible updates, requested evidence, decision, remedy, and resolution summary. Users should be able to track progress at /account/support/{ticket_id} when implemented.

3. Grievance Officer

Sobuh must publish genuine current grievance contact information before launch, including responsible officer or role, company/entity name, business/contact address, official email, complaint process, acknowledgement process, and expected resolution process. Do not invent an officer, phone number, or office address.

4. Current Contact Placeholder

Until final legal setup is complete, use the published grievance channel as the placeholder grievance mailbox in test and pre-launch environments. Replace this with counsel-approved details before public launch.