Cohorte Privacy Policy

Operator and responsibilities

Updated 17 October 2026. Cohorte is operated by MIKE MC FORMATIONS LLC, 1704 Llano St Ste B-1433, Santa Fe, NM 87505, USA. Contact: support@cohorte.io. This policy explains our processing; reading it does not constitute consent to marketing. Cohorte manages accounts and the operation of the platform. Schools decide how to use learner, prospect and teaching data within their organisation; contact your school about its own purposes and instructions.

Data we handle

The data depends on the features you use.

Account and school data: identity, email, profile, organisation membership, roles and enrolments; course content, learning progress, messages and files you provide; prospect information, forms, bookings and payment records needed for the service.
Google sign-in, if you choose it, provides account identity information such as name, email and profile image. It does not itself authorise calendar access. A calendar connection requires separate permission and a calendar selection.
For Google Calendar, Cohorte retrieves the list of calendars you can write to (identifier, name and time zone). It reads events in the selected calendar for the scheduling period and uses their identifiers, status and start/end times to calculate busy periods and avoid conflicts. Other details can be included in the provider response; they are not used to profile you.
Calendar access and refresh tokens are stored encrypted and associated with your user and school. Cohorte retains the selected calendar identifier/name/time zone, connection status and identifiers linking its bookings to calendar events. Technical logs and audit records help operate and secure the service.

Purposes, calendar use and sharing

We process data to provide requested account, teaching, community, booking and payment functions, support users and secure the service. Depending on the context and applicable law, processing relies on performance of a contract, legitimate interests in operating and securing the service, legal obligations or consent where required.

With your calendar permission, Cohorte creates and updates events for assigned booked calls and deletes the corresponding events when a booking is cancelled or reassigned. An event can contain the school and prospect names, time, public booking instructions and meeting link. These details are sent to your calendar provider and are visible according to your calendar sharing settings.
Authorised school members can access information according to their roles. Availability calculations affect offered booking slots; external calendar event contents are not published as a public agenda by this integration. Service providers process data needed for hosting, storage, communications and payments; a connected calendar provider receives the data required for that connection. Disclosure may also be necessary to comply with law or protect the service and its users.
Cohorte’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements (https://developers.google.com/terms/api-services-user-data-policy). Google data is used only to provide the requested integration. It is not sold, used for advertising or used to train general-purpose AI models. Human access is limited to circumstances allowed by that policy, such as your explicit consent, security investigations or legal obligations.
Providers may process data outside your country. Applicable transfer safeguards and the providers relevant to your use can be requested at support@cohorte.io. This policy does not promise storage exclusively in one country.

Protection and your choices

Access controls and encrypted calendar credentials help protect information. No system guarantees absolute security. You can decline a calendar connection and revoke Google access in your Google Account permissions. For access, correction, deletion, portability, restriction or objection requests, where applicable, contact support@cohorte.io; identify your account and school without sending passwords or access tokens. You may also complain to the competent data protection authority. Requests concerning a school’s records may require that school’s involvement.

Retention and disconnection

We retain information as needed to provide the service, meet applicable obligations and address security or disputes; the duration depends on the data and purpose. Disconnecting a calendar in Cohorte disables the connection, removes its stored credentials and clears pending authorisation attempts. It does not delete existing events in Google Calendar, booking records, connection metadata, event references or audit records. Remove unwanted calendar events in your calendar provider and contact support for deletion requests. Revoking access at Google prevents future authorised access but does not by itself erase records already held by Cohorte. No automatic fixed deletion deadline is promised here.

Updates and contact

Changes are published on this page with an updated date. Material changes requiring notice or consent will be handled according to applicable law. For questions about this policy or your data, write to support@cohorte.io or to MIKE MC FORMATIONS LLC at the postal address above.

Cohorte Privacy Policy

Operator and responsibilities

Data we handle

The data depends on the features you use.

Account and school data: identity, email, profile, organisation membership, roles and enrolments; course content, learning progress, messages and files you provide; prospect information, forms, bookings and payment records needed for the service.
Google sign-in, if you choose it, provides account identity information such as name, email and profile image. It does not itself authorise calendar access. A calendar connection requires separate permission and a calendar selection.
For Google Calendar, Cohorte retrieves the list of calendars you can write to (identifier, name and time zone). It reads events in the selected calendar for the scheduling period and uses their identifiers, status and start/end times to calculate busy periods and avoid conflicts. Other details can be included in the provider response; they are not used to profile you.
Calendar access and refresh tokens are stored encrypted and associated with your user and school. Cohorte retains the selected calendar identifier/name/time zone, connection status and identifiers linking its bookings to calendar events. Technical logs and audit records help operate and secure the service.

Purposes, calendar use and sharing

With your calendar permission, Cohorte creates and updates events for assigned booked calls and deletes the corresponding events when a booking is cancelled or reassigned. An event can contain the school and prospect names, time, public booking instructions and meeting link. These details are sent to your calendar provider and are visible according to your calendar sharing settings.
Authorised school members can access information according to their roles. Availability calculations affect offered booking slots; external calendar event contents are not published as a public agenda by this integration. Service providers process data needed for hosting, storage, communications and payments; a connected calendar provider receives the data required for that connection. Disclosure may also be necessary to comply with law or protect the service and its users.
Cohorte’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements (https://developers.google.com/terms/api-services-user-data-policy). Google data is used only to provide the requested integration. It is not sold, used for advertising or used to train general-purpose AI models. Human access is limited to circumstances allowed by that policy, such as your explicit consent, security investigations or legal obligations.
Providers may process data outside your country. Applicable transfer safeguards and the providers relevant to your use can be requested at support@cohorte.io. This policy does not promise storage exclusively in one country.