Report a listing, user or Story
Choose the material, describe the facts and retain submission confirmation.
Where to find it
- Material → Report
- Report form
In this guide
FayVay separates reports about another user’s content from support requests about your own account. The first requires an identifiable item and observable facts; the second needs details of the error and affected account. Choosing the appropriate channel helps direct the issue without promising a particular decision or deadline.
What to prepare
- Keep the exact material link and a short factual explanation. Use distinct links for different listings or Stories; a display name alone may not locate the item.
- Choose a reason matching the issue. Select a subreason where requested based on substance rather than how serious it sounds. Distinguish an assumption from something you observed directly.
- Include only necessary information. Omit passwords, security codes, other people’s documents and irrelevant private messages. Use the exact link and description for harmful material instead of redistributing it.
Choose the appropriate entry point
Listing and photographs
Open the listing and its available report action; a media viewer may offer a flag. Describe the specific photo and where it appears. A page report does not mean that the form accepts an arbitrary direct file URL.
Public user profile
The public user page provides a flag action. Use it for user-profile context. For unwanted contact, consider blocking separately; submitting a report does not itself block the person.
Story
Open the relevant public Story and its Report action. Choose an available reason, enter details and wait for confirmation. This flow targets that Story; do not substitute an unrelated listing link.
Other material or an unsupported link
If an action is missing, only changes local state or the form rejects the URL, use Support with the original link and explanation. Not every legacy Report control is promised to submit a report. Avoid inventing another URL merely to bypass validation.
Submit through the Report page
Check the URL
The Report form accepts this site’s /profile/slug or /user/slug links, including the corresponding ru-prefixed variant. External sites and other paths can be rejected. Enter the real link rather than the field’s example. If a newer public path is unsupported, use Support.
Enter the reason and details
Select a reason and any required subreason. Explain what happened and identify the relevant material. For a message-related concern, explain its connection with the profile and the relevant context. An insult or a demand for immediate removal does not replace an explanation.
Wait for confirmation
Submit and inspect the result. A successful submission through this page displays a FAY-style reference and received state. Keep the reference with the link. An error or a closed window is not proof that a report was received.
Receipt and outcome are separate stages
| Report received | A record exists for review. It is not confirmation of wrongdoing, a refund or a guaranteed sanction. |
|---|---|
| Report reference | Useful for follow-up support. The current user interface does not provide a public tracking portal for all report references. |
| Blocking | A separate contact control inside the product. It does not replace reporting or erase content already seen by the recipient. |
Example: reporting a photograph
Suppose a listing contains a photo you believe belongs to someone else. Open Report from that page, choose the matching reason and identify the image and any source you know. If you are asserting rights, also read the copyright reporting guide. Moderation needs the connection between the material and concern, not all of your personal files.
After submission
When is a decision made and will I receive email?
Receipt does not promise an automatic email, fixed review deadline or predetermined outcome. Retain confirmation. Contact Support about your submission rather than relying on a public tracker that is not provided.
How can I add information?
Give Support the reference, original link and new checkable information. Avoid mass duplicates or asking others to submit identical reports; repetition does not replace additional facts.
Submission fails
Check the local URL, reason, subreason and description. If requests are limited, wait until the action becomes available. For a persistent failure, describe it to Support without login secrets. Use local emergency channels for immediate danger.
FayVay