top of page
  • Where can I get support or report an issue with OpenSign?
    You can get support or report issues through our GitHub issue tracker or join our Discord community where our team and community members can help you troubleshoot any problems. Official support is also available under the cloud hosted plans.
  • How can I install OpenSign?
    To install OpenSign, you'll need to download the software from our GitHub repository and follow the installation instructions provided in the INSTALLATION.md file. If you have any issues, you can visit our community forum for support.
  • What is OpenSign?
    OpenSign is an open-source digital signature platform that enables secure signing of documents with ease and efficiency. It's designed to provide a free alternative to commercial e-signature services, offering transparency and customization opportunities to meet your unique business needs.
  • Can I contribute to the OpenSign project?
    We welcome contributions from the community. Whether you're a developer, a designer, or just an enthusiast, you can contribute to the OpenSign project through code contributions, documentation, translations, and more.
  • How does OpenSign ensure the legality of electronic signatures?
    Electronic signatures through OpenSign are created in a manner that meets the requirements of electronic signature laws in various jurisdictions, providing legally binding signatures.
  • Is OpenSign really free?
    Yes, OpenSign is completely free to use. Being open-source, it can be downloaded, used, and modified without any cost. We believe in democratizing digital signature technology for everyone. You only need to pay to use the cloud hosted version of the software.
  • What formats does OpenSign support for documents?
    OpenSign currently supports PDF documents, which are widely used for contracts, agreements, and other formal documentation.
  • Is OpenSign secure?
    Security is our top priority. OpenSign ensures document integrity by using advanced encryption methods, and we constantly update our platform to incorporate the latest in security practices. The best part is, our source code is open and being monitored by hundreds of developers constantly. This makes identifying any security issues significantly faster.
  • How can I verify a digital signature created with OpenSign™?
    Verification can be easily conducted through any software(we recommend Adobe Acrobat reader), which checks the digital signature against the document and the signer's digital certificate to ensure it has not been tampered with and remains valid. Adobe Acrobat shows a message "Signed and all signatures are valid" if the signature is valid and the document is not tempered with. You can click the "Signature Panel" to see other details of the signature.
  • How does OpenSign work?
    OpenSign allows users to upload documents, request signatures, and sign documents electronically. It uses state-of-the-art cryptographic algorithms to ensure that all documents are signed securely and are legally binding in most of the countries.
  • What is the differences between UETA and eIDAS?
    The Uniform Electronic Transactions Act (UETA) and the Electronic Identification, Authentication and Trust Services (eIDAS) regulation are both legal frameworks that facilitate the use of electronic transactions and signatures. However, they differ significantly in their scope, geographical applicability, and detailed provisions. Below are the key differences: Geographical Applicability: UETA: It is a United States law adopted by individual states, and it applies only within the United States. Not all states have adopted UETA, as some have their own electronic signature laws. eIDAS: It is a European Union regulation that applies uniformly across all EU member states. It also has implications for international transactions involving EU entities. Scope and Purpose: UETA: It provides a legal framework for electronic signatures and records in commercial or governmental transactions, validating their legality and enforceability. eIDAS: In addition to providing legal recognition of electronic signatures, eIDAS establishes standards for electronic identification and trust services for electronic transactions in the EU's internal market. Types of Electronic Signatures: UETA: Recognizes electronic signatures broadly without categorizing them into different levels of security or authentication. eIDAS: Clearly defines and distinguishes between different types of electronic signatures: simple electronic signatures (SES), advanced electronic signatures (AES), and qualified electronic signatures (QES), the latter having the equivalent legal effect of a handwritten signature within the EU. Electronic Identification: UETA: Does not specifically address electronic identification. eIDAS: Provides a clear framework for electronic identification schemes, allowing EU citizens to use their own national electronic identification schemes to access public services in other EU countries. Trust Services: UETA: Does not provide provisions for trust services related to electronic transactions. eIDAS: Covers a range of trust services including electronic seals, time stamps, registered delivery services, and certificate services for website authentication. Legal Recognition: UETA: Focuses on ensuring that electronic records and signatures are not denied legal effect solely because they are in electronic form. eIDAS: Not only ensures the legal effect of electronic signatures but also sets out the criteria for the mutual recognition of electronic identification across EU member states. Cross-Border Recognition: UETA: Does not have provisions for international recognition and is limited to the jurisdiction of the adopting states within the U.S. eIDAS: Ensures that a signature or service meeting the regulation's standards is recognized across all EU member states, facilitating cross-border business. Implementation: UETA: Being an act, it requires adoption by individual states, and there may be variations in how it is implemented in each state. eIDAS: As an EU regulation, it is directly applicable and enforceable in all EU member states without the need for national legislation. Both frameworks aim to facilitate electronic transactions, but eIDAS is more comprehensive, providing detailed standards for electronic identification and trust services, whereas UETA is more of a foundational legal framework for the use of electronic records and signatures in the United States. When engaging in electronic transactions or implementing digital signature solutions, it is crucial to comply with the relevant legal framework. OpenSign™, being a versatile digital signature platform, can be instrumental in helping entities adhere to such legal requirements. More information about how OpenSign™ aligns with these frameworks can be found on its GitHub repository. Please note, the information provided here is for general informational purposes and does not constitute legal advice. For advice on specific matters, consulting with a legal professional is recommended.
  • Does OpenSign™ provide a timestamp for digital signatures?
    Yes, OpenSign™ integrates timestamping into the digital signature process, providing an additional layer of validation and legal certainty regarding the time at which the document was signed.
  • What steps should I take to ensure my digitally signed documents are legally valid?
    While OpenSign™ provides a platform for digital signatures, legal validity also depends on the nature of the document, the identity verification of the signatories, and the laws of the jurisdiction. It is advisable to consult legal counsel to ensure all criteria for validity are met.
  • Is electronic signature the same as digital signature?
    No, electronic signatures are broader in definition and include any electronic process that indicates acceptance of an agreement or a record(for example annotating a PDF by drawing or typing a signature), whereas digital signatures are a specific type of e-signature using cryptographic techniques.
  • Can digital signatures created with OpenSign™ be used in court proceedings?
    Digital signatures created with OpenSign™ are intended to be legally robust. However, the admissibility of digital signatures as evidence in legal proceedings can vary and is determined by the laws of the jurisdiction in which the court is located.
  • How does OpenSign™ handle cross-border transactions?
    OpenSign™ facilitates the creation of digital signatures that are intended to be recognized globally. However, users should ensure that such signatures meet the legal requirements of all relevant jurisdictions in cross-border transactions.
  • Are digital signatures legally binding across different countries?
    Yes, digital signatures are legally binding in numerous countries, provided they adhere to the specific regulations and standards set forth by each jurisdiction, such as the eIDAS regulation in the European Union, the ESIGN Act in the United States, and similar laws in other regions.
  • How does OpenSign™ ensure the security of digital signatures?
    OpenSign™ employs advanced cryptographic techniques to ensure the integrity, non-repudiation, and authenticity of digital signatures. It utilizes industry-standard protocols to safeguard against unauthorized access and tampering.
  • Does OpenSign™ comply with global digital signature laws?
    OpenSign™ is designed to comply with the highest standards of digital signature technology, and while it facilitates the creation of digital signatures, the legal compliance in any given jurisdiction depends on the use case and adherence to local laws. OpenSign™ encourages users to consult with legal experts to ensure compliance with regional legislation.
bottom of page