A Project of |
Guidelines | Rants | Patterns | Poems | Services | Classes | Press | Blog | Resources | About Us | Site Map |
Home > Patterns > How to write a privacy policy > Explain security before and during the transaction |
|
Explain security before and during the transactionDon't just dash off a little paean to security in your general FAQ. Explain what makes your server secure, and why that matters to me, as a consumer--before I have to enter my credit card number. And put a condensed version inside any forms I have to fill out to complete the buy. Point out how your consumers can tell if they are really on a secure server (the change in the URL, the icons that show up on the status bar). In other words, tell people what you take for granted, as obvious, about security. Say more than you think is really needed, and folks will be grateful. Take a shot at explaining encryption, and the Secure Sockets Layer, if you dare. But concentrate on the benefits to the consumer. Most online transactions are safer than a trip to the local dry cleaner (where they keep a paper copy of your information), and a lot safer than e-mail. Explaining security is hard work Trying to explain why your site is more secure than a local restaurant can be a challenge, particularly when you are really just writing a label on a form. Sure, you can link to a fuller explanation in the FAQ or Privacy Policy, but make a solid effort to capture the gist of those ideas at the moment of action, so most people don't have to leave the page to learn what is going on. |
Related article Privacy policy, a chapter from Hot Text, Web Writing that Works (PDF, 255K, or about 5 minutes at 56K) |
Is this what I ordered?
Home |
Guidelines |
Rants |
Patterns |
Poems |
Services |
Classes |
Press |
Blog |
Web
Writing that Works!
|