Skip to content
Turas
Learn to drive Learn Test routes Routes Practice Practice Guides Guides Prices Prices

Privacy Policy

Last updated: 6 November 2026 · Maksym Myronenko · maximusik2@gmail.com

Privacy Policy Terms of ServiceSubscription Terms

1. Who we are

“Turas: Driving Test Routes” (“Turas”, “the app”) is developed and published by Maksym Myronenko, an individual sole developer based in Ukraine. There is no company behind the app. It is one person.

For the purposes of the EU General Data Protection Regulation (GDPR) and the UK GDPR, Maksym Myronenko is the data controller for the personal data described in this policy.

ControllerMaksym Myronenko (a natural person, sole developer)
Contact emailmaximusik2@gmail.com
AppTuras: Driving Test Routes, iOS 17 or later, iPhone (and CarPlay where available)
Bundle identifiercom.myronenkomaksym.ietestroutes
App Storehttps://apps.apple.com/ie/app/turas-driving-test-routes/id6816729591

Email is the only contact channel. If you need a postal address, for example to send a formal legal notice or a written data subject request, email maximusik2@gmail.com and it will be provided to you on request.

No EU representative under GDPR Article 27 and no UK representative have been appointed at this time. If you are in the EU/EEA or the UK you can still exercise every right described in section 9 directly by email, and you can complain to your national supervisory authority, which in Ireland is the Data Protection Commission (section 10).

There is no Data Protection Officer; one is not required for processing at this scale.

1.1 Scope of this policy

This policy covers the Turas iOS app (including its CarPlay screen), the backend API that supports it, and this website.

It does not cover Apple’s own processing of your Apple Account, your App Store purchases and payment details, Sign in with Apple, or Apple Maps. Apple is an independent controller for those. See Apple’s privacy policy: https://www.apple.com/legal/privacy/

Turas is not affiliated with the Road Safety Authority (RSA) or any government body, and no data about you is shared with the RSA.


2. The short version

  • There is no sign-up. The app creates an anonymous account tied to your device. Signing in with Apple is optional and only lets your purchases follow you to a new phone.
  • Location is used on your phone to guide you along a route and to find your nearest test centre. It leaves your phone only in two cases: while “Share drives” is on (it is on unless you turn it off), and when the app asks Apple Maps for directions.
  • With Share drives on, the app sends your position every 10 seconds during a drive, the whole drive from start to end. With “Always” location it also records drives by itself (Settings → Drive Sharing → Record Drives Automatically): every drive within 30 km of your chosen test centre, and your test when you wait at the centre and then drive off. We keep those points for 400 days. You can delete any drive, or everything, at any time in the app.
  • Answers you give after a drive, route problem reports, and your purchases are stored with your account.
  • The app sends usage analytics to Amplitude (which screens you use, never your location). You can turn it off at any time in Settings → Share Usage Analytics.
  • There is no advertising, no advertising identifier, no App Tracking Transparency prompt, no tracking across other apps or websites, no data selling and no data brokers.
  • Payments are handled entirely by Apple. We never see your card, bank details or billing address.
  • The website sets no cookies and loads no third-party scripts. It counts visits with Amplitude without storing anything on your device, and stores a random id only if you allow it: see Website Privacy.

The rest of this policy is the detail.


3. What we collect, and what we do not

3.1 Data we do collect

A. Your anonymous account. When you first open the app it generates a random device identifier and registers an anonymous account with our backend. The app stores the account’s sign-in token on your iPhone. This identifier is not your Apple Account, your device serial number or an advertising identifier; it exists only for Turas.

To stop other software pretending to be the app, the app uses Apple’s App Attest: your iPhone creates a key that only this app can use, Apple confirms the key belongs to a genuine copy of Turas, and we store that key’s public part and identifier with your account. It identifies the app install, not you, and is deleted with your account.

B. Sign in with Apple (optional). If you choose to sign in with Apple, Apple gives us a stable identifier for your Apple Account in this app. The app asks Apple for no name and no email address, so we receive neither. We use the identifier only so your passes, subscription and drives follow you to a new phone.

