What information this site may receive
If you use the contact form, the site can receive the information you enter, such as your name, email address, selected service, project summary, and any optional project details you choose to provide.
This page is a practical website privacy draft based on the current site setup. It is not presented as legal advice or as reviewed legal counsel.
If you use the contact form, the site can receive the information you enter, such as your name, email address, selected service, project summary, and any optional project details you choose to provide.
The current site uses a Netlify-compatible contact form setup. In production, submitted form data is posted securely through the configured form handling flow. TechneOG should only use submitted contact details to review the enquiry and respond through the details you provided.
This site only attempts to load Google Analytics if a valid Google Analytics ID is configured and the visitor has accepted analytics cookies through the on-site consent banner. If no valid analytics ID is configured, the banner is hidden and analytics are not loaded.
The site includes local event hooks for safe analytics-style tracking such as CTA clicks and contact form state changes. These event payloads are designed not to include personal form content like name, email address, phone numbers, free-text messages, or other user-written answers.
The current site uses browser storage for theme preference and analytics consent preference. If analytics is enabled through consent, Google Analytics may also use cookies or related technologies as part of its service.
This site provides a contact form, a public email contact option, and a WhatsApp contact option for direct enquiries. TechneOG should only use submitted contact details to review the enquiry and respond through the details provided or through the published contact routes.
This page may be updated as the site setup, hosting, analytics, or public business details change. If formal legal review is needed, that should be handled separately by the site owner.