Privacy

Who we are

Alphabeto is operated by WeCraft Tech Solutions Inc., a Canadian company.

What we collect

When you join the waitlist we store your email address, whether you described yourself as an independent teacher, an academy or something else, and the time you signed up. Nothing else is collected through the form.

Separately, and only if you accept analytics cookies (see below), we collect information about how you use this website: which pages you view, roughly where in the world you are, what kind of device and browser you use, and how you move around a page (clicks, scrolling and mouse movement).

Why

To tell you when Alphabeto opens, and to decide who to invite first. We won’t email you about anything else. With your consent, we also use website usage information to understand how people find and use this site, and to improve it.

Where it is kept and who sees it

Your waitlist details are stored in a private database hosted by Google Cloud in the United States. We don’t sell them or share them for advertising. Only the Alphabeto team can read them.

When you join the waitlist, a copy of your email address and role is also sent to our private internal operations dashboard, run by WeCraft Tech Solutions Inc. on Google Cloud, so we can see new signups and spot problems with the site. Team chat notifications about new signups show only a partly hidden version of your email address.

Website usage information, if you accept analytics cookies, is processed for us by Google (Google Analytics) and Microsoft (Microsoft Clarity), which may handle it on servers in the United States and elsewhere under their own terms. We don’t send them your email address, and we mask the email box on the waitlist form so Clarity never records what you type there.

Cookies and tracking

The first time you visit, a banner asks whether you accept analytics cookies. You can decline and the site works exactly the same.

• Your choice. We store it in one cookie of our own (alphabeto_cookie_consent) for one year, so we don’t ask again on every visit. It holds only “granted” or “denied”, and nothing about you.
• If you accept. Google Analytics sets cookies that let us count visitors and see which pages and sources they come from. Microsoft Clarity sets cookies and records anonymised clicks, scrolling and mouse movement, so we can see where people get stuck.
• If you decline. Neither tool sets cookies. Google Analytics may still receive a basic signal that a page was viewed, sent without cookies and not linked to you across visits. Microsoft Clarity is not loaded at all.
• Advertising. We don’t use advertising cookies and we don’t share this information with advertisers.

We also use Google Search Console, a tool that tells us how this site appears in Google Search. It collects nothing from you as a visitor.

You can change or withdraw your choice at any time: Cookie settings. Withdrawing stops further collection; to clear cookies already stored, use your browser’s settings.

Your choices

You can ask us to delete your details at any time. Contact details for these requests will be listed on this page before we send our first email.

The Alphabeto app

This part applies if you sign in to the app, as a teacher or as part of an academy. Alphabeto is in early access, so it describes how the app works today and we will update it as that changes.

What the app holds

• Your account. The email address you sign in with (by email link or with Google), your name if you give it or Google shares it, and which workspaces you belong to and in what role.
• Your students. What a teacher enters: a student’s name, first language, learning goal, English level over time, whether they are under 18, and which teacher they are assigned to. For a child we also keep the name and relationship of the parent or guardian who gave permission to record, and when. Students do not have accounts.
• Your lessons. The date and length of each recorded lesson, the moment the teacher confirmed the student agreed to be recorded, the audio (see below), the transcript and draft notes, the teacher’s edits, and the recap the teacher approved. From approved recaps we also keep a running summary for each student (the kinds of mistake that keep coming up, and the words learned); it is deleted with the student.
• Usage and plan. How many lessons a workspace has used each month, and its plan.

Recording and consent

A teacher records from their own browser: their microphone and the audio of the lesson tab. Before every recording the teacher confirms that the student, or a parent or guardian for a child, agreed to the lesson being recorded and processed by AI services to write lesson notes, and we store that confirmation with the time. Some students are children. Teachers and academies are responsible for getting that permission.

What happens to audio, notes and recaps

• Audio is sent in short pieces to a private storage area on Google Cloud in the United States. It is deleted once the notes have been made, and a safety rule removes anything left after 3 days.
• The transcript and draft notes can be opened only by the teacher who recorded the lesson. The teacher’s private tutor notes are never part of a recap and nobody else can see them.
• Nothing goes to a student until the teacher approves a recap. The owner and admins of an academy can see student names and levels, lesson counts and hours, and recaps the teacher approved. They cannot see transcripts, draft notes, tutor notes or audio.

AI services

Today the notes in the app are written by a placeholder, and no lesson audio or text is sent to any AI service. Before real speech-to-text or writing services are connected, we will name them on this page and update it.

Who else handles it

The app runs on Google Cloud and Firebase (sign-in, the database, audio storage, hosting and the sign-in emails), in the United States. Our private operations dashboard receives error reports (the kind of error and a general page address, never the error’s own text), counts such as how many lessons were processed, a signal that a signed-in teacher is online (the teacher’s sign-in address and an anonymous number), and the messages a teacher chooses to send us from the Help page, with their sign-in address so we can reply. It never receives audio, transcripts, notes or student names from the app; please don’t put them in a Help message either. If you accept analytics cookies, they work inside the app as they do on this site, and they never receive lesson content. We don’t sell this information or use it for advertising.

Keeping and deleting it

• A teacher can permanently delete a lesson they recorded. An owner or admin can delete any lesson or student, and an owner can delete the whole workspace. Deleting removes the transcript, notes, recap and any audio left, and cannot be undone.
• We keep a record that something was deleted (what kind, when, by whom and how many items, with no names or notes). Monthly lesson counts used for billing are kept, except when a whole workspace is deleted.
• Deleted data can remain in our encrypted database backups for up to 70 days before they expire.
• To have your sign-in account removed, or for any other request about your data, contact details will be listed here before the app is opened to the public.