Privacy Policy — EPTA English
Effective date: 13 October 2026. This page describes the EPTA English learning platform at this site.
Who operates the service
The application name is EPTA English. The legal name, tax identifier, and postal address of the operator are not published on this page.
Privacy and deletion requests: a dedicated contact address is not published on this page. You can also disconnect Google Calendar yourself, as described below.
Data you provide and data the site collects
Account data stored by the platform includes your email address, name, and sign-in credentials. The platform also stores the schedule, lesson records, and learning activity you enter. The site keeps a session in the browser so you can stay signed in. This policy does not describe a separate analytics product.
Google Calendar API
Google Calendar is optional. A teacher starts the connection. Students and site visitors are not asked to connect Google Calendar.
The app requests only these scopes:
https://www.googleapis.com/auth/calendar.events— read, create, update, and delete events on calendars the teacher can access.https://www.googleapis.com/auth/calendar.calendarlist.readonly— read the list of calendars.
From calendar events the app may store the title, description, location, link, start and end time, all-day flag, busy flag, recurrence rule, Google event id, recurring event id, iCal UID, and etag. The app can create, update, and delete lesson events in the connected calendar, including a video-meeting link when a lesson slot is created.
Why Google Calendar data is used
The data is used to show the teacher’s schedule, keep lesson appointments in sync with the calendar, see which times are busy, and avoid booking conflicts. It is not used for advertising, and it is not sent to the Skyla speaking practice.
Where it is stored
OAuth access and refresh tokens, the chosen calendar id, and sync state are stored in the application database, including the connection record and older token fields on the teacher account. Imported events are stored in the same database. This page does not claim that those fields are encrypted at rest.
Who else receives data
Calendar requests are sent to Google so the integration can run. The application database is hosted on the operator’s server infrastructure. Google user data is not sold. It is not used for ads, and it is not shared with a data broker.
How long it is kept
Disconnecting Google Calendar in the teacher profile stops sync, clears the access token, refresh token, and calendar id stored for that connection, and stops the push channel. Imported event rows are not deleted by disconnect. Events already created in Google Calendar are not removed by disconnect. The app does not call Google’s token-revoke endpoint; the teacher can remove EPTA English in their Google Account permissions.
If the user record is deleted, the database removes the calendar connection and the imported event rows that belong to that user. The product does not publish a fixed number of days for retention.
How to disconnect or ask for deletion
In the teacher profile, open Integrations and turn off Google Calendar. You can also remove the app’s access at Google Account permissions. A deletion request for the remaining imported rows needs the operator contact, which is not published on this page.
Your rights
You can ask for access, correction, or deletion of your personal data, and you can object to processing where the law allows it. Use the operator contact once it is published, or disconnect Google Calendar yourself.
Changes
The current text is the one on this page. The effective date is 13 October 2026. Continuing to use EPTA English after an update means you accept the updated policy.
Google API Services User Data Policy
Google user data is used only to provide the user-facing calendar and scheduling features described above. It is not sold. It is not used for advertising. It is not used to develop, improve, or train generalized or non-personalized AI or machine-learning models. EPTA English does not use the Google Calendar API to create AI-generated non-consensual intimate imagery.