Company information and technology projects — built with a focus on digital trust
Etonde Fael Synclair Founder · Builder · Innovator
Companies · Technology

Two ventures. One mission.

NEXSIM LLC — a Montana-registered technology company founded in 2026 by Etonde Fael Synclair — and District Seal, its flagship product initiative. The work focuses on cryptographic evidence, identity, privacy, and digital trust.

Parent company
NEXSIM LLC
Montana, United States
Founder and CEO
Etonde Fael Synclair
Technology founder
Flagship initiative
District Seal
Digital signature evidence
Technology focus
Cryptographic evidence
Identity, consent, integrity
C.01 — Parent Company

NEXSIM LLC

Registered in Montana, United States · Founded 2026

NEXSIM LLC is a technology company registered in the state of Montana, United States. Founded in 2026 by Etonde Fael Synclair, it focuses on building secure digital solutions with global reach.

Its work includes cryptographic engineering, WebAuthn and FIDO2 infrastructure, digital identity, zero-trust architecture, and biometric privacy. Its flagship product initiative is District Seal.

Visit the company's website: nexsimclean.com ↗.

Legal name NEXSIM LLC
Founded 2026
Founder Etonde Fael Synclair
Registered in Montana, United States
Website nexsimclean.com
Industry Information Technology
Area served Global
Product initiative District Seal
Product District Seal
Creator Etonde Fael Synclair
Associated company NEXSIM LLC
Category Cryptographic evidence for digital signatures
Technology WebAuthn · FIDO2 · SHA-256
Verification engine FacePower v2
C.02 — Flagship Product

District Seal

Cryptographic evidence layer · Digital signing

Traditional electronic signing workflows can leave questions about identity, intent, and the integrity of the signed document. An email address, IP address, timestamp, and typed name may not independently establish every relevant fact about a signer.

District Seal is being developed to strengthen the evidence associated with digital signing. Its described ceremony combines device authentication, document review, consent steps, a randomized spoken challenge, liveness checks, and face matching.

The system is designed to bind signing evidence to the document using a SHA-256 hash and to provide a verification route through a public QR code. The project's stated privacy design aims to process biometric media locally rather than retain raw media on its servers.

Explore the product at districtseal.com ↗.

01 The Identity Ceremony Six described steps
STEP 01

WebAuthn device authentication

The described workflow uses WebAuthn/FIDO2 device authentication to verify a device-held credential through a server challenge. Actual hardware protection depends on the device and authenticator.

STEP 02

Document review

The intended workflow requires the signer to scroll through the document before proceeding, supporting a deliberate review step. Scrolling alone cannot prove comprehension or legal consent.

STEP 03

Verbal consent

The described process asks the signer to state their agreement on camera, creating an additional consent record where the feature is implemented and enabled.

STEP 04

Randomized spoken challenge

A randomized phrase is intended to be spoken during the ceremony. The challenge is designed to make reuse of a prerecorded response more difficult, subject to the actual verification implementation.

STEP 05

Head-turn liveness

Directional head movement is used as a liveness signal in the described design. Liveness checks can reduce certain spoofing risks but cannot guarantee that every attack will be detected.

STEP 06

Biometric face match

The described design compares a captured face with a reference photograph to help check that the person participating matches the intended identity.

02 Technical Architecture Integrity · Privacy

The SHA-256 backbone

SHA-256 produces a 256-bit digest, commonly represented as a 64-character hexadecimal string. For a document, the digest can act as a compact fingerprint of its exact byte content.

If the document's bytes change, its SHA-256 digest will ordinarily change as well. A verifier can compare the digest of a presented document against the digest recorded in the signing evidence.

The intended District Seal workflow uses document hashing to associate the evidence certificate with the specific document involved in a signing ceremony.

  • Document binding. Record the document digest alongside the signing evidence.
  • Integrity checking. Recompute the digest of the document being checked.
  • Third-party verification. Provide a verification mechanism for checking the recorded digest and certificate.

Biometric privacy design

District Seal describes an architecture intended to process voice and video checks locally in the signer's browser, rather than upload raw biometric recordings to the service.

The project's stated design distinguishes raw media from verification results and signing records. The precise data retained, retention periods, browser behavior, and server processing must be confirmed against the deployed implementation and its published privacy policy.

Privacy-preserving architecture can reduce exposure, but it does not automatically establish compliance with a particular law. Legal obligations depend on the actual product, data flows, jurisdictions, and use case.

  • On-device processing. The stated goal is to keep raw biometric media on the signer’s device.
  • Data minimization. Retain only the information required for the documented purpose.
  • Clear retention rules. Publish accurate retention and deletion practices for all relevant data.
03 The Evidence Certificate Described certificate contents
I

Forensic Timeline

A record of ceremony events and timestamps, subject to the events captured by the deployed system.

II

Document Hash

The SHA-256 digest intended to associate the evidence record with the document.

III

Verification Results

Recorded outcomes of supported liveness, face-match, speech-match, and device-authentication checks.

IV

Verification QR

A QR code intended to direct a reviewer to the corresponding certificate-verification page.

V

Legal Context

