Extension Privacy Policy

1. Data we handle

• School and scheduling data: school, class and group identifiers, class names, teacher names and identifiers, subjects, rooms, teaching workloads, bell times, academic periods and timetables.
• Authentication: an edarsjadval token may be obtained from extension settings or an existing session in an open edarsjadval page. eMaktab requests use the existing session and necessary service tokens; the extension does not separately collect the eMaktab login password.
• Preferences: interface language, server address, insertion speed and selected period. Open tab addresses are checked to identify relevant eMaktab and edarsjadval pages.

2. Purpose and starting actions

Data is used to transfer teaching workloads from eMaktab to edarsjadval, link identifiers and insert a prepared timetable into eMaktab. The extension does not generate the timetable itself.

School data collection, server transfers and timetable insertion begin when the user starts the relevant action. An existing authentication token may sync automatically from an open edarsjadval page.

3. Local storage and retention

Preferences, the edarsjadval token, cached school data and prepared timetables are stored locally in the browser’s extension storage. They are not sent to Chrome sync storage. Local data is replaced when updated or removed when the extension is uninstalled.

Transferred data is stored in edarsjadval or the user’s configured server; inserted timetables are stored in eMaktab. Removing the extension does not automatically delete these services’ copies.

4. Recipients

When a transfer starts, school data is sent to the configured edarsjadval server. The authentication token is used to connect to that server. A local server receives requests on the same computer. If a custom server is selected, its operator receives the data.

Requests to retrieve school data and user-initiated timetable insertion requests are sent to eMaktab. Copies stored in these services are also subject to their own practices.

The extension does not transfer data for sale, advertising or advertising profiles. It has no functionality that sends data to advertising, analytics or tracking services.

5. Control and deletion

Users can change the server address and token, or save an empty token field in settings. Chrome extension settings allow users to manage site permissions, disable the extension or uninstall it. Uninstall the extension to remove its local data completely.

Correction and deletion of server-side or eMaktab copies must be performed in the relevant service or requested from its operator. Contact [email protected] for edarsjadval requests; do not send passwords or tokens.

6. Permissions and limitations

Site access and scripting permissions are used for eMaktab and edarsjadval integration. When a custom server address is configured, Chrome asks for access to that address. Automatic token detection is limited to the edarsjadval domain and supported local pages.

The extension is not designed to collect individual student profiles, grades, health or financial data, private messages or precise location. Browsing history is not stored.

HTTP localhost is supported for local development; use HTTPS for an external server. Executable scripts are included in the extension package; remotely hosted executable code is not loaded.

7. Limited Use and changes

User data obtained through Chrome is used solely for the data-transfer functionality described above. Its use complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

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