Privacy policy

Road to Permit · Version of 3 November 2026

Who we are

Road to Permit is made by Cloud Connected: Cloud Connected sp. z o.o., pl. Doktora Edwarda Łuczkowskiego 9, 22-100 Chełm, Poland, registered in the National Court Register (KRS) under number 0000863687, tax number (NIP) 5632442947. We decide how your data is used, so under the EU's General Data Protection Regulation (GDPR) we are the "controller".

Privacy contact: contact@cloudconnected.pl. Write to it about anything in this policy. For help with the app, write to contact@cloudconnected.pl or, once you have signed in, use Contact us in the app's Settings (see "Contacting us from the app").

This policy covers the Road to Permit app on iPhone, Android and the web, our website, roadtopermit.com, our Instagram profile, our posts on Facebook, and the driving-school partner programme: its application form and its Partner Portal.

In short

  • The app's first screen tells you what the app keeps, that it also collects usage statistics and that you can turn them off in Settings, and links this policy. Nothing goes to our server before you move on from it.
  • You can use the app without giving us your name or e-mail address. The app keeps your progress on your device and a copy on our server, in an account without your name or e-mail address. That copy reaches a new phone or your other devices only after you sign in with Google, Apple or your e-mail address.
  • Signing in, with Google, Apple or your e-mail address, is optional.
  • The app sends usage statistics, such as finishing a mission or opening the Plus offer, to our own server, linked to your account and your country. They never include your answers or your exam date. You can turn them off in Settings → Usage statistics.
  • The AI instructor is an AI, provided by Anthropic, and every learner can use it, with or without Plus. Before your first message the app tells you what is sent and asks for your permission; it sends nothing until you agree. We don't keep the text of your messages, unless you report an answer: then we keep that answer and your message before it, so we can check them.
  • If you write a review in the web game, a person on our team reads it before it is published. Our website then shows your rating, your comment and the name you typed, or no name, with a note if you got Plus free. You can withdraw it at any time.
  • If you rate the app or write a review in the App Store or on Google Play, Apple or Google publish it and show it to us with the name you use there; the app sends them nothing about you.
  • If you have signed in, you can write to our team from Settings → Contact us. We answer by e-mail at your account's address, and delete your message 12 months after you sent it.
  • If your state isn't in the app yet, you can tell us which it is, and ask for one e-mail when we add it. We send that one e-mail and then delete your address.
  • When you buy Plus on our website, Stripe takes the payment, and its payment page opens with your account's e-mail address, which our server sends it; we never see your card details.
  • We don't sell your data, we don't show ads, and we don't track you across other apps or websites.
  • Driving schools that will take part in our partner programme see only totals, never who you are; a number below 5 is never shown to them.
  • In the app you can download a copy of your data, and delete your account and your data, at any time.

What we collect and why

Your progress and settings

What: your answers (the question, the option you picked, whether it was right, how long you took, when), your missions and practice exams, your readiness score for each day, your streak freezes, postcards and achievements. Your settings: the app language and the explanation language, the state you're preparing for, your exam date, your daily study time, your reminder time and whether smart reminders are on, the car you picked, and your device's time zone. We also keep the app version and a random ID for each installation of the app; a new one is made after you reset your progress or delete your account.

Why: to run the course, work out your study plan and your readiness, and keep your progress when you change or add a device.

Legal basis: we need this data to provide the app you asked for (GDPR Art. 6(1)(b)).

Counts across all learners: once a day our server also counts, for each question, how many learners got it right on their first try and which wrong answer was picked most often. The app shows these counts under a question, for example "62% of learners get this one right on their first try", only once at least 30 learners have answered it, and our own test accounts are left out. The counts name no one, and nobody can see how you answered. Legal basis: our legitimate interest in showing learners which questions are tricky (GDPR Art. 6(1)(f)).

Your account

When you move on from the app's first screen, which tells you this, the app creates an account for you on our server. It has no name and no e-mail address, only a random ID. Even without a name, that ID ties your progress together, so the law treats it as personal data, and so do we. Nothing is sent to our server before that screen, and your progress is saved under the account once you finish the first setup.

The copy on our server does not work as a backup until you sign in with Google, Apple or your e-mail address (on the website and, from version 1.1, in the iPhone and Android apps). Until then the app shows no account ID, and it marks your sign-in session to be left out of your phone's backups, so expect a new phone, or the app installed again, to start a new account; the earlier one is deleted as "How long we keep it" describes. To keep your progress when you change phones, sign in first (Settings → Account).

If you choose "Continue with Google", Google gives our sign-in service your Google account ID and your e-mail address, and also your name and profile picture, as Google's permission screen shows. We keep only your Google account ID and e-mail address, and use them only to sign you in and to answer a message you send us from the app (see "Contacting us from the app"), and the address also to fill it in on Stripe's payment page when you choose to pay for Plus on our website (see "Purchases") and to warn you by e-mail 30 days before we delete an account you have not used for 24 months; see "How long we keep it" (proposed) and to tell you by e-mail about a change to Plus, to the app or to our terms; see the terms, sections 10 and 13 (proposed); our sign-in service removes your name and picture before it stores anything. We never see your Google password, and we don't post anything to your Google account. You can remove the app's access in your Google Account settings.

If you choose "Continue with e-mail", on the website or, from version 1.1, in the iPhone or Android app, you give us your e-mail address, and our sign-in service sends a six-digit code to it through Resend, our e-mail service; Resend receives the address and the e-mail's text. We keep the address with your account and use it only to sign you in, to answer a message you send us from the app and to fill it in on Stripe's payment page when you choose to pay for Plus on our website, as with Google. If no account has that address yet, our sign-in service opens one under it as soon as you ask for the code; it stays unconfirmed until you enter the code. If no code is ever entered, we delete that account automatically once 7 days have passed since the last code we sent to it, at our next daily clean-up, so within 8 days of that code. If our team has given that account free Plus, or access to the Partner Portal, before then, it stays until we delete it. The code works once and only for a short time. If you later sign in with Google or Apple and they give us the same address, it is the same account.

If you sign in on a device where you already had progress without signing in, we move that progress into your account and delete the account it was saved under.

If a device was signed in to your account and that sign-in ended elsewhere (you deleted the account on another device, or its session ended), then on the website, and in the iPhone and Android apps from version 1.1, the device keeps its copy of your progress for that account only. It sends nothing more of that progress to our server, and it signs in to no other account, a new account under the same address included, until that same account signs in on it again (the progress made in the meantime then goes up to it) or you reset progress on the device, which deletes the copy. A sign-in tried there with another account is ended at once, and nothing of the device reaches that account. But if no account had that e-mail address, Google account or Apple ID yet, the attempt still opens one on our server, holding only that address or ID and nothing else; it stays until you or we delete it. Version 1.0 of the apps does not keep the copy apart, and neither does a device on which an earlier version found that the sign-in had ended: there a sign-in with any account moves the copy into that account, and once the app starts again it saves the copy under a new account with no name, which a later sign-in moves into whichever account signs in.

If you sign in with Apple, Apple gives us an ID and an e-mail address, which can be a private relay address. We use the address as we use Google's: to sign you in, to answer a message you send us from the app, and to fill it in on Stripe's payment page when you choose to pay for Plus on our website. We keep no token from Apple yet. Once we have built the step that ends your Apple sign-in when you delete your account, we will keep a token from Apple for that alone. Until then, you can stop using Sign in with Apple for the app in your Apple Account settings.

Legal basis: Art. 6(1)(b).

Usage statistics

The app on iPhone, Android and the web sends usage statistics to our own server and to no one else. We use no third-party analytics tool in the app.

