Privacy policy

This policy covers the Drivings website, mobile apps, study tools, support and related features. It applies to visitors, guests, registered learners and people who contact us. RELOAD TECHNOLOGIES - FZCO operates the website and is the controller for the personal information it handles in running and supporting the web service. RELOAD TEKNOLOJİ LİMİTED ŞİRKETİ publishes the mobile apps and is responsible for the processing it controls in providing and supporting them.

When you use the same account on the website and in an app, account, study and entitlement records can be used across those surfaces to provide the service. App stores and other independent services handle some information under their own notices. Write to privacy@drivings.com about any of these activities. We can identify the responsible company for your request and route it to the right team.

• Account and access. We handle your email address, account identifier, sign in credentials through our authentication provider, display name and profile details you choose to provide. A guest session can have an account identifier before you provide an email. A sign in service may send an identifier, name or email depending on the permissions you grant it.

• Learning and preferences. We handle the course, jurisdiction, exam date or study preferences you give us, and record answers, attempts, lesson progress, scores, saved items and activity used to build your study plan.

• Billing and entitlements. We receive purchase and subscription identifiers, the item and price, payment status, trial and renewal dates, credit activity and details about refunds or disputes. Stripe handles full card details for web payments. We can receive limited details such as card brand and last four digits to help you identify a payment method. Stores and subscription services send purchase and entitlement information for app purchases.

• Support and evidence. We receive your contact details, messages and attachments, and relevant account or transaction information used to investigate. A pass guarantee request can include an official test result and related study evidence. We also handle verification details for privacy requests where needed.

• Email and notifications. If you subscribe to the daily question, we keep your email, region or US state, time zone, consent and confirmation history, and delivery, bounce or unsubscribe status. When you enable app notifications, we can use a device token and preferences to deliver them.

• Technical and usage data. We receive information such as IP address, device or browser type, app version, timestamps and request or diagnostic details. Depending on the feature and your settings, we may receive page and product events, a session identifier, a referring site, campaign parameters or mobile crash reports. We can infer a broad region from network information or use the area you select.

We use account and study information to sign you in, maintain access, save your work and recommend what to study next. We use billing records to activate plans, grant credits, record renewals, fix mistakes, handle refunds and reconcile payments. We use support information to reply, investigate a problem or assess a claim. Where we use tools to help triage enquiries or draft replies, those tools can process message text and the context needed for the enquiry.

We use technical records to deliver requests, diagnose faults, enforce access rules and protect against fraud and abuse. Where optional analytics are enabled, we use usage and campaign information to understand how people find and use Drivings. Some web payment attribution can associate a payment with a visitor or session identifier. With analytics enabled, a checkout flow can also pass the purchaser's email to DataFast to attribute a completed purchase.

We send communications that are needed for the service, such as sign in codes, purchase information and notices about your account. We use the preferences you set to deliver features such as the daily question and study reminders. Manage promotional emails through their unsubscribe link and app notifications through the applicable settings.

Where the UK GDPR, EU GDPR or a similar legal basis requirement applies, the ground depends on the purpose and circumstances.

• Contract or steps you ask us to take before a contract. We use necessary details to register or sign you in, deliver study and assistant features you request, provide paid access, manage billing and handle related support.
• Legitimate interests. Where appropriate, we use information to secure the service, prevent fraud, diagnose faults, understand service performance, resolve disputes and protect legal rights. We consider the impact on you and your right to object.
• Consent. We use consent where required for optional web analytics, relevant device access and communications you choose to receive. You can withdraw consent for future processing. This does not affect the lawfulness of processing before withdrawal.
• Legal obligations. We use and retain relevant information where required for tax, accounting, consumer protection, privacy rights and other applicable obligations.

You can read public material without registering. We need some information to provide an account or process a payment. A feature that needs a recording, attachment, notification permission or account connection will be limited if you choose to withhold it. Optional analytics choices are separate from access to core study features.

If you use the Drivings assistant, we process the prompt and relevant conversation context to generate a reply. Depending on the feature, that can include your selected course and study context, images or files you send, microphone audio, transcripts, generated audio, conversation summaries and saved memories. We may use authorised support tools to help resolve an issue you raise.

Model and voice providers, including OpenRouter and the model providers it routes to, and ElevenLabs when used, receive information needed for the requested operation. The exact information depends on the feature. We use conversation records and permitted memory to keep context across messages, and usage records to apply plan and credit limits. Use the relevant conversation and memory controls where available or contact us for help with a request.

Share only the information needed for your study question. Keep passwords, payment details and unrelated identity documents out of prompts, recordings and attachments. Use the refund or privacy request route for evidence intended for those requests.

When you use a documented Drivings tool through an external assistant, we receive the tool request and inputs supplied with it, such as the region, a search phrase or study preferences. Public tools can be used without linking a Drivings account. The host decides what parts of your conversation to include in a tool request.

If you authorise a connection, the personal progress tool can return account and study details within its approved read access, such as your name, region, course, exam date and recent learning activity. You can revoke the connection through the host or Drivings account settings where available. Your external assistant's privacy notice governs its copy of the information it receives.

The website uses necessary storage for functions such as sign in, regional settings and remembering your privacy choice. Optional web analytics use cookies or similar browser storage when allowed by your settings. Use Cookie preferences in the footer to change your selection. Our Cookie policy lists the main technologies, what they do and how long their browser storage lasts.

Mobile apps use app storage, session tokens and device permissions. Analytics or diagnostics used in the app, such as Firebase Analytics and Crashlytics where integrated, are separate from the website cookie setting. Manage the device permissions and choices available in the app and your operating system.

