Privacy Policy

1. Who we are

Axiovex Systems, LLC ("Axiovex Systems," "we," "us," or "our") is a Michigan company. This Privacy Policy explains how we handle information when you visit axiovexsystems.com (the "Site"). If you have questions about this policy, contact us at [email protected].

2. Information we collect

Information you provide. The Site has no accounts. (The separate Arcturus application described in section 18 is different: the organizations that take part in the program hold accounts there.) You can share personal information with us directly in six ways: by emailing us; through the contact form, which asks for your name, email address, topic, and message, and optionally your company; through the support form on our Support page, which asks for your name, reply email address, and a description of the problem (see the support section below); through the correction form at the end of our articles and on our Corrections page, which asks what looks inaccurate and, only if you want a reply, your email address (see the correction reports section below); by signing up for our newsletter with your email address (see the newsletter section below); or by joining one of our other lists — the pilot program waitlist or occasional marketing emails — with your email address and, for the waitlist, your name, company or organization, and role, and optionally your phone number, website, and a short note on what you are hoping to gain (see the lists section below). The contact form delivers your message to our mailbox, and we do not store form submissions anywhere else. Correction reports are the exception: they are stored in the Site's database so they can be checked and tracked, as the correction reports section below describes. Both forms are protected by Cloudflare Turnstile, a spam check run by Cloudflare (see the cookies and local storage section).

Information collected automatically. The Site is a static website hosted on Cloudflare Pages. Like most websites, our hosting provider processes limited technical data to deliver and protect the Site, such as your IP address, browser type, and the pages you request. We review aggregate statistics derived from this technical data — for example, how many requests each page receives and which countries the requests come from — to operate the Site. Those statistics are computed from our hosting provider's server logs; no analytics script runs in your browser. We do not combine this data with any other personal information. When you sign up for one of our lists, our anti-abuse rate limiting also records a one-way cryptographic hash of your IP address — never the address itself — so automated abuse can be slowed down. The contact and support forms do not record your IP address in any form.

What we do not collect. We do not use analytics scripts, advertising pixels, or other cross-site tracking technologies, and we do not set cookies of our own (the next section explains the full picture). We do not build profiles of visitors, and we do not knowingly collect information from children.

3. Cookies and local storage

Cookies. We do not use cookies for tracking, advertising, or analytics, and nothing on the Site reads cookies set by anyone else. One feature can set a single first-party cookie: if you use the article Like button, the random token described below may be stored as a cookie for this Site only, as a fallback for browsers that do not keep local storage, so your like is still there when you come back. That cookie holds the random token and nothing else. Because we run no optional tracking, there is no cookie banner and nothing to opt out of here.

The spam check on our forms. The contact form, the support form, the correction form, the newsletter signup, and the pilot waitlist signup each include a spam check called Turnstile, run by Cloudflare. The check runs in a frame served by Cloudflare, and while it runs Cloudflare may use its own strictly necessary storage on its own domain (challenges.cloudflare.com). That storage belongs to Cloudflare, exists only to tell people from automated bots, and is not used to track you across other websites. If you block it, the forms cannot verify a submission and will not send.

Local storage on your own device. A few features keep small pieces of information in your browser's local storage, on your device only. They are never sent to us or to anyone else:

• Whether you dismissed the breaking-news banner, so it stays dismissed;
• For our audio editions, where you stopped listening — the chapter and the position, kept for seven days so you can pick up where you left off — and the playback speed and narrator voice you chose.

The article Like token. If you tap Like on an article, your browser creates a random token and keeps it in local storage, or in the cookie described above where local storage is not kept. The token is sent to us with your like and unlike requests, and what we store on our side is only a one-way cryptographic hash of it, next to the article it belongs to (see section 19). The token is not linked to your name, an account, or an email address. To remove it, unlike the article or clear this Site's data in your browser.

You can clear these at any time through your browser's site-data settings; the Site works without them. All of the Site's media, including the audio editions, is served from this Site itself, so no outside media service sees what you read or listen to here.

4. How we use information

We use the information described above only to:

• Operate, secure, and maintain the Site;
• Respond to emails and inquiries you send us;
• Check correction reports and correct the Site's published content where a report is right;
• Count article likes in aggregate, as section 19 describes; and
• Comply with legal obligations.

We do not use your information for advertising, and we do not sell or share your personal information with third parties for marketing purposes.

5. How we share information

We share personal information only in these limited circumstances:

