HyracHub

Privacy Policy

Last updated: 13 November 2026

This document is provided in English, which is the authoritative version.

HyracHub is a learning platform where people follow courses and collections, earn certificates, and join organizations (“communities”) such as schools, academies and NGOs. This policy explains what personal data HyracHub processes and why. Where you interact with a community’s content or its messaging line, that community is the controller of its relationship with you and HyracHub acts as its processor; for the platform itself, HyracHub (a product of Hyrac Tech) is the controller. Contact: [email protected].

1. The data we process

  • Account — your email, display name, optional profile picture, language, and authentication data (a password hash or the social sign-in you choose).
  • Learning activity — the packs and collections you open, lesson progress and mastery, quiz answers, certificates earned, and items you save or bookmark.
  • Organization membership — the communities you join, your role, and (only if you consent at join) the progress you choose to share with a community.
  • AI Coach questions — the questions you ask the Coach (in the app or over a messaging line) and the answers given, used to answer you and, in aggregate and without identifying you, to improve the service.
  • Scholarship matching preferences (only if you use the Scholarships matching feature) — the study destinations, study levels and field you choose, and your nationality, used only to show you the scholarships you are eligible for. You choose to provide these and can change or delete them at any time. We use your nationality solely to check funder eligibility rules — not to infer your ethnicity, and not for any other purpose (see section 3a).
  • Scholarship alerts opt-in — whether you asked us to send scholarship deadline reminders and a weekly matches digest, and the dates you opted in and out.
  • Messaging / reach lines — see section 3.
  • Direct messages with a community — if your community turns on messaging, the text of the messages you exchange with its coordinators, who sent each, and the timestamps (see section 3b). These are stored on our own systems and are never sent through an outside messaging provider.
  • Payments — if you buy a pack or subscription, our payment processor handles your card or mobile-money details; we receive only a confirmation and minimal transaction metadata, never full card numbers.
  • Support and communications — messages you send us and the system and notification emails we send you.
  • Technical — basic request logs (IP, device or browser, timestamps) for security and reliability, and cookieless, aggregate analytics (self-hosted Plausible) that set no cookies and do not identify you.

2. Why we process it, and our legal basis

  • Provide your account, learning and certificates — performance of a contract.
  • Answer your Coach questions — contract and our legitimate interests.
  • Let you join and share with a community — consent (for sharing) and contract (for membership).
  • Send proactive community updates (section 3) — your consent.
  • Let you and your community message each other (section 3b) — performance of your membership with that community, and our legitimate interests in supporting it.
  • Register you for a live session, remind you, and issue a certificate (section 3c) — performance, plus your consent for SMS/WhatsApp reminders or a named certificate.
  • Show you matching scholarships, storing your preferences and nationality (section 3a) — your consent.
  • Send scholarship deadline reminders and the weekly matches digest (section 3a) — your consent.
  • Security, fraud prevention and reliability — legitimate interests and legal obligation.
  • Process payments — contract and legal obligation.
  • Aggregate, non-identifying analytics and service improvement — legitimate interests.

3. Messaging lines and community updates (reach)

Communities may offer a line where you can ask questions on WhatsApp, SMS or Telegram and get answers drawn from their published materials, and — on Telegram — opt in to occasional updates.

Asking questions (inbound). When you message a line, we process your message to answer it. We identify repeat conversations using a salted, one-way hash of your phone number or chat — we do not store your raw number for this. Message content is processed to generate an answer (see section 4).

Community updates (opt-in broadcast). You receive proactive updates only if you explicitly opt in (for example, by tapping “Get updates”). For this — and only this — we store your Telegram chat ID (so we can reach you), which community you subscribed to, and your opt-in and opt-out dates. This is personal data, kept on the basis of your consent.

  • Every update names the community and tells you how to stop.
  • Send STOP at any time (or email us) to unsubscribe — we stop immediately and keep only a minimal suppression record so we do not message you again. You can ask us to erase that too.

3a. Scholarship matching and alerts

Applies only if you use the Scholarships feature, currently offered to some communities. You can save a preference profile (study destinations, study level, field, and nationality) so we can show you the scholarships you are eligible for. We match you with a simple, transparent rule over published scholarships — no automated decision is made about you, and your profile is not shared with the scholarship providers.

You can opt in to deadline reminders (sent about two weeks and three days before a matched award’s deadline) and a weekly matches digest. These come to your in-app inbox and, only if you have connected a messaging line, to that line. Every alert tells you how to stop. You can turn alerts off or delete your whole preference profile at any time from the Scholarships settings, or by contacting us. Turning off alerts leaves only a minimal record so we do not message you again — ask us and we will erase that too.

