Skip to content

Windows ads: requirements and risks ​

Read this before you ship a Windows app with dlserve ads. It covers what your app must have, where you can publish it and what can go wrong.

What your app must have ​

  • An ads on/off setting in your app, wired to the SDK's SetAdsEnabled call. See the SDK guide.
  • A way to tell users the app shows ads. For example, one line in your installer: "Your app is free because it shows a few ads as Windows notifications while it's open. You can turn them off in the app's settings." Check with your own legal adviser what you need.
  • A privacy policy that covers the ads. Start from the privacy policy template.
  • An Installed apps entry that points at your app's folder.
  • No administrator start. The SDK stays quiet when your app runs elevated.
  • Your own signature on dlserve.dll, if you sign your app. Sign it in the same step as your .exe.
  • The DLL untouched. Don't modify, rename or repackage it, and don't imitate its dialog.

Where you may ship ​

  • Your own website: yes.
  • Microsoft Store: not allowed. Don't ship a build that contains dlserve.dll there. Store-signed MSIX packages stay quiet as a safety net, but an EXE or MSI listed in the Store does not.
  • winget: not supported yet. Don't submit.
  • Steam and itch.io: their rules don't allow ads like these. dlserve doesn't block them for you, so don't ship ads there.
  • Epic Games Store: allowed with its Promotional Content declaration.

Store rules change. Check each store's current rules before you publish.

Security software ​

Ads shown outside an app's own window can be treated as potentially unwanted by some security software. Nobody can clear this in advance. If a product flags your installer or app, it can affect the reputation of your signing certificate too. If only dlserve.dll is blocked, your app keeps running without ads.

What dlserve does ​

  • Every ad is labelled Ad and carries your app's name and icon.
  • The browser opens only when someone clicks an ad.
  • Nothing runs after your app closes. The SDK adds no services, startup entries, scheduled tasks or tray icon.
  • There is a daily cap and at least 10 minutes between two ads.
  • Do Not Disturb is respected.
  • dlserve can pause ads for one placement (the Paused by dlserve badge), for one SDK version, or everywhere. It takes effect at each app's next check.

Children ​

Don't use dlserve in apps made for children. If you know a user is under 13, start the SDK with the childDirected option set to true for that user, or don't start it, and it stays off. See the SDK reference.

If a security product flags your app ​

Contact support with the product's name, the detection name, your app's version and the file.

What we don't promise ​

  • That any store, security product or regulator will accept your app.
  • Fill or revenue. Whether there is an ad for a person depends on where they are and what's available.
  • Legal advice. Where the SDK asks people before ads is how it behaves, not a legal opinion.

Related: Windows SDK guide, Privacy policy template, Windows app ads.