HTML5 game publishing

A Quarterly Compliance Audit for Your Games Section

Five blocks to check every three months: embeds, feed use, wording, the site around the games and your account, drawn from the Partner Terms.

PlayKovo Team3 min read
Games currently available on PlayKovo. Open a title to see its current listing.

You agreed to the Partner Terms once, when you registered a website, copied an embed code, used the feeds or opened the dashboard. Sites change after that: new pages, a new theme, a new plugin, a different editor. This post turns the terms into a checklist you can run every three months, so that a games section that was fine at launch is still fine a year later.

Why an audit helps

Most breaches of the terms are not deliberate. They come from a new plugin that strips an attribute, an editor who adds "our games" to a page, or an old feed script that nobody remembers. The terms allow PlayKovo to remove games, disable embeds for a domain or remove a site from the program at any time. A short audit costs an hour and lets you fix things before anyone else has to point them out.

Block 1: the embeds

  1. Open five game pages, on desktop and on a phone. Do the games load and play?
  2. View the page source after load. Is the src still the /embed/<slug> address as copied?
  3. Is the allow value complete? See the allow attribute.
  4. Is there any referrerpolicy="no-referrer" on the frame, or a site-wide policy header that does the same? See the referrer post.
  5. Is there any element placed over a game, such as a banner, a floating button or an invisible link?

Block 2: the feed

  1. When did your last successful sync run? Does it fetch no more often than every five minutes?
  2. Do any games on your site no longer appear in the feed? The terms say to review the feed regularly and remove games that no longer appear.
  3. Do stored images and descriptions belong only to games you embed? See using thumbnails and cover images.
  4. Are cached copies refreshed?

Block 3: what the text says

  1. Search your site for "our games", "we made", "created by us", "developed by" and similar phrases next to the games.
  2. Check page titles, meta descriptions, newsletters, social posts and any app store text.
  3. Check that no game appears in another portal, marketplace, contest or catalog under your name.
  4. Check credits and developer names where the catalog shows them.

The wording rules are in describing games without claiming them and using the PlayKovo name and logo.

Block 4: the site around the games

  1. Is there a privacy policy that mentions the games and links to PlayKovo's policy? See cookie notices and a privacy policy.
  2. Is the consent banner working as the law in your region requires?
  3. Does the site contain or promote anything the terms rule out, such as illegal content, pirated material, malware, adult sexual content, hate speech, harassment or content that exploits minors? The terms list these as reasons you may not use the catalog.
  4. If your audience is young, have you reviewed your responsibilities? See children and partners.
  5. Do you offer rewards or prizes for launching games? You must not.

Block 5: your account

  1. Is the contact email current and read by someone?
  2. Are all registered websites ones you still own or operate?
  3. Are there websites you stopped using that still have embeds?
  4. Does anyone besides you have access to the dashboard login, and should they?

Keep a record

A simple table with the date, what you checked and what you changed is enough. If you ever receive a question from PlayKovo, you will be able to show that you review regularly. It also helps a colleague who takes over the site.

When you find a problem

Fix it first, then, if it was a breach of the terms and may have been visible to others, consider telling PlayKovo at [email protected]. If you are unsure whether something is allowed, the terms themselves invite you to ask before you publish. The full text is in the Partner Terms, and our plain-language summary is in the Partner Terms in plain language.

We use optional cookies for site analytics and site advertising. You can change your choice later. Privacy policy.