Last updated: October 8, 2026
This notice explains how GlideAX handles information through glideax.com, our enquiry form, website chat and Security Risk Advisor. For privacy questions or requests, email support@glideax.com with “Privacy” in the subject.
Please do not enter passwords, API keys, security logs, confidential documents or sensitive personal information into the website form, chat or assessment.
Enquiries and conversations
When you contact us, we receive the details you provide, such as your name, email address, organization, organization size, service interests, preferred timeline and message. We use them to respond, understand your request and discuss suitable services. Our contact form uses WPForms and sends enquiries to our business email hosted by Hostinger. WPForms entry backups are currently disabled.
Website chat is provided by tawk.to. It processes messages, contact details you choose to provide and technical information such as IP address, browser information, visited pages and timestamps. Chat is for general enquiries; it is not an emergency incident-reporting channel. A customer engagement may have separate agreed contact and information-handling arrangements.
The security assessment
The assessment asks for categorical business context and self-reported security practices. It calculates scores and recommendations in your browser. It does not connect to your accounts, scan your infrastructure or verify your answers. The assessment does not require a name or email address.
Answers and results are held in the assessment’s working browser session. You can clear them using “Clear answers and results.” A report you download is saved to your device, where you control its storage and sharing. Sending a report to GlideAX is a separate choice.
Optional AI processing
You can use the scored assessment and roadmap without requesting AI processing. If you authorize and request an AI briefing, your selected assessment answers are sent through GlideAX’s server to OpenAI to generate additional explanations and priorities. Contact-form messages and chat conversations are not included in that assessment request.
Our AI integration does not save assessment answers or generated briefings to its own database. It uses the API’s “store: false” setting. This does not mean zero retention by the provider: OpenAI may keep abuse-monitoring logs containing inputs and outputs for up to 30 days, or longer for legal or safety reasons. OpenAI states that API data is not used for model training by default. See OpenAI’s API data controls.
To control abuse and usage, the integration keeps usage counters and a temporary identifier derived from your IP address. The rate-limit identifier expires after one hour. Hosting and security systems may keep separate technical logs. AI explanations can be inaccurate and do not establish compliance or confirm that an environment is secure.
Cookies, analytics and technical information
Our hosting and website services process technical information, such as IP addresses, requested pages, browser details and timestamps, to deliver and protect the website. WordPress uses cookies for administrator sign-in. The chat service uses cookies and browser storage to operate conversations and recognize a session.
The website uses Google Analytics to understand visits, traffic sources and page interactions. Google may process online identifiers, device and browser information and approximate location. This notice does not itself block cookies or make analytics conditional on consent.
You can manage or delete cookies through your browser and use Google’s Analytics opt-out browser add-on. Blocking cookies or scripts may affect chat or other features. You can contact us by email instead of chat and use the assessment without its optional AI briefing.
Service providers and international processing
We use service providers to host the website, deliver email, operate chat, measure website use and generate an optional AI briefing. These include Hostinger, tawk.to, Google and OpenAI. Information may be processed outside Canada, including in the United States, and may be subject to laws and lawful access requirements in those locations.
Read the provider notices for details: Hostinger, tawk.to and Google. Links to LinkedIn or other external websites take you to services with their own privacy practices.
How long we keep information
For enquiries and chat conversations that do not become customer engagements, our retention policy is to review and delete the records 12 months after the last contact, unless an ongoing request, dispute or legal obligation requires longer retention. This is a review-and-deletion policy, not a promise of automatic deletion on a particular day. Residual copies may remain in backups until those backups expire under the provider’s process.
Customer engagement records are retained according to the agreed service arrangements and applicable recordkeeping requirements. Provider security logs, analytics records and AI processing have their own retention settings and requirements; the 12-month enquiry policy does not override those systems.
Your choices and privacy requests
You can ask what personal information we hold about you, request access or correction, request deletion, or withdraw consent for an optional use by contacting support@glideax.com. We may need to verify your identity and clarify the request. Rights and exceptions depend on applicable law, including requirements to retain certain records. Withdrawing consent does not undo processing already completed and may affect a service that depends on the information.
We will review privacy concerns and explain our response. If a concern remains unresolved, you may contact the relevant privacy regulator, including the Office of the Privacy Commissioner of Canada.
Security and changes to this notice
The website uses HTTPS. No internet service can guarantee absolute security. Share only the information needed for your enquiry; agree a suitable transfer method with us before sending sensitive evidence for a professional engagement.
We will update this notice when our practices change and show the revision date above. Where a new purpose requires additional consent, we will seek it before using information for that purpose.