Legal
Privacy
Last updated November 5, 2026
This page explains what the Wirewalk Institute of AI (operated by Wirewalk) collects when you use institute.wirewalk.com and its learner area, and why. Questions or requests: sales@wirewalk.com.
What we collect
- Account: your name, email address, optional organization, and a password stored only as a salted hash.
- Learning records: enrollments, lessons completed, exam attempts and scores, and certificates issued.
- Purchases: what you bought, the amount and its status. Card payments are processed by Stripe; we never receive your card number.
- Inquiries and waitlist sign-ups: what you send through the teams form, the organization inquiry form or a waitlist form — name, email, organization, team size, the course you asked about and your message. For organization inquiries, also your role, country and state, approximate number of learners, the audiences and topics you choose, your timeline, payment method, and procurement and integration needs. Each submission is stored with the IP address and browser user-agent it came from, which we use to spot and block abuse.
- Teams, training campaigns and organization pricing:
- When you join a team, its owner and managers see your name, email, and your progress, exam results and certificates for the courses the team gave you or assigned to you in a training campaign. They do not see your other courses.
- For a course you already had before a campaign assigned it, your team sees that you have access to it, but not your progress or whether you completed it, unless you choose to share it.
- Reminder emails before the due date, and once if training is overdue, can be turned off in your account; the one email telling you training was assigned is always sent.
- If your organization has a pricing agreement, we check whether it applies to you from your team membership or from your verified email address's domain, which your organization has proved it controls by DNS.
- Apart from that, your organization is not told which courses you buy for yourself, including ones bought at your organization's pricing.
- Security records: IP addresses and timestamps used to limit repeated sign-in and sign-up attempts, and the IP address and user-agent recorded with each inquiry as described above. For the AI instructor's course finder, help desk and feedback buttons, we limit requests per network using a keyed hash of your network address (never the address itself), kept for up to two days.
- Campaign source: if you arrive through a tagged link (for example one of our ads on Reddit), the link's campaign tags (
utm_source,utm_medium,utm_campaign,utm_content,utm_term), Reddit's click ID (rdt_cid, if the link carries one) and the page you landed on are saved with your account when you sign up, so we can tell which campaigns lead to sign-ups. If you then send the teams or organization inquiry form, the same kind of arrival details go with that inquiry (see In your browser). Our servers do not send them to Reddit or anyone else. - AI instructor usage: when you use Ellery, the AI instructor, we keep counts, not text: how many requests each mode received per day, the number of tokens used and the cost, grouped by your organization (your team, or your verified work email domain, such as
example.com) so we can apply per-organization limits; how many you have used today against your daily allowance (these counters are deleted after two days); and anonymous thumbs-up or thumbs-down counts. When a safety check fires (for example, text that looks like an exam question or an attempt to change the grader's instructions), we record a short reason code linked to your account, the mode and the course, so we can pause the AI instructor for an account that keeps doing it; these records are deleted after 90 days. We do not store the text of your questions, Ellery's answers, your practice submissions or your role-play conversations. See AI instructor (Ellery). - Page and button counts: on selected public catalog and information pages, we count page loads; on campaign pages, we count landing views and main-button clicks. These are anonymous daily totals: a fixed page or button name and a count per day. No IP address, cookie, email address or user ID is stored with those totals. The public page-load script sends only the fixed event name, omits request credentials and the referring address, uses no cookies or browser storage, and does not run when your browser signals Do Not Track or Global Privacy Control. It does not send query strings or capture how you arrived. Counts are not unique visitors: reloads and some bots can count, while blocked JavaScript or failed requests can leave visits uncounted. These counters do not reconstruct historical visits or identify organic search traffic.
AI instructor (Ellery)
Ellery, the AI instructor on this site (lesson questions, practice questions, the prompt sandbox, practice conversations, graded exercises, the course finder and the help desk), is powered by Anthropic's API. Anthropic processes these requests for us as a service provider.
- What is sent to Anthropic: the text you type (your question, prompt, reply or submission) and the course material Ellery needs to answer: the text of the lesson, or the scenario or exercise you are practicing, or our public course list and help pages. No exam content is ever sent: exam questions and answers stay on our servers. We do not send your name, email address, organization, account ID or IP address. Before your text is sent, we remove things that look like email addresses, phone numbers, card numbers, API keys and similar identifiers, from the message you just wrote and from the earlier messages in the same conversation, but please use invented data in exercises anyway.
- Training: under Anthropic's commercial terms, Anthropic's policy is that it does not use inputs or outputs from its commercial products, including the API, to train its models by default. See Anthropic's "Is my data used for model training?" and its Commercial Terms of Service. Anthropic's own retention and privacy terms apply to the data it processes.
- Where conversations are kept: in your browser, for the page you are on (a practice conversation is kept for that browser tab, and your last exercise submission and its feedback in your browser's local storage so you can improve it). They are not stored by us. Only the counts described above are kept.
- Feedback: the "Was this helpful?" buttons record only the rating and an optional reason code, not the conversation.
- Hand-offs: if you press "Report an error / contact support" in the help desk and send the form, your message (and your email address, if you are not signed in) goes to our support inbox, like the error-report form.
- Voice: "Listen" reads lessons aloud with your browser's built-in voices. Push-to-talk uses your browser's speech recognition, which may use your browser vendor's service: in some browsers, such as Chrome, audio is sent to the browser maker's servers to be transcribed. We never receive or store audio; only the text you choose to send reaches us.
What is public
A certificate's verification page is public by design. It shows the name on the certificate, the course or program, the issue date, the exam score and whether it is valid. It does not show your email address or any other account details.
Open Badge files: if you download your certificate as an Open Badges 3.0 file from your certificate page, the file contains the name on the certificate, the course or program, the dates, the score, a position in our public revocation list and a salted hash of your account email address. The hash does not show the address, but anyone who knows or guesses the address can check it against the hash. It never contains the email address itself, your account ID or the reason for any revocation. Anyone you give the file to can read what it contains. The file does not update itself: after a renewal or a name correction you download it again. Wallets and verifiers that check a badge download our public revocation list from this website (/badges/status/1.json); it contains no personal data.
What we use it for
To run your account and courses, grade exams, issue and verify certificates, process purchases, answer inquiries, send the emails the service needs (such as sign-in codes and certificates), and protect the service from abuse. We do not sell personal data. This site uses no third-party advertising or analytics trackers. We use the anonymous aggregate counters described above; no ad pixel is loaded.
Who processes it for us
- Cloudflare hosts our application and database, and may present a bot check on sign-up and in the help desk and course finder.
- Stripe processes payments.
- GitHub Pages hosts this public website.
- Google Fonts serves the typeface used for headings, so your browser requests it from Google.
- Anthropic provides the AI model behind Ellery, the AI instructor, through its API (see AI instructor (Ellery)).
- Resend, our email delivery provider, sends account and certificate emails and delivers inquiry and waitlist notifications to our sales inbox (the inquiry itself is first stored on Cloudflare).
In your browser
We store a sign-in token in your browser's local storage while you are signed in, your light or dark theme choice, a short-lived copy of the price list, your read-aloud voice and speed, which Ellery tips you have dismissed, your last graded-exercise submission and feedback, and, only if you arrived through a tagged campaign link, those campaign tags for up to 30 days so they can go with your sign-up (the browser copy is deleted when you create an account, or when it expires). Separately, for inquiries, your browser keeps for up to 30 days how you first and most recently reached this site: campaign tags and any ad click ID in the link (utm_*, gclid, gbraid, wbraid, msclkid, rdt_cid, li_fat_id, fbclid), the page you landed on (without its query string) and the name of the referring website (not its full address). It is sent only with a teams or organization inquiry you submit, never on its own and never to a third party. There are no tracking cookies.
How long we keep it
Learning records and certificates are kept while your account exists so certificates stay verifiable. Training campaign assignment records are kept while the team exists or until you leave it; the log of reminder emails records which reminder was sent and when, not the email text. Purchase records are kept as long as accounting law requires. Ask us to close your account and we will delete or anonymize what we are not required to keep; a certificate you have shared can be withdrawn from public verification on request.
Your choices
You can update your name and organization, and turn off training reminders from your team, in your account. To get a copy of your data, correct it, or have it deleted, email sales@wirewalk.com from the address on your account.