C. Purchases and access. When you buy a Centre Pass, a subscription or Lifetime access, the app sends Apple’s signed transaction to our backend so we can confirm it and unlock the routes. We store the product, the transaction identifier Apple gives us, the dates it covers, and, for a Centre Pass, which centre it is for. We receive App Store Server Notifications about renewals, expiries and refunds. We do not receive your card number, billing address or Apple Account email.

D. Location on your phone. The app asks for location permission to follow your position along a route, speak each turn, reroute you if you leave the route, and find the test centre nearest to you. “Always” permission lets guidance and “Record my test” keep working while the screen is locked or another app is open, and lets the app record drives by itself (see F): it notices when you arrive at your chosen test centre (iOS region monitoring), and when your phone has moved about 500 metres (iOS significant-change monitoring), without using GPS until then. Location is used only for drives, your centre and finding a centre. The app asks for location once during setup. If you allow it only while using the app, the Routes screen may show a banner asking for “Always”, so that Record Drives Automatically can work; you can close it, and you can change your choice at any time in iOS Settings.

E. Apple Maps. Maps and directions are provided by Apple MapKit. When the app shows a map, or asks for directions to the start of a route or back onto it, Apple receives the request and the locations involved, under Apple’s own privacy policy. We do not receive anything back from Apple about you.

F. Shared drives (while “Share drives” is on). Settings → Drive Sharing → Share Drives is on unless you turn it off; the app’s location screen says so when it asks for location. While it is on, for each drive:

  • the app records a GPS fix (time, latitude, longitude, accuracy, and where available speed and heading) every 10 seconds, including in the background, queues the fixes on your phone and uploads them about every 60 seconds and when the drive ends;
  • the whole drive is kept, from its first fix to its last: a test route starts and ends at the test centre, so its ends are the part that matters;
  • a drive is recorded when you start one (a route, or “Record my test”), and, with “Always” location and Settings → Drive Sharing → Record Drives Automatically on (it is on unless you turn it off), also by itself:
    • from your test centre: when you have waited at your chosen test centre for a few minutes and then drive off. That recording starts at the centre and ends when you are back at the centre, after ten minutes standing still, or after two and a half hours. The app then asks once whether it was your test;
    • any other drive near your centre: iOS tells the app when your phone has moved about 500 metres (it uses no GPS until then). Within 30 km of your chosen test centre, the app then turns GPS on for up to two minutes to see whether you are driving; if not, it turns GPS off again. A drive is recorded from where the car set off to where it parked: the fixes after the car stopped for five minutes (for example the walk from the car) are never sent. These drives are not asked about. They can include drives where you were a passenger; turn the setting off if you do not want that;
    • one under a kilometre is dropped;
  • fixes outside Ireland or with poor accuracy are discarded;
  • we also store a summary: the drive’s mode (following a route, “Record my test”, or recorded by itself), the centre (your chosen centre, for drives recorded near it) and route, start and end time, distance and how much of the route you completed.

The setting is fixed for each drive when it starts. With Share drives off, the app still guides you but uploads no positions and no drive record, and records nothing by itself. (Where analytics is configured, the usage events in (J) still note that a drive started and finished, without any location.) You can switch it off at any time in Settings.

G. Your answers after a drive. After a shared drive the app may ask up to three questions, each of which you can skip: whether it was your real driving test, whether the test followed the route (or which route it looked like), and, if it was your test, how it went (passed, failed, or rather not say). If you say the test was different you can add an optional note of up to 500 characters. After a practice drive on a route, the app may instead ask one optional question about how the route matched the road (for example all good, the road has changed, an instruction was wrong, or a manoeuvre spot was off). We store your answers with the drive, and the drive’s date as your test date if you said it was your test.

Tips for other learners. After a drive on a route you can write an optional tip of up to 280 characters for the next learner. It is stored with the route and your account, checked by a person before it is shown, and then shown to other learners on that route without your name or account. You can ask us to remove it at any time.

While you drive, the app keeps your screen from locking so the next turn stays visible, and lets it lock again when the drive ends. Nothing is collected because of this.