• Hosting, delivery and account services. Vercel and Supabase help run the website, serve requests, authenticate learners and store records. Other network, email, notification or support providers receive the information needed to deliver their function.
• Billing and subscriptions. Stripe processes web payments and can use transaction data for its own payment, fraud and legal purposes. Apple or Google handles its store's transactions. RevenueCat helps us match app purchases to Drivings access. The relevant provider's notice describes its own uses.
• Measurement and diagnostics. Our own reporting tools and services such as DataFast, Mixpanel and mobile diagnostics providers receive the event and diagnostic information needed for the relevant measurement, according to the feature and settings.
• AI and other requested features. Model, voice, transcription, mapping and similar providers receive the request information needed to deliver the selected feature.

People authorised to support or operate Drivings can access information needed for their duties. We may disclose relevant information to authorities, courts, advisers or affected parties where required by law or reasonably necessary for a lawful dispute, security incident or legal claim. If a corporate transaction affects the service, information may be disclosed as needed for that transaction under appropriate confidentiality and legal safeguards.

See the Trust Center service providers for more information about key providers and links to their notices.

Drivings companies and providers can handle data from more than one country, including the countries where our companies are based and the locations used by providers for hosting, processing and support. A provider's list of available regions can differ from the locations used for a particular feature.

Where applicable data protection law restricts an international transfer, the transfer must have an authorised basis, such as an adequacy decision or applicable contractual safeguards. Contact privacy@drivings.com to ask which locations and safeguards apply to your information or for access to relevant safeguards where available.

We determine retention by the type of record, the reason we collected it, whether you still use the feature, the need to keep evidence of an order or dispute and any legal obligation or limitation period. Cancelling a subscription stops renewal. It leaves your account and study history available unless you also close the account or ask us to remove information.

• Account and learning records. We use these to provide access and recover your study history while the account is available. Account deletion closes sign in and can remove or de-identify account records. Some linked records can remain, including on accounts with payment history. See Account deletion.
• Billing and claims. Relevant purchase, invoice, payment, credit and dispute records can be kept to reconcile transactions, meet accounting or tax duties and handle claims. Support and verification records can remain where needed to follow up, prevent abuse or document the outcome of a request.
• Service and measurement records. We consider how long we need technical logs for security and reliability, and analytics for measurement. Browser storage expires separately from server records. Aggregated information that can no longer identify you may be kept for reporting.
• Email suppression. If you unsubscribe, or a delivery is bounced or reported as spam, we can retain the minimum record needed to honour that choice and avoid sending again.

Backup copies may persist until the applicable backup cycle runs. If you need to know the retention criteria or duration for a particular record, contact us with the type of record and account involved.

Depending on the law that applies, you can ask for access to your information, correction, deletion, restriction or a portable copy. You can object to certain processing, including direct marketing, and withdraw consent when we rely on it. You may also be able to ask for an explanation or review of a decision made using your information, or complain to your data protection authority. Drivings uses learning activity to personalise study suggestions and assess recorded completion for features such as the pass guarantee.

Write to privacy@drivings.com or use Contact us. Describe the request, identify the relevant account or feature and tell us where you live if it helps us identify your rights. An authorised representative can contact us with proof of authority where applicable. We may ask for information proportionate to the request to verify identity. We respond within the time required by law. In the UK this is normally one month, subject to any extension or other timing rule the law allows.

If you want to remove particular records, see Data removal and privacy requests. In the UK, you can complain to the Information Commissioner's Office. In another jurisdiction, you can contact the authority responsible there.

If an applicable state privacy law gives you rights, you can use the request routes above to confirm whether we process your information, ask what we collect or disclose, obtain a copy, correct inaccuracies, or request deletion. Depending on your state, you may also have the right to opt out of certain sale, sharing, targeted advertising or profiling, limit some uses of sensitive personal information, or appeal a decision on a request. You can exercise your applicable rights without unlawful discrimination.

The sections on collection, use and recipients describe the categories of information relevant to Drivings. We use website analytics for our own measurement and attribution. Our web analytics respect supported Global Privacy Control and Do Not Track signals. You can also manage optional storage through Cookie preferences and write to us to make an applicable opt out or appeal request. California residents can learn more from the California Privacy Protection Agency.

If the EU GDPR applies, you can complain to the supervisory authority in the European Economic Area responsible for your place of residence, work or the alleged infringement. Use the privacy request routes above to exercise rights such as access, rectification, erasure or objection. EU General Data Protection Regulation

Where Türkiye's Personal Data Protection Law applies, Article 11 includes rights to learn whether we process your data, how we use it and to whom we transfer it, and to ask for correction or deletion where applicable. Submit a request to the responsible company using a method permitted by Turkish law, including in writing at its address below. If you are unsure which company is responsible, contact us. The authority's guidance explains the response period and when you may complain. Türkiye's Personal Data Protection Authority

Where the UAE Federal Personal Data Protection Law applies, you may have rights to correct inaccurate data or ask us to restrict or stop certain processing. Use the privacy contact above to make your request. UAE Government guidance on data protection

Drivings study accounts are intended for people aged 16 and older. If you are a parent or guardian and believe a younger person has supplied information to Drivings, email privacy@drivings.com. Describe the account or feature involved and your relationship to the learner. We will review access, retention and deletion in line with the law that applies.

We use HTTPS for service connections, account and staff access controls, and dedicated providers for authentication and payments. The Security policy explains the safeguards and how to report a problem. Protect your sign in credentials and tell us promptly if you suspect unauthorised access.

We update this policy when our processing, providers or applicable requirements change. We will give additional notice of material changes where required, and seek consent before any new use that requires it. The latest review date appears at the top of the page.

Use privacy@drivings.com for questions about this notice, to make a privacy request or to discuss how we handled one. Include the name of the feature or product and the email you used, if applicable. Keep sensitive verification information out of the first message.