Privacy Policy

1. Who is responsible for the data

The data controller is the individual who runs the DriveShark service. For questions about data processing, access to your data or its deletion, write to support@driveshark.com.ua. In your message give the email you signed in with, so that we can find your profile and check that the person writing is its owner.

2. What data we process

• Sign-in data: an email address and the technical data needed to confirm it and protect the sign-in. If you choose Google, we also receive your unique Google identifier, the verified email address, the profile name and, if there is one, the address of the profile photo. DriveShark requests only the openid, email and profile permissions, does not receive your Google password and does not read Gmail, Google Drive, your calendar or contacts. If you sign in with a code, a one-time code is sent to your email address; the database stores not the code itself but its cryptographic fingerprint, and the code becomes invalid after 10 minutes.
• Profile data: display name, driving licence category, planned exam date, language, time zone, role, and the dates the account was created and updated.
• Learning data: started and completed practice sessions and mock exams, questions shown, answers chosen, correctness, answer time, progress by question and topic, streaks of correct answers and the review schedule.
• Technical data: IP address, the address of the requested page, time of the request, browser or app type, response codes, and service records about errors and security. They may end up in the web server and application logs.
• Support requests: the chosen topic, the text of the message, a screenshot if you added one, and also your name, email, account identifier, licence category, the address of the page the request was sent from, browser type and time. You take the screenshot yourself: the browser will ask you to choose a tab, window or screen, and before sending you will see the image and can remove it.
• Subscription data: the chosen plan, term, payment status, amount, currency and transaction identifier. Full payment card details are processed by the payment provider, not by DriveShark.
• Advertising data: the source and campaign of the visit, an advertising or cookie identifier, technical data of the browser or device and conversion events — for example, creating an account or taking out a subscription. Your answers, progress, email, full payment details or profile contents are not passed to advertising platforms.

We do not receive the full card number, CVV, geolocation, or the contents of your mail, contacts or Google files.

3. Where the data comes from

You provide your email and profile settings yourself. Google profile data comes from Google after you choose “Continue with Google”. Payment data comes from the payment provider you choose. Learning and technical data are created while you use DriveShark.

4. Why and on what basis we process the data

• we create an account, confirm sign-in and maintain the session;
• we save progress, select reviews and produce mock exam results;
• we set up, record and renew a subscription and provide the paid features;
• we provide support, diagnose errors and protect the service from abuse;
• we comply with the law and protect the rights of users and of the service owner.

The legal bases are your consent, the need to provide the service you asked for and, in cases provided for by law, compliance with a legal obligation or protection of a legitimate interest that does not override your rights.

5. Browser local storage

DriveShark does not show third-party advertising inside the service, but it advertises the service itself on external platforms. To measure such campaigns, the site uses advertising cookies, pixels or conversion events only after your consent. Declining non-essential trackers does not restrict the learning features; you can change your choice in the consent settings on the site.

After you sign in, the session token is stored in the browser’s localStorage. During the redirect to Google, random sign-in protection values are temporarily stored in sessionStorage and deleted after you return. You can clear the token with the “Sign out” button or by deleting the site’s data in your browser.

6. Who receives the data

We do not sell personal data. DriveShark advertises its own service on external platforms and, after your consent, passes them the limited advertising data described above to measure campaigns and conversions. Data may be received by:

• Google — for signing in to the service and for loading the profile photo in your browser, in line with the settings and policies of your Google account;
• Hetzner Online GmbH — as the provider of server infrastructure in Germany, where the application and the database run;
• Resend, Inc. (USA) — sends the emails with sign-in codes and the support requests from the support form; the emails pass through Amazon Web Services infrastructure in Ireland. Resend receives the recipient address and the content of the email;
• Cloudflare, Inc. — serves the DNS of the driveshark.com.ua domain and forwards emails sent to support@driveshark.com.ua to the service owner’s mailbox at Google. Support requests from the form are not stored in the DriveShark database;
• The payment provider, named before you set up a subscription — to accept the payment, refund money and inform DriveShark of the subscription status;
• Advertising platforms named in the consent settings — to determine which campaign brought the user, measure sign-ups and subscriptions and produce advertising performance reports;
• public authorities or other persons — only when the law requires it or it is necessary to protect rights.

Because Google, Resend, Cloudflare, advertising platforms and the server in Germany are used, data may be processed outside Ukraine, including in the EU and the USA. We pass on only the data needed for the relevant service.

7. How long the data is kept

Profile and learning data are kept while the account exists and they are needed for the service to work. Payment records are kept for the period needed for accounting, refunds, disputes and compliance with the law. Technical logs and backups are kept for a limited time needed for security and for restoring operation. Emails with support requests are kept in the mailbox for as long as needed to reply and to investigate the problem.

Deleting your account in your profile stops access immediately: the current token stops working, and signing in again and creating a new account with the same email address or Google identity are blocked. The profile, the sign-in link and the learning history are marked as deleted but are not automatically erased from the database. This is needed for the integrity of related records, to prevent re-registration and to handle possible claims.

If you want to separately demand correction, anonymisation or final destruction of data, write to support@driveshark.com.ua. We will comply unless the law obliges or allows us to keep the relevant records.

8. How we protect the data

We use HTTPS, access restrictions, token verification, logging of security events and backups. Access to the production system is limited. At the same time, no method of transmission or storage gives an absolute guarantee of security.

9. Your rights

You can:

• find out what data about you is processed, its source, location and the purpose of processing;
• get access to your data and demand correction of inaccurate information;
• object to processing or withdraw consent where the processing is based on consent;
• demand deletion or destruction of data if it is processed unlawfully or is inaccurate;
• complain to the Ukrainian Parliament Commissioner for Human Rights or to a court.

To make a request, write to support@driveshark.com.ua. Before fulfilling a request we may ask you to confirm your identity. Withdrawing consent does not make processing carried out before the withdrawal unlawful.

10. Changes to the policy

We may update this policy because of changes to the service or the law. The new version is published on this page with a new date. We will inform you of material changes in the DriveShark interface where that is practically possible.

Related documents

See also the Terms of Use. Go back to the DriveShark home page.