Audience

Consent collectors, organization administrators, project managers, and compliance teams.

Applies to

FairConsent Mobile App and Web Platform.

1. Purpose of This Document

This document explains the relationship between:

• Recording consents on the device
• Uploading consents
• Visibility of consents in the web platform

It exists to clarify when consent data becomes visible to admins and to prevent misunderstandings about data availability.

Uploading consents and completing a project are not the same action.

2. Recording a Consent vs. Uploading a Consent

In FairConsent, these are two distinct steps.

Recording a Consent

When a consent is recorded:

• The consent is saved locally on the device
• A consent PDF is generated
• The consent appears in the project overview on the device

At this stage:

• The consent is not visible in the web platform
• Admins cannot access or review it

Uploading a Consent

Uploading is a separate, explicit action.

When consents are uploaded:

• Data is transferred from the device to the platform
• Consents become visible to organization admins
• Uploaded consents are preserved even if the project is later completed

Uploading does not:

• Complete the project
• Remove local data from the device

3. When Consents Become Visible in the Platform

From the platform perspective:

• Only uploaded consents are visible
• Consent counts reflect uploaded data only
• Offline or locally stored consents are invisible to admins

If a consent has not been uploaded:

• It does not exist in the platform
• It cannot be reviewed, exported, or integrated

4. Uploading During a Project

Consent collectors can upload consents:

• After each recorded consent
• Multiple times during a project
• Or once at the end of the project

Uploading can be done:

• While online
• Without completing or closing the project

This allows flexibility while keeping visibility under control.

5. Uploading vs. Completing a Project

These actions serve different purposes:

If consents are not uploaded before completing a project:

• They are removed from the device
• They cannot be recovered
• They never become visible in the platform

The app provides a warning before this happens.

6. Common Misunderstandings

This document exists to prevent assumptions such as:

• “Recording a consent automatically uploads it”
• “Admins can see consents immediately”
• “Closing a project uploads everything”
• “Offline consents appear later automatically”

These assumptions are incorrect.

7. Recommended Best Practices

To ensure correct visibility and data safety:

• Upload consents regularly during a project
• Upload all required consents before completing a project
• Check the project overview for upload status
• Train field teams on the difference between recording and uploading
• Do not rely on project completion to upload data

8. What This Means for Organizations

For organizations using FairConsent:

• Platform visibility depends on collector actions
• Uploaded data is the system of record
• Operational clarity is essential for compliance

Clear processes around uploading reduce risk and confusion.

9. Related Documents

For full context, also review:

• FairConsent – How It Works & What You Should Know
• Consent Collection – Main App Flow
• Offline Mode – Limitations & Risks
• Completing a Project – Warnings & Consequences

Final Note

Uploading consents is the only way to make data available in the FairConsent platform.

Understanding this distinction is critical for correct usage and compliance.