PRIVACY POLICY
Introduction
DRAFT — COMPLETE BEFORE PUBLICATION. [EDIT: Describe the scope of this privacy notice, the services it covers and the legal entity responsible for personal information. Confirm which activities actually take place on your website before publishing.]
[EDIT: Explain the purpose of this notice and the markets or audiences it covers. Do not assume the laws cited by another brand apply to your business.]
[EDIT: Explain which information is necessary to provide your services, which is optional and the consequences of not providing it. Ensure that the wording matches the fields used in your checkout and forms.]
[EDIT: Identify any separate privacy information for recruitment, business partners or other activities. Remove references to services that you do not offer.]
[EDIT: Add links to your own related policies where appropriate. No reference-brand links are included in this template.]
About us
[EDIT: Enter the registered legal entity operating AETARE, its business registration details where required, and its role in handling personal information.]
[EDIT: Provide a working privacy contact email or request channel, and identify any relevant representative or privacy officer only if applicable.]
AETARE[EDIT: Legal entity name]
[EDIT: Business mailing address]
[EDIT: City, postal code and country]
[EDIT: Explain any external websites or independently operated services relevant to this notice and where their own privacy information can be found.]
Information collected and how it is used
[EDIT: Confirm the data categories you actually process. The table below is a layout and review checklist, not a statement that all listed categories are collected.]
| Category | Details to confirm |
|---|---|
| Identity and contact details | [EDIT: Specify the names, delivery contacts or other identifiers actually collected and their purposes.] |
| Profile information | [EDIT: Include only optional or required profile fields actually used; explain their purpose.] |
| Payment information | [EDIT: Distinguish provider-held payment credentials from transaction references visible to the store.] |
| Official identity records | [EDIT: Remove if not collected. If applicable, specify the limited circumstances and relevant purpose.] |
| Sensitive or protected characteristics | [EDIT: Remove if not collected. Review any applicable special requirements before including this category.] |
| Order and return records | [EDIT: Specify the actual transaction information retained for fulfilment, support or other stated purposes.] |
| Browsing and service activity | [EDIT: List the actual logs, analytics or event data generated by enabled services.] |
| Device and account identifiers | [EDIT: Identify the relevant technical identifiers and the services that receive them.] |
| Location information | [EDIT: Distinguish a delivery address or approximate location from precise location tracking; remove unsupported claims.] |
| Audio or visual material | [EDIT: Include only recordings, images or uploads actually processed for a stated purpose.] |
| Business or recruitment records | [EDIT: Describe relevant partner or applicant information, or remove if outside this notice's scope.] |
| Preferences and inferred interests | [EDIT: Include only profiling or inferred information that your systems actually create, with its purpose.] |
Customers and enquiries
[EDIT: Describe information used for orders, accounts, delivery, returns and customer support. Identify the source and purpose of each category, distinguishing information received by the store from information handled directly by payment providers.]
- [EDIT: Information needed for order fulfilment and account administration.]
- [EDIT: Support messages and related order references.]
- [EDIT: Any optional information and how the customer can choose not to provide it.]
Email subscriptions and marketing
[EDIT: Identify the actual subscription service, enrolment method, message tracking if enabled, and available unsubscribe or preference controls. Do not promise controls that have not been implemented.]
Site visitors and cookies
[EDIT: Audit the cookies, analytics, advertising tools, server logs and embedded services active on your site. Explain what they collect, why, and how the visitor can manage relevant choices.]
[EDIT: Name your actual preference-management method and cookie notice if applicable. This page alone does not create a consent banner or disable tracking tools.]
Business contacts
[EDIT: Describe supplier or partner information only where this activity is covered by the notice. Remove this subsection if covered separately.]
Recruitment
[EDIT: Include applicant processing only if you accept applications through the services covered here. Otherwise remove this subsection or refer to an appropriate separate notice.]
Basis for processing
[EDIT: Have the basis for each processing activity assessed under the laws applicable to your business and customers. Match it to the purposes described above rather than copying a generic list.]
- [EDIT: Activity, applicable basis and any required explanation.]
- [EDIT: Where consent is used, explain how it is obtained and withdrawn.]
- [EDIT: Where applicable, identify relevant obligations or interests with suitable detail.]
Recipients and transfers of information
[EDIT: List the actual categories of recipients and their purposes, such as the providers used for payments, delivery, hosting, email and analytics. Check how each service processes the information.]
[EDIT: Explain any other disclosures that apply to your business. Make accurate statements about advertising-related sharing or sale where relevant; do not insert an unsupported promise that information is never shared.]
[EDIT: Identify applicable cross-border processing and any required safeguards or disclosures. Do not name agreements or transfer mechanisms that your business has not verified.]
Retention of personal information
[EDIT: Enter the actual retention periods or meaningful criteria for orders, support records, marketing subscriptions, analytics and other data described in this notice.]
[EDIT: Describe any necessary distinctions for records retained to meet obligations, backups or disputes, and ensure the wording matches your deletion and retention procedures.]
Protection of personal information
[EDIT: Describe appropriate safeguards that are actually in place without exposing confidential security details or promising absolute security.]
[EDIT: Include the verified contact process for reporting a privacy or security concern and any appropriate information about incident handling.]
Privacy choices and rights
[EDIT: Explain the rights and choices available to the people covered by this notice under applicable law. Avoid presenting rights, exceptions or response deadlines from another jurisdiction as universally applicable.]
- [EDIT: Applicable access, correction or deletion request arrangements.]
- [EDIT: Applicable portability, objection or restriction arrangements.]
- [EDIT: Relevant consent withdrawal, marketing and tracking choices.]
[EDIT: Give the actual request channel, proportionate verification process, applicable timing and any available escalation or appeal process. Never ask users to send passwords or session cookies as proof of identity.]
Location-specific information
[EDIT: Insert regional disclosures only after determining which requirements apply to your business. Identify the region and keep this wording consistent with the rest of the notice.]
Children and younger users
[EDIT: Describe your intended audience, any applicable age-related rules and the steps taken if information from a child is identified. Do not choose an age threshold merely because another store uses it.]
Privacy enquiries and complaints
[EDIT: Provide your working complaint channel and the process for handling privacy concerns. Include any applicable regulator or appeal information after reviewing the relevant jurisdiction.]
Updates to this privacy notice
[EDIT: Explain how revisions are published and how significant changes are communicated where appropriate. Set the revision date only when the final policy has been approved.]
[EDIT: Approved policy revision date]
