SafeWorld Ads

SafeWorld AdsSecurity

How we keep it safe.

SafeWorld moves money based on what games and websites tell it, so we don't take their word for anything. Here's what we check and how accounts are protected.

Signing in.

We don't use passwords at all, so there's none to steal or reuse.

  • You sign in with a code we email you.

    It's 6 digits, works once and expires after 10 minutes. We only store a hash of it, and we limit how often codes can be requested.

  • Passkeys for consoles

    Advertiser, publisher and staff consoles also need a passkey, every time you sign in.

  • Sessions expire

    After 7 days, or as soon as you sign out. The cookie can't be read by scripts.

  • Staff actions are logged.

    When one of us approves a campaign, changes a publisher's terms or releases a held reward, it's recorded with who did it and when.

Catching fake completions.

Every finished ad is checked against a fixed set of rules before the reward is released. Tick the boxes to see how it decides.

  • We look at how fast it was finished, how many came from the same person and how new the account is.
  • We also look at each site or game as a whole: sudden spikes, or lots of brand-new players at once.
  • One warning sign holds the reward for a person to review. Two block it.
  • New publishers have a daily cap until we have seen real traffic from them.

Someone just finished an ad. Tick what's true about it.

Paid

Nothing looks off, so the reward goes through.

Keeping the money straight.

Rewards and publisher earnings are kept as lists of entries that are only ever added to. A balance is the total of its entries, so nobody can quietly edit a number.

  • If a request is sent twice by mistake, it still only pays once.
  • An advertiser's money is set aside when an ad starts and spent only when the reward is confirmed.
  • Reversing a reward adds a new entry. The history stays as it was.
  • We can switch off new activity across the whole platform straight away if something goes wrong.

We don't trust the browser.

Anything that runs on someone's device can be changed by them. So the decisions are made on our servers.

  • Rewarded sessions are started by a publisher's server with a secret key. Public keys are refused.
  • Server keys are shown once and stored as hashes. Callback secrets are encrypted.
  • Callbacks are signed with HMAC-SHA256 and a timestamp. We reject ones that arrive twice.
  • Every request is checked against the account it's acting for, so one advertiser can't read another's campaigns.

This website.

  • Nothing from other companies

    These pages don't load trackers, analytics, fonts or scripts from anyone else's servers.

  • Locked-down scripts

    The public pages will only run script and style files that come from this site. Anything injected is blocked by the browser.

  • Encrypted

    HTTPS only, and the pages refuse to load inside a frame on another site.

  • Less data to leak

    We store IP addresses and browser details as hashes, and a game's player IDs too.

Found a security problem?

Email security@safeworld.cc and tell us what you found and how to reproduce it. We read every report and we'll write back.

  • Please don't open, change or delete data that isn't yours.
  • Please don't run tests that slow things down for other people.
  • Give us a fair amount of time to fix it before you publish anything.
  • The details are also at /.well-known/security.txt.

Want to try it early?

Request access