Who we are
[Legal entity name, registered address, and the contact details of the person or team responsible for data protection enquiries. Name your Data Protection Officer if you are required to have one.]
Legal
This page is a placeholder structure and is excluded from search engines until the final text is in place.
Draft structure
Last updated: [date]. Replace every bracketed section below with reviewed text.
[Legal entity name, registered address, and the contact details of the person or team responsible for data protection enquiries. Name your Data Protection Officer if you are required to have one.]
[List each category: information submitted through forms or email, information collected automatically such as IP address and browser type, and anything collected via cookies or analytics. Be specific, vague categories are the most common weakness in a policy.]
[For each purpose (answering enquiries, delivering services, recruitment, marketing), state the purpose and the lawful basis you rely on (consent, contract, legitimate interests, legal obligation).]
[Which cookies you set, which are strictly necessary, and which require consent. Name your analytics provider and link its policy. If you deploy anything beyond strictly necessary cookies, you need a consent banner before it loads: the site does not have one yet.]
[Named categories of processors: hosting, email, CRM, analytics. State whether data is transferred outside its country of origin and what safeguards apply.]
[Retention period per category, and what triggers deletion.]
[Access, correction, deletion, portability, objection, and withdrawal of consent, plus how to exercise them, how quickly you will respond, and which regulator a visitor can complain to.]
[The measures you actually take: encryption in transit and at rest, access control, staff training, breach notification process. Do not describe controls you do not have.]
[How you notify people about changes, and the date this version took effect.]
Contact for privacy enquiries: info@infoane.com