Consent Collection – Main App Flow

chaAudience

Consent collectors, project managers, and organization administrators.

Applies to

FairConsent Mobile App.

1. Purpose of This Document

This document explains the main consent collection flow in the FairConsent mobile app.

It describes:

• The sequence of actions taken by a consent collector
• What the app displays at each stage
• How data moves from local storage to the platform
• Where critical decisions occur

This document reflects actual product behavior and focuses only on the primary flow.

2. Core Principle: Project-Based Consent Collection

All consent collection in FairConsent happens within a project.

A project acts as:

• A container for one or more recorded consents
• The unit for uploading, exporting, and completing work
• The main reference point throughout the collection process

The Project Overview screen is the central screen of the app and is revisited repeatedly during the flow.

3. Starting the Flow

The main flow begins when the user taps:

• “Record a new consent”, or
• “Record a consent for [Organization Name]” (when a valid B2B subscription is available)

This action always leads to creating or entering a project.

4. Step 1 – Enter Project and Collector Information

At the start of a project, the consent collector provides:

• Project details
• Consent collector information
• Responsible organization (optional, depending on setup)

Once this information is submitted:

• The project is created
• The user is taken to the Project Overview screen

This information remains visible throughout the project lifecycle.

5. Step 2 – Project Overview Screen (Main Hub)

The Project Overview screen displays:

• Project name and location
• Consent collector details
• Responsible organization (if provided)
• Number of consents recorded

From this screen, the collector can:

• Record a new consent
• View recorded consents
• Upload recorded consents
• Export and share files (Individuals use case)
• Complete the project

After every recorded consent, the user returns to this screen.

6. Step 3 – Recording a Consent

When the collector taps “Record new consent”, the following sequence takes place.

6.1 Consent Giver Information

The collector enters information about the consent giver.

6.2 Presenting the Consent

The consent is presented to the consent giver using one of the supported formats:

• Text
• Visual
• Audio

The available format depends on the consent configuration and context.

6.3 Consent Approval

The consent giver approves the consent using one of the supported methods:

• Signature
• Photo
• Audio confirmation

This approval becomes part of the recorded consent.

6.4 Optional Scenarios

Depending on the situation, the collector may additionally:

• Record consent for a child
• Record consent for a group member
• Add a witness

These steps are optional and appear only when relevant.

6.5 Generated Consent PDF

After the consent is approved:

• A consent PDF is generated
• The collector can review the PDF immediately

The PDF includes:

• Consent terms
• Approval method
• Associated assets (such as images or audio)

7. Step 4 – Return to Project Overview

After a consent is recorded:

• The user is returned to the Project Overview screen
• The number of recorded consents is updated

From here, the collector may:

• Record another consent
• Upload recorded consents
• Export or share files
• Complete the project

This loop repeats until the collector finishes their work.

8. Step 5 – Uploading Recorded Consents

At any point during the project, the collector can choose to upload recorded consents.

Uploading:

• Transfers locally stored consent data to the platform
• Makes consents available in the web portal
• Does not close the project

Uploading can occur:

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

9. Step 6 – Exporting and Sharing Files (individuals)

In Individuals usage, the collector may:

• Export and share consent files
• Including associated assets such as approval images or audio files

This is typically done before completing the project.

10. Step 7 – Completing the Project (Critical Step)

When the collector finishes the project, they tap “Complete project”.

Before completion:

• A warning message is displayed
• The total number of recorded consents is shown
• The app indicates whether there are consents that have not yet been uploaded
• The collector must explicitly confirm they are ready to proceed

Only after confirmation can the project be completed.

Completing a project:

• Removes consent data from the device
• Keeps uploaded data safe in the platform
• Is treated as a final action

This behavior is intentional and explicit.

11. Key Characteristics of the Main Flow

• The Project Overview screen is the central hub
• Recording a consent always returns the user to the project
• Uploading and completing are separate actions
• Local data removal is explicit and confirmed
• The collector controls when each step occurs

12. What This Means for Users

For consent collectors

• Review the Project Overview before completing a project
• Upload consents before closing if platform access is required
• Understand that completing a project clears local data

For organizations

• Projects reflect deliberate user actions
• Uploaded data remains accessible in the platform
• Local device storage is temporary by design

Related Documents

• FairConsent – How It Works & What You Should Know
• FairConsent – User Experience Overview
• Offline Mode – Limitations & Risks
• Completing a Project – Warnings & Consequences

Final Note

The main flow in FairConsent is designed to be:

• Explicit
• Traceable
• Suitable for real-world field conditions

Understanding this flow is essential before using FairConsent in production.