How Opcilo protects sealed documents

Security at a glance

Compact summary of controls already described on this page — not a certification badge row.

At-rest encryption

AES-256 on Azure

Integrity

SHA-256 seal fingerprint

Transit

TLS

Identity provider

Microsoft Entra

Malware path

Microsoft Defender for Storage on sealing path

Active production regions

Azure UAE North and Canada Central (multi-region)

Document plane (Gulf)

Azure UAE North

Document plane (Americas)

Azure Canada Central

Explicit non-claim

Not end-to-end encrypted; no SOC 2 / ISO claimed

What we prove

Every seal carries a SHA-256 fingerprint of the exact file bytes you sealed. Recipients open a verification link and can confirm integrity without creating an account — verification does not require trusting our brand reputation alone.

Signatures prove agreement. Opcilo proves the file has not been altered since sealing.

What we encrypt and how

Stored documents are encrypted at rest with AES-256 on Microsoft Azure. Connections use TLS in transit.

Workspace data is isolated per organization so one customer’s sealed files are not visible to another.

What we don’t claim

We do not claim end-to-end encryption. Sealing and PDF processing require server-side access to file contents — claiming otherwise would be inaccurate.

We are transparent about this because many “secure” document tools are not. Prefer named algorithms and clear boundaries over vague assurances.

Threat model (summary)

Primary risks we design against: a sealed file being swapped or altered after issue; unauthorized access to stored documents; malware uploaded on the sealing path; and impersonation of an issuer’s public trust profile.

Out of scope for Opcilo’s cryptographic seal: whether document statements are true, whether a person completed government ID checks, and whether a signature is legally binding. Those are separate products and claims.

Recipients can independently hash-check a file against the seal. Abuse of seals, payment details, or business trust pages can be reported from the product surfaces that show them.

Where your data lives

Opcilo production runs in two active Azure regions — UAE North and Canada Central — so organizations can keep sealed documents and seal metadata in the Available region they choose for the workspace.

Gulf document plane: Azure UAE North (with geo-backup to UAE Central where configured). Americas document plane: Azure Canada Central. Choosing a plane keeps that workspace’s documents in that region; we do not move them around the world by default.

Identity, billing, and some notifications may involve other subprocessors and regions. See the subprocessors register for the current map — we do not claim that every byte of every related service stays inside a single country.

Who can access your files

Uploads are scanned for malware on the sealing path using Microsoft Defender for Storage, so infected files are not treated as normal sealed documents.

Opcilo staff do not routinely open customer documents. Support access is limited to ticket-initiated investigation when needed to resolve an issue you raise — not casual browsing of sealed files.

Audit and access logging

We retain security and operational logs for a limited period appropriate to reliability, abuse investigation, and incident response. Account and legal-consent events are retained as described in the Privacy Policy.

Authenticated customers can see engagement and activity timelines for their own seals and inbox workflows where the product exposes them. Public verification pages do not expose recipient browsing history.

A customer-exportable, immutable enterprise audit log product with long retention SLAs is not yet a published offering — we will state it here when it is.

Privacy Policy (retention)Ask about audit logging

Retention and deletion

Free share links expire after 7 days as an exposure-reduction control on download access — not a claim that verification becomes impossible forever.

Opening a verification code can still show seal status after a Free share link expires; link expiry limits file download/share exposure, not the existence of the seal record.

Public file check on the verification page: your upload is sent for a one-time hash check. It is not saved as a sealed document and is discarded when the check finishes. That does not claim the bytes are purged from every temporary buffer, log, or backup plane.

Account and workspace deletion follow our Privacy Policy. Deep-link the Privacy Policy for the current retention language — we do not invent permanence for hash verify in this Trust Center.

Ask about retention (Privacy)privacy@opcilo.com

Backups

Gulf document plane uses Azure geo-backup to UAE Central where configured. Canada Central is the Americas document plane.

We do not publish a customer-facing RPO/RTO number on this page. Detailed recovery objectives remain an operations topic — not yet a public SLA claim.

Key management

Platform encryption keys are managed through Azure services and Managed Identity for service-to-service access — no storage account keys in application config.

Customer-managed keys (CMK): not yet.

MFA and roles

Sign-in uses Microsoft Entra. Workspace roles control who can seal, invite, and administer inside a team.

Org SSO / SCIM: roadmap / not yet.

Infrastructure partners

Opcilo is built on Microsoft Azure for document storage and related platform services, with multi-region deployment across active UAE North and Canada Central planes. Sign-in uses Microsoft Entra.

Vendor details and processing locations are listed in our subprocessors register.

Controller and processor

For personal data in Customer Content, the customer organization is typically the controller and Opcilo acts as processor under our Data Processing Addendum (DPA).

A public DPA download URL is not yet published on this site. Until it is, request the DPA via Contact or privacy@opcilo.com, and review the Privacy Policy language for processing roles.

Contact us for the DPAPrivacy mailbox

Compliance posture

We design controls with GDPR-aligned practices in mind, and we continue review work relevant to KSA PDPL and UAE data protection expectations for MENA buyers.

We do not claim SOC 2, ISO, or PDPL certification on this page. Roadmap: pursue formal attestations and state them here with dates when completed — not before.

Penetration testing

Independent penetration testing: not yet. We will publish scope and dates here when a program is complete — no fabricated completion date.

Incidents and vulnerability disclosure

Report security issues to security@opcilo.com. We acknowledge responsible disclosure and will coordinate incident notification with affected customers as required.

See /.well-known/security.txt for the preferred contact. Confirm the mailbox is monitored before treating this as a launch-ready disclosure channel.

security@opcilo.comsecurity.txt

Independent verification

Open the link or enter the code to see seal status and integrity. To confirm a file you hold matches the seal, upload a copy for a one-time hash check on the verification page — it is not saved as a sealed document and is discarded when the check finishes.

Free recipient links expire automatically after a short window to reduce unnecessary exposure; paid plans can choose longer durations.

You do not need to trust Opcilo’s reputation alone — confirm integrity on the verification page.

Trust Badge and Issuer Verified

A Trust Badge and public business page at /v/{slug} show Issuer Verified (KYB) after Opcilo reviews business registration materials for a Pro+ workspace. Recipients see who sealed the file — carefully.

Issuer Verified does not prove that document statements are true, that a person completed identity checks, or that a signature is legally valid. It is not a statement that the company is honest.

Email-verified accounts are not Issuer Verified. Person identity checks on signers are not available today.

See Trust Badge on FeaturesWhat we don’t claimSee pricing for Pro+