Skip to main content

Security

Trust, with the details included.

How Fidescript approaches account protection, document access and responsible information handling.

Accounts & sessions

Email and password accounts use a dedicated authentication service. Passwords are stored as hashes, and authentication rate limits are backed by the database. Deployed sessions use secure cookies; the installed cookie configuration uses HttpOnly and SameSite=Lax.

Customer and attorney registration are distinct. Public registration cannot create administrators, and profile edits cannot change an account’s role. Email recovery delivery, web social login and privileged multi-factor authentication are not ready.

Access with a defined purpose

The API checks the signed-in account, role and resource permissions. Critical database commands repeat workflow eligibility checks. A visible button or browser-supplied status is never authorization.

Document access depends on ownership and the relevant appointment or credential review. Administrators have scoped access to qualifying ENP application credentials, not general access to everyone’s files. Private query caches are partitioned by account and eligibility.

Document safeguards

Private PDF uploads are limited to enabled development and test environments. The implementation validates file type, PDF structure, size and page count. Stored revisions are immutable, and reads verify SHA-256 checksums. Download access is authorized and audited.

These checks do not provide malware scanning, a legal signature or archival certification. Production scanning, recovery and retention operations remain outstanding. Use synthetic documents only.

Identity is a separate check

Registration and document upload do not establish identity. The configured live-presence verification flow is development assurance only, with separate consent, attempt limits and server-retrieved outcomes. It is not National ID authentication or legally sufficient identity evidence.

Production identity assurance and production video admission are unavailable. Attorney account type, internal application review and current commission eligibility are separate checks.

Information & communications

Application logs use curated errors and request identifiers instead of document contents, passwords, cookies or raw provider errors. Application audit events record workflow actions; these internal records are not an official Electronic Notarial Book.

Configured communication workflows keep message history in the platform’s database and use communication services to support updates and video connections. Video credentials expire within 120 seconds and renewal rechecks access. An already issued credential is not immediately revoked. The application does not implement call recording.

Deployment & shared responsibility

The implementation includes exact-origin request controls, bounded payloads and server-only secrets. Production safety still depends on verified domain and cookie configuration, provider setup, private storage operations, backups, retention, incident response and legal readiness.

Protect your password and device, sign out on shared devices, and do not submit real identity or legal records during development. No independent certification, government accreditation or security audit is asserted here.

Reporting a concern

A verified public security reporting address has not been published. Existing development collaborators should use their agreed private operator channel. Do not post sensitive records, tokens or exploit details publicly. The Contact page records current channel availability.