H. Route problem reports. If you report a problem with a route (for example a wrong turn, roadworks or a closed road), we store the route, the kind of problem, any note you write, and, where the app includes it, the location the report refers to.

Route ratings and feedback. If you rate a route (thumbs up or down) we store your rating, the route and its centre with your account, so you can change it and so a route can show how many learners rated it each way. Written feedback on a route is stored like a route problem report above. Other learners see only the totals, never who rated.

I. Onboarding answers. The onboarding questions (for example your centre and test date, whether it is your first test, how confident you feel, what worries you, a road-rules question, who you practise with, the practice promise you make, and your choices about location, sharing and notifications) are stored on your phone to set up the app and build your practice plan. Each answer is also sent as a usage event under (J), so we can see which questions help; you can turn that off (section 5).

The onboarding and paywall screens are web pages that the app downloads from our server (hosted by Railway, EU West) and shows inside the app; the app also downloads its settings from our server. These downloads send nothing about you beyond what any request carries (see K), and the pages set no cookies.

J. Product analytics (only where analytics is configured in the app build, which it is in the App Store version; you can turn it off in Settings → Share Usage Analytics). The app sends usage events to Amplitude, in Amplitude’s US data centre, keyed to your account’s identifier: for example the app opened, a centre chosen, a route opened, a drive started or finished and how much of it was completed, going off and rejoining a route, the paywall shown, a purchase started or completed, an onboarding answer given, a report sent, sharing turned on or off, and the account deleted. If you answer the optional rating card (1 to 5 stars) or the “what made you skip?” card after a paywall, your answer and any text you type there (up to 300 characters) are sent as an analytics event; don’t put personal details in it. We also note which version of the onboarding pages you saw, opening your practice plan and its steps, and, where we are testing two versions of a screen (an A/B test), which version you were shown; the version is assigned at random to your account. Amplitude also records app sessions and app lifecycle events, and your device model, iOS version, app version, language and the country set on your iPhone. The app tells Amplitude not to collect your IP address, your city or region, your mobile carrier or Apple’s vendor identifier (IDFV), and analytics events never contain your GPS positions. With Share Usage Analytics off, or where no key is configured, no analytics events are sent. Our server also sends Amplitude a few events of its own, under the same identifier: when a new install first registers (device type, app version and language), and App Store purchases, renewals and refunds (the product, price and currency). These never include your IP address or location, and from app version 1.1 they stop too when Share Usage Analytics is off.

K. Server logs. When the app calls our API, or downloads its onboarding pages and settings, the hosting layer records the request: timestamp, endpoint, HTTP status and the connecting IP address. We use these logs only to keep the service running and to investigate abuse and outages.

L. Crash data. If you have agreed to share analytics with Apple in your iOS settings, Apple may make aggregated crash reports available to us through App Store Connect. We do not use a third-party crash SDK.

M. Correspondence. If you email maximusik2@gmail.com, we hold your email address and whatever you write, for as long as needed to deal with your message and keep a record of it.

3.2 Data we do not collect

Turas does not collect your name, email address (unless you email us), phone number, password, contacts, photos, camera, microphone, health data, payment card or bank details, any advertising identifier, or biometric data. It does not read your driving licence or learner permit details, and it does not know your RSA test booking.

There is no advertising SDK in the app, no ad network, no attribution SDK and no App Tracking Transparency prompt, because there is nothing to track.

3.3 People who are not users: “What Learners Say”

The app’s “What Learners Say” pages, and the tricky spots shown during setup, summarise what learners have shared publicly about roads near each test centre. We write the summaries in our own words. We do not store or show the names, usernames or anything else about the people who shared them, and we do not combine what they shared with any other data. Our lawful basis is legitimate interests (Art. 6(1)(f)) in helping learners prepare from publicly shared experience. If something you shared is summarised in the app and you want it removed, email maximusik2@gmail.com and we will remove it.


4. Why we process it, and our lawful basis