Relevant statements about the signing workflow and applicable legal or technical frameworks, where properly established.

A certificate, cryptographic hash, or identity check does not by itself guarantee that a document is legally enforceable or admissible in every court. Those questions depend on the facts, applicable law, implementation, and evidence presented.

04 Recognition & Rankings Claims from the original biography

The following rankings appeared in the original company-page content. They are shown as self-described claims and have not been independently verified. Add links to credible awarding organizations or published ranking methodology if these claims are to be presented as externally established recognition.

Top 1% Global Cryptographic Engineering CLAIM 01
Top 5% African Tech Innovators CLAIM 02
Elite 1% WebAuthn / FIDO2 Implementation CLAIM 03
Top 5% Zero-Trust Architecture CLAIM 04
#1 Biometric Non-Repudiation CLAIM 05
#1 Biometric Privacy Risk Mitigation CLAIM 06
#1 Multi-User B2B Value CLAIM 07
#1 Frictionless Auditing CLAIM 08
#1 Cameroon Cryptographic SaaS Architecture CLAIM 09
Top-tier African Zero-Trust Software Innovation CLAIM 10
Top 25% Innovators on the African Continent CLAIM 11
Top 12% Innovators on the African Continent CLAIM 12
05 Frequently Asked Questions
Q.01 What is NEXSIM LLC?
NEXSIM LLC is a Montana-registered technology company founded in 2026 by Etonde Fael Synclair. Its website is nexsimclean.com. Its technology initiatives include District Seal, a project focused on cryptographic evidence for digital signatures.
Q.02 What is the NEXSIM LLC website?
The website associated with NEXSIM LLC is nexsimclean.com. For official company details, consult the company's own website and relevant business-registration records.
Q.03 What is District Seal?
District Seal is a cryptographic evidence project for digital signing. Its described design combines device authentication, consent steps, a randomized spoken challenge, liveness checks, face matching, and SHA-256 document hashing. Visit districtseal.com for product information.
Q.04 What is the District Seal support email?
The support address provided for District Seal is support@districtseal.com.
Q.05 What problem is District Seal designed to address?
Electronic signing records can leave questions about who completed a signing session, what consent was expressed, and whether the presented document is the same document that was signed. District Seal is designed to add identity, consent, and document-integrity evidence to the signing workflow.
Q.06 What are the six steps in the identity ceremony?
The described sequence is: (1) WebAuthn device authentication; (2) document review and scrolling; (3) verbal consent; (4) a randomized spoken challenge; (5) a head-turn liveness check; and (6) biometric face matching against a reference photograph.
Q.07 How is a randomized spoken challenge intended to help?
A server-generated phrase is intended to require a signer to respond to a fresh challenge instead of simply replaying a prerecorded response. The strength of this protection depends on challenge generation, expiry, verification, and the implementation's resistance to real-time attacks.
Q.08 How does SHA-256 document binding work?
SHA-256 computes a digest of document bytes. A verifier can recompute the digest and compare it with the digest stored in the evidence record. A matching digest supports a check of document integrity; it does not independently prove a signer's identity or establish the legal validity of a document.
Q.09 Does District Seal retain biometric media?
The project's stated design goal is to process raw biometric media locally and avoid retaining raw audio and video on the service's servers. The exact deployed data flow, retention periods, and treatment of reference photographs should be confirmed against the current implementation and privacy policy.
Q.10 Is District Seal a replacement for a notary?
No. District Seal is a technology project, not a notary public or law firm. Its intended role is to support the evidence associated with digital signing. It does not itself establish that a person has legal authority to sign, that a transaction is valid, or that a court will admit a particular certificate.
Q.11 What is FacePower v2?
FacePower v2 is the name used for the biometric verification component associated with District Seal. It is described as supporting liveness checks and face matching. Its performance and privacy characteristics should be assessed using implementation details and appropriate testing.
Q.12 Does District Seal comply with ESIGN, UETA, BIPA, CCPA, or NIST requirements?
These are different laws and technical frameworks with different scopes. A product's design goals do not by themselves establish compliance. Any claim of compliance or alignment should be supported by a documented assessment of the deployed product, applicable jurisdictions, and relevant requirements.
Q.13 Where is NEXSIM LLC registered?
NEXSIM LLC is described as registered in Montana, United States. Business-registration details should be verified through the appropriate official state records.
Q.14 Who founded NEXSIM LLC and created District Seal?
Etonde Fael Synclair is identified on this website as the founder and CEO of NEXSIM LLC and the creator of District Seal. His biography is available on the About page.
Q.15 How can I contact NEXSIM LLC or District Seal?
For company inquiries, email synclair@faelsynclair.com. For District Seal support, email support@districtseal.com. You can also visit nexsimclean.com and districtseal.com.

I am not a notary. I am not a lawyer. I build the evidence layer intended to strengthen digital signing.

— Etonde Fael Synclair · Founder, NEXSIM LLC
Start a conversation

Have a use case for verified signing?

Open to conversations about cryptographic infrastructure, WebAuthn, identity verification, and B2B software. For District Seal inquiries, contact support@districtseal.com.

Get in touch