What an event holds: which step you reached, when, the state you study for, the app's language, the screen it came from, the platform (web, iPhone or Android), and the country, and only these details, each from a fixed list:

  • the app is ready on this device (no details);
  • your study plan was settled: your daily study time, whether you set a reminder time, which of the app's eight cars you drive, and whether you gave an exam date, never the date itself;
  • the map came into view (no details);
  • a new mission started: its topic, and whether you started it from your current point on the map;
  • a mission ended: its kind (a mission, a review, a drill, a checkpoint, a practice exam or a road trip), the number of questions and of right answers, whether it was the end of the free part, your readiness afterwards, whether its end showed a look at Plus and its price, which the app shows at most once at each of a few mission ends, and the ID of that learning session, which links the event to the session's record on our server;
  • the Plus offer opened: whether it opened by itself, once, the first time the free questions ran out, or from a look at Plus at a mission's end, and no details when you opened it yourself; you tapped its button before signing in and were sent to sign in, started buying Plus, were sent to the payment page, came back from it, and Plus became active, each with the store (our website's payment page, the App Store or Google Play);
  • in the iPhone and Android apps from version 1.1, what became of a course update (see "Course updates in the apps" under "Technical data"): whether it was applied, refused, failed or is waiting, one word from a fixed list for the reason, and the update's number;
  • in the web game, it was opened from the practice check on our website (no details);
  • a step of the first setup or of the study plan was shown, or you left it with its "Skip": the step's name, and whether it was skipped;
  • a mission was left before its end, by closing it or going back, or because the app went to the background: the mission's kind and topic, the number of questions answered, of right answers and of questions in it, whether it was your first drive, whether it was closed or went to the background, and the ID of that learning session;
  • at the end of your first drive, how you answered the reminder offer: a reminder on your phone, Google Calendar, the calendar file, or "Not now"; for a phone reminder, whether your phone allows the app's notifications; and whether you changed the time it suggested, never the time itself (see "Reminders");
  • the device is one of our team's (no details; see below).

Each event also has an ID of its own: a random one, or, for a mission left before its end, one made from the session's ID and the reason, and for the reminder offer, one made from the session's ID and your answer, so that we keep it once. An event never holds your individual answers, your exam date, a message you typed or any other text you wrote. Our server refuses an event that carries a detail not on these lists. The country is the one that the network in front of our server works out from your IP address, as two letters; we never keep your city, your region, your IP address or your browser's details with an event.

Our team's devices: our team opens the web game once with the link `?internal=1` on its own phones and computers. The device then remembers it, and every account on that device sends the event above, which labels the account as a test account in our admin panel. A test account is left out of our figures and out of every count of the partner programme (see "Partner referrals"). The label stays when the device forgets the link, and only our team can change it. If you sign in on a device of our team, for example while we help you, your account gets the label too; you can ask us to remove it (see "Your rights"). The link changes nothing else, and anyone who opens it can only label the accounts of their own device.

Linked to your account: each event is sent with your sign-in session and kept with your account's ID, so we can follow how one learner moves through the course, for example from the first mission to a practice exam.

Why: to learn which parts of the course help learners and where they stop, to improve the course and the study plan, to see how many learners open the Plus offer and buy it, and, in the iPhone and Android apps from version 1.1, to see whether course updates reach them and work.

When nothing is sent: before you move on from the app's first screen; in a version of the app without our server; and once you turn usage statistics off.

Your choice: usage statistics are on unless you turn them off in Settings → Usage statistics. The app's first screen says so. Turning them off stops every later event from that device; the choice is kept on that device only, so set it on each device you use, and it stays as you set it when you reset your progress. Events already sent stay until they are deleted as below. To have them deleted sooner, delete your account, or write to us (see "Your rights"); an account that never signed in cannot be matched to an e-mail, so for it, delete the account or reset your progress in the app.

Who sees them: our team, in our admin panel (see "Our admin panel"). They are not sent to driving schools or anyone else.

How long: deleted 13 months after we receive them, by a daily job, and at once when you delete your account. "Download my data" includes them.

Legal basis: Art. 6(1)(f), our legitimate interest in improving the course and in knowing how the app is used and bought. You can object to this use at any time; the switch in Settings does it for later events.

Partner referrals

We are preparing a partner programme for driving schools. It is not open yet. No school can be listed, ranked or credited until we have checked its driving-school licence and it has accepted a partner agreement that our lawyer has approved; no school has. The programme runs on our website and in the web game only, never in the iPhone or Android app, and its public ranking covers Florida only.

A school's link. A school can give its students a link to roadtopermit.com that carries the school's code and, optionally, how the link was shared (its website, a direct link, the front desk, e-mail or social media). When you open our website from such a link, the website:

  • keeps the school's code, the way the link was shared and the time, and nothing else, in your browser's local storage for 30 days; if you already followed another school's link in those 30 days, the first one stays;
  • removes the code from the address bar, and adds the code of the link you followed to the website's links to the game;
  • tells our server, once for that page, that a page was opened through a school's link: that link's code, the page's address, the way that link was shared and the platform. Our server records the time it received the report.

If you have turned usage statistics off in the web game in the same browser, the website does none of this and removes a school's code it kept.

In the web game, a school's link is used only after you have moved on from the first screen and only while usage statistics are on. The game keeps the school's code with the way the link was shared and the time, in local storage for 30 days (first link wins), and, for as long as the browser tab is open, which school it has already reported. It reports the game's opening once per school and tab, and only from a page opened with the school's link. The code of the link that opened the game, or otherwise the code it keeps, then travels with your next usage statistics events, never with the Plus offer's or a purchase's. Our server credits only the first school that is active in the programme.

No visitor ID. Neither the website nor the game creates an ID for your browser or device. Our server counts a visit once a day per school, under a code it makes from the day, the school's code and your IP address with a key only our server has; it does not keep your IP address, the code changes every day, and once the day is over the code is replaced by one made from nothing about you, so it can no longer be matched to any IP address. These visit records are kept 13 months and then deleted. Our server records visits and referrals only for a school that is active in the programme; while none is, it records neither.

Which school brought your account. When an event from the game carries the code of a school that is active in the programme, our server records, once, that this school brought your account: the school, the time our server received it, your state and the way the link was shared, and later when it last saw that school's code. A later link from another school never changes it. Whether you then studied, or finished a mission, is read from the learning sessions the app uploads, never from usage statistics. The record is deleted 13 months after it was made, and at once when you delete your account.

What a school sees. In its private Partner Portal, a school sees only totals for the last 30 and 365 days: visits through its links, how often the website and the game were opened, how many learners its links brought, how many of them studied and how many finished a mission, overall and, for the last 30 days, by the way its links were shared, and its place in the ranking. Any number below 5 is shown as "fewer than 5", and a figure that would let a number below 5 be worked out from the others is hidden too. Schools never see your account ID, name, e-mail address, answers, readiness, exam date, location, purchases or any other study progress, and purchases never count in anything a school sees.

The public ranking. Once schools take part, the website's Florida pages in English and its page for driving schools, and the Florida postcards of the web game, may list the active schools of a city, ranked by points from the last 30 days: 100 for each learner who studied after following the school's link, 35 more for each of them who finished a mission, and 1 per visit, up to 99. They show the school's name, city, rank and website and, only when the number is 5 or more, how many learners studied after following its link (and, in the web game, its visits). No place in the ranking is paid for; if one ever were, we would label it "Sponsored". A school's website opens without telling it which page you came from.

We leave out of every count the accounts our team has labelled as test accounts or scripts. We don't use the school's code to track you across other apps or websites or for advertising.

