Questions for the PlayKovo Partner Team: What to Include

The partner team is a small address with a lot of possible questions. A message with the right details gets a useful answer on the first reply. A vague one leads to a round of "which site? which game?". This post lists what to include for the common kinds of request, with short templates you can copy.

The partner pages give one contact address for questions about embeds, website registration and the catalog: [email protected]. Use it for partner matters. Game-specific complaints and legal notices follow the process in the Partner Terms; see takedowns.

• The domain of your site, exactly as it appears in the address bar.
• The email you used for your partner account, if you have one.
• The page address where the problem occurs.
• What you expected and what happened, in one or two sentences each.
• The date and time if it was a one-off, with your time zone.

Add: the game's slug or title, the browser and device, whether it works on playkovo.com directly, and what the browser console says. A screenshot of the console is better than a description. Before writing, run through five problems and their fixes, since the answer is often in your Content-Security-Policy or in a stripped attribute.

Subject: Embed blank on example.com/games/rainbow-run
Domain: example.com
Page: https://example.com/games/rainbow-run
Game: rainbow-run
Browser: Chrome on Android
Console: [paste the first error line]
Works on playkovo.com directly: yes

Add: the registered domain, the date of your own test launch, whether you accepted cookies on your site when you launched, and whether the iframe has any referrerpolicy attribute. The docs list these checks, and a message that already answers them saves a round trip. Remember that numbers are estimates and exclude visitors who decline cookies; see the dashboard post before asking why they differ from your own analytics.

Add: the domain, the contact email, the problem in a sentence, and any error text. Never send a password. The team does not need it and you should not share it in a message.

Describe the need, not just the solution. "I run a site for ages 6 to 9 and need a way to filter out shooting games" gives more to work with than "add a kids filter". Say how many games you embed and how you fetch them (copy-paste or feed). Requests are not promises, so write them as suggestions.

Quote the section number and the sentence you are unsure about, then describe your planned use. "Section 7 forbids rehosting images. I plan to cache thumbnails on my CDN to list the games I embed. Is that allowed?" is a message that can be answered with a yes or no. Keep the reply, since it records what you were told. The wording of the Partner Terms remains the authority.

Include the slug, what you saw (text, image or behaviour), and why it is a problem for your audience. If you have already removed it from your site, say so. This helps even when the problem is not a legal complaint, as the catalog improves from such reports. For real intellectual property complaints, use the route described in the terms.

• Passwords, keys and personal data about your visitors. The terms say not to pass visitor personal data to PlayKovo.
• Long screen recordings when a single screenshot shows it.
• Several unrelated questions in one message. One topic per email gets cleaner answers.

The partner pages do not promise a response time for general questions, so avoid planning a launch around an unanswered email. The takedown process has its own deadline in the terms (three business days for a valid request), but everything else is best effort. Write early, keep your message short and complete, and follow up once if you hear nothing.

Before writing, the catalog documentation answers many questions directly.