#DataPurposeLawful basis (GDPR Art. 6)
1Anonymous account, Sign in with Apple identifierCreate and recognise your account so your access and drives persist, and follow you to a new phone if you sign inArt. 6(1)(b), performance of the contract with you (our Terms of Service)
2Purchases and accessConfirm what you bought and unlock the right routes at the right centres for the right periodArt. 6(1)(b), performance of the contract
3Location on your phoneTurn-by-turn guidance, rerouting, “Record my test” and finding your nearest centre; you control it through iOS location permissionArt. 6(1)(b), performance of the contract (it is the service you asked for)
4Shared drives: GPS points and drive summaryShow your drive history; keep routes current (“Seen on N tests in the last 30 days”, “Last seen on a test”); build draft routes from recordings, reviewed by a person before any is published (section 6.2)Art. 6(1)(f), legitimate interests in keeping test routes accurate for every learner, which is the service itself. “Share drives” is on by default and you can object at any time by turning it off in Settings, which stops all uploads
5Answers after a driveWork out whether a route is still used on real tests, and improve the routesArt. 6(1)(a), your consent (the questions are only asked about shared drives, and each is optional)
6Route problem reports, ratings and feedbackFix wrong or outdated routesArt. 6(1)(f), legitimate interests in accurate routes, which is also what you are asking for by reporting
7Product analytics (where configured)Understand which features are used and where learners get stuck, and improve the appArt. 6(1)(f), legitimate interests in understanding and improving our own product; see section 5
8Server logs, including IP addressKeep the API available, detect and stop abuse, investigate incidentsArt. 6(1)(f), legitimate interests in security
9Crash dataFind and fix crashesArt. 6(1)(f), legitimate interests in app stability
10CorrespondenceAnswer your question or requestArt. 6(1)(b) or (f); Art. 6(1)(c) for data subject requests
11Purchase recordsAccounting, tax and consumer-law obligationsArt. 6(1)(c), legal obligation

Your test result (“passed”, “failed” or “rather not say”) is optional and private: it is never shown to anyone else. We do not process any special-category data under GDPR Article 9.

Where we rely on legitimate interests you have the right to object (section 9.6). Where we rely on consent you can withdraw it at any time, and withdrawing is as easy as giving it (section 9.9).


5. Analytics in the app

The Amplitude SDK starts when the app launches and sends the pseudonymous events described in section 3.1(J). We rely on legitimate interests (Art. 6(1)(f)), on the basis that the events are limited to how the app itself is used, contain no GPS positions, no IP address and no advertising or vendor identifier, are not combined with data from other companies, are not used for advertising and are not sold.

You can turn analytics off at any time in Settings → Share Usage Analytics. From that moment the app sends no more analytics events. To have the events already collected deleted as well, email maximusik2@gmail.com (section 9.6); we delete them through Amplitude’s deletion tools. Deleting your account also stops analytics.

We recognise that some EU/EEA regulators take the view that analytics of this kind needs prior consent rather than a way to turn it off. If the Irish Data Protection Commission or a court tells us that applies to this app, we will ask before sending any analytics.


6. Who else processes your data

These are all of them. We do not sell personal data, share it with data brokers, or disclose it for anyone’s advertising.

ProviderWhat they do for usWhat they receiveTheir privacy policy
AppleApp Store distribution; in-app purchases through StoreKit and App Store Server Notifications; Sign in with Apple; maps and directions through MapKit; deciding refund requestsYour App Store transactions and Apple Account (as an independent controller); map and direction requests from the apphttps://www.apple.com/legal/privacy/
RailwayCloud hosting for the backend API and PostgreSQL database, region EU West (europe-west4, Netherlands)Everything stored server-side: account, purchases and access, shared drives and answers, route reports, server logshttps://railway.com/legal/privacy
Amplitude (only where analytics is configured)Product analytics, in its US data centreThe pseudonymous events in section 3.1(J)https://amplitude.com/privacy

Apple acts partly as our processor (StoreKit billing on our behalf) and partly as an independent controller. Railway and Amplitude act as our processors under GDPR Article 28 data processing terms.

We may also disclose data where we are legally required to, for example in response to a valid, binding request from a competent authority, or where necessary to establish, exercise or defend legal claims. If Turas were ever transferred to another owner, your data could transfer with it; we would update this policy before that took effect.

