Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

What FairConsent Does NOT Do

Audience

Organization administrators, consent managers, consent collectors, and compliance teams.

Applies to

FairConsent Mobile App and Web Platform.

1. Purpose of This Article

This article explains the intentional limitations of FairConsent.

It exists to:

  • Prevent incorrect assumptions
  • Set clear expectations before deployment
  • Avoid misuse of the app and platform
  • Reduce operational and compliance risks

These limitations are by design. They are not missing features or bugs.

2. FairConsent Does NOT Automatically Back Up Data

  • FairConsent does not automatically back up consents recorded on the app
  • FairConsent does not guarantee that offline data is preserved indefinitely
  • FairConsent does not store local data once a project is completed]

Until consents are uploaded, they exist only on the app.

3. FairConsent Does NOT Upload Consents Automatically

  • FairConsent does not upload consents in the background without user action
  • FairConsent does not upload consents automatically when internet becomes available
  • FairConsent does not upload consents when a project is completed

Uploading consents is a manual, explicit action performed by the consent collector.

4. FairConsent Does NOT Recover Lost or Deleted Data

  • FairConsent does not recover consents lost due to device damage or loss
  • FairConsent does not restore consents cleared when a project is completed

If a consent was not uploaded before completion, it is permanently lost.

5. FairConsent Does NOT Bypass Roles or Permissions

  • FairConsent does not allow admins to see non-uploaded consents
  • FairConsent does not allow collectors to access platform data
  • FairConsent does not allow users to perform actions outside their assigned role
  • FairConsent does not grant special visibility “just in case”

Roles define capabilities, not exceptions.

6. FairConsent Does NOT Share Data Between Organizations

  • FairConsent does not share data across organizations
  • FairConsent does not allow cross-organization visibility
  • FairConsent does not merge or transfer consents between organizations
  • FairConsent does not provide “global admin” visibility

Each organization is strictly isolated.

7. FairConsent Does NOT Replace Organizational Processes

  • FairConsent does not replace internal training or field procedures
  • FairConsent does not decide when projects should be closed
  • FairConsent does not validate operational correctness
  • FairConsent does not guarantee compliance without proper usage

FairConsent is a tool that supports compliance it does not enforce it alone.

8. FairConsent Does NOT Eliminate User Responsibility

  • FairConsent does not make decisions on behalf of users
  • FairConsent does not protect against incorrect usage
  • FairConsent does not remove the need for clear instructions and training

Critical actions (uploading, completing projects) always require explicit user decisions.

9. Why These Limitations Exist

These limitations exist to ensure:

  • Clear accountability
  • Data integrity
  • Predictable behavior
  • Compliance with consent and data-protection principles

FairConsent prioritizes clarity and safety over hidden automation.

10. Related Articles 

For full context, also review:

  • FairConsent – How It Works & What You Should Know
  • Consent Collection – Main App Flow
  • Offline Mode – Limitations & Risks
  • Uploading Consents & Platform Visibility
  • Completing a Project – Read This Carefully
  • User Roles Explained
  • Organization Separation & Data Boundaries

Final Note

Understanding what FairConsent does not do is as important as understanding what it does.

This clarity protects:

  • Field teams
  • Organizations
  • Data subjects
  • Compliance obligations


Need More Help?

For any questions or support, reach out to us at customersupport@fairpicture.org