I am making an online version of an application for a customer, and part of the application is a "authorization to release personal information" waiver. I need to have something in place to accept and record the authorization, but it is not a tablet app, so signing is not an option.
I figure I will just add a checkbox with some code to not allow the user to continue without checking it, but I need to know what the behind the scenes standards are. All the info on the app is being stored in a server so, should I add a bit field in the db for 'accepted waiver' or something like that?
I've run across this before, but I have seen it plenty on the web. If I could get a link to an article with the official word, that would be super.
Thank you for reading my post and yes, I proudly wear a neck beard.
1 Replies - 193 Views - Last Post: 24 September 2012 - 04:13 PM
Replies To: Legally acceptable mechanisms for signatures, waivers, etc, on the web
Page 1 of 1