TS will provide reasonable assistance, proportionate to its role, with security-related obligations, DPIAs, consultations with authorities, and data-subject requests that Customer receives and directs to TS.


Capitalized terms not defined here have the meanings in the Agreement or applicable law.


Trusted Signatures (“TS,” “we,” “our”) and the counterparty identified in the applicable order form (“Customer”) agree to this Data Processing Addendum (DPA), which forms part of the agreement governing Customer’s use of the Services.


Customer must not send PHI in document content, filenames, content-derived metadata, or support materials.


If required, TS may execute a HIPAA Business Associate Rider (Operations-Only) that covers Operational Metadata (e.g., API logs, SHA-256 digests, certificate/validation status data) and expressly excludes document content.

May occur depending on conditions in source.


The Services are not designed to receive or store PHI.


Where Customer Personal Data is transferred to TS in the U.S. or another third country, the parties incorporate the appropriate Standard Contractual Clauses (EU 2021/914 C2P) and, as applicable, the UK IDTA/UK Addendum and Swiss addenda.


If there is a conflict between this DPA and the Agreement, this DPA controls to the extent required by law; otherwise, the Agreement controls.


The Agreement’s limitations and exclusions of liability (including ToS §15) apply to this DPA.


Liability & precedence Annex I — Processing details

Account/contact data; API/service logs (timestamps, IPs, user/tenant IDs, endpoint, status/latency); document-verification metadata (SHA-256 digests, certificate serials/issuer, validation outcomes); identity data provided for Publisher Identity onboarding (org details, authorized contacts, proofs).

Liability & precedence > Annex I — Processing details

