edarsjadval Privacy Policy

1. Data we handle

The platform handles school, class and group names and identifiers, teacher names and identifiers, subjects, rooms, teaching workloads, working hours, constraints and generated timetables entered or imported by the user.

• Google account name, email, profile picture and authentication tokens are used for sign-in.
• The browser stores the interface language, session and some display preferences.
• When feedback is submitted, the service handles the message and any contact details voluntarily entered by the user.

2. Purpose of school data

School data is used to generate timetables, check constraints, and save, view, edit and export the generation results. It is not used for advertising, advertising profiles or sale.

Account data is used for sign-in and access to the appropriate school workspace. Optional support messages are used to reply to the request and resolve the reported problem.

3. Storage

School data and generated timetables are stored on the server in the user’s edarsjadval workspace. The browser stores a session token, account details, language and display preferences. Unsent feedback may be stored locally when a network request fails.

Data is retained in the workspace for working with timetables. Users may correct or delete it, or request information about retention. Clearing browser data does not automatically delete server-side copies.

4. Who can access the data?

Timetable data is available to the edarsjadval service and users with access to the relevant school workspace as needed for its features. If the user enables public timetable sharing, people with the link can see school, class, teacher, subject and room names in the timetable. Public sharing can be disabled.

Google/Firebase services provide Google sign-in. If no profile picture is available, a name may be sent to ui-avatars.com to create a fallback avatar. These sign-in and avatar services do not receive the school data submitted for timetable generation.

Exporting a timetable or transferring it to another system through the extension is a separate action started by the user. The extension’s transfer practices are explained in its own policy.

5. Control, correction and deletion

Users can correct or delete school data and timetables through the relevant workspace controls. Requests to delete an account or server-side data can be sent to [email protected]. Do not include passwords or tokens in a request.

Signing out or clearing the site’s browser data removes the local session; it does not replace deleting timetables on the server.

6. Security and other services

Account tokens authenticate requests to the relevant server and control workspace access. Review the data shown in a timetable before enabling its public sharing link.

Google/Firebase, the avatar service and external systems selected by the user have their own privacy practices. This policy describes the edarsjadval platform’s use outlined above.

7. Policy changes

If data handling changes, this page and its last-updated date will be updated. Both the Uzbek and English policies are available without signing in.