Legal basis: Art. 6(1)(f), our legitimate interest in measuring which schools bring learners and in keeping the ranking fair and resistant to manipulation. You can object: in the game, turn usage statistics off, which also deletes the stored code; on the website, clear the site's data in your browser; or write to us.

Driving-school partner applications

If a driving school applies to the partner programme, we collect what the form asks for: the school or DBA name, the legal business name if given, the state, city, county, business address and ZIP code, the website, the driving-school licence or registration number if given, the languages and services, any notes, and the partner contact's name, e-mail address and phone number. We also record the version of the programme's rules accepted with the application, when it was accepted, that the applicant confirmed the authority to apply for the school, the review status and our review note. If the applicant asks for free promotional materials, we record which items and the shipping name and address. A school can also apply, as our page for driving schools suggests, by writing to contact@cloudconnected.pl; we use what it writes for the same purposes.

Applying creates no account and gives no portal access. Once our e-mail service is set up (see "E-mails about the partner programme"), we send one confirmation to the e-mail address given, the same whatever that address is, and tell our team that a new application has arrived, with the school's name, city and state. Our limits on the form use a code made from your IP address and one made from the e-mail address, with a key only our server has, kept two days.

A person on our team reviews every application. If we approve it, we create the school's record, not yet listed, with its referral code, and give the contact access to the Partner Portal: an invitation to set a password, or, if the address already has a Road to Permit account and its owner has confirmed the address, that account. The school is listed only after we have checked its licence and recorded its acceptance of the partner agreement: who signed it, when, and where the signed copy is kept. If we reject the application or ask for changes, we e-mail the contact with our note.

We use this information only to review the application, run the partnership, list an approved school, give portal access, write to the school about the programme, and send the materials asked for. We never use it to profile learners or to advertise to them.

How long: an application that is rejected or withdrawn is deleted 24 months after its last change, and one left open without any change is deleted after 12 months. An approved application stays while its school's record exists; once that record is removed, the application is deleted when 24 months have passed since its last change. A materials request is deleted 24 months after it is delivered or cancelled. If the contact's Road to Permit account is deleted, the application stays, as the school's business record, without the link to that account.

Legal basis: Art. 6(1)(b), steps the school asks for before a partnership; Art. 6(1)(f), our legitimate interest in security, fraud prevention, record keeping and running the programme.

The Partner Portal

People from an approved school sign in to the Partner Portal with their e-mail address and a password. We keep their account (e-mail address, sign-in records), their role at the school, when they were invited and when they last signed in. The school's record holds its business details, its contact person's name, e-mail address and phone number, its licence number and when and by whom we checked it, the agreement's version, who signed it and when, where the signed copy is kept, and our notes. We keep these while the school takes part, and as the law requires for business records afterwards. A member who wants their portal account closed writes to us. Legal basis: Art. 6(1)(b), the partnership; Art. 6(1)(f) for our notes and security.

Our admin panel

A few people on our team, whose accounts we have enabled for it, use a private admin panel. Each signs in with a password and a code from an authenticator app; a password alone does not open it.

What they see: for an account, its e-mail address if it signed in, whether it signed in and how, when it was created and last used, its settings and study plan (the exam date included), its learning sessions, readiness, achievements, postcards, purchases and usage statistics with their country, and our team's label for it. They also see partner applications and the schools' records, with the exact counts of each school, the reviews learners write and the messages learners send us from the app, each with the e-mail address of the account that sent it.

What they can do: label an account (a real learner, a test account, a suspected test account or a script) with a note; give or take back free Plus; end an account's sign-in sessions; delete an account's progress on our server, or the whole account; send a password reset; approve or reject a learner's review, or take a published one down; mark a message from the app answered, or open it again; review partner applications and run the schools' records.

The record of what they do: every change they make is logged with who acted, on which account and when, with no e-mail address and no note, for a review only its ID and our reason, never its text or name, and for a message from the app only its ID and whether it is answered, never its text; viewing an account, and exporting a list they have loaded, are not logged. Our server's functions cannot change or delete a log entry; a daily job deletes entries after 24 months. If an account is deleted, its log entries lose the link to it.

Why: to support learners, keep the service and its purchases working, keep test accounts and scripted activity out of the figures, review partner schools and prevent abuse. Legal basis: Art. 6(1)(f). Our label of your account and its note are in "Download my data" and are deleted with your account.

The Reels tab: a member of our team who makes our social-media videos may have access to one part of the panel only, the Reels tab, which shows no learner's data. There that team member uploads a still frame of our own driving footage and picks the state it was filmed in; the frame is used only to suggest a question from our course that fits it. The panel shrinks the frame, our server removes its location and camera data, and sends it once to Anthropic with that state's list of questions; we don't keep it. A frame may show other road users, pedestrians or number plates; nothing else about them is sent, and the video the tab makes is recorded from our game and holds none of the footage. We delete the finished videos once they are 14 days old, the next time our admin panel is opened, and the record of each request, with no free text, after 90 days. Legal basis: Art. 6(1)(f), making our own marketing material.

The AI instructor

The AI instructor answers questions about traffic rules, road signs, the exam and the app. Every learner can use it, with or without Plus and whether or not you have signed in, within a daily limit: in the web game, and in the iPhone and Android apps from version 1.3 (versions 1.1 and 1.2 of the apps open it with Plus only). Without Plus it discusses the free part of your state's course; with Plus, the whole course. The buttons that open it name the AI instructor ("Ask AI instructor", and after a wrong answer in your first drive "Why? Ask the AI instructor"), and the chat is marked "AI" for as long as it is open.

Before your first message, the app tells you that the instructor is an AI, not a person, that Anthropic provides it, what is sent and what we keep, and that its answers can be wrong; then it asks for your permission. Nothing is sent until you choose "Agree"; with "Not now" nothing is sent. Your choice is saved with your account, so it applies on your other devices too, and you can withdraw it at any time in Settings; the app then asks again before your next message. If we change the provider, send it more data or use the data for a new purpose, the app asks you again.

When you send a message, the app sends it to our server with the ID of the question you're looking at (not its text), your explanation language, your device's time zone and the earlier messages of the conversation. Our server adds the question and its explanation from our own content, and sends the last six messages, yours and the instructor's, to Anthropic. Before it does, it replaces e-mail addresses, phone numbers and ID numbers in your messages with placeholders; it cannot recognise names or street addresses. With the messages goes a code made from your account ID with a key only our server has: Anthropic can use it to spot abuse, and only we can link it back to your account. We don't send Anthropic your name, e-mail address, IP address or account ID.

Please don't type names, addresses, document numbers, health details, immigration status or other sensitive information in the chat. The instructor doesn't need them, and a line under the box where you type reminds you.

We don't store the text of your messages or of the answers, except when you report an answer (below). On your device the conversation stays only until you close the app, reset your progress or delete your account. For each message we keep a record without any text: the date, the question ID, the language, the AI model, how many tokens it used, the cost, how long it took and how it ended. We use these records for the daily limit, to control costs and to prevent abuse, and keep them as "How long we keep it" says.

Under every answer, "Report this answer" lets you tell us that an answer is wrong or misleading, harmful or offensive, or something else, with a comment if you like. Before you send it, the app says what goes with it: the answer, your message it replied to, the reason and your comment, the state and the question you were asking about, and the app's language, version and platform, linked to your account. Our server first checks that it gave you that answer, then replaces e-mail addresses, phone numbers and ID numbers in your message and your comment with placeholders, and keeps the report for our team, who read it to correct the instructor. A report goes to no one else: not to Anthropic, and it is never published. You can send up to ten reports a day. We delete a report 90 days after we have dealt with it, and 180 days after you sent it at the latest; it is in "Download my data" and goes when you delete your account. Please don't type personal details in the comment.

