Completing a Project – Read This Carefully

Audience

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

Applies to

FairConsent Mobile App.

1. Purpose of This Document

This document explains what completing a project means in FairConsent and why it is a critical action.

It exists to ensure that users clearly understand:

• What happens to consent data
• What is final and what is not
• When recovery is possible — and when it is not

Completing a project should always be a deliberate decision.

2. What “Completing a Project” Means

When a project is completed in the FairConsent mobile app:

• Consent collection for that project stops
• The project is marked as closed
• Active consent data is removed from the device
• The project can no longer be edited or extended

Completing a project is not the same as uploading consents.

3. What the App Shows Before Completion

Before a project can be completed, the app clearly shows:

• The number of recorded consents
• Whether some consents have not been uploaded
• A warning that completing the project may affect local data

The user must explicitly confirm their decision to proceed.

These warnings are intentional and cannot be skipped.

4. What Happens After Completion

After a project is completed:

• Uploaded consents remain available in the platform
• Unuploaded consents are no longer active on the device

At this point, the outcome depends on whether the user belongs to an organization with an active FairConsent subscription.

5. Project Recovery

(Available for 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 via the platform.

Important points:

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

If recovery is approved:

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

If recovery is rejected or the 7-day period expires:

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

This mechanism is designed to prevent accidental data loss, while preserving accountability and compliance.

6. 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 local consent data
• Unuploaded consents cannot be restored

This behavior is intentional and consistent.

7. What Completing a Project Does NOT Do

Completing a project does not:

• Automatically upload missing consents
• Guarantee that data can be recovered
• Make unuploaded consents visible in the platform
• Allow admins to restore data without approval
• Override upload or visibility rules

Uploading remains the only way to make consents available in the platform.

8. Best Practices Before Completing a Project

Before completing a project, it is strongly recommended to:

• Upload all required consents
• Review the project overview carefully
• Confirm that the platform shows the expected consent count
• Treat recovery as an exception, not a workflow step

Organizations should ensure that collectors are trained on these steps.

9. Why FairConsent Works This Way

This design ensures:

• Clear responsibility for user actions
• Predictable and auditable outcomes
• Protection against silent data loss
• Alignment with data-protection principles

FairConsent prioritizes clarity and accountability over hidden automation.

10. Related Documents

For full context, also review:

• Consent Collection – Main App Flow
• Uploading Consents & Platform Visibility
• Offline Mode – Limitations & Risks
• What FairConsent Does NOT Do
• User Roles Explained

Final Note

Completing a project is meant to be a final step, not a routine action.

Understanding its consequences — and the limits of recovery — is essential for correct and compliant use of FairConsent.