Offline Mode – Limitations & Risks

Audience

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

Applies to

FairConsent Mobile App.

1. Purpose of This Document

This document explains how offline mode works in FairConsent and the risks and limitations associated with it.

Offline mode exists to support field work in real conditions.

It is not a data backup mechanism.

Understanding these limitations is essential to avoid data loss.

2. What Offline Mode Does

When the device is offline:

• Consent collectors can continue recording consents
• Consents are stored locally on the device
• The app clearly indicates that it is offline
• No data is sent to the platform

Offline mode allows work to continue — it does not change data rules.

3. What Offline Mode Does NOT Do

Offline mode does not:

• Upload consents automatically
• Back up data to the platform
• Make consents visible to admins or managers
• Protect data from device loss or damage

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

4. Risks of Working Offline

Working offline carries inherent risks:

• Device loss or damage may result in permanent data loss
• Data stored locally is not visible or auditable
• Offline data cannot be reviewed by the organization
• Upload delays increase the risk of accidental loss

Offline mode should be treated as temporary, not a working state of record.

5. Offline Mode and Project Completion

Completing a project while consents are still offline has serious consequences:

• Unuploaded consents are removed from active use on the device
• Uploading after completion is not possible without recovery

What happens next depends on whether the user belongs to an organization with an active FairConsent subscription.

6. Limited Recovery After Completion

(Organizations with an Active Subscription Only)

For users who belong to an organization with an active FairConsent subscription:

• An encrypted copy of the project data remains on the device for up to 7 days
• During this period, the consent collector may request recovery
• An organization admin must explicitly approve or reject the recovery request

Important:

• Recovery is not automatic
• Recovery is time-limited
• Recovery is not guaranteed
• Recovery does not upload consents

If approved:

• The project is restored on the device
• The collector may upload the missing consents

If rejected or after 7 days:

• The encrypted data is permanently deleted
• Recovery is no longer possible

7. Individual (Non-Organization) Usage

For users who are not part of an organization with an active subscription:

• No recovery mechanism is available
• Completing a project permanently removes offline data
• Unuploaded consents cannot be restored

This behavior is intentional and consistent.

8. Key Rule to Remember

Uploading consents is the only way to make them safe and visible in the platform.

Offline mode is designed for continuity — not storage.

9. Best Practices When Working Offline

To reduce risk:

• Upload consents as soon as internet access is available
• Avoid completing projects while offline
• Monitor the number of unuploaded consents
• Train collectors on offline limitations

Organizations should plan workflows with offline risks in mind.

10. Related Documents

For full context, also review:

• Consent Collection – Main App Flow
• Uploading Consents & Platform Visibility
• Completing a Project – Read This Carefully
• What FairConsent Does NOT Do
• User Roles Explained

Final Note

Offline mode enables field work — but responsibility remains with the user.

Understanding its limits is essential for safe and compliant use of FairConsent.