Anthropic processes your messages for us under a data processing agreement.

AI answers can be wrong. The official handbook decides. The instructor gives no legal or immigration advice; for questions about documents or status, it points you to the official website of your state's licensing agency (in Florida, FLHSMV).

Legal basis: Art. 6(1)(b) to answer you; Art. 6(1)(f), our legitimate interest in limits, costs and preventing abuse, for the records, and in the accuracy and safety of the instructor's answers, for the reports you send.

The website's AI guide

Our website can offer a free AI guide that answers questions about getting a permit or a licence in a state, from our own pages. We switch it on and off; while it is off, the website does not load it at all. It is not the AI instructor of the app, and it needs no account.

When it is on, an "Ask AI" button opens it. Before your first question it shows a notice: an AI from Anthropic writes the answers from our pages and they can be wrong; they are not legal advice, and Road to Permit is not a government agency; answers about visas or immigration status repeat what the official agency publishes, and you should check them with the agency or an immigration attorney before you act; don't share personal information; your question goes to Anthropic; and, where the website uses it, that a security check by Cloudflare runs first. Nothing is sent until you accept the notice. Your acceptance is kept in your browser's session storage until you close the tab.

What is sent: your question (up to 900 characters), the state, the language, the address of the page you are on and up to two of your earlier questions in this conversation, to our server; never the guide's answers. Since 7 October 2026 a question about a visa or another immigration status is answered like any other, and the answer ends with a fixed note: it is based on the agency's official information, it is not legal advice, and you should confirm it with the agency or an immigration attorney. Please ask about a type of visa or status without describing your own situation; if you mention your own status, it is sent with your question. For every question our server first replaces Social Security numbers, other ID numbers, e-mail addresses and phone numbers with placeholders, then sends Anthropic your question, up to two of your earlier questions and the text of up to three of our pages about that state. It sends no IP address and no ID. Where we have switched it on, Anthropic may search the official websites our pages cite for that state to answer; it searches no other site.

What we keep: not your questions and not the answers. To limit how many questions one network can ask, we keep a code made from your IP address with a key only our server has, never the address itself, for two days. We also keep each day's totals of questions, tokens, searches and cost, with nothing about you, for 13 months.

Legal basis: Art. 6(1)(b) to answer the question you ask; Art. 6(1)(f), our legitimate interest in limits, costs and preventing abuse.

Exam results you report

After your exam date, the app asks how it went. Answering is optional, you can choose "Prefer not to say", and the score is optional too. We save your answer with your readiness and your chance of passing at that time.

We use it for two separate things:

  • to show your result on all your devices and adjust your plan (Art. 6(1)(b));
  • to check how well our readiness estimate predicts real results, so that we can make it more accurate for every learner (Art. 6(1)(f), our legitimate interest in an accurate estimate). This check never changes anything for you, and you can object to it (see "Your rights").

Reviews you write

You write a review for our website in the web game at roadtopermit.com/play/. Once you have signed in there, with Google or with an e-mail code, you can write us one in Settings → Account, and after your third mission the game asks you once on that device; you can choose "Not now". The web game does not offer Sign in with Apple yet: if you signed in with Apple on iPhone, you can write one only by signing in to the web game with an e-mail code at the same e-mail address, which reaches your account when your Apple sign-in shares that address with us rather than Apple's private relay address (our terms, section 7.3). The iPhone and Android apps ask you instead for a rating in the App Store or on Google Play (see "Ratings in the App Store and on Google Play"); they don't show a review you wrote for our website, which you read and withdraw in the web game. An account that never signed in cannot write one, and neither can an account of our team or one in a partner driving school's portal (our terms, section 20); a review whose account joins our team or such a portal after writing it is not published, and leaves our website if it was. We never give Plus, a discount or anything else for a review, and getting Plus free never depends on writing one.

What you write: a rating from 1 to 5 stars, a comment of up to 500 characters, and how to sign it: a name you type yourself (2 to 40 characters, and never your e-mail address), or no name, so that it shows as "Road to Permit learner". We keep it with your account's ID, the app's language at the time, when you sent it, and our decision: waiting, published or not published, with its reason and when we decided. You can have one review at a time.

Whether you got Plus free: when you send a review, when we publish it and whenever your Plus changes while we keep your review, our server works out from our purchase records whether your account ever got Plus without paying, with a promotion code that took the whole price or as a gift from our team, even if that Plus has since ended, and keeps the answer with the review. A purchase refunded to you does not count. If your account ever got Plus free, our website shows "Got Road to Permit Plus free" next to the review, as US rules on endorsements (the Federal Trade Commission's) ask; once it shows, it stays, and "Download my data" gives you the same answer. We tell you here rather than on the review form, because the form never mentions Plus: a review and Plus are not linked.

What we publish: nothing until a person on our team has read your review and approved it. Our website's home page, in every language, shows the six most recently approved reviews, each with:

  • your rating;
  • your comment as you wrote it, with extra blank lines left out (invisible control and text-direction characters are removed when you send it);
  • the name you typed, or "Road to Permit learner";
  • the month we approved it;
  • "Got Road to Permit Plus free", where it applies.

Our server also tells the page which language the app was in when you wrote the review, so that the page shows your text correctly. Anyone who visits roadtopermit.com can read your review while it is among those six, and search engines may copy it. When newer reviews are approved, an older one stays approved but is no longer shown, and shows again only if newer ones leave the site (withdrawn, taken down, or deleted with their account); no other page lists it. We never publish your e-mail address, your account ID, your state, your progress or anything else about you, and we never change your words or shorten them.

Please sign with a first name or a nickname, never your full name (first and last), and keep personal details out of the comment: nobody's full name, address, phone number, e-mail address, documents, immigration status or health, your own included. We don't publish a review whose comment or signature holds them.

How we decide: a person on our team reads every review and either approves it as it is or does not publish it, and may take a published review down later. Our reasons are about what a review says, never about its rating; they are in our terms, section 20. The web game's Settings → Account shows you whether your review is waiting, published or not published, and why.

Who sees it: before it is published, only our team, in our admin panel, with the e-mail address of the account that sent it; once it is published, anyone, as above.

Your choices: "Withdraw my review" in the web game's Settings → Account deletes your review from our server at once, and our website stops showing it within a few minutes. You can then write a new one. Deleting your account deletes your review too, and "Download my data" includes it.

How long: a published review stays until you withdraw it, you delete your account or we take it down. One we don't publish, or take down, is deleted 90 days after our decision. One still waiting is deleted 12 months after you sent it.

Legal basis: publishing your review rests on your consent (GDPR Art. 6(1)(a)), which you give by sending it and withdraw by withdrawing the review; this does not affect what was published before. Reading a review before it is published, the words "Got Road to Permit Plus free" and our record of each decision rest on Art. 6(1)(f): our legitimate interest in publishing only honest reviews, keeping personal information and abuse off our website, and following the US rules on endorsements.

Ratings in the App Store and on Google Play

In the iPhone and Android apps, after your third mission, the app asks Apple or Google once on that device to show their own rating prompt, and Settings → Account has a link to the store's page for writing a review; whether the prompt shows is Apple's or Google's decision. The app sends the store nothing about you and links nothing to your Road to Permit account.

What we receive: Apple or Google publish your rating, and any review you write, under their own terms, and show each written review to us in their consoles for app developers: in the App Store, the nickname you use there, your review's title and text, its stars, your country or region and the date; on Google Play, your Google Play name, your review's text, its stars, its language and date, and your device's model, its Android version and the app's version. A rating without a review reaches us only in the store's totals.

What we do with it: we read reviews there to learn what to improve and to answer questions, and we may reply to one; Apple or Google then publish our reply under your review. We can't change or delete your review, and we keep no copy of it outside those consoles. Because nothing links it to your Road to Permit account, it is not in "Download my data" and is not deleted with your account: you change or delete it in the store, under Apple's or Google's terms.

Legal basis: Art. 6(1)(f): our legitimate interest in knowing what learners think of the app, improving it and answering them.

Contacting us from the app

In the web game, and in the iPhone and Android apps from version 1.5, Settings has Contact us: for a question, a bug in the app, a mistake in a question or a text, a payment or refund, an idea or anything else. Everyone sees it, but only an account you have signed in to, with Google, Apple or your e-mail address, can send a message, because we answer by e-mail at your account's address. If you have not signed in, the app tells you so before you write anything, and offers the sign-in. Before you send, it tells you where we will answer and what we keep.

What we keep: your message (up to 2,000 characters; invisible control and text-direction characters are removed when you send it), the category you chose, the state you are studying for, and the app's language, version and platform (iPhone, Android or web), linked to your account, with when you sent it and whether and when we answered it. We don't store your e-mail address with the message: our team sees your account's address when it reads the message. You can send up to 5 messages in 24 hours. The app keeps nothing of your message on your device.

Who sees it: only our team, in our admin panel. Your message stays on our server with Supabase; it goes to no AI and is never published. Our answer is an ordinary e-mail from our team's mailbox, which Microsoft 365 provides (see "Who receives your data"), to your account's e-mail address; if you reply, your reply reaches the same mailbox.

How long: we delete your message 12 months after you sent it, whether or not we have answered it. It is in "Download my data", and it is deleted when you delete your account.

Please don't put passwords, card numbers or ID numbers, such as a driver's license, passport or Social Security number, in your message. We don't need them to help you.

Why: to answer you, and to fix what you tell us about, such as a bug or a mistake in a question. Legal basis: Art. 6(1)(b), to answer what you ask us about the app you use; Art. 6(1)(f), our legitimate interest in an app that works and questions that are right, for keeping your message after we answer it and for fixing what it reports.

Asking for your state

If the state where you take your test isn't in the app yet, the state step, and the state in Settings, let you tell us which it is ("My state isn't listed"), so that we add the states people ask for most first. You can also ask us to e-mail you once when we add it; that box is never ticked for you.

What we keep: the state you chose and the app's language, linked to your account (also one you haven't signed in to), with when you asked. If you ticked "E-mail me once": the e-mail address you typed, if you haven't signed in; if you have signed in, nothing more, because we use your account's address when the e-mail goes. Choosing again replaces your earlier choice. Our team sees only how many people asked for each state, never who asked.

