Privacy policy
Draft—complete the bracketed details before inviting real users.
Effective date: [EFFECTIVE DATE]
This policy describes how [OPERATOR LEGAL NAME] (“we,” “us,” or “our”) handles personal information in connection with this application (the “Service”). It addresses what information is collected, why it is used, who receives it, how long it is kept, and the choices or rights that may be available. Contact us about this policy or your information at [PRIVACY CONTACT].
[COMPLETE: Identify the Service and people covered by this notice. If the operator handles information for another organization, explain that relationship and the relevant contact. Do not claim a controller, processor, business, or service-provider legal status without confirming the actual arrangement.]
Information we collect and why
Personal information can include information you provide directly, information created as you use a service, and information supplied by others. The categories actually collected by this Service, their sources, and the purposes for using them are set out below. A category is not permission to collect information that has not been disclosed or to use it for an unrelated purpose.
[COMPLETE: Replace this block with the actual categories, sources, and uses. For an account-enabled application, cover login identifiers, account/profile fields, authentication and recovery records, and content users create or share. Check the running application and its providers for request or security logs, device information, support correspondence, and any other collection. Add payment, analytics, advertising, location, sensitive information, or information from third parties only when actually present. State the applicable processing bases where required. Do not turn this list of possibilities into a claim that all are collected.]
Information necessary to provide a requested function can be different from information requested for an optional purpose. [COMPLETE: Explain which information is required or optional, what happens if it is not provided, and the actual controls for optional communications or other optional uses.]
Cookies and similar technology
A cookie is a small piece of information stored by a browser. Browser controls can generally block or delete cookies. Restricting a cookie needed for a particular feature can prevent that feature from working. Other storage and tracking technologies may require different controls.
[COMPLETE: Describe this Service's actual cookies and similar technologies, their purposes and lifetimes, any third-party access, and the controls users can exercise. Verify session and security storage. Explicitly settle any analytics or advertising use and any required choices. Include any advertising or CAPTCHA services actually used.]
Access, sharing, and service providers
The fact that information is stored by an application does not by itself explain who can see it. Information shared with other users, access by the operator, and processing by outside providers need separate descriptions.
[COMPLETE: Explain the actual visibility of content and account information to other users, administrators, the public, and organizations administering an account. Describe staff access and its purposes. Identify actual providers or recipient categories and the data and purposes involved, including hosting, email, storage, support, payment, analytics, and any AI processing that is used. Describe any other disclosures, including legal requests, protection of rights, or a business transfer. State the actual sale, sharing, targeted-advertising, and training practices and applicable choices. Do not promise “we never sell,” “staff only access with consent,” or “we never train models” without verified practices supporting the statement.]
If you follow a link to another service or choose to provide information to another provider, review that provider's privacy notice as well. This notice does not establish the practices of an independent third party.
Retention, removal, and account closure
Removing content from an application screen, closing an account, and deleting all retained copies are different operations. A useful retention description must account for the information still held in active systems, logs, backups, and provider systems, as well as any applicable preservation obligations.
[COMPLETE: State the actual retention periods or concrete criteria for each relevant category, the account-closure and content-deletion process, any backup or provider delays, and any lawful exceptions. Explain how to request deletion and what remains afterward. Confirm the process operationally. Include retained copies in backups and provider systems; do not promise deletion deadlines that the operator cannot meet.]
Security and processing locations
No online service can promise complete security. Information about safeguards should describe measures that are actually used, rather than imply that risk has been eliminated.
[COMPLETE: Describe the security measures the operator can accurately state, the actual processing/storage countries, and any applicable international transfer arrangements. Confirm provider and backup locations as well as the application host. Do not promise encrypted backups, particular certifications, U.S.-only storage, or a data-processing addendum that has not been established.]
Your choices and rights
Depending on applicable law and the circumstances, you may have rights to access or obtain a copy of personal information, correct it, request deletion, restrict or object to particular processing, withdraw consent for processing based on consent, or receive information in a portable form. Some laws provide choices about sale, sharing, targeted advertising, or significant automated decisions. Rights may be subject to conditions and exceptions; their availability depends on the law that applies to you and the relevant processing.
To raise a privacy question or request, contact [PRIVACY CONTACT]. We may need information to verify that a request concerns you, or that you are authorized to act for someone else. Do not send passwords in a privacy request. A request to delete information needed for an account or feature may affect the availability of that account or feature.
[COMPLETE: Provide the actual request channels, verification and response process, account controls, applicable opt-out and consent-withdrawal mechanisms, and any required appeal, representative, or supervisory-authority information. Confirm applicable rights and regional disclosures for the intended audience. Do not claim that every right or a self-service export/delete control is available everywhere.]
Audience and changes to this policy
[COMPLETE: Explain the intended audience and any age restrictions or practices involving children. Confirm the actual audience and any practices involving children's information.]
[COMPLETE: Describe how the operator will keep this notice current and communicate changes, including any legally required notice or new choice. Use an effective date that reflects the completed policy. Terms acceptance at signup is not consent to unrelated processing or marketing.]
Questions about this policy or personal information: [PRIVACY CONTACT].