Keep processing close
The hosted Test Studio runs document capture and OCR on your device. Its document images and extracted information are not uploaded to this portal.
CEBS ID SECURE TRUST CENTERConfidence starts
Confidence starts
with clarity.
Understand where your information goes, how workspace access is protected and what each document result can tell you.
Practical controls. Clear responsibilities. Transparent capability status.
BUILT AROUND YOUR WORKFLOW
Three principles. One clear boundary.
A successful read is the beginning of a review process. Secure integration means understanding the full journey, from camera access to your application decision.
Protect shared work
Authenticated access, organization membership and role checks separate your workspace from other customers. Evaluation access is managed for each organization and edition.
Make evidence explicit
Extracted content, data consistency and physical originality are separate outcomes. Missing qualified evidence remains unavailable or inconclusive.
FOLLOW THE INFORMATION
A transparent path from capture to review.
Browser-local processing reduces document transfers in this hosted workflow. Your own integration must still define consent, access, storage and retention.
You choose to capture
The camera starts after an explicit action. The browser asks for permission. Stop the flow or leave the capture page to release the camera.
Your browser reads
Versioned SDK assets and OCR models load from this site. Captures and extraction results are processed in the browser for review.
Your application decides
Review extracted information against the document. Apply your own authorization and escalation process before taking an operational action.
| Information | Where it is handled | What to know |
|---|---|---|
| Document images and extracted content | Browser in the hosted Test Studio | Not submitted to this portal by the capture workflow. Do not paste them into support text. |
| Accounts and organization membership | Portal account database | Used for sign-in, recovery, membership and role-based access. |
| Projects and evaluation access | Portal account database | Records edition, hostname, environment and evaluation expiry. A project is not a production license. |
| Evaluation usage | Portal account database | Client-reported edition, completion outcome and bounded duration. No document content in these counters. |
| Quote and support requests | Portal account database | Stores the text you intentionally submit and its review status. |
| Account confirmation and recovery | Transactional email service | Expiring action links are delivered by email. Account passwords are not included. |
WORKSPACE SECURITY
Access should match responsibility.
The portal implements concrete account and request controls. Your team remains responsible for account hygiene and the permissions granted within its organization.
Account credentials
Passwords are hashed with scrypt. Secure, HttpOnly, SameSite session cookies identify server-side sessions over HTTPS. Sign out to revoke the current session.
Organization boundaries
Project, quote and support records are checked against the signed-in organization. Membership roles control privileged actions; restricted administration is separately authorized.
Protected actions
Forms use request forgery protection and origin validation. Rate limits reduce repeated account requests. These controls complement your integration security review.
Recovery you control
Confirmation and reset links are expiring and single use. Saved recovery codes are single use. Password changes and resets revoke existing account sessions.
For workspace owners
- Use individual accounts and a password manager.
- Invite only the people who need access.
- Choose roles according to actual work responsibilities.
- Store recovery codes separately from the account password.
For integration teams
- Keep application authorization on a trusted backend.
- Use HTTPS and versioned runtime assets.
- Do not expose secrets or trust browser counters as verified evidence.
- Test session expiry, role boundaries and recovery before launch.
KNOW WHAT A RESULT MEANS
Different editions. Explicit evidence boundaries.
Edition scope describes the intended workflow. Qualification status describes what can responsibly be relied upon today.
Identity Recognition
OCR evaluationCapture documents and extract structured information for review. Essential completeness and document-specific checks support the reading workflow.
A readable result does not establish issuer authenticity or physical originality.
Explore SENSEDocument Authenticity
Controlled evaluationExplore guided multi-frame capture, presentation evidence and structured assessment interfaces.
Physical originality remains unavailable or inconclusive until qualified detectors and an approved evidence-trust architecture are in place.
Explore GUARDAI Fraud Intelligence
Controlled evaluationExplore advanced analysis interfaces for synthetic documents, portrait manipulation and tampering assessment.
Unqualified fraud models must not produce a production approval. Independent training, evaluation and evidence requirements remain separate.
Explore SHIELDPREPARE WITH YOUR TEAM
A practical review before production.
Use these review areas to align engineering, security, privacy and business owners. A completed portal evaluation does not replace deployment approval.
Documents and devices
Validate every target market, document generation, language workflow and physical device family using authorized samples and independent ground truth.
Data handling and privacy
Agree the lawful basis, user notice, data access, retention, deletion and contractual processing requirements for your deployment.
Secure integration
Review HTTPS, content security policy, worker configuration, asset integrity, camera cleanup, authorization and sanitized monitoring.
Operational recovery
Assign support and incident responsibilities. Test account recovery, backup restoration, rollback and failure escalation. Confirm off-host recovery arrangements.
Evidence and policy
Separate extraction from originality and fraud outcomes. Preserve blocked or review-required states where qualified evidence is missing.
Commercial activation
Agree permitted origins, edition, volume, support, renewal and production licensing before enabling a commercial integration.
ANSWERS WITHOUT ASSUMPTIONS
Common security and privacy questions.
Does browser-local processing mean nothing reaches the server?
Document images and extracted information stay in the hosted Test Studio browser workflow. The portal still handles accounts, workspace configuration, requests and limited evaluation counters. Your own application may add separate processing that must be reviewed.
Can a photo or successful scan prove originality?
No. OCR extracts readable content. Distinguishing a physical original from a copy needs qualified detection and trustworthy evidence. GUARD and SHIELD remain controlled evaluations where those dependencies are unqualified.
Is every country and language already supported?
No universal coverage or verified language count is claimed. Confirm the specific document profiles, generations, scripts and devices for your target users before rollout.
Does this page claim a security certification?
No. This page describes implemented portal controls and current capability boundaries. It does not assert a certification, independent audit attestation or regulatory approval. Discuss the evidence required for your procurement review with CEBS.
How are retention and deletion requests handled?
Use authenticated Support to initiate an account or organization request. CEBS must verify authority before acting. Live records and recovery backups have different lifecycles; agree the applicable production retention terms separately.
How should I report a security concern?
Open a support request with a concise description, affected area, timing and safe contact route. Do not submit passwords, recovery links or document content. Request an agreed secure exchange before sharing sensitive evidence.
LET US HELP YOU REVIEWBring your requirements.
Bring your requirements.
Build a clearer release plan.
Discuss your deployment, document coverage and security review through your workspace.