FairConsent FAQ

Built for field reality. Trusted by Communications, Legal & IT.

FairConsent helps organizations collect and manage informed consent, online or offline, and connect it directly to the images and videos in their DAM.

No paperwork. No grey zones. Just clear, defensible rights for every visual you publish.

Basics

A field-ready consent app + web platform to collect informed consent (even offline), then store the signed PDF and mapped consent fields centrally, directly alongside your images and videos in your DAM.

Teams that publish people’s stories at scale: NGOs, INGOs, universities, CSR and brand teams, and production partners. If you need clear permissions, withdrawals, and audit trails attached to visuals, this is for you.

FairConsent isn’t just signatures, it’s informed consent. Use multilingual templates, add audio/visual explanations, handle minors and guardians, capture offline, and link signed PDFs + metadata straight to your DAM so rights actually govern usage, not just sit in folders.

Yes. Capture full consent — terms, signatures, photos, audio, witnesses — without connectivity. Data syncs automatically when you’re back online.

All of them. Use defaults or add your own text, audio, and visual explanations. Designed to ensure understanding across languages and literacy levels.

Guardian-led consent with child details. Record identity and relation, capture optional child assent, and keep everything in one signed PDF + metadata record.

Getting Started

Start a trial → download the app → create a project → collect a test consent. You’ll see the signed PDF and fields appear on the platform within minutes.

Invite by email and assign roles. Collectors focus on capture; managers control templates, exports, and integrations.

Use our starter templates or build your own. Add languages, audio/visual explanations, minors/guardian variants, and any fields you later map to your DAM.

Open project → explain → capture (photo/audio/signature) → add witnesses/guardian if needed → save → upload when online. Integrated DAMs automatically receive the signed PDF + consent fields.

Yes. Bulk-import legacy PDFs and tag them with identifiers, subject, status, expiry, and terms, so historic permissions become searchable and enforceable.

One click. Download zipped PDFs and a CSV/JSON of metadata, or share a read-only audit link per record.

Legal & Compliance

Yes, privacy by design. Clear purposes, explicit consent records, data-minimization options, subject-rights workflows, and documentation to support your DPIA.

Within the EU or Switzerland. Offline data lives on the device until uploaded; platform data is encrypted and access-controlled.

Yes. Standard DPA/SCCs, subprocessors list, and security documentation are available for procurement.

Mark a record as withdrawn → your DAM flags affected assets automatically (or you get a report for manual setups). Withdrawn assets become un-usable in searches and downloads. Non-integrated setups get clear reports/instructions. Rights respected end-to-end.

By storing context and proof: the signed PDF, consent terms version, language, audio/visual explanation, timestamps, collector identity, witnesses, and notes — all forming a defensible audit trail.

No. We provide the tooling and documentation; your legal team defines policy and compliance choices.

Technical

Five are live (ResourceSpace, Frontify, Canto, Orange Logic, AWS S3), more coming soon. We connect FairConsent records to leading DAMs so the signed PDF and mapped fields (status, identifier, terms, expiry, minor/guardian, audit URL) sit with the asset. Don’t see yours? Request an integration.

The signed PDF and all mapped fields. Fields drive filters/badges (e.g., “withdrawn,” “expires soon”) and link back to the source record for one-click audits.

Near real-time via webhooks. Most updates (new consents, edits, withdrawals) usually propagate within minutes. Batch options are available if your DAM prefers scheduled syncs.

Yes. Pull records, push updates, subscribe to events (created/updated/withdrawn). Sandbox keys available for testing before going live.

Encryption in transit and at rest, scoped API tokens, role-based access, full audit logging. Regular backups and tested restore procedures support your RPO/RTO needs.

Absolutely. Add custom fields and map them to your DAM’s custom metadata so governance matches your taxonomy, not the other way around.

Available on request for enterprise plans. SAML/OIDC options help centralize access.

You can still govern effectively. Export PDFs + metadata, use suggested field names, and adopt our “withdrawn/blocked” flag pattern until your connector is live.

Use our changelog and status page. Subscribe to release notifications so integration owners get notified before changes roll out.

Hours, not months. Load templates, connect your DAM, map fields, and test — most teams pilot within a single day.

Why Teams Switch to FairConsent

Because rights need to live where your assets live. FairConsent links verifiable consent records (PDF + fields) next to each file in your DAM, enabling search, filters, and enforcement—reducing legal and reputational risk.

✔ Fewer takedowns
✔ Faster approvals
✔ Lower compliance risk
✔ Hours saved per project

Teams save hours per project, and organizations avoid costly re-edits or removals when permissions are unclear.

Quite the opposite. One app, offline-ready, multilingual, built for real-world interviews. Collect once, govern everywhere.

Bring FairConsent to your next project

Learn more

Short forms. Local languages. Offline capture. Easy withdrawal. Use FairConsent to record, manage, and honor consent across teams and countries.

Book a demo