1. Controller and scope of this policy
The data controller is Jerzy Jabłoński, driving school, Bogusława Kleszczyńskiego 10, 32-100 Proszowice, Poland. Contact: 606 720 252, jablonskiprawko@gmail.com.
This policy covers jablonski-naukajazdy.pl, enquiries about training and the Jerzy Jabłoński driving lesson booking panel. The panel is used to organise lesson appointments and keep track of lesson hours.
2. Accounts and access to panel data
A student receives an invitation from an instructor and activates their account. Students sign in using an email address and password. Google Calendar connection is a separate instructor feature; students do not sign in with Google or grant the panel access to their own calendars.
Students can access their own bookings and lesson hour records. Authorised school instructors can access student profiles, bookings, courses, lesson hour records and the change history needed to organise training. An optional profile picture is accessible to its account holder and authorised instructors; a student can also see the picture of the instructor assigned to their course. The service providers listed in section 5 also participate in processing data.
3. Data we process
| Area | Data |
|---|---|
| Account | Email address, first and last name, phone number, optional profile picture, activation status and authentication data handled by the sign-in service. |
| Bookings | Instructor, appointment, lesson duration, meeting point, status, notes and the reason for a booking decision. |
| Training and lesson hours | Course type, allocated hours, recorded minutes, lesson outcome and description, and the person approving the record. |
| Notifications and history | Notification content and read status, and a change log recording the person, time, operation and changed values. |
| Instructor's Google Calendar | An encrypted Google refresh token, a short-lived access token handled in server memory, selected calendars, booking and event links, synchronised lesson data and busy periods. See section 6. |
| Website | Information submitted through the contact form and technical request data, such as IP address, browser information and connection time, needed by hosting and external services. |
Do not include health information, criminal conviction information or other unnecessary sensitive details in booking notes or the contact form.
4. Purposes and legal bases, including the contact form
- Training administration and steps before entering into a contract — arranging appointments, student accounts, bookings, lesson hour records and related messages: Article 6(1)(b) GDPR.
- Answering other enquiries — correspondence and handling your request as the controller's legitimate interest: Article 6(1)(f) GDPR.
- Legal obligations — training and financial records required by law: Article 6(1)(c) GDPR.
- Security and resolving issues — maintaining the service, preventing abuse, keeping an operation history and establishing or defending legal claims as legitimate interests: Article 6(1)(f) GDPR.
The website contact form requires your name and email address. Phone number, subject and message are optional. Without contact details we cannot reply through the form; you may call us instead. Your message is sent through Web3Forms to the controller's mailbox.
Providing data is voluntary, but account and booking data are necessary to use the corresponding panel features. Reading this policy or using the service does not constitute consent to unrestricted data processing.
5. Providers and data recipients
- Netlify — hosting the public website and handling its network requests. Netlify privacy policy.
- Lovable Cloud and Supabase infrastructure — hosting the panel, its database, authentication and profile files. Lovable privacy policy, Supabase privacy policy.
- Lovable Email — sending account and booking messages; this service receives the recipient's address and message content. Lesson messages may include the instructor's name and phone number for appointment enquiries. The email configuration uses the technical domain notify.jablonski-naukajazdy.pl.
- Inngest — handling reminders, booking changes and synchronisation jobs. Depending on the operation, requests include booking identifiers and dates, job identifiers or instructor identifiers. Job submission uses the Lovable connector. Jobs retrieve the current data needed for the operation, and step results may be processed in the service's execution history. Inngest privacy policy.
- Google — direct instructor authorisation through OAuth 2.0 and Google Calendar API operations as described in section 6.
- Web3Forms and the email mailbox provider — delivering and handling contact form messages.
- Google and Elfsight — external website elements described in section 8. Google privacy policy, Elfsight privacy policy.
Providers may use subprocessors and infrastructure outside the European Economic Area, including in the United States. Their data protection terms describe processing locations, subprocessors and transfer safeguards. You may contact the controller for information about the handling of your data and a copy of the applicable safeguards. We do not sell personal data.
6. Google Calendar connection for instructors
The instructor initiates the Calendar connection, grants authorisation directly on Google's website through OAuth 2.0, and selects a lesson calendar and any additional calendars that block availability. The panel server exchanges a one-time code for Google tokens and calls the Google Calendar API directly. The panel synchronises bookings with the selected lesson calendar and takes busy periods into account when offering appointments.
Purpose and permission scopes
The integration uses two Google scopes, displayed before access is granted:
https://www.googleapis.com/auth/calendar.calendarlist.readonly— read the list of calendars.https://www.googleapis.com/auth/calendar.events— read, create, update and delete events in calendars available to the connected account; the panel uses these operations to manage bookings and check availability in calendars selected by the instructor.
Data sent to Google
A lesson event may contain the student's first and last name, course category, duration, appointment, meeting point, status, and the used or projected lesson hours and course allowance. The description of a confirmed lesson may contain notes entered with the booking. Do not enter health information or other unnecessary sensitive details there.
For confirmed lessons, the student's email address is added as an event attendee. Google may send an invitation, an appointment update or a cancellation. A pending lesson request is marked in the calendar without inviting the student. Receiving an invitation does not connect the student's Google account to the panel. Visibility to other people also depends on the instructor's calendar sharing settings.
Booking, calendar and event identifiers and update markers are also used to maintain synchronisation. Changing or cancelling a booking in the panel may update or delete the corresponding event in Google.
Data read from Google and synchronised to the panel
The panel reads the calendar list and retrieves events from selected calendars. This includes times, status, title, description, location, attendee addresses, colour and technical event linking data. In the lesson calendar, an appropriately described event may be matched to an active course using an attendee's email address or their first name, last name and course category. The panel then saves or updates the relevant booking, time, location, description and status. The instructor can also confirm a pending request by assigning the appropriate event colour or reject it by deleting the event.
For other events used to block availability, the busy-period table stores the calendar and event identifiers and the start and end of the busy period, without copying event titles or descriptions into that table. Standard event-list synchronisation uses a moving window from 60 days in the past to 210 days ahead; linked lessons may also be checked through separate requests. This window is not a deletion deadline for training records.
Event links and synchronisation settings are stored in the panel database. Technical Google notifications about calendar changes trigger synchronisation; jobs may be handled through Inngest. The integration also updates booking-related notifications, reminders and operation history.
We use Google API data only for the connection and synchronisation features described here. Its use and transfer are subject to the Google API Services User Data Policy, including the Limited Use requirements, and the Google Workspace user data and developer policy. We do not sell this data or use it for advertising or marketing. Google Workspace API user data is not used to develop, train or fine-tune AI/ML models. Data transfers to providers are limited to operating the disclosed features, security or legal obligations within Google's rules.
Disconnecting and deleting data
An instructor can use the “Odłącz” (Disconnect) button in the Calendar settings. The panel sends Google an authorisation revocation request and deletes the local refresh-token record, calendar settings, stored busy periods and notification-channel records. The associated cached access token is also cleared from the server process handling disconnection. Bookings and training records remain in the panel; disconnecting does not automatically delete events already saved in Google Calendar.
You may also revoke access in your Google Account connections settings. Local data deletion and revocation by Google are separate operations; if a connection problem occurs, check permissions in your Google Account as well. Revoking access in Google alone does not automatically erase data from the panel database. Contact the controller to request deletion of an account, remaining event links or training data.
7. Data protection mechanisms
We use technical and organisational measures to protect user data, including Google Calendar data, against unauthorised access, disclosure and alteration.
- Encryption in transit — HTTPS/TLS. Communication with the public website and panel, and server connections to Google APIs and other external services, use HTTPS/TLS to protect data during transmission.
- Encryption of stored refresh tokens. The Google
refresh tokenis encrypted on the server using AES-256-GCM before it is stored in the database, with a random initialisation value and integrity protection. The decryption secret is handled in the server configuration. Short-livedaccess tokensare handled in server process memory and renewed using the refresh token. - Authentication and authorisation. Calendar connection, configuration, synchronisation and disconnection functions verify the user's session and instructor role on the server and operate on that account's connection. OAuth
stateis signed with HMAC-SHA256, bound to the instructor starting the connection, and valid for ten minutes. Panel data access is restricted using roles and database Row Level Security (RLS) rules. Section 2 explains access to booking and school staff data. - Restricted access to tokens and private busy periods. Encrypted authorisation data and technical busy-period and synchronisation-channel tables are handled by the backend. Ordinary browser accounts have no direct access to the token table. Students see their own lessons and available appointments, not the contents of private events in calendars used to block availability.
- User control. The instructor initiates the OAuth connection. The panel does not obtain the password to their Google Account. The instructor may disconnect or revoke access as explained in section 6; requests to delete remaining data are handled by the controller under sections 9 and 10.
8. Browser storage, cookies and website services
The panel maintains the sign-in session in browser storage (localStorage). It may also store a sidebar preference cookie for seven days. These support authentication and the interface; signing out does not delete booking history from the database.
The public website loads Google Fonts, a Google Maps footer map, an Elfsight reviews widget on the reviews page, a Google spreadsheet for prices, and carousel library resources from cdnjs on the home page. When these resources load, the provider receives connection data, including the IP address and browser information, and may process its own identifiers or cookies as part of its service. Browser settings can restrict their operation.
Panel hosting may process technical service and error data under Lovable's terms. The absence of advertising in the panel does not mean that all external services on the public website do not process data.
9. How long we retain data
- Account, booking and lesson hour data — while the panel is used and training is provided, and afterwards as necessary to meet legal obligations and establish or defend claims.
- Correspondence — while an enquiry is handled, and longer only where needed to document arrangements or legal claims.
- Change history and notifications — as needed to ensure security and resolve booking and lesson hour matters.
- Encrypted Calendar refresh token, settings, busy periods and notification-channel records — until the local connection is removed in the panel or the controller handles a request. Event links stored with bookings and training records follow the retention criteria for bookings and lesson hours. Signing out or revoking Google authorisation alone does not automatically delete all these records.
Data required by law or necessary to handle legal claims may be deleted only after the relevant retention basis ends. Account and data deletion requests can be sent by email.
10. Your rights and contact
Depending on the legal basis and circumstances, you have rights of access, rectification, erasure, restriction, portability and objection. Where particular processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Send requests to jablonskiprawko@gmail.com. We normally respond within one month. In cases permitted by the GDPR, the period may be extended; we will explain the extension and its reason. You may also complain to the President of the Polish Personal Data Protection Office (UODO).
11. Decisions and updates
An authorised instructor decides on booking acceptance or changes and lesson hour records. The panel automatically checks availability rules, hour balances and deadlines, and schedules reminders. We do not make solely automated decisions producing legal or similarly significant effects within the meaning of Article 22 GDPR.
The current version of this policy is published at this address. Changes to the use of Google APIs require corresponding application behaviour and appropriate information for users.