Security was our most important design consideration. Like all credible e–commerce sites sensitive credit card information is always collected on and transmitted to SSL	encrypted pages. However, we go beyond that.
Credit card processing is done by linking our site to the secure servers at a payment gateway like Authorize.net, a leading provider of Internet Protocol (IP) based payment gateway	services since 1996. The gateway servers	receive the credit card information we send, process the transaction, and then send us back the transaction approval (or	rejection).
So all we do with a credit card number is transmit the number securely to the gateway and then discard it.	We	designed	our	system	to	ensure	that we	never have to store	credit	card	numbers	on our	servers. Amplify, the event administrator, and any potential hacker have no access	to	a registrant's	credit	card	number.
Registrants do not have to allow cookies when registering through our pages. It was a basic design criteria from the	beginning.
We do not sell or otherwise provide any information in our	database to third parties unless legally required to do so.
No third parties are involved in handling credit card information.
If you do chose another registration vendor, check the procedures they use to protect your registrants' credit card information. At the right we give some of the ways that security can be breached.
Is credit card number information collected on a	non-secure	web	page (no https://... in the page address)?
Does the registration data base include credit card information? If so, what security measures are taken to protect the information (are strong passwords enforced, who has access, how is access controlled)?