Privacy Policy

Scope

EMBA Learning OS is a private learning-management system operated for one Executive MBA cohort by a designated Learning Manager. It is not a consumer product, has no public sign-up, and is not offered to the general public.

This policy describes what data the system accesses, what it stores, how it is used, and who it is shared with. It covers the Google integrations described below and this public website.

Google Calendar data

The system maintains one dedicated EMBA schedule calendar in the Learning Manager's Google account. It uses these scopes:

• https://www.googleapis.com/auth/calendar.events — to create, update, and remove the calendar events the system itself manages.
• https://www.googleapis.com/auth/calendar.readonly — to locate the events it previously created, and to look up the calendar it writes to.

These scopes are used only to keep course sessions, assignment deadlines, and selected notices in that calendar. The system does not read, index, or copy unrelated calendars or unrelated events.

What is stored locally for each synchronized item is a small mapping record: an internal item identifier, the Google event identifier, a fingerprint of the content the system last wrote, and the time it was written. Calendar event content is not copied back into the system's database.

Gmail data

The system also reads one authorized mailbox — the Learning Manager's own — to discover programme announcements, using a separate Google OAuth client from the Calendar integration above, with a single scope:

• https://www.googleapis.com/auth/gmail.readonly — read-only. The system never sends, modifies, labels, or deletes mail.

Raw messages are not stored. For each discovered message the system keeps the Gmail message and thread identifiers, timestamps, the sender address, a content hash, and extracted plain text from candidate messages, which is stored with a 30-day expiry marker.

Nothing from a mailbox is published automatically. Only what the Learning Manager explicitly confirms becomes a course record visible to the cohort.

Automated analysis

Where extracted email text is analyzed automatically, that analysis runs on a language model hosted locally on the same machine as the rest of the system. Mail content, calendar content, and course records are not sent to any external AI or LLM provider.

Credentials

OAuth tokens are stored server-side, on the operator's own machine, in files restricted to the operating-system account that runs the service. They are not kept in version control, are not transmitted to any third party, and are never exposed by this website. The public pages you are reading hold no credentials and reach no Google API.

How data is used — and not used

• Used only to operate EMBA Learning OS for the authorized cohort: maintaining the course record and projecting it to the schedule calendar and to the cohort's own notification channel.
• Not sold, rented, or licensed to anyone.
• Not used for advertising or ad targeting.
• Not used to build profiles, and not used for any purpose unrelated to the cohort's coursework.
• Not used to train any machine-learning model.

EMBA Learning OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sharing

The system does not share data with third parties for their own purposes. Data leaves the operator's machine in only two directions, both of them destinations the cohort already uses:

• Google Calendar — the schedule events described above, written to the Learning Manager's own calendar.
• The cohort's own chat workspace — a short notification when a new assignment or notice is published, containing the same information already shown on the board.

There are no analytics providers, advertising networks, or data brokers involved.

Access control

The EMBA board is not publicly reachable. It is restricted to explicitly authorized accounts through an identity gate in front of the service, and the ability to create or change course records is granted to a narrower allowlist still. There is no public registration, and this website provides no path into the board.

This website

This site is two static pages. It sets no cookies, runs no third-party or analytics scripts, loads no external resources, collects no personal information, and has no accounts or forms. As with any web service, ordinary request metadata such as an IP address and browser user-agent may appear transiently in server and network-provider logs.

Retention

Extracted email text is stored with a 30-day expiry marker. Beyond that marker, the system does not currently operate a formal retention schedule or an automated deletion job: course records, discovery metadata, and calendar mappings are kept for as long as the system is operated for the cohort. This is stated as it actually is, rather than as a policy the implementation does not yet enforce.

Anyone whose data appears in the system may ask for it to be removed using the contact address below.

Revoking access

The Google account owner can withdraw the system's access at any time at myaccount.google.com/permissions. Once access is revoked the system can no longer read that mailbox or maintain that calendar.

Changes

If this policy changes, the revised version is published on this page and the "Last updated" date above is changed with it.

Contact

Questions about this policy or about data held by EMBA Learning OS: [email protected]