FairConsent User Experience Overview

Audience

Organization administrators, consent managers, project managers, consent collectors, and compliance teams.

Applies to

FairConsent Mobile App and Web Platform.

1. Purpose of This Document

This document provides a high-level overview of how FairConsent is experienced in real usage.

It focuses on:

• What users see
• What users do
• How the system responds
• What behaviors are intentional and enforced

This document is intended as a starting point for clients and teams before using FairConsent in real projects.

It is not a technical specification.

2. Who Uses FairConsent

FairConsent supports two primary user experiences:

Consent Collectors (Mobile App)

People who collect consent in the field, such as:

• Photographers and videographers
• NGO or humanitarian field staff
• Project-based contractors or freelancers

They primarily interact with the mobile app.

Organization Admins & Consent Managers (Web Platform)

People responsible for:

• Managing consent terms
• Reviewing collected consents
• Managing users and access
• Overseeing compliance and visibility

They primarily interact with the web platform.

3. Consent Collection Experience (Mobile App)

Starting a Project

Consent collectors:

• Open the FairConsent mobile app
• Start a new consent collection project
• Enter basic project and collector information
• May associate the project with an organization if applicable

The app is designed to be:

• Simple
• Fast
• Focused on human interaction, not configuration

Recording Consents

During a project, the collector:

• Records consent giver information
• Presents consent terms (text, visual, or audio)
• Captures consent approval (signature, photo, or audio)
• Optionally records consent on behalf of a child or group member
• Can review the generated consent document after each recording

Each consent is explicitly linked to:

• A specific project
• A specific organization (if applicable)

Project Overview Screen

Throughout the project, the collector can see:

• Project details
• Collector information
• Organization information (if applicable)
• Number of recorded consents
• Upload status

After each consent, the collector returns to this screen.

Offline Usage

FairConsent supports working offline:

• Consents can be recorded without internet access
• Data is stored locally on the device
• The app clearly indicates offline status

Offline mode supports continuity — it does not change data rules.

Uploading and Completing a Project

At any time, the collector may:

• Upload recorded consents
• Continue collecting additional consents

When the collector finishes:

• They may complete (close) the project
• The app shows clear warnings before completion
• Completion is treated as a deliberate, final action

Uploading and completing a project are separate steps.

4. Platform Experience (Web Platform)

Platform Access

Admins and consent managers use the platform to:

• View uploaded projects and consents
• Review consent status
• Manage consent terms
• Manage users and access

The platform prioritizes:

• Visibility
• Oversight
• Clear status indicators

Platform Visibility

On the platform:

• Only uploaded consents are visible
• Consent counts reflect uploaded data only
• Closed projects are clearly identified
• Visibility is restricted by role and organization

The platform reflects finalized data — not in-progress device data.

5. Recovery (Limited and Controlled)

After a project is completed:

• A limited recovery mechanism may be available for users who belong to an organization with an active FairConsent subscription
• Recovery is time-limited, encrypted, and requires admin approval

Recovery:

• Does not upload consents
• Does not change platform visibility rules

For details, see Completing a Project – Read This Carefully.

6. How FairConsent Is Designed to Work

FairConsent is designed to support real-world consent collection while avoiding hidden behavior.

Key design choices include:

• Designed for field conditions

  The app works in real environments, including limited connectivity.

• Clear actions with clear outcomes

  Important actions always have predictable results.

• Protecting collected data

  Some actions are intentionally final to avoid mistakes or unclear states.

• Warnings before important steps

  Users are clearly warned before actions that may affect data.

• Strict separation between organizations

  Data collected for one organization is never visible to another.

7. Important Things to Understand Early

Some behaviors are intentional:

• Offline data is not visible until uploaded
• Completing a project has consequences
• Recovery is limited and not guaranteed
• Roles and organization boundaries are enforced

These are design choices, not system errors.

8. What This Means for You

For field teams

• Follow the defined consent flow
• Upload consents regularly
• Be careful when completing projects

For admins and managers

• Understand visibility rules
• Set expectations before deployment
• Train collectors on uploads and completion

For organizations

• FairConsent prioritizes clarity, accountability, and compliance
• User actions are explicit and traceable

9. Related Documents

For deeper understanding, refer to:

• Consent Collection – Main App Flow
• Uploading Consents & Platform Visibility
• Offline Mode – Limitations & Risks
• Completing a Project – Read This Carefully
• User Roles Explained
• Organization Separation & Data Boundaries
• What FairConsent Does NOT Do

Final Note

FairConsent is designed to make consent clear, intentional, and traceable.

This overview exists to ensure all stakeholders start from the same understanding before using the platform in real-world scenarios.