The e-mail: when your state is added, our server sends you one e-mail, in the app's language, through Resend (see "Who receives your data"), and deletes your address right after. We send nothing else to that address. If you never tick the box, we never e-mail you about it.

How long: your address, until that e-mail goes, and at most 24 months after you last asked; then we delete it. The state you chose stays with your account, as a count, until you delete your account. It is in "Download my data".

Why: to know which states to add next, and to tell you once when yours comes, as you asked. Legal basis: Art. 6(1)(f), our legitimate interest in adding the states people need, for counting your choice; Art. 6(1)(a), your consent, for the e-mail, which you can withdraw by choosing again without the box ticked, or by deleting your account.

Technical data

When the app or the website talks to our servers, our providers record technical data: your IP address, the type of device or browser, the time, and the address requested. We use it to deliver the service, keep it secure and prevent abuse, for example by limiting how many new accounts one network can create. For the limits of our public forms and functions, we keep codes made with a key only our server has from your IP address (and, for the partner form, from the e-mail address given; for usage statistics, from your account ID), never the address or the ID itself, for two days.

Course updates in the apps. From version 1.1, the iPhone and Android apps check roadtopermit.com for updated course content (questions, explanations and translations) and download it, so they need no app update for it. Our host, Netlify, records the technical data above for each of these requests, and the address requested shows which state's course is downloaded; the requests carry no cookie, no account ID and no other identifier. The app checks that each update was published by us before it uses it, and keeps the downloaded course on your device until you reset your progress or delete your account; the number of the newest update it has checked stays after a reset, as it says nothing about you. While usage statistics are on (see "Usage statistics"), the app also sends one more event: whether an update was applied, refused, failed or is waiting, with one word from a fixed list for the reason and the update's number, and nothing else.

Legal basis: Art. 6(1)(f), our legitimate interest in running a secure service.

Our website

When you visit roadtopermit.com, our host, Netlify, records the technical data above for every request. The free game at /play/ does not use Google Analytics. The website's state pages show a "Last updated" date: the day their content last changed. Our home page asks our server for the reviews we have published and shows them (see "Reviews you write"); that request carries nothing about you beyond the technical data above.

