Frequently Asked Questions

It’s a consent-first way to monetize your apps: your users choose to share their device’s unused internet connection in exchange for a benefit you define, and you get paid for every consenting active device.

Devices that opt in join a residential proxy network operated by ELEGANT NETWORKS PTE. LTD., the company that also operates anyip.io. Business customers route requests to public websites — product pages, prices, search results — through the internet connections and IP addresses of consenting devices. Requests run only when the device is idle so users are never interrupted, and the whole flow is built to meet GDPR and CCPA consent requirements.

Whether you offer a free, paid, or ad-supported app, you can decide when to integrate the anyIP SDK offer into your user flows to maximize revenue.

Here are three examples of how you can use anyIP SDK to optimize your revenue:

• Paid app: At the end of a paid app’s trial period, offer anyIP SDK to the user in exchange for a trial extension or access to a limited version of the paid app. This gives you more time to convert the user to payment — and generates additional revenue until they convert.
• Free, ad-supported app: Offer anyIP SDK to the user as an alternative to the ad-supported version. This can improve the user experience and retention while generating more revenue than the ad-supported version.
• Free app: Ask your users to support you by accepting the anyIP SDK offer.

The SDK ships disabled by default and renders its own consent screen — publishers can’t modify, skip, or restyle it. Users see a plain-language disclosure of what sharing means, with accept and decline given equal visual weight.

Only after an explicit accept does the device join the network, and every opt-in and opt-out is recorded as a signed consent receipt. Users can withdraw at any time from the SDK settings, by uninstalling the app, or via our web opt-out page — and declining never degrades your app.

It is an additional revenue channel that can be implemented in parallel to your existing monetization in order to maximize revenue. In some cases, anyIP SDK is more profitable than standard premium (license or subscription) or free (ad-supported) revenue models.

It improves the user experience for your app. Offering a few premium features for free or removing ads means happier users, more organic downloads and better reviews.

It supports valuable business use cases by helping companies fight internet fraud, consumers find better prices online, and universities and researchers access high-quality data.

We hate that answer too, but: it depends. On what? Mostly on your user base of active users, the quality of their internet connection, and their geographic location. We have a lot of experience with this, so we can estimate how much you can earn with anyIP SDK. Contact one of our experts to get an estimate.

Want a quick ballpark? Try the calculator:

Customer requests fetch pages from large public websites — including e-commerce, travel, and consumer-brand sites — to keep business datasets up to date.

Since we create the original requests to specific websites, we know which URLs are visited at all times. As an additional layer of security, we use leading third-party web-filtering software to ensure that only allowed sites are indexed.

We receive the same web content that a regular user would see when visiting a webpage from their phone. For example:

• The average review score of a product on an e-commerce website
• The price of a London to New York flight ticket on an airline site
• The text of an ad on a social network
• Search results of a specific query (e.g. “best pizza in town”)

We never access your app’s data or your users’ accounts, files, or browsing. To operate the network we process only what’s needed to route traffic and prove consent: the device’s IP address, a pseudonymous device identifier, and the signed consent receipt. We don’t collect names, emails, contacts, messages, or browsing history.

No.

No. Customers send requests to our secure gateway, which routes them through a consenting user’s connection to the public website and returns the page content. Customers receive the web content and the country of the exit connection — never your user’s identity, device details, or any personal data. Customers agree to terms that restrict usage to publicly available web data.

We welcome new partners, and the process is quick and easy. Book a meeting with our partnership team.

Eligible partners operate apps distributed through the official app stores and channels of our supported platforms: the Apple App Store, Google Play, and trusted Windows and macOS desktop distribution.

You are always welcome to contact our team with any questions at contact@anyip-sdk.com

Your earnings are based on the number of daily active users that have opted in to anyIP SDK.

Want a quick ballpark? Try the calculator:

• If a device has our SDK installed, holds a valid opt-in consent, and is online, we count it as ‘active’ (whether or not we actually sent traffic through it).
• At the end of each day, we have the total number of unique active devices.
• We pay for every unique device, every day — so at the end of the month we add up the daily totals.
• We multiply that total by your rate.

You can see your earnings at any time on the anyIP SDK control panel. For any questions, you can also contact your account manager.

We support payment by wire transfer, Wise, Payoneer, PayPal, and cryptocurrency — the choice is yours. Payment is made against a valid invoice within the first five days of the month.

Our customers — banks, universities, e-commerce companies, and brands you know — buy access to the network through anyip.io, our residential proxy platform. They use it to download publicly available web data: web statistics, price comparisons, ad verification, and other verified business processes.

In general, companies use publicly available information (for example, product prices) for detailed research and financial analyses. But in many cases, when companies use their own IP address to browse the internet, they can get inaccurate data. So getting the web page from a user’s IP address helps companies see the web as regular users see it — which ensures complete and accurate data.

Here are some examples of when companies get more accurate information from websites by using different IP addresses:

• To protect their brand: Are sites selling fake versions of my product?
• To protect their users: Are advertisers showing ads for products I don’t allow (for example, firearms)?
• To offer the best prices: What are the real prices?

We help them get accurate information, which helps companies expand their databases and improve their products, services, and pricing.

Currently you can use anyIP SDK to monetize apps that run on:

• Windows
• macOS
• Android
• iOS

We support native Android apps written in Java or Kotlin, as well as cross-platform development frameworks such as Flutter and Unity.

Implementation is fairly simple. Please contact us to receive the implementation guide for your app’s platform(s).

No. The internet connection may only be used when the device is not busy with other tasks. We carefully safeguard device resources and ensure that traffic uses only the device’s available resources, in a way that will not substantially affect the device’s operation.

No. Nothing is left on your user’s device.

We only download traffic that is equivalent to a few web pages per day. In any case, remember that any data access will take place only when the device is idle, so it will not slow the device down.

No, we do not use any device storage.

Very little. In fact, your user will never feel it running or experience any slowdown in their apps.

No. CPU is only used when we send traffic, which happens only when the device resources are available, so the user never feels it.

A few hours, or one day including testing.

No.

Yes, please. Tell us about significant updates — especially anything that changes how your app presents the anyIP SDK offer or the consent screen — so we can re-verify the integration.

No. We can work side by side with other SDKs (e.g. AdMob, ironSource, and others).

Around 8 MB.

Yes — consent is the core of the product design. Participation is based on explicit, informed, opt-in consent collected on an SDK-rendered consent screen, recorded with signed consent receipts, and revocable at any time. We are committed to meeting the requirements of the GDPR and the CCPA, including data minimization and giving data subjects real control over their choice.

Yes. We built it under the strictest security guidelines and monitor it constantly.