Deadlines and eligibility rules are set by the providers and can change; always confirm them on the provider’s official page (see the Terms).

3b. Direct messages with your community

If a community you belong to turns this on, you can send it private messages and its coordinators (admins) can reply — all inside HyracHub. We store the messages you exchange, who sent each, and the timestamps, so your conversation is there when you come back.

Only you and that community’s admins can see your conversation with it. We keep the content on our own systems and do not send it through any outside messaging provider: a “new message” alert may reach you by your in-app inbox or email, but it only tells you a message is waiting — it never contains the message text. You read messages in HyracHub.

You can ask us to delete your messages at any time, and closing your account erases them. This is available only to members of a community, for messaging that community (not between individual members), and is subject to the acceptable-use rules in the Terms.

3c. Live sessions and workshops

If a community you belong to runs live sessions or workshops, you can register to attend. We store your registration (your name and email — or, if you register as a guest, the name and email you give us — and your time zone) and, once the session happens, your attendance (whether you joined, and for how long). If a session awards a certificate of completion, we issue one to attendees who took part; a certificate’s public verification page shows what the session was and when, and your name only if you ask us to put it on the certificate.

Reminders. By default we remind you by email before a session starts. A session may also offer text (SMS) or WhatsApp reminders — these reach you only if you give a phone number and opt in when you register, and are delivered by our messaging providers (see section 5). You can stop them by replying STOP or by cancelling your registration.

Being invited. A community may invite you to a session using contact details (email, and sometimes a phone number) its organisers already hold or add — for example because you are a member, or because you gave the community your details. The organiser decides who to invite and is responsible for having a lawful basis for those details; we act as their processor. An invitation email always lets you decline or unsubscribe, and you only become a registrant if you choose to register.

Follow-up messages. An organiser may message the people connected to a session — those invited, registered, who attended, or who did not — with confirmations, reminders, a thank-you (which may include a recording link and a feedback request), or a ‘sorry we missed you’ note. These go by email by default; SMS or WhatsApp are used only where you gave a phone number and opted in. Every email carries a one-click unsubscribe, and you can stop texts by replying STOP.

Registration questions and feedback. An organiser may add extra questions to the registration form (for example a dietary requirement); your answers are stored with your registration and visible to that community’s organisers, so please don’t enter sensitive information unless it is necessary. After a session you may be invited to leave a rating and comment, which is stored with your registration. For an in-person or hybrid session, opening your personal check-in link records that you attended.

Questions during a session. You can ask a question during a live session — it goes to the host, who may answer you, and other attendees may see and upvote it (we show the question text, not your name). Where the organiser turns it on, a question the session’s material clearly answers may be replied to automatically by our AI, always labelled “answered automatically”; the organiser can withdraw or correct any such answer, and anything for the host (logistics, opinion, personal) still goes to a person. See section 4 for how the AI processes your question.

Engagement during a session. So the host can see how the session is going and improve it, we measure engagement as it happens: how many people are present over time and how long you stay; the reactions and raised hands in the room; whether you take part in a poll or quiz (and, for a quiz, whether your answer was right); questions you ask; and use of the AI Coach. We also measure two simple signs of attention — whether the session tab is the one you’re looking at (your browser tells us only that this tab is in the foreground, never what else is on your screen, and never your camera or microphone), and how far through a video or audio clip the host plays you get. We do not watch your screen, your other tabs or apps, your typing, or your camera — only what happens in the session itself. These signals are combined into a simple, published engagement score. By default they are counted anonymously, using a one-way code in place of your name; your name is attached and shown to the organiser only where you consented when you registered, and group figures shared more widely are only ever shown for groups of at least three people. This data is kept with the session and removed with it, or when you close your account or ask us to erase your session data.

In the room. The live meeting room can carry your microphone, camera and — if you choose to present — your screen. Your camera and microphone start switched off: you are never seen or heard until you turn them on yourself, and you can turn them off again at any time. If the host splits attendees into smaller breakout groups, those group rooms work the same way. This is live media passed between the participants through our own self-hosted meeting service; we do not store it unless the session is being recorded (see ‘Recording’ below). Where a session is for an audience that includes under-18s, the organiser can mark it so, which keeps breakout rooms audio-only (no camera).

Voice processing. For some sessions the organiser may turn on live voice processing in the meeting room. This can tidy up your microphone sound, and — if you choose it yourself, or if the organiser turns it on for everyone in a session meant to be anonymous — disguise your voice so you are harder to recognise. The processing happens on your own device, before your sound is sent to anyone, so your original voice does not leave your device and we do not keep it. A disguise changes how your voice sounds; it is not a guarantee that you cannot be identified, and while it is on the room shows you that your voice is being disguised. If a session is both disguising voices and being recorded, the recording captures the processed (disguised) sound, not your original voice.