On the public website pages, we count visits with Plausible Analytics, for every visitor and without asking, because it identifies no one. Plausible sets no cookies and stores nothing on your device. Your browser sends Plausible the address of the page, the page that sent you there, your browser, operating system and device type, and your IP address. Plausible uses the IP address to find your country and, together with your browser's details and a key that changes every day, to tell one day's visits apart; it then discards the IP address and never stores it. We see only totals, such as visits per page, per country and per source. On the website it also counts, in the same way and with nothing more about you, how often links to the game at /play/, to the App Store and to Google Play are tapped, and on which page (the link's kind only), how often the game bar's Play button and the language hint are used, and how often the practice check on /dmv-practice-test/ (and its pages in the other languages) is started and finished and its game and store links are tapped: the step's name only, never your answers or your score. In the free game at /play/, Plausible counts visits and the screens you open in the same way, but only while your usage statistics are on (see "Usage statistics"); when you turn them off, the game tells Plausible to send nothing. The iPhone and Android apps do not use Plausible. Legal basis: our legitimate interest in knowing how people find and use our website (GDPR Art. 6(1)(f)).

On the public website pages, Google Analytics is optional. It does not load until you choose Accept analytics. If you accept, Google Analytics measures the pages you visit, the page that sent you there, and technical information such as your browser, device type and approximate location derived from your IP address. It may set analytics cookies such as `_ga` to distinguish visits. We disable Google advertising signals and do not use this data for advertising. If you reject analytics, no Google Analytics tag is loaded. Your analytics choice is stored in your browser so that we can respect it on later visits.

Legal basis: your consent (GDPR Art. 6(1)(a)); where the ePrivacy rules apply, analytics storage on your device also starts only after your consent. You can change your choice at any time with the Privacy choices control on the website.

Our Instagram profile and Facebook posts

We run Road to Permit's profile on Instagram, road_to_permit, a business account where we post short videos. Most of our website's pages link to it at the bottom. It is a plain link: the pages load nothing from Instagram, and nothing goes to Instagram until you follow it; even then, our website asks your browser not to tell Instagram which page you came from. On Instagram, Meta, which provides Instagram in the EU through Meta Platforms Ireland Limited, processes your data under its own privacy policy, as its own controller, including for its cookies and advertising; we have no say in that.

Instagram's statistics. Meta gives us statistics (Insights) about our profile and our posts, made from what people do on them. For these statistics, Meta Platforms Ireland Limited and we are joint controllers (GDPR Art. 26), but only for creating the records behind them and adding them up. Meta provides its Page Insights Controller Addendum for this. As Meta's page Information about Page Insights Data says, Meta is responsible for telling you about this processing and for letting you exercise your rights. Meta alone decides which records it makes, and we never see them, only the totals.

What we see: from the statistics, totals only, never who did what: for example how many accounts our posts reached and how often they were viewed, how many people visited our profile, and, once enough people follow us, our followers' age ranges, gender, main cities and countries, and when they are active. We also see what you show or send us there: your public profile (your username, name and picture) when you follow us, like or comment on a post, mention us or write to us; your comments; and your messages to us. None of it is part of your Road to Permit account, so "Download my data" does not include it.

Facebook. We have no Facebook Page. Someone who works with us shares our posts from their own Facebook account and in topic groups on Facebook, and Facebook gives us no statistics about them. Meta, which provides Facebook in the EU through Meta Platforms Ireland Limited, processes everything that happens on Facebook, including likes, comments and shares, under its own privacy policy, as its own controller. If you write to that person about Road to Permit, we see your message with your Facebook name and picture and use them only to answer you, and we keep your message as "How long" below says. If you like, comment on or share a post that person shared, they see it with your Facebook name and picture, as anyone there can; we use a comment only to answer it, and it stays until you, that person or, in a group, the group's admins delete it. We run no ads or other paid promotion on Instagram or Facebook; if that changes, this policy will say so before it starts.

Legal basis: Art. 6(1)(f), our legitimate interest in presenting Road to Permit, answering the people who write to us and knowing how far our Instagram posts reach.

How long: your messages to our Instagram profile: we delete a conversation from our inbox once it is handled, at the latest 6 months after its last message; until then it stays in Instagram, and you can unsend your own messages at any time. Your messages about Road to Permit to the person who shares our posts on Facebook: that person deletes the messages about Road to Permit in their Messenger once they are handled, at the latest 6 months after the last one (proposed). Today: until that person deletes them; you can unsend your own messages as far as Messenger allows. Your comments under our Instagram posts stay until you or we delete them, and your comments on Facebook as the "Facebook" paragraph above says. Meta decides how long it keeps the statistics.

Your rights: about the statistics, you can write to Meta or to us; only Meta holds the records behind them, so we pass a request about them on to Meta. About your messages and comments, write to us (see "Your rights"), or unsend your messages (on Facebook, as far as Messenger allows) or delete your comments on Instagram or Facebook, whose settings also let you download your data there.

Purchases

On our website you buy Plus from us. Stripe, our payment provider, runs the payment page: you give your card details, and where needed your billing address, to Stripe, not to us, and Stripe e-mails you the receipt. On the website you may also buy Plus without signing in: the purchase then belongs to the account the app made for you without your name or e-mail address, our server sends Stripe only that account's ID, and you type your e-mail address on Stripe's page; right after paying, the app asks you to sign in so that Plus stays yours on every device. If you buy with an account you have signed in to, when you choose to pay (with the Plus offer's button; if you sign in first, the payment page then opens by itself, once), our server sends Stripe your account ID, so that Plus reaches your account, and your account's e-mail address, so that the payment page opens with it filled in. Stripe receives both as soon as our server makes the payment page, before it opens, also if it then does not open or you leave it without paying. Our server takes the address from your signed-in session, which it checks, never from anything else your browser sends; if it could not send one, Stripe's page asks you for your e-mail address, and you give it to Stripe there. Before it makes the page, our server checks that your account does not have Plus already, so that you do not pay for it twice. Stripe tells us which payment it was, that it was paid, and later whether it was refunded or disputed. We keep that payment's reference and state with your account ID: Plus ends if the payment is refunded or reversed. If a promotion code takes the whole price, there is no payment: Stripe tells us that the payment page was completed with a code, and we keep what you got, from which store and when, with no payment reference. That is how our server knows you got Plus free (see "Reviews you write").

The offer when you come back: on the website, once you have used up the free missions, Plus costs 20% less for the next 48 hours, once per account. To decide this, our server looks at the missions you have already synced, and keeps only your account ID and when your offer starts and ends; it never shows you the offer again, used or not. While it lasts, our server asks Stripe for the reduced price; Stripe learns no more about you than with any other purchase.

In the Android app you buy Plus in Google Play, and in the iPhone app in the App Store; the store handles the payment, and we never see your card or bank details. The app gives the store your account ID with the purchase, so that Plus reaches your account, and our server checks the purchase with Google or Apple and records what you bought, in which store and when.

The first time our server records a purchase, it e-mails our team a notice through Resend, our e-mail service, that names no buyer: the store, the product, the states, the amount of a website payment, the time, whether it was a test and whether a promotion code paid for it. To send it only once, our server keeps a code made from your account ID and the purchase's reference at the store, from which neither can be read.

What Plus includes, and how refunds work, is in the terms.

Legal basis: Art. 6(1)(b); the records we must keep for accounting and tax, Art. 6(1)(c).

E-mails about the partner programme

Our server sends the partner programme's e-mails (the confirmation of an application, the notice to our team, the result of a review) through Resend, an e-mail service, when we have set it up; without it, no such e-mail is sent. Resend receives the recipient's address and the e-mail's text. Invitations to the Partner Portal and password resets are sent by our sign-in service.

Reminders

In the iPhone and Android apps, reminders are scheduled by the app on your phone; we don't send them from a server. Your reminder time is saved with your study plan so that it follows you to your other devices. The app asks your phone for permission to show notifications only after you choose a reminder: on the study plan's reminder screen, in Settings, or with "Remind me" at the end of your first drive.

The web version can't send you reminders. At the end of your first drive it offers a daily event for your own calendar instead, made in your browser: a calendar file (.ics) that your browser saves and you open in your calendar app, or a link that opens Google Calendar's page with the event filled in. The event holds its title and text, the time you chose, the days it repeats (until the day before your exam date, or for 30 or 60 days), the web game's address and a random ID that we keep nowhere; nothing that identifies you, your device or your account. We don't receive the event, and the web version does not store the time you chose. If you open the Google Calendar link, your browser sends the event's details to Google, which handles them as part of your Google account under Google's own privacy policy; the link opens without telling Google which page you came from.

What we don't collect

For learner accounts, we don't ask for your age, date of birth, home address, phone number, identity documents or immigration status. Driving-school partner applicants separately provide business and contact details and optional shipping details as described under "Driving-school partner applications". We don't use a learner's device location: learners choose their state and, in the office finder, their county. The only place we keep is the country in usage statistics, which our server's network works out from the IP address; never a city or a region. The app doesn't access your contacts, photos, camera or microphone. We use no advertising IDs, no third-party analytics tool in the app and no crash-reporting tools. If we start using a new service that receives personal data, we'll name it in this policy first.

Who receives your data

WhoWhat they do for usWhat they receiveRole
SupabaseSign-in, database, server functions, logs and backupsEverything described above, and the technical data of each requestProcessor
NetlifyHosts our website and the web version of the appThe technical data of each requestProcessor
AnthropicThe AI behind the instructor, the website's AI guide when it is on, and the question suggestions in our admin panel's Reels tabYour messages to the instructor, and the questions you ask the guide, as their sections describe; frames of our own driving footage, as "Our admin panel" describesProcessor
StripeRuns our website's payment page and takes the paymentYour card details and billing details, and your e-mail address where we could not send it, which you give on Stripe's page; your account ID and your account's e-mail address, from us, when you choose to payProcessor for the payment; independent controller for its own legal duties, such as fraud prevention
ResendSends the codes of the e-mail sign-in (on the website and, from version 1.1, in the iPhone and Android apps), the partner programme's e-mails when we have set them up, a notice to our team of each new purchase, which names no buyer, and the one e-mail that your state has been added, if you asked for it ("Asking for your state")The recipient's e-mail address and the e-mail's text; for a purchase notice, our team's address and what "Purchases" listsProcessor
Google Analytics (Google LLC) — only after consent on public website pagesVisit statistics for the websiteAs "Our website" describesAnalytics service provider; Google's own terms also apply
Plausible Analytics (Plausible Insights OÜ, Estonia)Visit statistics for the website and the web game, without cookiesAs "Our website" describesProcessor
GoogleSign in with Google; Google Play (downloads and payments); Google Calendar, if you add the web game's reminder thereWhen you sign in with Google: that you signed in to our app. On Google Play: what Google's own policy describes. If you open the web game's Google Calendar link: the reminder event in it, from your browser, never from us (see "Reminders")Independent controller
AppleSign in with Apple; the App Store (downloads and payments)As GoogleIndependent controller
Meta (Meta Platforms Ireland Limited in the EU)Instagram, where we have our profile, and its statistics about it; Facebook, where someone who works with us shares our postsNothing from our app or website. On Instagram and Facebook: what Meta's own policy describesIndependent controller; joint controller with us for our profile's statistics, as "Our Instagram profile and Facebook posts" describes
Microsoft (Microsoft 365, Outlook)Our privacy and support e-mail addresses, and the mailbox from which we answer the messages you send us from the appWhat you write to us, with your e-mail address; our answer to a message you sent from the app, with your account's e-mail address, and any reply you sendProcessor
Visitors to roadtopermit.comNothing for us: they read our websiteA review you wrote, once we publish it, as "Reviews you write" describesThe public
Driving schools in the partner programme, once it opensNothing for us; they promote Road to PermitTotals only, as "Partner referrals" describes, never a number below 5Not a recipient of learners' personal data

Processors work for us under data processing agreements and may use your data only to provide their service to us.

Google and Apple act on their own account, under their own privacy policies, and so does Meta, except for our profile's statistics, for which it is a joint controller with us.

We don't sell your personal data and don't share it for advertising. We disclose data to authorities only when the law requires it.

The app and the website link to official websites, such as your state agency's, and the partner listings will link to schools' websites. When you open one, that site's own privacy policy applies.

Where your data is stored

Our providers store and process data in the United States. Google Analytics may process website analytics data in the United States and other locations under Google's terms.

Plausible stores the website's visit statistics in the EU.

We are based in the EU, so when data leaves the EU we protect it with the European Commission's standard contractual clauses or the EU–US Data Privacy Framework, depending on the provider. You can ask us for a copy of these safeguards.

How long we keep it

These periods are design decisions. A period marked “proposed” is not decided yet; until it is, the period after "today" applies.

DataHow long
Your account and progress, if you never signed inDeleted automatically when the app has sent nothing new for 180 days and you bought nothing. The progress on your device stays, and is saved again when the app next connects
Your account and progress, if you signed indeleted 24 months after your last activity, after we warn you by e-mail 30 days before (proposed). Today: until you delete the account
An account opened by a code you asked for and never enteredDeleted automatically by a daily clean-up once 7 days have passed since the last code we sent to it, so within 8 days of that code. If our team has given the account free Plus or access to the Partner Portal before then: until we delete it
An account opened by a sign-in that a device refused because it keeps another account's progress ("Your account"): only the e-mail address, Google account ID or Apple IDUntil you or we delete it
Usage statistics13 months after we receive them, or until you delete your account, if sooner
Which partner school brought your account13 months after it was recorded, or until you delete your account, if sooner
Visits through a partner school's link (a daily code, no IP address)13 months
Codes made from IP addresses, e-mail addresses and account IDs for our limits2 days
The website's AI guideYour questions and the answers: not kept. Each day's totals, with nothing about you: 13 months
Partner applications and materials requestsAs "Driving-school partner applications" says
Our team's label of your account, and its noteUntil you delete your account
Your reviewPublished: until you withdraw it, you delete your account or we take it down. Not published, or taken down: 90 days after our decision. Waiting: 12 months after you sent it
A rating or review in the App Store or on Google PlayWe keep no copy. Apple or Google keep it under their terms until you change or delete it there
A message you sent us with Contact us in the app12 months after you sent it, whether or not we have answered it, or until you delete your account, if sooner
The state you asked us to add, and the address for its one e-mailThe state: until you delete your account. The address: until that e-mail goes, at most 24 months after you last asked
Messages and comments on our Instagram profile, and messages and comments about Road to Permit on FacebookMessages to our Instagram profile: we delete a conversation once it is handled, at the latest 6 months after its last message; until then it stays in Instagram, where you can unsend your own messages. Messages about Road to Permit in the Messenger of the person who shares our posts on Facebook: that person deletes them once they are handled, at the latest 6 months after the last one (proposed). Today: until that person deletes them; you can unsend your own messages (as far as Messenger allows). Comments under our Instagram posts: until you or we delete them. Comments on the posts that person shares on Facebook: until you, that person or, in a group, the group's admins delete them. Instagram's statistics: as Meta decides
The record of our team's actions24 months; an entry about your account loses the link to it when the account is deleted
A frame uploaded to our admin panel's Reels tabNot kept. The videos it makes: deleted once 14 days old, the next time our admin panel is opened; the record of each request: 90 days
AI message records (no text)90 days (proposed). Today: 13 months
An answer of the AI instructor you reported, with your message before it and your comment90 days after we have dealt with it, and 180 days after you sent it at the latest
Daily AI totals and the per-minute AI counter12 months after your last message (proposed). Today: 13 months
Our sign-in service's security records (IP address, and the e-mail address of a signed-in account)180 days (proposed). Today: to confirm; they are not deleted with the account
Server logsat most 90 days (proposed). Today: our providers' settings, to confirm
Backupsat most 30 days (proposed). Today: to confirm
Purchase recordsWhat you bought, and a website payment's reference and state: until you delete the account. Stripe, Google and Apple keep their own records under their policies. Accounting records: as the law requires
The code that keeps our team's notice of a purchase to one ("Purchases")Kept, since the app sends your purchases again for as long as you have them. Once your account is deleted, nothing can link the code to you or to the purchase
Data on your deviceUntil you reset your progress, delete your account or remove the app; a school's code, 30 days
The file of "Download my data" on iPhone and AndroidUntil your next download, a reset, a deletion or the next start of the app

Downloading and deleting your data

  • Settings → Account → Download my data gives you a file with your account and everything our database keeps for it, and what the app keeps on this device: your progress, settings and results, your usage statistics, your review, if you wrote one, the instructor's answers you reported, the messages you sent us with Contact us, the state you asked us to add, which partner school brought your account, if one did, and our team's label of your account. On a phone the app opens the share sheet, so you choose where the file goes; on the web your browser saves it. The file does not include our sign-in service's own logs of sessions and sign-in events (IP address, device type).
  • Settings → Account → Delete account and data deletes your account and everything our database keeps for it at once, your review and your messages to us included, then clears the app on this device, the AI conversation and a stored school code included; on a device of our team it leaves the device's mark (see "Our team's devices" under "Usage statistics"). What it does not delete is in the last point below.
  • Settings → Account → Withdraw my review, in the web game, deletes your review on its own, at any time.
  • If you never signed in, Reset progress in Settings also deletes your data on our server. If you are offline, the app finishes it when it is back online.
  • If you are signed in, Reset progress clears this device and signs it out. Your account keeps your data. The reset screen says which of the two will happen.
  • Removing the app does not delete your data on our server. Delete your account first.
  • Deleting your account deletes what our server keeps, not the copy another of your devices keeps. That device stops syncing; on the website and from version 1.1 of the apps it also sends nothing more of that copy to our server and signs in to no other account with it ("Your account" says what version 1.0 does). Reset progress there to delete it.
  • Copies in our providers' backups and logs disappear when those expire. Our sign-in service's security records are not deleted with the account; see "How long we keep it". The record of our team's actions keeps an entry without the link to your account until it is 24 months old. The code for each purchase's notice ("Purchases") stays, and without your account nothing can link it to you.

If you never signed in, the app is how we know the data is yours: use Download my data and Delete account and data there. We don't ask for documents or an e-mail address.

Your rights

Under the GDPR you can:

  • get a copy of your data, also in a machine-readable format;
  • have it corrected;
  • have it deleted;
  • limit how we use it;
  • object to the uses based on our legitimate interests, such as usage statistics and partner referrals;
  • withdraw your consent, where we asked for it, for example to publishing your review, by withdrawing it; this does not affect what we did before.

Download and delete in the app, as above; change your settings in the app, where Settings → Usage statistics turns usage statistics off. For anything else, write to contact@cloudconnected.pl. We answer within one month; if a request is complex, we may take up to two more months, and we tell you so within the first month.

You can also complain to a data protection authority, for example in the country where you live or work. Our lead authority is the President of the Personal Data Protection Office in Poland (Prezes Urzędu Ochrony Danych Osobowych, UODO; uodo.gov.pl).

If you live in the United States

Wherever you live, you can see and change your settings in the app, turn usage statistics off, download a copy of your data (Settings → Account → Download my data) and delete your account and data (Settings → Account → Delete account and data). You can write to us at contact@cloudconnected.pl about anything else, and we will answer.

The law of the state where you live may give you further rights, such as appealing our answer to a request, or letting someone you authorize make a request for you. Where such a law applies to us, we follow it. We won't treat you differently for asking.

We don't sell personal data, don't share it for cross-context behavioral advertising or use it for targeted advertising, and don't use it to profile you in ways that have legal or similarly significant effects. So browser opt-out signals such as Global Privacy Control change nothing in what we do.

Young learners

Many of our learners are teens preparing for a learner's permit, which Florida issues from 15 (other states: to confirm). The app collects the same data from them as from everyone else, and only the data this policy describes. It doesn't ask anyone's age or date of birth. It has no public profiles, no messages between users and no ads, and signing in is optional. A learner who has signed in to the web game may write a review there: a person on our team reads it before it is published, it is signed with a name the learner types or with none, and we don't publish one that holds personal information. A learner who has signed in can also write to our team with Contact us; only our team reads the message, and we answer by e-mail at the account's address. Purchases in the iPhone and Android apps go through the app stores, whose family features let a parent approve them. The AI instructor needs no purchase: every learner, teens included, can use it, signed in or not. Before the first message the app says that the instructor is an AI provided by Anthropic and what is sent, and asks for permission; nothing is sent until the learner agrees, and a parent or guardian can withdraw that permission in Settings on the teen's device. The partner programme's school listings will appear only on our website and in the web game, and schools see no number below 5.

The app is not meant for children under 13. If we learn that a child under 13 has an account, we delete its data on our server.

A parent or guardian can download or delete a teen's data in the app on the teen's device, and turn usage statistics off there. For an account signed in with Google, Apple or an e-mail address, they can also write to contact@cloudconnected.pl; we find the account by its sign-in e-mail address and, before we act, confirm the request by e-mail with the account's owner. An account that never signed in has no name or e-mail address a request could be matched to, so for it the app on the teen's device is the way.

Automated estimates

The app estimates your readiness, your chance of passing and your study plan automatically, from your answers. These estimates only guide your studying: they never block the app or any feature, never change a price, and we never pass them to anyone else, such as an employer, a school, a driving school or an agency. They have no legal or similarly significant effect on you. A partner school's ranking counts how many learners studied after following its link, never any learner's readiness or answers.

Cookies and storage on your device

The app itself does not use analytics cookies. Plausible, which counts visits on the public website pages and in the web game, sets no cookies and stores nothing on your device; in the game, turning usage statistics off writes one entry, `plausible_ignore`, that tells it to send nothing.

On the public website pages, if you accept analytics, Google Analytics may set analytics cookies such as `_ga` and related cookies. We do not load Google Analytics before you accept it. We store your analytics choice in the browser's local storage so that we can respect it; you can change that choice with the Privacy choices control.

The website's pages can show two small notices: a bar at the bottom about the free game, and, when your browser prefers another of the website's languages, a line at the top offering the page in that language. When you close one of them, use it, or (for the language line) choose a language from the menu, the browser keeps one entry in its local storage so that it does not show that notice again: `roadtopermit.game-bar` or `roadtopermit.language-hint`, holding only the word `closed`. It is a preference you chose; it holds no personal data and identifies no one, and it is not sent to us or to anyone else. If your browser refuses local storage, the notice may show again.

The practice check on /dmv-practice-test/ and its pages in the other languages keeps one entry in your browser's local storage, `rtp-check-seen`: the numbers of the questions it has shown you and which of your checks showed each one, so that your next check asks you others first. It holds no answer, no score and nothing about you, and it is not sent to us or to anyone else; your answers and your score stay on the page and are gone when you leave it. If your browser refuses local storage, a later check may repeat some questions.

The app stores data on your device, in the app's or the browser's local storage, because it needs it to work: your progress, your settings (your choice about usage statistics included), your sign-in session and a few small preferences, such as which of its own notes about Plus it has already shown you (the offer that opens by itself once when the free questions run out, and the look at the full course after your second and third missions), so that each shows only once. None of that app storage is used to track you. On Android, the app turns the phone's backups off for this data (Google's backups and transfers to a new phone). On iPhone, the app marks its storage to be left out of iCloud and computer backups. To move your progress to a new phone, sign in with Google, Apple or your e-mail address (your e-mail address in the apps from version 1.1) first (Settings → Account). In a web browser, the browser decides what it keeps.

If you follow a partner school's link, the website and the web game keep that school's code, the way the link was shared and the time in local storage for 30 days, and the web game keeps, until you close the tab, which school it has already reported (see "Partner referrals"). Neither identifies your browser or device. An ID that earlier versions of the website kept for partner referrals is deleted wherever the website or the game finds it. While the website's AI guide is on, the browser keeps your acceptance of the guide's notice in its session storage, once you give it, until you close the tab. When you ask for an e-mail sign-in code, the app keeps the address you gave, and the time the code went, in its session storage, so that the step where you enter the code is still there if the page reloads while you read your e-mail. The app no longer uses that entry once an hour has passed since the code went, and deletes it the next time it reads it. The entry also goes when you sign in, whichever way you sign in, when you choose "Use a different e-mail", reset your progress or delete your account, and when you close the app or the tab. Only the address goes back to our sign-in service, with the code you type; nothing else is sent from it.

Security

Data travels encrypted. On our server, each account can reach only its own data. The keys to our AI provider stay on our server, never in the app. Your sign-in session is stored on your device, and the app marks it to be left out of the device's backups. Anyone who can use your unlocked device can still open the app with your progress, so reset or delete in the app before you pass a device on. Our admin panel opens only with a password and a code from an authenticator app, and every change made in it is recorded in a log that our server's functions cannot change.

Changes to this policy

When we change this policy, we update the version date at the top. If a change affects how we use your data, we'll tell you in the app before it applies.

Contact

Cloud Connected sp. z o.o., pl. Doktora Edwarda Łuczkowskiego 9, 22-100 Chełm, Poland. Privacy: contact@cloudconnected.pl. Support: contact@cloudconnected.pl.