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

Completing a Project – Read This Carefully

Audience

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


Applies to

FairConsent Platform and Mobile App.

1. Purpose of  This Article

This article 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

Completing a project should always be a deliberate decision.

2. What “Completing a Project” Means

When a project is completed in the FairConsent Platform or app:

  • Consent collection for that project stops
  • The project is marked as completed
  • Any active consent data not yet uploaded will be removed from the app

Completing a project is not the same as uploading consents.

3. What the platform shows before completion

  • Ensure that all consent collectors have uploaded every consent they collected, and confirm this before completing the project by marking I confirm that all consent collectors have uploaded the required consents

  • Uploaded consents will remain safe in the platform.

4. What Happens After Completion

After a project is completed:

  • Uploaded consents remain available in the platform
  • Non-uploaded consents are no longer active on the app

5. Individual (Non-Organization) Usage

For users who are not part of an organization:

  • Completing a project permanently removes local consent data
  • Non-uploaded 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
  • 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

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 Articles

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.



Need More Help?

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