Skip to content
Legal

Privacy notice

What we collect, why we have it, and how long we keep it — covering both the businesses we work with and the end users who complete offers on a publisher's property.

Drafted 2 October 2026.

1. Who is responsible for what

For business contacts — the people who apply, sign in and run campaigns or placements — OpusWall decides why and how the data is processed.

For a publisher's end users, the publisher holds the account and the identity. We receive an opaque identifier and technical details about the request, and we use them only to attribute conversions, to pay for them and to check them for fraud. We never receive a user's name, e-mail address or payment details from a publisher, and publishers are contractually required not to send them.

2. Data about business contacts

We use it to assess applications, to operate accounts, to answer questions and to keep the platform from being abused. The lawful basis is the performance of a contract, or our legitimate interest in running the service and defending it against fraud.

  • Application details: company, contact name, e-mail address, country, website, and the answers about traffic or product given on the form.
  • Account details: name, e-mail address, role, organization and the timestamp of the last session.
  • Correspondence: messages sent through the contact form or by e-mail, and our replies.
  • Technical details of a submission: the browser user agent, a one-way digest of the IP address, and any campaign parameters in the link that brought you here.

3. Data about a publisher's end users

This exists to attribute a completed goal to the right publisher and to pay for it, and to detect automated or duplicated completions and connections that hide their location. Raw IP addresses are not stored: they are reduced to an irreversible digest used for rate limiting and fraud checks. A completion that may repeat another user's completion of the same offer from the same device or network is held for a person at OpusWall to review; a time zone that disagrees with the connection is only noted. Neither decides anything on its own, and what they found is seen only by OpusWall's staff — not by the advertiser, not by the publisher.

We do not build advertising profiles, we do not sell data, and we do not use this information to target anyone with advertising elsewhere.

  • The opaque user identifier the publisher sends us, and any pass-through values it attaches to it.
  • Which offers were opened, when, and which placement they were opened from.
  • Technical details of the request: user agent, approximate country, device type and a one-way digest of the IP address.
  • When an offer is started: a random identifier the wall keeps in the browser's local storage, kept in our database only as a one-way digest, and the time zone the browser reports, compared with the time zone of the place the IP address is located in. Only whether the two disagree is kept, and the two zones only when they do.
  • Conversions attributed to those clicks, with their amounts in cents.

4. Who else sees it

When a user opens an offer, the advertiser receives our click identifier and the parameters their tracking link asks for to run their own attribution — which can include the opaque identifier the publisher gave the user, the publisher's own tracking values, the device type and, when it is known, the country. They do not receive a name, an e-mail address or anything else that identifies the person.

When a conversion is confirmed, the publisher receives the details of that conversion, including the identifier they themselves supplied.

Some offers on the offerwall come from partner offerwalls we work with — today Monlix (monlix.com). To list them, our server asks the partner which of its offers are available to the user, and sends it the user's IP address, the browser's user agent and a pseudonymous identifier: a random code, or one derived with a secret key, that is never the identifier the publisher gave the user and cannot be traced back to it without our key. When the user opens one of those offers, their browser goes on to the partner's site, which receives what any website receives — the IP address, the user agent and the browser's language — and the same pseudonymous identifier, with which the partner later tells us that a step was completed. Offer images are loaded from the partner's own image server, which learns that the offer was shown. The partner never receives the user's name, e-mail address, the publisher's identifier for the user or anything that signs the wall's address, and what it does with the data it receives is governed by its own privacy notice.

Beyond that, data is shared only with the suppliers that run the platform for us — hosting, database and e-mail delivery — and only to the extent they need it. They act on our instructions.

5. How long we keep it

How long something is kept follows from why we hold it, so there is no single expiry date across the platform. In outline:

  • Applications and the decisions on them: kept while the relationship lasts, and afterwards for as long as we may need to explain a decision.
  • Accounts: for the life of the organization.
  • Clicks and conversions: kept as financial records for as long as the money they represent may be questioned.
  • The device identifier's digest and the time-zone comparison recorded when an offer is started: 455 days — the 90 days a later completion is compared against, plus the longest time limit an offer's step can be given — then deleted automatically. What the duplicate check found on a conversion is kept with that conversion.
  • Contact messages: kept while the question is open and for a reasonable period afterwards.
  • Rate-limiting digests: pruned automatically after a short window.
  • Postback logs: an advertiser's postbacks for 90 days; test notices to a publisher for 30 days; real notices to a publisher for as long as the conversion they belong to.

6. Your rights

Depending on where you live, you may have the right to ask what we hold about you, to have it corrected, to have it deleted, to restrict or object to how we use it, and to receive a copy.

An end user should start with the publisher whose site or app they used, because the publisher holds the account that connects an identifier to a person. If something still needs resolving on our side, write to us with the site and the approximate date and we will find it.

7. Where the data lives

The platform database is hosted in the European Union. Where a supplier processes data outside it, that transfer is covered by the safeguards the law requires.

8. Contacting us

Privacy questions and requests go to our legal address, listed on the contact page. The identity of the operating company and its data protection representative are to be completed before launch.

Questions about this document: legal@opuswall.net