Getting started
User Consent

User Consent

You must obtain the user’s consent when implementing the Fleetshare SDK in your application. It’s essential to ensure that users are fully aware of and agree to share their bandwidth with EarnFM and third parties.

⚠️
Consent is not just a UI requirement — every consent decision must be recorded with EarnFM through the Consent API. Devices without a granted consent on record are not able to connect.

Importance of User Consent

  1. Legal Compliance: Obtaining consent helps ensure compliance with data protection regulations like GDPR and CCPA.
  2. Transparency: It promotes transparency in your application’s operations and builds trust with your users.
  3. Ethical Considerations: Respecting user choice aligns with ethical practices at EarnFM.
  4. Contractual Obligation: Your supplier agreement requires informed, explicit, opt-in consent from every end-user, with auditable records.

Implementing User Consent

When implementing user consent for the Fleetshare SDK, follow these practices:

Clear Communication

  • Clearly explain what bandwidth sharing entails and how it benefits the user (e.g., ad-free experience, free credits).
  • Use simple, non-technical language that all users can understand.
  • The prompt must be opt-in — sharing must never start before the user actively accepts.

Detailed Information

  • Offer a link to a more detailed explanation or FAQ about the bandwidth sharing process.
  • Include information about data usage, privacy considerations, and potential impacts on the user’s internet connection.

Easy Opt-out

  • Give users a simple way to turn sharing off later (e.g., a settings toggle).
  • When they opt out, record it by sending a revoke through the Consent API.

Default Consent Text

If you don’t want to write your own wording, the Consent API page contains a recommended default consent text you can use as-is (just fill in your app name).

Example Consent Flow

  1. Present the consent information when the user first launches the app or before activating the Fleetshare SDK.
  2. Record the user’s decision (accept → grant, decline → revoke) with the Consent API or the SDK’s storeConsent helper.
  3. If the user consents, start the SDK.
  4. If the user declines, do not start the SDK and potentially offer alternative features.
  5. If the user later opts out, stop the SDK and send a revoke.
PrerequisitesConsent API