Does the Offerwall Track You? What Sharklio Collects

Does the offerwall track me? What data the Sharklio wall collects

The Sharklio offerwall records what it needs to show you offers, credit the ones you complete, and stop fraud: the user ID your site or app assigns you, your IP address and the approximate location and internet provider that come from it, device and browser details, a device identifier used for fraud prevention, and the offers you view, start and complete. It does not ask for your name, email address or other direct identifiers, and advertisers do not receive them from Sharklio. Everything in this article follows Sharklio’s privacy policy (last updated October 29, 2026), which is the binding version if the two ever differ.

Sharklio is a pay-per-result affiliate network. The offerwall is the page a website, app, game or community (the publisher) opens for you so you can earn its coins or points by completing offers. If you are new to offerwalls, Are offerwalls legit? explains the model first.

Who is responsible for your data

Two companies handle your data when you use a Sharklio wall, and each is responsible for its own part:

• The publisher runs the site or app you use. It is responsible for your account there, the rewards it offers, paying them, and its own privacy notice. That notice should tell you the offerwall is provided by Sharklio, and the publisher must get any consent your local law requires before your data reaches Sharklio.
• Sharklio (operated by Shark Earnings LLP) decides how offer activity is recorded, attributed and checked for fraud, so it is the controller for that processing.

This split matters when you have a question. Your coin balance and payouts belong to the publisher. How the wall recorded your clicks, and what data Sharklio holds about you, belongs to Sharklio.

You have no Sharklio account as an end user. Sharklio knows you only through the identifier the publisher puts in the wall link, which is why the privacy policy calls it a pseudonymous user identifier: on its own, it does not say who you are. Sharklio asks publishers not to send names, email addresses or other direct identifiers in it.

What the wall records, and why

Here is everything the privacy policy lists for end users, with the reason each item is there:

The legal bases the policy gives are legitimate interests for running the offerwall, recording clicks and completions and preventing fraud, plus obligations towards advertisers and offer partners for the fraud checks.

Fraud checks and the IP reputation check

Advertisers pay only for genuine results, so the wall has to tell real users apart from bots, farms and people hiding their location. The privacy policy describes these measures:

• An IP check. When you open the wall or start an offer, your IP address is checked to detect connections that hide where you really are, such as VPNs and proxies, because offers cannot be tracked reliably through them. The check uses an IP reputation service listed in the privacy policy. The policy keeps the provider’s name out of public view so it cannot be used to get around the check, and Sharklio gives it to you on request.
• A device identifier and device signals. The wall sets no cookies of its own. It keeps one random device identifier in your browser’s local storage and, when you start an offer, reads device signals such as browser and graphics characteristics and your time zone. These help recognise one person using several accounts. They are used only to prevent fraud, never for advertising or to follow you across other sites.
• A connection check in your browser. Before an offer opens, a fraud prevention provider’s script checks your connection in the browser. It receives your IP address, browser and device details and the wall’s page address, which includes the pseudonymous ID your publisher assigned. The policy lists this provider by category, and Sharklio gives the name on request.
• An ad blocker check. The wall sends one request to a Google ad server address to see whether an ad blocker would stop offers from being tracked. Google receives your IP address and browser details, but no identifier from Sharklio.
• Limits. How often each user can complete an offer, and how fast requests can arrive.
• Blocks for networks and accounts that have abused the service.
• Human review of missing reward reports, where staff may reverse completions or ban accounts.

These measures can mean an offer is not shown, a completion is rejected or reversed, or a network or account is blocked from offers. If the IP check flags your connection, offers stay hidden until you connect normally. VPN or proxy detected on an offerwall walks through what to do.

Who receives your data

Sharklio does not sell personal data. It shares end user data with these parties, each for a narrow reason:

The publisher gets the country, device type and IP address so it can credit you and check the completion for fraud. Advertisers confirm results from their own systems, and the pseudonymous ID they receive is enough to stop the same person from completing an offer twice without telling them which account on which site you use.

Once you open an offer, you are on the advertiser’s own site or app. Those pages set their own cookies under their own policies, and Sharklio’s policy does not cover them, so read their privacy notice before you share anything with them.

What the wall does not collect or do

• No name, email address or phone number. The wall has no field that asks for them, and Sharklio asks publishers not to send them.
• No GPS location. Location is approximate and comes from your IP address.
• No advertising identifier in the mobile SDKs. The iOS SDK documentation says the SDK does not track users across apps and does not use the advertising identifier, and its privacy manifest declares no tracking. The Android SDK documentation says the same for the advertising ID.
• No sale of personal data, and no sharing for cross-context behavioral advertising, as the policy uses those terms for US state privacy laws.
• No tracking across unrelated websites by Sharklio.

On iPhone, Apple’s If an app asks to track your activity page explains that App Tracking Transparency makes apps ask before tracking you across other companies’ apps and websites, and that if you choose Ask App Not to Track, the developer cannot access the advertising identifier (IDFA). Apple’s User Privacy and Data Use page for developers defines tracking as linking data from your app with other companies’ data for targeted advertising or advertising measurement, or sharing it with data brokers (checked on October 29, 2026). The Sharklio SDK does not ask for that permission, because it does not use the advertising identifier. The publisher’s app may still ask for its own reasons.

How long the data is kept

The privacy policy sets these periods for data that concerns end users:

When data is no longer needed, Sharklio deletes or anonymizes it. A legal obligation or an active dispute can keep the relevant records longer, until it ends.

Your rights and how to contact Sharklio

What you can ask for depends on where you live. The privacy policy covers three groups:

• EU, EEA and UK. If the GDPR or UK GDPR applies, you can access your data, have it corrected or erased, restrict processing, get it in a portable form, object to processing based on legitimate interests, withdraw consent, and not be subject to a decision based solely on automated processing that has legal or similarly significant effects. These rights come from Articles 15 to 22 of the GDPR on EUR-Lex. Sharklio answers within one month, and you can also complain to the supervisory authority where you live or work.
• US states. In California and states with comparable laws, you can ask to know the categories and specific pieces of personal information collected, the sources, the purposes, and who it is shared with, and ask for a copy, correction or deletion. You may use an authorized agent.
• Canada. Under PIPEDA and, where it applies, British Columbia’s Personal Information Protection Act, you can access your information, ask for corrections, and withdraw consent within legal and contractual limits.

For any of these, write to privacy@sharklio.com. Because Sharklio knows you only through the publisher’s identifier, include the name of the site or app and, if you can, your user ID there. Sharklio may ask you to confirm them, or to verify your identity. Questions about your balance or payouts go to the publisher.

For publishers: what to tell your users

If you run the wall on your site or app, your users will ask the questions above, and part of the answer is your job:

• Your privacy notice should say the offerwall is provided by Sharklio, and you must get any consent your users’ law requires before their data reaches it.
• Use a random or internal user ID in the wall link. The postback returns it with the country, device type and IP address of each completion, so store only the fields you need.
• Keep the wall away from anyone under 16. The privacy policy says it is not intended for them, and publishers must not show it to them.
• For apps, declare the data the SDK collects in App Store Connect and the Google Play Data safety form, as the SDK docs list it: user ID, device ID, approximate location, and the offers a user views, starts and completes.

Offerwall GDPR guide for publishers covers privacy notices, consent and deletion requests in depth, and How the Sharklio offerwall works shows where the user ID and postback fit.

Frequently asked questions