What Makes a Useful RequestClear Information Helps Us Find the Right Page
The directory contains individual profile posts, area pages, nationality pages, category collections, menus, cards, images, and structured data. A support message needs enough context to identify which part is affected.
Always include the URL
Two pages can contain similar names or profile cards. The complete URL tells Site Support exactly where the issue appears. Copy the address from the browser instead of describing the page only as “the Marina one” or “the Russian page.”
Separate the problem from the requested action
Explain what is wrong and what outcome is requested. For example: “The language field on this profile says French, but it should say English. Please correct that field.” This is clearer than a general complaint without a requested result.
Identify the affected image or section
When a page contains several gallery images, profile cards, or headings, mention which one is involved. A screenshot may help, but the URL and written explanation are still important.
Keep evidence relevant and non-sensitive
Some image-rights, identity, or removal requests may require enough information to assess the connection with the content. Do not send more personal information than necessary. General support should never ask for card numbers, passwords, or banking login details.
Use one message for one main issue
Combining a profile correction, technical problem, removal request, and unrelated navigation question in one long message can delay review. Start with the most important issue and identify it clearly.