Frequently asked questions

Short answers for developers evaluating GetPassive.

1. What does GetPassive do?

It helps approved developers earn passive revenue from unused bandwidth on devices where their app is installed.

2. Do I need to build a new user interface?

No. The standard model is a clear clause in your existing Terms and Conditions. The SDK does not render any UI of its own.

3. What do developers keep?

Developers receive 80% of net revenue attributed to their approved app fleet.

4. When are payouts sent?

Payouts are processed monthly through Stripe Connect after earnings are finalized.

5. Are exact earnings guaranteed?

No. Earnings depend on uptime, region mix, valid activity, device availability, and demand.

6. What runtimes does the SDK support?

Node.js 18 or newer today. The SDK ships as an ES module package, @getpassive/sdk, on the GetPassive private npm registry. Browser and React Native SDKs are planned for future versions.

7. Can I test before going live?

Yes. New developer API keys start in test mode. Live promotion is admin-only after review.

8. What data is collected?

Bandwidth activity and operational signals needed to run the SDK. No personal data, app content, or tracking profile is collected.

9. What happens if a payout fails?

The console shows the failed status and the action needed, usually updating Stripe Connect or bank details.

10. Who should integrate GetPassive?

Developers with approved apps that run on devices with stable internet access and enough uptime to generate passive bandwidth revenue.

Last updated June 11, 2026