Account/contact data; API/service logs (timestamps, IPs, user/tenant IDs, endpoint, status/latency); document-verification metadata (SHA-256 digests, certificate serials/issuer, validation outcomes); identity data provided for Publisher Identity onboarding (org details, author...


Customer will not submit sensitive data unless required and lawfully justified.


If unresolved in good faith, Customer may suspend the affected functionality or terminate the impacted order(s) with a pro-rata refund of prepaid, unused fees.


Trusted Signatures, 4 Saint Albans Rd W, Hopkins, MN 55305.


TS will post updates at /docs/subprocessors.


Within 15 days of an update, Customer may reasonably object on data-protection grounds.


Liability & precedence Annex II — Security measures (summary)

(c) Cryptography: TLS in transit; encryption at rest where applicable; keys protected by FIPS 140-validated HSMs (Level 3 where applicable).

Liability & precedence > Annex II — Security measures (summary)


Contacts You may contact us at support@trusted-signatures.com, or for legal notices at Michelle@trusted-signatures.com and Brad@trusted-signatures.com.


(e) Systems security: hardened images, patching, change control, segmentation.


(j) Vendor risk: Subprocessor due diligence; SCCs/UK addendum as needed.


(k) Customer controls: API key hygiene; permission scoping; revocation tools.


References • Subprocessors: https://trusted-signatures.com/docs/subprocessors/ • Privacy Policy: https://trusted-signatures.com/privacy/ • Terms of Service: https://trusted-signatures.com/terms/


As provided by Customer (e.g., account contacts, API users; document-verification metadata).


Data subjects may include Customer’s personnel, end users, and vendors.


Operating PDF sealing/verification workflows; security, support, and billing.


Processing of Customer Personal Data for the term of the Agreement and the retention windows in §8.


TS will ensure personnel accessing Customer Personal Data are bound by confidentiality and receive appropriate privacy/security training.


TS will process Customer Personal Data only: (a) to provide, secure, and support the Services; (b) per Customer’s written instructions (including the Agreement and this DPA); or (c) as required by law (with notice to Customer unless prohibited).


TS will not: (a) sell Customer Personal Data; (b) share it for cross-context behavioral advertising; (c) process it outside the business purpose of providing the Services; or (d) combine it with personal information from other sources except as permitted for security, fraud prevention, or service operations.

TS will not: (a) sell Customer Personal Data; (b) share it for cross-context behavioral advertising; (c) process it outside the business purpose of providing the Services; or (d) combine it with personal information from other sources except as permitted for security, fraud pr...


At termination or upon Customer request, TS will delete or return Customer Personal Data, unless retention is required for legal, security, audit, or trust-program reasons; in that case, TS will protect the data per this DPA and delete on the next standard cycle.


Typical retention windows are described in the Privacy Policy.


(a) For Account, Billing, Support, and Site data, TS acts as controller/business (see our Privacy Policy).


(b) For Customer-submitted technical data processed to operate the Services (e.g., API logs, SHA-256 document digests, certificate serials/issuer, validation outcomes), TS acts as processor/service provider on Customer’s documented instructions.


TS will notify Customer without undue delay after becoming aware of a Personal Data Breach involving Customer Personal Data and will provide information reasonably available to assist Customer with legal notification duties and remediation.


TS maintains appropriate technical and organizational measures, including: encryption in transit and at rest (where applicable); SSO/MFA; role-based access and least privilege; audit logging and monitoring (AWS CloudWatch); vulnerability management; secure SDLC; incident response; and HSM-backed key protection using FIPS 140-validated modules (Level 3 where applicable).

TS maintains appropriate technical and organizational measures, including: encryption in transit and at rest (where applicable); SSO/MFA; role-based access and least privilege; audit logging and monitoring (AWS CloudWatch); vulnerability management; secure SDLC; incident respo...


Customer authorizes TS to use Subprocessors to provide the Services.


Customers may object to a new Subprocessor under the process in Annex I §D.


TS maintains a live list at: Subprocessors List.


TS may update Subprocessors by updating that page (which constitutes notice).


TS will impose data-protection obligations no less protective than those in this DPA and remains responsible to Customer for each Subprocessor’s performance of those flow-down obligations (subject to the limitations in the Agreement).


Current Subprocessors Certificate authority, registration authority, and trust services (Identity products)

Data processed: Organization identity data (as provided by Customer for validation), certificate serials/issuer, request/response metadata.

Current Subprocessors > Certificate authority, registration authority, and trust services (Identity products)


EU Advanced Provider: Sectigo Limited and affiliates (CA/RA, OCSP/CRL, and RFC 3161 Time-Stamping Authority)


Purpose: Organization certificate issuance, validation/revalidation, suspension/revocation; certificate status checks; trusted timestamps.


Safeguards: Sectigo CPS/Subscriber terms; SCCs/UK Addendum as applicable.


Current Subprocessors Cloud hosting & compute

Data processed: Account/contact data, API logs, document-verification metadata (no PDFs).

Current Subprocessors > Cloud hosting & compute


Purpose: Hosting of application services, databases, and storage.


Questions about this list or data processing or for legals notices contact us at:


support@trusted-signatures.com Michelle@trusted-signatures.com and Brad@trusted-signatures.com.


Customers may object to a new Subprocessor under the process defined in the DPA §7.4.


TS may add or replace Subprocessors to improve reliability, security, or functionality.


Current Subprocessors Payment processing

Data processed: Billing contact data and transaction metadata; no full card numbers or CVV are stored by TS.

Current Subprocessors > Payment processing


Current Subprocessors Public Site Analytics

Data Processed: Web site activity (user opt-in required)

Current Subprocessors > Public Site Analytics


Purpose: Public site analytics (https://trusted-signatures.com)


Certain providers may also act as independent controllers for their own purposes (e.g., payment processing fraud/chargebacks) or make independent trust-program decisions (e.g., CA issuance/revocation); TS is not responsible for those independent activities.


Subprocessors process limited personal information on TS’s behalf and are bound by data-protection and confidentiality terms.


This page identifies the third-party Subprocessors that Trusted Signatures (“TS”) uses to deliver the Services.


TS remains responsible to you for each Subprocessor’s performance of the data-protection obligations we flow down to them under our DPA (subject to the limitations in our Terms).


We process SHA-256 digests, timestamps, and certificate status (OCSP/CRL) required for signing/verification.


2025-10-31: Initial Trust & Security page published (added HIPAA operations-only stance, AWS region, DPA/BAA/Subprocessors).


Signing keys are protected by FIPS 140-3 Level 3-validated HSMs; keys are generated, stored, and used within the cryptographic boundary.


Retention: security and API logs typically 12–24 months; verification metadata retained for the life of the account and a reasonable period thereafter.


What we process: account/billing data, API/service logs, SHA-256 digests, certificate serials/issuer, OCSP/CRL responses, timestamp tokens.


Document trust standards (validation context)

AATL (Adobe trust ecosystem) and eIDAS Advanced (AdES) for PAdES via appropriate providers/programs.


Viewer trust stores and configuration determine on-screen validation banners.


If you believe you've found a security issue, email privacy@trusted-signatures.com with steps to reproduce.


Legal notices: Michelle@trusted-signatures.com, Brad@trusted-signatures.com.


Security & compliance frameworks FIPS 140-3 (cryptography).

Our cryptographic operations run inside FIPS 140-3 Level 3–validated hardware security modules (HSMs).

Security & compliance frameworks > FIPS 140-3 (cryptography).


Security & compliance frameworks GDPR/CPRA (privacy).

All personal or organizational data collected for identity verification or billing is processed under GDPR lawful-use and retention principles.

Security & compliance frameworks > GDPR/CPRA (privacy).


Contact us to request a DPA, and Subprocessor List.


Trusted Signatures is a controller for account/billing/support and a processor/service provider for limited operational data (e.g., digests, logs, certificate status).


We comply with EU data-protection requirements for customer information.


Security & compliance frameworks HIPAA/PHI (operations-only).

Because we never receive PDF content or metadata (including filenames), Publisher is safe to use with PDFs containing PHI.

Security & compliance frameworks > HIPAA/PHI (operations-only).


If required, TS will execute a limited BAA covering narrowly defined operational metadata (e.g., API logs, digests, certificate status).


See our HIPAA BAA Rider (Operations-Only).


Security & compliance frameworks ISO 27001 (alignment).

ISO 27001 is the international standard for managing information security.

Security & compliance frameworks > ISO 27001 (alignment).


It provides a framework for how an organization protects data, controls access, and monitors risks.


Trusted Signatures follows ISO 27001-aligned practices through its cloud providers and internal controls, ensuring operational security complements our product’s compliance with ISO 32000, the open standard that defines the PDF format itself.


Security & compliance frameworks PCI DSS (payments via Stripe).

All credit-card transactions and billing data are handled securely by Stripe.

Security & compliance frameworks > PCI DSS (payments via Stripe).


Trusted Signatures processes payments through Stripe, a PCI DSS Level 1–certified provider.


We never store or transmit cardholder data on our own systems.


Security & compliance frameworks SOC 2 (provider).

Our hosting and infrastructure providers (e.g., AWS) maintain SOC 2 Type II certification for operational security, data availability, and confidentiality controls.

Security & compliance frameworks > SOC 2 (provider).


Trusted Signatures inherits these assurances as part of its secure cloud deployment.


Data Processing Addendum (DPA) Subprocessors HIPAA BAA Rider (Operations-Only): Available upon request Privacy Policy Terms of Service


Our service operates on non-reversible SHA-256 digests and certificate status data to apply standards-based seals.


Trusted Signatures ("TS") is built to minimize data exposure: we don't upload or store your PDFs.


For account, billing, support, marketing, and site analytics, TS is a data controller (a “business” under U.S. state privacy laws).


For customer-submitted content and metadata processed to seal/verify PDFs (e.g., document digests), TS acts as a data processor/service provider on your instructions, per our Terms and any data processing addendum (DPA).


For payment processing, TS is the billing controller (merchant of record) deciding who is billed, for what, and when; Stripe processes payment card data on our behalf.


Stripe may also act as an independent controller for its own purposes (e.g., fraud, disputes/chargebacks, and regulatory compliance).


11. Additional disclosures for California & certain U.S. states

Submit requests to privacy@trusted-signatures.com.


We act as a service provider/processor for customer content and as a business/controller for account, billing, and site interactions.


CA/RA decisions and program rules (e.g., AATL/EU trust lists) govern lifecycle outcomes.


For Publisher Identity (AATL OrgID / EU Advanced OrgID), identity data you supply is used to coordinate with CAs/RAs and related trust services for issuance, revalidation, suspension, or revocation.


If you instruct TS to attach OCSP/CRL and/or RFC 3161 timestamps, associated third-party validation metadata may be processed and retained to support verification.


TS does not upload or store your PDF documents for Publisher sealing; we may process and retain non-content document digests and verification metadata for audit and fraud-prevention.


Their privacy practices are governed by their policies.


Cookies and similar technologies for essential operations, security, and analytics (see §8).


For AATL OrgID and EU Advanced OrgID onboarding and lifecycle, we may collect organization identity data you provide (e.g., business name, addresses, registration numbers, authorized contacts, and proof documents) to coordinate with Certificate Authorities (CAs) and Registration Authorities (RAs).

For AATL OrgID and EU Advanced OrgID onboarding and lifecycle, we may collect organization identity data you provide (e.g., business name, addresses, registration numbers, authorized contacts, and proof documents) to coordinate with Certificate Authorities (CAs) and Registrati...


Messages, tickets, diagnostics, and related metadata.


Name, email address, organization name, billing contacts, subscription details, transaction metadata.


We log API requests for auditing, security, and usage tracking.


We may receive limited payment metadata (e.g., last four digits, card type, expiration month/year, tokens, transaction outcomes).


Where required, we process and may retain non-content metadata such as SHA-256 digests, timestamps, certificate serial numbers/issuer, validation outcomes, and signer identity fields you instruct us to apply—strictly for verification, audit, and fraud-prevention purposes.


3. How we use information (purposes & legal basis)

We use information to: (a) provide, secure, and operate the Services (contract/legitimate interests); (b) authenticate and manage accounts, keys, and entitlements (contract/legitimate interests); (c) prevent abuse, fraud, and security incidents; investigate errors (legitimate interests/legal obligations); (d) issue and manage organization certificates for Identity products with CAs/RAs/TSA/OCSP/CRL services (contract/legal obligations/legitimate interests); (e) process payments and comply with tax, accounting, and regulatory requirements (legal obligations/contract); (f) provide support and communicate about updates, billing, and policy changes (contract/legal obligations); (g) improve the Services and develop features (legitimate interests); and (h) send optional product and event communications (consent where required; you may opt out).

We use information to: (a) provide, secure, and operate the Services (contract/legitimate interests); (b) authenticate and manage accounts, keys, and entitlements (contract/legitimate interests); (c) prevent abuse, fraud, and security incidents; investigate errors (legitimate ...


A current list of core subprocessors is available on request.


(c) Trust services for signing/validation.


Cloud hosting, security/monitoring, analytics, support, and payment processing—bound by confidentiality and data-protection terms.


Stripe’s processing of payment card data is governed by its own terms and privacy notices.


We disclose limited information as follows: (a) Service providers/subprocessors.


We disclose necessary billing and transaction data to Stripe to process payments, prevent fraud, and handle disputes.


Where applicable, to CAs/RAs, time-stamping authorities (TSA), and revocation/validation services (OCSP/CRL) to issue, validate, suspend, or revoke certificates and timestamps per program rules.


(b) security and API logs: typically 12–24 months (longer if needed for investigations, regulatory, or audit purposes);


(c) document-verification metadata (no PDFs): retained for the life of the account and a reasonable period thereafter to support audit trails and dispute resolution, unless law or program rules require a different period.


You may request deletion of account data; we may retain data we must keep for legal, security, or operational reasons.


API keys and sensitive metadata are stored securely with restricted access.


No system is 100% secure; we cannot guarantee absolute security.


If you are an end user of a TS customer, please direct your request to that customer; we will support them in our processor/service-provider role.


To exercise these rights, contact us at privacy@trusted-signatures.com.


Privacy questions or requests: privacy@trusted-signatures.com Postal Address: Trusted Signatures, 4 Saint Albans Rd W, Hopkins, MN 55305 For legal notices, you may also contact michelle@trusted-signatures.com and brad@trusted-signatures.com


For EEA/UK/Swiss data, we rely on appropriate safeguards (e.g., Standard Contractual Clauses) and will enter a DPA upon request.


Capitalized terms not defined here have the meanings given in our Terms of Service.


Change summary (10/31/2025): We clarified roles (controller vs. processor), named core providers (Stripe, AWS, Sectigo, AWS CloudWatch), added retention windows, and included U.S. state privacy rights.


This Privacy Policy explains how we collect, use, disclose, and protect personal information in connection with our Services.


Trusted Signatures (“Trusted Signatures,” “TS,” “we,” “our,” or “us”) is committed to protecting your privacy.


Use of Trusted Signatures ("TS") service is subject to these Terms and our Privacy Policy.


We may modify or discontinue features; for material changes, we’ll post updated Terms.


12.2 HIPAA; limited BAA (operational metadata only).


If required, TS may execute a Business Associate Agreement (BAA) that covers only Operational Metadata processed to operate the Services (e.g., API/service logs, non-reversible document digests such as SHA-256, certificate/validation status data).


In case of conflict between this §13.2 and a signed BAA, the BAA governs solely with respect to PHI in Operational Metadata within its defined scope; otherwise, these Terms apply.


The BAA will expressly exclude document content (including PDFs), filenames, and content-derived metadata.


The Services are not designed to receive or store PHI.


You are responsible for (i) preventing PHI from being sent to the sealing endpoints or support channels; (ii) redacting PHI from diagnostics you provide; and (iii) promptly notifying TS if you believe PHI was transmitted in violation of this §13.2.


You must not transmit PHI to TS in requests or content, PDF-derived metadata, or support ticket materials.


14. No warranties; limitation of liability

To the maximum extent permitted by law: (a) TS and its affiliates, suppliers, and service providers will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, loss of business, or loss of data, arising out of or relating to the Services, including any issuance, suspension, revocation, expiration, or invalidation of a certificate or trust-program change, even if advised of the possibility of such damages; and (b) TS’s aggregate liability for all claims relating to the Services will not exceed the amounts paid by you to TS for the Services during the twelve (12) months preceding the event giving rise to liability.

To the maximum extent permitted by law: (a) TS and its affiliates, suppliers, and service providers will not be liable for any indirect, incidental, special, consequential, or punitive damages, or for lost profits, loss of business, or loss of data, arising out of or relating ...


Without limiting the foregoing, TS makes no guarantee regarding: (a) the legal enforceability of any signature or seal in any jurisdiction; (b) the availability, inclusion, or continued inclusion of any certificate or provider in any trust program or list; or (c) uninterrupted or error-free operation of the Services.

Without limiting the foregoing, TS makes no guarantee regarding: (a) the legal enforceability of any signature or seal in any jurisdiction; (b) the availability, inclusion, or continued inclusion of any certificate or provider in any trust program or list; or (c) uninterrupted...


Documents sealed prior to termination will remain valid, provided the certificate used to seal them are not revoked.


Sections intended to survive (including payment obligations, confidentiality, IP, disclaimers, limitations of liability, and indemnities) will survive termination.


We may suspend or terminate the Services, or your access to them, with or without notice, if we determine that: (a) you have breached these Terms or applicable CA Subscriber terms; (b) payment is overdue or your payment method fails; (c) your use poses a security, legal, compliance, or reputational risk (including suspected fraud, abuse, or credential compromise); (d) a third-party provider (including a CA, time-stamping, or revocation service) suspends, revokes, or refuses required services; (e) your use would violate export control, sanctions, or other applicable laws; or (f) continuing to provide the Services is commercially impracticable due to circumstances beyond our reasonable control.

We may suspend or terminate the Services, or your access to them, with or without notice, if we determine that: (a) you have breached these Terms or applicable CA Subscriber terms; (b) payment is overdue or your payment method fails; (c) your use poses a security, legal, compl...


These Terms are governed by the laws of the State of Minnesota.


2. Who we service; what we do (and don't)

See §15 for warranty disclaimers and limitations.


The Services are not designed to receive PHI; see §5 and §13.2.


Validation results depend on the recipient’s PDF viewer trust configuration and on PDF features such as certification signatures (DocMDP), legal attestations, and incremental updates, which can affect how changes are flagged or permitted.


You may contact us at support@trusted-signatures.com, or for legal notices at Michelle@trusted-signatures.com and Brad@trusted-signatures.com.


These Terms are the entire agreement regarding the Services.


You may not assign these Terms without our consent; we may assign to an affiliate or in connection with a merger or sale.


We may update these Terms from time to time.


Your continued use of the Services after the effective date of any changes constitutes your acceptance of the updated Terms.


Test keys are for evaluation and may use self-signed or test certificates; they are not appropriate for production due to lower assurance.


You are responsible for credential hygiene, including (a) key rotation, (b) secure storage, and (c) immediate revocation on suspected compromise.


Publisher can attach revocation data (OCSP/CRL) and trusted timestamps (e.g., RFC 3161) and enable long-term validation (LTV), and may set certification (DocMDP) permissions to allow or restrict post-seal changes (e.g., form-fill or additional signatures) without breaking trust.


Publisher does not by itself confer inclusion in any third-party trust program.


Validation indicators shown to recipients (e.g., “Certified by …”) are determined by the viewer’s trust store and settings.


AATL recognition depends on third-party trust-program rules and the recipient’s viewer configuration.


Issuance, suspension, and revocation decisions are made by the CA and may affect downstream validation.


Provides issuance and lifecycle management of organization-validated (OV) document signing certificates through a Certificate Authority (CA) recognized within the Adobe Approved Trust List (AATL) ecosystem, for use with Publisher sealing.


TS does not guarantee inclusion or continued inclusion in any trust list.


4.3 Publisher Identity — EU Advanced OrgID


Provider decisions (issuance, suspension, revocation) may impact validation; TS does not control those decisions.


Provides issuance through a Certificate Authority (CA) and lifecycle management of organization-validated (OV) certificates recognized within EU “Advanced” trust paths (i.e., via EUTL-listed providers) for use with Publisher sealing.


Qualified (QES) certificates are not available.


Trust recognition depends on the relevant EU trust framework and recipient configuration.


TS implements industry-standard PDF signing constructs consistent with ISO 32000 (PDF) and PAdES behaviors, including approval vs. certification signatures, DocMDP/FieldMDP permission dictionaries, inclusion of OCSP/CRL revocation data and RFC 3161 timestamps where available, and support for incremental updates and LTV to the extent supported by the chosen certificate, timestamp, and recipient software.

TS implements industry-standard PDF signing constructs consistent with ISO 32000 (PDF) and PAdES behaviors, including approval vs. certification signatures, DocMDP/FieldMDP permission dictionaries, inclusion of OCSP/CRL revocation data and RFC 3161 timestamps where available, ...


4.5 Dependencies, Disclaimers, and Customer Responsibilities

Availability, inclusion in trust programs (e.g., AATL, EU trust lists), and validation banners are outside TS’s control.


Because validation depends on recipient software and trust stores, indicators and permissions enforcement (e.g., for DocMDP) may vary by viewer and configuration.


Certificates, timestamps, and revocation information are provided by third parties.


Customer must provide accurate organization data, respond to CA/RA requests, protect credentials/keys, and request revocation if data becomes inaccurate or credentials are compromised.


Overview: Trusted Signatures (“TS”) provides tools to apply standards-based digital signatures/seals to PDF documents and, where purchased, to procure and manage organization certificates used for those seals.


Validation outcomes depend on recipient trust settings and applicable standards behavior (e.g., certification signatures, DocMDP/FieldMDP permissions, legal attestations, and incremental updates).


If you choose optional hosted features now or later, we will process only what is necessary and minimize retention.


Neither the customer, TS, nor our vendors can access the private keys associated with those certificates, even through direct access to the physical hardware in which the keys are stored.


The Services are not designed to receive or store protected health information (PHI).


TS may process limited operational metadata (e.g., API/service logs, document digests such as SHA-256, certificate serials/issuer, validation outcomes) necessary to operate the Services; such processing does not include document content.


With respect to our Publisher Identity products, TS will create and maintain the private keys for customer OV certificates inside Hardware Security Modules (HSMs).


You must not transmit PHI to TS in: (a) PDFs or other document content; (b) content-derived metadata; (c) support tickets or attachments; or (d) free-form request fields.


You will not: (a) use the Services for any unlawful, deceptive, or fraudulent purpose; (b) interfere with, disrupt, or reverse-engineer the Services; (c) disclose or permit use of API keys outside your organization; (d) misrepresent your or any organization’s identity; or(e) exceed rate limits or otherwise abuse shared resources; (f) transmit or include PHI in sealing requests, filenames, or support communications, except for limited operational metadata processed by TS solely to operate the Services as described in §13.2.

You will not: (a) use the Services for any unlawful, deceptive, or fraudulent purpose; (b) interfere with, disrupt, or reverse-engineer the Services; (c) disclose or permit use of API keys outside your organization; (d) misrepresent your or any organization’s identity; or(e) e...


7.1 Third-party providers; policy control

CA operations, issuance criteria, audits, and lifecycle decisions (issuance, suspension, revocation) are governed by the CA’s Certification Practice Statement and Subscriber Agreement, which are incorporated by reference.


Trusted Signatures (“TS”) uses third-party Certificate Authorities (CAs) and related trust services (e.g., OCSP/CRL revocation, RFC 3161 time-stamping).


Inclusion in trust programs (e.g., Adobe trust ecosystem/AATL, EU trust lists) and any addition or removal from such lists are outside TS’s control.


Validation indicators (e.g., “Certified by …”, warnings) depend on recipient software, local trust stores, and configuration; outcomes may vary across viewers.


You are responsible for (a) monitoring the status and suitability of any certificate you use; (b) providing accurate organization data and completing CA/RA validation; (c) keeping contacts current; (d) complying with applicable CA Subscriber terms; and (e) promptly requesting revocation and ceasing use if certificate data becomes inaccurate, is suspected compromised, or validation requirements change; and (f) determining whether your intended use of digital signatures/seals satisfies applicable legal or regulatory requirements in the jurisdictions where you operate or send documents.

You are responsible for (a) monitoring the status and suitability of any certificate you use; (b) providing accurate organization data and completing CA/RA validation; (c) keeping contacts current; (d) complying with applicable CA Subscriber terms; and (e) promptly requesting ...


If a certificate expires, is suspended, is revoked, or becomes otherwise invalid (including due to trust-list changes), the Services may fail to produce a verifiable signature for recipients, or previously sealed PDFs may validate differently over time (e.g., loss of LTV if revocation/timestamp data cannot be refreshed).

If a certificate expires, is suspended, is revoked, or becomes otherwise invalid (including due to trust-list changes), the Services may fail to produce a verifiable signature for recipients, or previously sealed PDFs may validate differently over time (e.g., loss of LTV if re...


Refunds or credits are not provided for Certificate Authority or trust-program actions (including issuance delays, suspensions, revocations, removals, or policy changes), viewer/trust-store variance, or other third-party decisions or events that affect validation, and are separate from the limitations in §15.

Refunds or credits are not provided for Certificate Authority or trust-program actions (including issuance delays, suspensions, revocations, removals, or policy changes), viewer/trust-store variance, or other third-party decisions or events that affect validation, and are sepa...


7.6 Mitigation guidance (non-contractual)

Do not include PHI in sealing requests or support materials; see §13.2.


To reduce disruption, (i) maintain current contacts with the CA, (ii) monitor certificate status, (iii) maintain and test key-compromise procedures, and (iv) include OCSP/CRL data and RFC 3161 timestamps to support long-term validation where available.


7.7 Additional duties for Publisher Identity (AATL OrgID / EU Advanced OrgID)

Promptly request revocation and cease use if credential compromise is suspected or organization data becomes inaccurate.


Qualified Electronic Signature (QES) certificates are not provided.


Use issued certificates only as permitted by the applicable CA Subscriber Agreement and Certification Practice Statement (CPS), which are incorporated by reference; (d) Compromise & inaccuracy.


You acknowledge that issuance, suspension, and revocation decisions are made by the CA/RA and may affect downstream validation; TS is not responsible for those decisions; and (f) Scope note.


8. Validation variance & standards notice

Different viewers may surface these checks differently depending on their trust configuration.


PDF supports approval and certification signatures.


You authorize us (and our processor) to charge fees and applicable taxes.


By using our services, you agree to these terms.


Change summary (10/31/2025): We clarified certificate/trust-program rules (including no refunds for CA/trust-list actions), expanded customer security/legal-use responsibilities, refined termination triggers, and standardized warranty/limitation terms.


Welcome to Trusted Signatures ("TS","we","our").