• Service providers. Companies that help us operate the Site process information on our behalf and only as instructed by us: Cloudflare hosts the Site, runs the spam checks on our forms, and stores the newsletter subscriber list and the Site's database, which holds correction reports and article like counts; Microsoft (Microsoft 365) provides our email, receives contact-form deliveries, and sends the newsletter from our own mailbox; GitHub stores support reports submitted through our Support page, in a private repository that only Axiovex staff can access (see the support section below). We use Resend to send report mail and other email we originate. Article narration is synthesized by ElevenLabs from the article text we publish; no visitor information is sent to it.
• Legal requirements. If required by law, court order, or government request, or where we believe disclosure is necessary to protect our rights, visitors, or the public.
• Business transfers. In connection with a merger, acquisition, or sale of assets, information may be transferred as part of that transaction.

6. Data retention

We keep email correspondence for as long as needed to respond to your inquiry and maintain business records, then delete or archive it when it is no longer needed. Newsletter records are kept while you are subscribed; if you unsubscribe, we keep your address only on a suppression record so it cannot be re-added without a fresh confirmation (see the newsletter section). A newsletter confirmation link expires after 48 hours. Pilot waitlist records are kept while the pilot is forming and running, and unconfirmed entries on any of our lists are deleted 30 days after signup (see the lists section). Technical logs retained by our hosting provider are subject to that provider's own retention practices. Correction reports are kept as part of the Site's correction record; an email address left on a correction report is deleted 90 days after the report is settled (see section 19). Article like counts are kept as aggregate counts, and the hashed tokens behind them are kept while those counts are maintained.

7. Data security

We use reasonable administrative, technical, and physical safeguards to protect information in our care, including encrypted (HTTPS) connections to the Site. No method of transmission over the internet is completely secure, and we cannot guarantee absolute security.

8. Your rights

Depending on where you live, you may have rights over your personal information:

• California residents (under the CCPA/CPRA) have the right to know what personal information we hold about them, to request deletion or correction, and to opt out of any sale or sharing of personal information. We do not sell or share personal information as those terms are defined by California law. We will not discriminate against you for exercising these rights.
• European Economic Area and UK visitors (under the GDPR/UK GDPR) have rights including access, rectification, erasure, restriction of processing, data portability, and objection to processing. Our lawful bases for processing are our legitimate interests in operating the Site and responding to inquiries, and compliance with legal obligations.
• Other U.S. states with consumer privacy laws grant similar rights of access, correction, deletion, and opt-out of sales or targeted advertising.

To exercise any of these rights, email [email protected]. We will verify your identity before responding and will respond within the time required by applicable law.

9. Children's privacy

The Site is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us and we will delete it.

10. Third-party links

The Site links to third-party websites and services, including LinkedIn, GitHub, our public course materials, and the websites of organizations we belong to. This policy does not apply to those sites; their own privacy policies govern your use of them.

11. Do Not Track

Because the Site uses no tracking technologies, there is nothing to disable in response to Do Not Track signals.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will post the updated policy on this page and revise the "Last updated" date above. When a change is material, the updated policy will say so on this page, describe what changed, and state the date the change takes effect.

13. Contact us

Questions about this Privacy Policy or our privacy practices: [email protected].

14. The Axiovex Signal newsletter

If you subscribe to The Axiovex Signal, our monthly newsletter, we collect your email address, your subscription status, the timestamps of your signup, confirmation, and any unsubscribe, and which signup form you used (for example, the one on the Signals page or in an article) — nothing else. We use that information only to send the newsletter you asked for. Subscribing requires a confirmation click (double opt-in); until you confirm, nothing is sent to your address.

Two processors handle this data for us: Microsoft (Microsoft 365 sends the newsletter from our own tenant mailbox) and Cloudflare (which hosts this Site and stores the subscriber list). We do not sell subscriber information, and we do not share it with anyone beyond those two processors.

The newsletter carries no tracking pixels and no per-reader analytics: we do not record whether you open an issue or click its links. We keep only aggregate counts — how many issues were sent, bounced, or complained about.

Every issue carries a one-click unsubscribe, and it takes effect immediately. When you unsubscribe, we keep your address on a suppression record — held so that the address cannot be silently re-added — and it is never used for any other purpose. Subscribing again is always possible, and always takes a fresh confirmation click.

Unsubscribing stops the emails. If you would rather have your record removed entirely — including from the suppression record — email [email protected] and we will delete it.

15. Our lists: the newsletter, the pilot waitlist, and occasional marketing

Axiovex keeps three separate lists, and every signup form on this Site offers the same choice among them: The Axiovex Signal (our monthly newsletter, section 14 above), the pilot waitlist, and occasional marketing emails. The lists share one record per person: if you join more than one list, we keep a single contact record for you, with a separate membership for each list you chose — when you joined it, when you confirmed, and when you leave it. Joining one list never joins you to another, and leaving one list never changes the others. Each list can be left in one click from any email it sends, and pilot emails and confirmation pages also offer a link that leaves every list at once.

