While setting up a production Authorize.net account for the OT compact, we were requested to share the privacy policy for the Compact Connect Application. This is not currently defined. The system does collect email addresses at the time of user registration, and Authorize.net collects billing information in order to process credit card transactions
We will be working with legal to help define this privacy policy for us. Once it is defined, this ticket involves including that privacy policy so that users may view it.
Notes
Currently, Authorize.net collects the card number, cvv, expiration, first and last name of cardholder, and zip.
Questions
- Q: Do we need a privacy policy for staff users as well?
- Q: Does the practitioner privacy policy need to include what information Authorize.net collects?
Assumptions
- Assumption text...
Estimate: ?? hrs
Implementation Notes
QA Notes
While setting up a production Authorize.net account for the OT compact, we were requested to share the privacy policy for the Compact Connect Application. This is not currently defined. The system does collect email addresses at the time of user registration, and Authorize.net collects billing information in order to process credit card transactions
We will be working with legal to help define this privacy policy for us. Once it is defined, this ticket involves including that privacy policy so that users may view it.
Notes
Currently, Authorize.net collects the card number, cvv, expiration, first and last name of cardholder, and zip.
Questions
Assumptions
Estimate:
?? hrs?? hrsImplementation Notes
QA Notes