Announcements

We’ve added Web sealing to Publisher — Trusted PDF Sealing, so teams can seal PDFs directly in the browser and download the sealed result without uploading documents to Trusted Signatures servers.

What’s now available

• Browser-based PDF sealing for fast, local, no-upload document sealing
• Test certificate mode for teams evaluating the flow before subscribing
• Trusted Signatures certificate mode for Publisher subscribers who want Acrobat to show Trusted Signatures as the sealer
• Organization certificate mode for Publisher Identity subscribers who want Acrobat to show their company or organization as the sealer
• New documentation for the browser flow, certificate modes, and pricing behavior

How the new browser flow works

• The PDF stays local. The document remains in the browser during sealing and is never uploaded to Trusted Signatures servers.
• Test users can validate the workflow first. The free test certificate seals the PDF, but the output is not Adobe-verifiable and does not show the Acrobat blue seal.
• Publisher subscribers can move to trusted output. With Publisher, the same browser flow can seal with the Trusted Signatures certificate.
• Identity subscribers can show their organization as signer. Publisher Identity uses the same browser flow while switching the signer shown in Acrobat to the customer organization.
• Pricing stays consistent. Web sealing uses the same Publisher usage pricing as CLI and API sealing, and the same Publisher subscription supports web, CLI, API, Cloud Connector, and Zapier usage.

Where to start

• Web sealing docs
• Publisher overview
• Publisher Identity
• Pricing

We’ve expanded Publisher — Trusted PDF Sealing with cloud connector deployment paths and Power Automate support so teams can keep orchestration, storage, and workflow controls inside their own environment while preserving the same reader-visible trust outcome in Acrobat/Reader.

What’s now available

• Publisher Cloud for customer-managed deployment patterns across Azure, AWS, GCP, and Kubernetes
• Cloud Connector for Power Automate for Microsoft-centric workflow teams already operating the Cloud Connector for Azure
• Deployment and integration docs for Azure, AWS, GCP, and Kubernetes
• Updated RAG resources and code snippets covering cloud connector setup and invocation patterns

Why teams use these paths

• Keep PDFs in your environment. Cloud connector patterns are built for customers that want document handling, storage, and runtime controls inside their own cloud boundary.
• Use the workflow tools you already run. Power Automate can trigger sealing as a native workflow step without requiring a separate custom application layer.
• Standardize across platforms. Platform teams can use one trusted PDF sealing model across serverless, container, and workflow-driven systems.
• Preserve recipient experience. Recipients still validate the resulting PDF in Acrobat/Reader and other compatible PAdES viewers.

Where to start

• Publisher Cloud
• Cloud Connector for Power Automate
• Cloud Connector docs
• Power Automate guide

We’ve launched Publisher Identity to pair with Publisher — Trusted PDF Sealing, so your organization can put your name in the certified signature seal using standards-based certificates for cleaner validation in Adobe Acrobat/Reader and along EU “Advanced” trust paths.

What’s in the launch

AATL OrgID: Organization-validated certificates recognized in Adobe’s trust ecosystem (AATL) for use with Publisher sealing. EU Advanced OrgID: Organization certificates suitable for EU “Advanced” trust paths (via EUTL-listed providers).

Why teams choose TS over DIY OV

• Less hassle. We coordinate CA/RA steps (KYC, revalidation, evidence collection), track renewals, and handle lifecycle events—so your team doesn’t have to learn CA policy or chase paperwork.
• Lower hidden costs. Avoid building/maintaining PKI workflows, HSM custody, audit trails, and trust-program nuance; use our standard process and support instead.
• Consistent validation. We align sealing behavior with Adobe-documented validation (certification vs. approval signatures, DocMDP/FieldMDP, incremental updates) to help recipients see the right trust banners.
• One vendor, clear terms. Single contract, predictable billing, and documented responsibilities (no-refunds for CA/trust-program actions are clear upfront).
• Operational guardrails. Renewal reminders, compromise procedures, and audit-ready metadata (OCSP/CRL, optional RFC 3161 timestamps if you choose to enable LTV).

How it works

1. Complete CA/RA onboarding with your org details and authorized contacts.
2. Use the issued org certificate with Publisher to seal PDFs.
3. Optionally include OCSP/CRL and RFC 3161 timestamps to support LTV where available.

Learn more about: Publisher Identity

We’ve updated our Terms of Service and Privacy Policy. The updates take effect on November 30, 2025. Highlights:

• Certificates & trust programs: clearer rules, including no refunds for CA/trust-list actions.
• Customer responsibilities: key hygiene, rights to sign/seal, and legal-validity checks.
• Termination: refined triggers (security/fraud, third-party provider/CA actions, sanctions/export).
• Warranty & liability: standardized disclaimers and damage exclusions, 12-month cap.
• Privacy: clarified roles (controller/processor), named providers (Stripe, AWS, Sectigo, AWS CloudWatch), set retention windows, and added state-law rights.

Review the full documents:

• Terms of Service
• Privacy Policy

If you do not agree with these updates, please stop using the Services before the Effective Date. Questions? Contact privacy@trusted-signatures.com.