Vloggi Confirm: the easiest way to determine whether a video is human-generated
Human-generated video
Real video in the age of AI slop.
Collect video from real people, with the evidence of its origin attached from the start. Vloggi Confirm brings together capture data, chain of custody and human declarations so your team can assess the source—not just the pixels.
For the strongest collection evidence, require fresh responses through the device camera.
The problem
AI slop makes convincing video easy. Trust is harder.
A polished clip tells you little about who made it, how it was captured or what happened before it arrived. Anonymous files, missing context and separate permission forms leave your team piecing together the story.
The solution
Build the evidence at collection.
Invite people to record a fresh response. Keep the capture evidence, contributor details, declarations and submission record together. Collect human-generated footage with a stronger basis for confidence than an unexplained file in a cloud folder.
Feature spotlight
See the evidence behind each submission.
01 · Device-camera capture
Recorded 09:41
02 · Connected submission record
Submitted 09:42 · Declaration recorded
03 · Find it in your library
From device to dashboard.
Review capture source, device category, recording time, media details and editing markers in your Vloggi dashboard. Connect that technical evidence with the person, project and declarations behind the clip.
More than a metadata check.
Human participation, consent, capture continuity and contextual consistency contribute different evidence. Together, they make the submission easier to assess and investigate.
Built for confidence
Technical evidence. Human responsibility.
Vloggi camera
No
Device evidence
See how the video entered Vloggi and the available camera and media markers. Keep timestamps and recording characteristics with the submission.
A connected chain of custody
Link the capture session, original file and recorded consent. Checksums identify file bytes; the connected records explain how the submission reached your library.
I confirm this submission is my own recording and will disclose any material AI-generated elements.
☑ I confirm.Human accountability
Ask contributors to confirm their own recording and disclose material AI involvement. Present project-specific declarations before submission, alongside the content-assignment terms.
- Capture method
- Human participation
- Consent and identity evidence
- Media provenance and Content Credentials
- Context and consistency
- AI analysis
Strong human-origin confidence
Review the supporting evidenceA score with supporting evidence
The Human-Origin Confidence Score (HOCS) summarizes a versioned integrity assessment. Read the evidence and cautions with the result, rather than treating a number as a stand-alone answer.
Upload security
Protect the upload. Preserve the evidence.
Upload protections help prevent automated abuse and require malware clearance before a submission is accepted.
Bot protection
Server-side Cloudflare Turnstile checks help block automated abuse. Reused verification tokens and attempts to start an upload without permission are rejected.
Controlled file transfer
Upload permissions are tied to the browser session and intended files. Checksum verification checks the transferred data, while safe retries avoid duplicate upload sessions and submissions.
Malware clearance
The exact stored file version must receive malware clearance before submission can complete, keeping the clearance linked to the file being accepted.
How it works
Start with a person, not an anonymous file.
1. Set the capture rules
Choose camera responses when human origin is the priority. Configure prompts, contributor fields and the declarations your project needs.
2. Collect a fresh response
Contributors answer on their device and confirm the terms presented. Their responses and submission details travel into the same project.
3. Review the evidence
Open the clip in your library, inspect its capture evidence and review the contributor context before reuse or escalation.
Vloggi Confirm
Already have a video? Check the file.
Assess before you use it.
Vloggi Confirm checks available Content Credentials, AI disclosures and file-integrity signals, and returns a Human-Origin Confidence Score (HOCS). Your video stays on your device; a small evidence summary is scored securely.
Need a reliable supply? Collect it with Vloggi.
Checking an existing file cannot recreate a missing capture history. For ongoing campaigns, research and evidence workflows, collect directly with Vloggi so participation, permissions and provenance stay connected from the beginning.
Use cases
When human origin matters.
Inspections & compliance
Collect fresh site or asset responses with capture evidence, contributor accountability and job context.
Education & assessment
Gather student performances and prompted responses with contributor details and a traceable submission record.
Media & audience content
Source human-generated audience footage with reuse permissions and evidence your reviewers can inspect.
Customer proof
Structured submissions for high-stakes review.
NSW Education Standards Authority
NESA uses Vloggi to manage student video submissions for showcase selection. It is a practical example of collecting people’s work with the details reviewers need, rather than chasing anonymous files.
Independent certification
ProudlyHuman™ certified.
Vloggi is ProudlyHuman™ certified. Videos verified as human through Vloggi Confirm carry ProudlyHuman™ certification.
Certification applies to videos verified as human—not automatically to every uploaded file.
Our approach
Pro-human. Not anti-AI.
AI can help transcribe, tag, search and organize video. It should not hide whether a person created the underlying footage. Vloggi keeps human contribution, reuse rights and source evidence at the center of the workflow.
Common questions
Know what supports the confidence.
How do I get the strongest confidence that a video is human-generated?
Collect fresh, prompted camera responses through Vloggi and combine capture evidence with contributor details, declarations and the connected submission record. For maximum-assurance requirements, speak to us about a managed enterprise capture workflow.
Does a score of 100 mean a 100% guarantee?
No. HOCS is an evidence score, not a probability. The current Confirm guidance reserves 100 for eligible managed capture with a verified participant, an attested registered app, bound consent, validated capture-to-upload evidence and no contradictions. Ordinary browser recording does not automatically qualify. Read the current scoring guidance →
Is Confirm an AI-slop or deepfake detector?
Confirm emphasizes prevention and accountability at collection: who contributed, how the video arrived and which supporting evidence is available. Confirm also assesses an existing file’s available provenance and integrity signals. Neither visual plausibility nor a strong score certifies that the events shown are true.
What if a video has no Content Credentials?
Missing credentials do not mean a video is AI-generated. Many genuine videos lack C2PA records. Review the capture, participation, consent and contextual evidence alongside the file findings.
Can I still accept existing video files?
Yes. Use an upload-enabled collection workflow when existing footage is appropriate. Require device-camera responses when fresh capture is essential; uploaded files may carry less capture-history evidence.
How do bot protection and malware checks protect uploads?
The upload flow combines server-side bot checks, browser- and file-bound upload permissions, checksum verification and malware clearance for the exact stored file version. They protect the submission process; they do not by themselves establish human origin or replace the HOCS evidence assessment.
Is Vloggi ProudlyHuman™ certified?
Yes. Vloggi is ProudlyHuman™ certified. Videos verified as human through Vloggi Confirm carry ProudlyHuman™ certification.
Get started
Collect real video. Keep its story intact.
Build a library of human-generated footage with contributor context, permissions and capture evidence connected from the start.