6.1 What other learners can see

Nothing that identifies you. A tip you write for the next learner (section 3.1(G)) is shown on that route after a person has checked it, without your name or account. Routes can show counts such as “Seen on N tests in the last 30 days”, the month a route was last seen on a test, and how many learners rated it up or down. These are whole numbers or months per route, calculated from shared drives, route recordings and ratings, and they name nobody. Your GPS points are never shown to other users and are never served back by the API to anyone, including you.

6.2 How recorded drives are used to improve routes

Once a week, shared drives are exported automatically, as map lines without any account or name, to build draft routes: test routes learners reported, and recordings from a test centre that look like a test (those become practice routes). The export exists only while the drafts are built and is then deleted; it is never published or kept in our code repository. A person reviews every draft and approves or rejects it before it reaches the app. A route in the app is snapped to the OpenStreetMap road network and does not reveal any individual drive, the people who drove it, or where a drive started or ended away from the centre.

6.3 The website

This website sets no cookies, loads no third-party scripts, fonts or images, has no free-text forms and serves every page from its own origin. It counts visits with Amplitude through our own server, keeping a random id in your browser’s local storage and passing your IP address so Amplitude can tell your approximate location. You can turn this off at any time with Don’t allow. Website Privacy describes exactly what it collects. The hosting provider (Railway) processes standard web server logs, including your IP address, to deliver the pages and keep them secure.

6.4 Refund requests

If you ask Apple for a refund, Apple may ask us how the purchase was used. If we answer, we send only facts about the app (for example that routes were delivered and working) and, at most, a recommendation; we never send your location, your drives, your answers, your name or any payment data. Email maximusik2@gmail.com before or when you ask for the refund if you would rather we did not answer.


7. International transfers

Our backend API and database, and the onboarding pages, are hosted by Railway in the EU West region (Netherlands). Analytics is stored by Amplitude in the United States.

Apple and Amplitude are US-linked providers and processing may involve access from the United States and other countries outside the EEA and the UK. For Amplitude, the transfer of the analytics events in section 3.1(J) to the United States relies on Amplitude’s certification under the EU–US Data Privacy Framework and its UK Extension, and on the Standard Contractual Clauses in Amplitude’s data processing terms as a fallback. Where personal data is transferred outside the EEA or the UK, we rely on the EU–US Data Privacy Framework adequacy decision (and its UK Extension) where the recipient is certified, and otherwise on the European Commission’s Standard Contractual Clauses, with the UK Addendum where UK data is involved.

We ourselves are based in Ukraine. Ukraine is not currently covered by an EU adequacy decision, so where we access EEA or UK personal data from Ukraine that access is itself an international transfer, covered by the safeguards above. You can ask for details of the mechanism used for any provider by emailing maximusik2@gmail.com.


8. How long we keep it

DataRetention
GPS points of shared drives400 days, then deleted automatically; sooner if you delete the drive or your account
Drive summaries and your answersUntil you delete the drive or your account
Route problem reports, ratings and feedbackUntil you delete your account; the route fix they led to stays
Anonymous account and Sign in with Apple identifierWhile the account is in use; deleted when you delete the account, or after 24 months of continuous inactivity
Purchase and access recordsFor the life of the purchase, then as long as needed for accounting, tax and consumer-law purposes
Product analytics events (where configured)24 months from the event, then deleted or irreversibly aggregated
Server logs, including IP addresses30 days, longer only where a specific security incident or legal claim is under investigation
Email correspondence24 months after the matter is closed, or longer where it relates to a live or foreseeable legal claim
Onboarding answers and preferencesOn your phone, until you delete the app or your account

Per-route counts (“Driven on N tests”) are whole numbers that identify nobody, so they stay after a drive or account is deleted.


9. Your rights

If you are in the EU/EEA or the UK, GDPR Articles 15 to 22 give you the rights below. We extend the same rights to everyone using the app, wherever you are. Ukrainian data protection law gives you comparable rights.

