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 Document

This document 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 a device
• Guarantee that offline data is preserved indefinitely
• Store local data once a project is completed

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

3. FairConsent Does NOT Upload Consents Automatically

FairConsent does not:

• Upload consents in the background without user action
• Upload consents automatically when internet becomes available
• 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
• Restore consents cleared when a project is completed
• Reopen closed projects to retrieve missing data

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 unuploaded consents
• Allow collectors to access platform data
• Allow users to perform actions outside their assigned role
• 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
• Allow cross-organization visibility
• Merge or transfer consents between organizations
• 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
• Decide when projects should be closed
• Validate operational correctness
• 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
• Protect against incorrect usage
• 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 Documents

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