Supporting Docs (Why, What, Where?)

Card Offices may elect to request Supporting Documentation from their cardholders.  Organizations use this supporting documentation to verify for themselves that the person submitting the photo is the intended recipient by having the user submit a photo ID with the cardholder’s name on it.  


The photo is compared to the submitted photo for facial recognition and given a confidence score that the 2 photos are indeed the same person.  RemotePhoto is Optical Character Recognition (OCR) enabled to collect text from a submitted ID and compare it to text entered for the cardholder within RemotePhoto. 


HelperBot is proprietary, meaning it belongs exclusively to CloudCard for use in RemotePhoto and is not shared with or connected to any facial recognition database.  HelperBot performs facial recognition, calculates a confidence score, and makes it visible only within the Organization Card Office that has requested the Supporting Documentation.  


Any Supporting Documentation that is collected will be deleted either at download of the submitted photos or deleted at a maximum of 180 days. The organization may make this time less, but cannot increase past 180 days. 


Some Frequently Asked Questions -

Does the ID have to be Government Issued?


  • No, these are often the easiest to request.  Card Offices can request most types of picture identification that contains text such as name, address, etc. for them to validate cardholder to submitted photo. 

Is my ID secure?


  • All photos, supporting docs, information, etc. are encrypted in transit using HTTPS and TLS v.1.2 and at rest using AES-256. 

Is my ID sent through a security, government, or facial scanning database?


  • No. HelperBot only compares the submitted photo to the photo on the ID.  

What about CloudCard employees?


  • all CloudCard staff are subject to background checks, non-disclosure agreements, security policies, and security training
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us