question

Frequently Asked Questions

KloudSigning is a web application that enables users to obtain electronic signatures for PDF files.

"Beta" refers to the phase of the software development cycle in which software is feature-complete but may have performance issues or contain unknown bugs, or issues.

The current version of KloudSigning is available as a closed beta release. This means that we are limiting the number of active users so that we can:

  1. Evaluate the ability of our infrastructure to scale as our user base grows
  2. Identify any remaining bugs, or issues
  3. Ensure our service provides a smooth and intuitive user experience

If you believe you have found a bug in our software, please visit our Contact Us page for information about how to direct your communication to us.

Adobe Acrobat Reader DCTM. KloudSigning is intended to be used in conjunction with Adobe Acrobat Reader DCTM. At this time, document certification and electronic signature validation is only supported using Adobe Acrobat Reader DCTM. KloudSigning is not affiliated with AdobeTM in any way. Support questions should be directed to support@kloudsigning.com and not to AdobeTM.
No. Signing credits do not expire at the end of the month or ever. You paid for them; so, you should be able to use when you need them.
If emails are not being received from KloudSigning, please check your "Spam" or "Junk" mail folder. We are working hard to manage our email delivery reputation, but some messages are still filtered by some email service providers. You can help us out by adding notifications@kloudsigning.com to your trusted contacts.
  1. Fonts: Lesser-known, proprietary fonts, or fonts that require a license, are not supported. If your PDF document contains such fonts, a fallback font will be used in its place when displaying the pages of your PDF to users during the document signing process.
  2. Page color: PDF pages should be white. We use black text when creating the electronically signed documents; so, if you have colored pages, the auto-inserted fields (names, initials, date, signature) may not be visible in the final, signed PDF file.
  3. KloudSigning uses a self-signed Certificate Authority to generate certificates for our servers to digitally sign PDF files. Our CA is not universally trusted yet (we hope it will be in the future). As a result, you must manually trust the KloudSigning CA in order to validate the digital signatures created by our service. No need to worry, the trust process is simple, and we provide a straight-forward guide to help you. You can access it here.
Because Adobe Acrobat Reader DCTM does not initially trust the KloudSigning Certificate Authority, Acrobat ReaderTM cannot validate the document certification. Please follow these steps to configure Acrobat ReaderTM to trust the KloudSigning Certificate Authority. KloudSigning is not affiliated with AdobeTM in any way. Support questions should be directed to support@kloudsigning.com and not to AdobeTM.
Because Adobe Acrobat Reader DCTM does not initially trust the KloudSigning Certificate Authority, Acrobat ReaderTM cannot validate the document certification. Please follow these steps to configure Acrobat ReaderTM to trust the KloudSigning Certificate Authority. KloudSigning is not affiliated with AdobeTM in any way. Support questions should be directed to support@kloudsigning.com and not to AdobeTM.
You must contact the party that requested your signature. You will need to ask them to send you a copy of the signed document, the signing log, and a copy of your signed Electronic Signature and Delivery Disclosure and Consent.