The pilot waitlist. If you join the waitlist for our pilot program, we collect the information the form asks for: your name, your company or organization, your email address, and whether you are joining as an employer, educator, participant, partner (such as an accelerator or investor), or other — and, only if you choose to add them, your phone number, your website, and a short note on what you are hoping to gain. We also record when you signed up and when you confirmed.

We use that information for one purpose: forming and running the pilot. We use it to contact you about the cohort, to match employers, the education institution, and participants to each other, and to plan from the needs people state. The waitlist is a working list for that follow-up — it is not a marketing list, and joining it does not subscribe you to anything else. Follow-up from the waitlist is personal: a founder may email or call you using the details you gave us. There are no bulk mailings from the waitlist. When the pilot is forming, we may introduce waitlist members to each other — an employer to the institution, a participant to a program — using the details you provided, as part of the follow-up you asked for.

Occasional marketing. If you join the marketing list, we send emails from Axiovex from time to time — no more than about once a month — about Axiovex's own services, events, training sessions, and offers. That list is separate from the monthly newsletter and from pilot waitlist messages: joining it, or leaving it, never affects the others. Joining the newsletter or the marketing list adds only your email address; the extra details on a person's record exist only when they joined the waitlist and gave them.

Joining any list requires a confirmation click (double opt-in). If you check more than one list on the same form, one click confirms exactly the lists you checked — and only your email address is added to the newsletter and marketing lists; the rest of the form stays in the waitlist record only. The same two processors handle this data: Cloudflare stores the lists, and Microsoft sends the confirmation and welcome emails. We do not sell list information, and we never share addresses for anyone else's marketing.

If you never confirm, we delete the entry 30 days after you signed up. If you would like your record removed at any time, use the link in any email from us, or email [email protected] and we will delete it entirely.

16. Our Disclaimer

This policy covers personal information only. Reliance on the Site's published content — our analysis, the figures we republish, and the projections we show — is covered by our Disclaimer.

17. Support reports

If you file a report on our Support page, we collect your name, your reply email address, the category you chose, and the report text you write. The report is stored as a ticket in a private system that only Axiovex staff can access, and we use it only to respond to your report and to address what you reported. Replies come by email from [email protected].

The support form is built to keep personal information out of tickets. It warns you before you write, and it steers the categories that usually involve personal information — privacy or consent questions, security reports, and concerns about a match — to email instead of the form. It also checks each report before it is filed: a report that appears to contain a Social Security number or a password is not filed at all, and text that looks like someone’s email address or phone number is removed from the report before filing, with the ticket flagged for staff review. If you email a support request instead, the details stay in that email thread; our ticket for it records only the category, the date, and a reference.

We keep support reports while a report is being worked and for as long as needed for our business records afterward. To ask about a support report, or to have one deleted, email [email protected].

18. The Arcturus application

The AXIOVEX Arcturus application — the workforce and capability planning program described on our Arcturus page — runs at arcturus.axiovexsystems.com under its own privacy policy: “Privacy Policy — the Arcturus application,” at https://arcturus.axiovexsystems.com/privacy/. That policy describes how the application handles information, and it governs the application. This policy governs this Site. The waitlist described in section 15 remains the only public door to the program, and joining it creates no account.

19. Correction reports and article likes

If you report an inaccuracy, on an article or through our Corrections page, we collect the report text you write, the page it concerns, the date, and your email address only if you chose to leave one for a reply. You do not need an account or an email address to send a report. The report is stored in the Site's database, and a copy is emailed to our support mailbox so the founders see it. We use it only to check the claim and, where the report is right, to correct the page. Reports are never published. A correction we make is recorded in a dated log, headed "Corrections and updates", at the end of the article, where anyone can read it; the log never names or describes the person who reported the problem.

The correction form is protected by the same Cloudflare Turnstile spam check described in section 3, and it checks each report before storing it: a report that appears to contain a Social Security number or a password is not stored at all, and text that looks like someone's email address or phone number is removed from the report before it is stored, with the report flagged for staff review.

We keep the report itself as part of the Site's correction record. If you left an email address, we delete it 90 days after your report is settled. To ask about a correction report, or to have one deleted, email [email protected].

Articles carry a Like button. Liking needs no account and asks for nothing about you. Your browser creates a random token, kept on your device as section 3 describes; our server keeps only a one-way cryptographic hash of that token with the article's name, which is how we count one like per browser. The count is a rough signal: one per browser on one device, not a count of readers or of people, and we never present it as anything else. Nothing in the like record identifies you, and unliking the article removes the record.