Legal
What we collect, and who ever sees it.
A summary of the published privacy policy, in the order people actually ask. It is a summary, not the policy. Where the two disagree, the published document wins.
Ten answers from the policy.
| The question | What the policy says |
|---|---|
| Who holds the data | AXL EdTech Booster, LLC, 16192 Coastal Highway, Lewes, Delaware 19958, USA. |
| What is collected about you | Information that identifies you, gathered when you register, buy, contact support or join a webinar. |
| Card numbers | The policy states the company does not directly collect card numbers for the platform; payment is handled through shopping-cart and gateway providers. |
| What the servers log | Date and time, IP address, device, operating system, browser, language, login details, ISP, and the pages you arrived from and left by. |
| What it is used for | Running your account, service messages you cannot opt out of, optional marketing you can, plus auditing, analysis and product research. |
| Who it is shared with | Service providers doing the work (hosting, email, payments, banking, video, support), contractually bound to protect it. Also on lawful legal process, and to a buyer or trustee in a sale, merger or bankruptcy. |
| Is it sold | The policy states personal information is not shared with third parties for their marketing. |
| Your rights | Access, correct or delete your data by writing to support@axl.tech. Deletion can be refused where it is legally required, needed for a legitimate business purpose, or would take undue effort. |
| How it is protected | Commercially reasonable measures, access restricted to staff under confidentiality obligations, and SSL on pages that carry personal or financial data. How the platform itself is fenced is on the security page. |
| Children | Restricted to people aged 18 and over. The policy says it does not knowingly collect information from anyone under 18. |
| If you connect Google Meet | The calendar-events scope only, to create, update and delete booking events. Never used for advertising, never sold. Tokens are encrypted at rest and deleted on request after you disconnect. |
Restated from axl.tech/docs/privacy, which is the text that governs. Nothing here grants a right the policy does not, and nothing here removes one.
Six questions the policy does not answer.
These are the ones a procurement review opens with. The published policy does not cover them, so this page will not pretend to.
- •How long data is kept. No retention period is stated, for any category, in either document.
- •Which sub-processors. The policy names categories of provider, not companies. We could not find a published list; tell us you need one and we will say where it stands.
- •A Data Processing Agreement. Not offered in the policy. Ask before you assume one exists.
- •GDPR machinery. No lawful basis, supervisory authority or EU representative is named, and there is no CCPA section. AWS in Frankfurt is a hosting fact, not a compliance claim.
- •How fast a deletion request is answered. The policy commits to “reasonable” requests without a deadline.
- •Which cookies, by name. The policy describes cookies in general terms and names none. We listed the ones we could verify ourselves: the cookie page.
Ask at info@axl.tech and you will get a plain answer, including where it is “not yet”.