Skip to main content
DoubleData supplies the participation notice. You control its layout and explain any benefit offered by your app.

​
Ethical participation

Make sharing an informed, voluntary choice. Explain the benefit and resource costs before asking: third-party requests use the person’s public IP, bandwidth, battery, and power, and may affect connection performance or incur network charges. Show the complete DoubleData notice with equally clear Enable sharing and Decline actions. Dismissal is a decline. Keep unrelated app features available after refusal, and never enable sharing silently or hide withdrawal controls.
  1. The person opens sharing options in your app.
  2. Your built-in or custom presenter shows the purpose, full text, operator, contact, and privacy link.
  3. Explicit acceptance permits a session to start. Decline or cancellation leaves sharing off.
Requests then run automatically without individual prompts. The SDK records the notice version and content hash with consent; these are receipt metadata, not screen copy.

​
Monetization and rewards

You can present an optional app benefit alongside participation. State what the person receives, how it is earned, and any limits before they choose. Keep benefit messaging separate from the supplied notice and avoid guaranteed-income claims. Use SDK connection status and traffic counters to show sharing activity. These counters do not calculate earnings or establish a payout balance. Keep reward balances and payment decisions in your backend, using confirmed settlement records and the terms of your integration.

​
Pause and withdraw

Keep sharing status, Pause, and Withdraw consent accessible. Pause stops traffic; resuming requires current consent and remaining quota. Withdrawal invalidates permission immediately, stops active sharing, and blocks reconnection until a new acceptance. Close the client when its owner exits and await cleanup off the UI thread before replacing it. Current notice · Privacy · Configuration.