Live captions and translation. For a multilingual session the organiser may turn on live captions — the current speaker’s words shown on screen as text and, where the session offers more than one language, translated into the language you chose. To do this the speaker’s audio is sent, in short pieces as they talk, to a speech-to-text provider that turns it into text, which is then translated for your language (see section 4). Only the person presenting is transcribed — not the audience; you are transcribed only while you are the one speaking. The captions appear and then fade: we do not store them, and the short audio pieces are turned into text as they pass through and are not kept. The room shows you when captions are on, and a speaker is told their speech is being captioned and translated before their microphone is used this way.

Recording. Most sessions are not recorded. If one is, you are told before it starts — a notice in the lobby and a recording indicator in the room — and your continued attendance is your consent; a recording is kept for the organiser’s internal use and is never published without a separate, explicit decision. The online meeting room runs on our own self-hosted service, not a third-party video platform.

Replays. An organiser may capture a replay of a session — a re-playable version of the presented stage (the slides, media, polls and results the host shows), not a video of the people in the room. If the organiser additionally chooses to record their narration audio, that is the host’s voice only; you are muted by default, and the same recording notice is shown before it starts, so anything you choose to say if you unmute may be recorded. A replay is shared with attendees only if the organiser publishes it (the separate, explicit decision above). Replays are kept until the organiser deletes them, and are removed when you close your account or ask us to erase your session data.

  • Basis: performance (you asked to attend), plus your consent where you give it (a named certificate, or SMS/WhatsApp messages).
  • You can cancel your registration at any time from the link in your confirmation, and closing your account removes your registrations, invitations, answers and feedback; ask us and we will erase your session data.

4. AI processing (the Coach and live captions)

Your Coach questions are answered by large-language-model providers we use as processors (currently OpenAI and xAI, and web-search providers for freshness). We send them your question and the relevant grounding content; we do not permit them to train general models on your content. Answers are educational and may be imperfect — see the Terms.

Live captions (section 3c), where a session turns them on, use a speech-to-text provider (currently Google) to turn the current speaker’s audio into text, and a large-language-model provider (currently Anthropic) to translate that text into attendees’ languages. We send them only the speaker’s spoken words for that purpose, and — as with the Coach — do not permit them to train general models on your content. Translations are produced live and may be imperfect.

5. Who we share it with (processors)

We do not sell or rent your data. We share it only with vendors that process it on our behalf under a data processing agreement, and only as needed:

  • Messaging delivery — Twilio and Meta (WhatsApp), Africa’s Talking (SMS/USSD, where enabled), and Telegram Messenger Inc. (Telegram delivery for the reach lines and opt-in updates).
  • AI — OpenAI, xAI and Anthropic (question answering, and live-caption translation), Google (live-caption speech-to-text), and web-search providers (freshness).
  • Email — Resend (system and notification email).
  • Payments — our payment processor or processors (card and mobile money).
  • Hosting and infrastructure — our cloud host and self-hosted analytics.

6. International transfers

Some processors are outside your country (for example, US-based). Where EU or UK data is involved we rely on appropriate safeguards (adequacy decisions, Standard Contractual Clauses, or the EU-US Data Privacy Framework) and record them.

7. Retention

We keep account and learning data while your account is active, and delete or anonymize it after closure except where we must retain records (for example, tax records for payments). Reach-line message content is short-lived; broadcast subscriptions are kept until you opt out (then only a suppression record). Your scholarship preference profile is kept until you delete it or close your account, and your scholarship alerts opt-in is kept until you opt out (then only a minimal suppression record). Direct messages with a community (section 3b) are kept until you or the community delete them, or you close your account (which erases them). Your live-session registrations and attendance (section 3c) are kept until you cancel, we or the community delete them, or you close your account. We delete data earlier on a valid erasure request.

8. Your rights

Subject to local law you can request access, correction, deletion, restriction and portability, object to certain processing, and withdraw consent (including for community updates) at any time. Contact us at [email protected]. You may also complain to your local data-protection authority.

9. Children

HyracHub is intended for general audiences; some communities serve young learners. Where a community enrolls minors it is responsible for obtaining any required parental consent. We do not knowingly collect data from children below the applicable age of consent without it; contact us to remove such data.

10. Security

We use encryption in transit, access controls, secrets kept out of source control, and least-privilege practices. No system is perfectly secure; we notify affected users and authorities of a breach as required by law.

11. Changes and contact

We will post changes here and, for material changes, notify you. Questions or requests: [email protected] (interim, until [email protected] is provisioned).