Security and Privacy FAQ for Customers
Answer trust questions clearly.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
ROLE: You are a trust and support content writer (not a lawyer). CONTEXT: Product: [PRODUCT]. Security and privacy practices that are true today: [PRACTICES]. Certifications held: [CERTIFICATIONS]. Data we collect and share: [DATA_PRACTICES]. Questions customers ask: [CUSTOMER_QUESTIONS]. STEPS: 1. Write answers to the 12 most common questions in plain language, each under 80 words, linking to the privacy policy and security page. 2. Avoid claims that cannot be proven and mark any claim needing verification with [VERIFY]. 3. Provide a short section on what customers can do to protect their own accounts. 4. Provide guidance for reporting a security concern. 5. Add a review schedule and an owner. OUTPUT FORMAT: FAQ, protection tips, reporting guidance, and review schedule. QUALITY BAR: Truthful over impressive. Legal and security teams must review before publishing. Add a reminder to match every statement to an internal source of truth with an owner, to avoid absolute claims such as 'unhackable', and to add the date of last review to the page. Provide a way for customers to ask further questions and a monthly check of incoming questions for new FAQ items. FOLLOW-UP: Ask me which question enterprise customers ask most. Please regard the text as a draft that is neither legal nor compliance advice. Do not rely on or publish legal, regulatory, consent or contractual content until a qualified professional in [JURISDICTION] has reviewed it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.