Compliance & review policy
What GetPassive enforces around app reviews, restricted countries, and device qualification. Applies to every developer with an approved app.
Country restrictions
GetPassive does not operate in the following countries or territories. Any device located in one of these regions will not be counted, used, or monetized in any way — even if your app is installed there and the user has consented.
- Iran
- Lebanon
- Syria
- North Korea
- Cuba
- Palestine
- Sudan
- Crimea
- Luhansk People’s Republic and Donetsk People’s Republic
You do not need to block these countries inside your app. Our gateway enforces the restriction at the network layer.
When app changes require re-review
Every approved app must be submitted for re-review when certain changes happen. Use this table as the rule:
| Change you’re shipping | Re-review required? |
|---|---|
| SDK version upgrade only (no integration changes) | No — ship freely |
| Visual/design updates, copy, game flow, layout | No — ship freely |
| New features that don’t touch SDK or consent | No — ship freely |
| Changes to your consent screen content, layout, or wording | Yes |
| Moving the consent prompt to a different point in the app | Yes |
| Modifying the opt-out flow or removing the opt-out menu entry | Yes |
| Changing the value/incentive offered for opting in | Yes |
| Initialising the SDK in a new app flow or platform | Yes |
When re-review is needed, open your app in the developer dashboard and click Submit a new version. You can keep shipping your old approved version while the new one is under review — we won’t deactivate it.
Approved apps that ship a re-review-required change without being re-reviewed may have their SDK keys suspended.
Device qualifying thresholds
For a user’s device to count toward your earnings, it must clear several thresholds. These exist to protect end-user experience and to ensure only genuinely available devices contribute to earnings.
| Signal | Threshold |
|---|---|
| Battery level (mobile) | ≥ 25% — or any level if the device is on charge |
| Device on charger | Overrides battery threshold |
| CPU load (rolling 30s avg) | ≤ 60% — we back off above this |
| Network type | Wi-Fi or Ethernet (cellular not eligible) |
| Outbound bandwidth in use | ≤ 50% of measured upstream capacity |
| Minimum daily uptime (mobile) | 30 minutes online & eligible |
| Minimum daily uptime (desktop / TV / IoT) | 2 hours online & eligible |
| VPN/proxy detected | Not eligible while active |
| Datacentre IP detected | Not eligible |
Devices that briefly drop below a threshold remain registered — we just stop counting them as active for that period. Devices that fail thresholds chronically may be dropped from your active fleet.
Shared-device revenue split
If a single user device has two or more apps using GetPassive opted in on the same day, the active-day credit is split equally across the participating apps.
- Two apps from different developers on the same device: each counts as 0.5 active-days.
- Two apps from the same developer on the same device: counts as 1 active-day total (no double-counting).
This avoids inflating the global active-device count and keeps payouts fair to the underlying device population.
Last updated June 29, 2026