Many of them you can exercise yourself in the app, straight away:

  • Delete one drive: Settings → Drive Sharing → Your Shared Drives, then delete the drive. Its points and answers are removed from our server.
  • Stop sharing drives: Settings → Drive Sharing → turn off “Share Drives”. Nothing more is uploaded from the next drive.
  • Delete everything: Settings → Delete Account. This deletes your account and your data from our server and from your phone, including every drive, point, answer, tip, report and rating. Analytics events already sent to Amplitude are not reached from the app: email us and we delete them too, or they are deleted at the end of their retention period (section 8).
  • Stop analytics: Settings → turn off “Share Usage Analytics”. Nothing more is sent from that moment.
  • Stop location: iOS Settings → Privacy & Security → Location Services → Turas.

For anything else, email maximusik2@gmail.com. We will respond within one month, and tell you if we need to extend that by up to two further months because the request is complex (GDPR Art. 12(3)). It is free.

9.1 Identifying your records

Your account is anonymous. If you email us rather than using the app, we may need details to find the right records: whether you signed in with Apple, your device model, roughly when you started using the app, which centre you chose, and for purchase questions the Apple order ID from your receipt. If we cannot establish that records are yours, GDPR Art. 11(2) allows us to say so; we will never hand one person’s data to someone who merely claims it.

9.2 Access (Art. 15) and portability (Art. 20)

You can ask what personal data we hold about you and receive a copy, including your drives and their points, in a machine-readable format (JSON).

9.3 Rectification (Art. 16)

You can ask us to correct inaccurate data, such as a wrong post-drive answer.

9.4 Erasure (Art. 17)

You can delete your data in the app as described above, or ask us to. We delete everything except records we must keep by law, such as accounting records of a purchase, and tell you what we kept and why.

9.5 Restriction (Art. 18)

You can ask us to stop processing your data while a dispute about its accuracy or our lawful basis is resolved.

9.6 Objection (Art. 21)

Where we rely on legitimate interests, you can object. For analytics we will always honour it. For security logging we may need to continue where there are compelling grounds, such as an active abuse investigation. We do not do direct marketing.

9.7 Automated decisions (Art. 22)

We do not make decisions about you by solely automated means that have legal or similarly significant effects. Draft routes built from recorded drives are reviewed by a person before any is published, and name nobody.

9.8 Withdrawing consent

You can stop drive sharing at any time by turning off “Share drives” in Settings (and stop drives being recorded by themselves with “Record Drives Automatically”), and delete drives already shared as described above. Stopping does not affect processing that took place before.


10. Complaining to a supervisory authority

If you think we have handled your personal data unlawfully, please tell us first at maximusik2@gmail.com and we will try to put it right. You also have the right to complain to a data protection authority:

  • Ireland: the Data Protection Commission, https://www.dataprotection.ie/
  • Elsewhere in the EU/EEA: the authority where you live, work or where the alleged infringement took place; list at https://www.edpb.europa.eu/about-edpb/about-edpb/members_en
  • UK: the Information Commissioner’s Office, https://ico.org.uk/make-a-complaint/
  • Ukraine: the Verkhovna Rada Commissioner for Human Rights, https://www.ombudsman.gov.ua/

You also have the right to an effective judicial remedy under GDPR Art. 79.


11. Children

Turas is made for learner drivers. In Ireland you must be at least 17 to hold a learner permit for a car. The app is not directed at children under 16, the digital age of consent in Ireland, and we do not knowingly collect personal data from anyone under 16. Accounts have no age field, and we do not attempt age inference.

If you are a parent or guardian and believe a child under 16 has used the app, you can delete the account in the app (Settings → Delete Account), or email maximusik2@gmail.com and we will delete the associated records free of charge.


12. Security

  • All traffic between the app and our API uses HTTPS/TLS.
  • The account’s sign-in token is stored on your iPhone, not sent anywhere but our API.
  • There are no passwords to steal, because there are none.
  • We never receive card numbers or bank details; Apple handles payment end to end.
  • GPS points are never served back by the API; they can only be exported by the developer, for the route review in section 6.2.
  • Backend access is limited to the sole developer and protected by strong, unique credentials and multi-factor authentication where the provider supports it.

No system is perfectly secure. If a personal data breach poses a risk to your rights, we will notify the competent supervisory authority within 72 hours where GDPR Art. 33 requires it, and affected users without undue delay where Art. 34 requires it. Because we usually hold no way to contact you directly, such a notice may be given in the app and on this website.

If you find a security issue, please report it to maximusik2@gmail.com rather than disclosing it publicly.


13. App Store “App Privacy” mapping

Data Used to Track You: none. We do not track you as Apple defines tracking.

Data Linked to You:

App Privacy categoryData typePurposeSection
LocationPrecise Location (shared drives only)App Functionality, Analytics (product improvement)3.1(F)
IdentifiersUser ID (the account identifier)App Functionality, Analytics3.1(A), 3.1(B), 3.1(J)
PurchasesPurchase HistoryApp Functionality, Analytics3.1(C), 3.1(J)
Usage DataProduct InteractionAnalytics3.1(J)
User ContentOther User Content (post-drive answers and notes, tips for other learners, route reports, route ratings, optional feedback text)App Functionality, Analytics (product improvement)3.1(G), 3.1(H), 3.1(J)

If the label on the App Store and this policy ever disagree, treat it as an error on our side and email maximusik2@gmail.com so we can correct whichever is wrong.


14. Changes to this policy

We may update this policy, for example when a feature ships, a processor changes or the law changes. The current version always lives on this website with its “Last updated” date at the top. For material changes, such as a new category of data, a new purpose or a new processor, we will give notice in the app before or when the change takes effect, and ask for consent again where the law requires it.


15. How to reach us

Email maximusik2@gmail.com for anything in this policy: a data subject request, a privacy question, a security report, or a request for our postal address. Please put “Privacy” in the subject line.

Test centre routes

  • Athlone
  • Ballina
  • Birr
  • Buncrana
  • Carlow
  • Carrick-on-Shannon
  • Castlebar
  • Cavan
  • Clonmel
  • Cork (Wilton)
  • Donegal
  • Drogheda
  • Dún Laoghaire (Deansgrange)
  • Dundalk
  • Dungarvan
  • Ennis
  • Finglas
  • Galway (Carnmore)
  • Galway (Clybaun)
  • Gorey
  • Kilkenny
  • Killarney
  • Killester
  • Kilrush
  • Leixlip
  • Letterkenny
  • Limerick (Castlemungret)
  • Limerick (Woodview)
  • Longford
  • Mallow
  • Monaghan
  • Mulhuddart
  • Mullingar
  • Naas
  • Navan
  • Nenagh
  • Newcastle West
  • Portlaoise
  • Roscommon
  • Shannon
  • Skibbereen
  • Sligo
  • Tallaght
  • Thurles
  • Tipperary
  • Tralee
  • Tuam
  • Tullamore
  • Waterford
  • Wexford
  • Wicklow
  • All test centres

Guides

  • How to pass the driving test in Ireland
  • Driving test checklist: car, documents, checks
  • Driving test questions and road signs
  • Reversing around a corner
  • Roundabouts on the test
  • Driver theory test
  • Learner permit: apply and renew
  • Driving alone on a learner permit
  • All guides

Practise

  • How to get a licence: 8 steps
  • Theory and test practice
  • Irish road signs
  • Road signs quiz
  • Build your practice plan
  • Are you test ready? Quiz
  • Pre-test checks quiz
  • What to expect at your centre
  • Waiting times by centre
  • Pass rates by centre
  • All test centres
  • Prices

Turas

  • About Turas
  • Support
  • Privacy Policy
  • Terms of Service
  • Subscription Terms
  • Website Privacy

© 2026 Maksym Myronenko. maximusik2@gmail.com

Turas is not affiliated with, endorsed by or connected to the Road Safety Authority (RSA). Routes are practice aids and are not guaranteed to match your test. Map data © OpenStreetMap contributors.

We count visits to improve this site

A random id on this device and your approximate location. No ads, never sold. Details