Privacy Policy

Your NOL tag ID never reaches us

The balance checker on the home page asks for the 10 digit tag ID printed on the back of your card. That number is validated in your browser, held in your browser and shown back to you so you can copy it in one tap. It is not transmitted to us, and there is no server of ours waiting to receive it: this site is a set of static files, so there is no form submission and no database behind it.

The balance check itself happens on rta.ae. RTA protects its form with a robot check that is verified on RTA's own server, which is why no third party site can read a balance for you and why our checker hands you to the official page with your number ready to paste. What RTA does with the tag ID once you enter it there is governed by RTA's own privacy terms, not by this policy.

A Clear button sits next to the input. Press it and the stored ID is removed from your browser immediately. The same happens when you clear site data in your browser settings, and in a private window nothing survives the session at all.

What the site keeps in your browser

Three small values are written to your own browser storage, never to us. Two live in sessionStorage and disappear when you close the tab: the tag ID for the check you are running, and a counter of how many checks you have run in this session, which the page uses to shorten the processing animation on a repeat check. The third lives in localStorage and holds the last tag ID you entered, so a returning visitor does not have to dig the card out again.

The keys are named neutrally rather than with anything that identifies a card or a person, and none of them is readable by another website. If your browser blocks storage, as some private modes do, the tools still work; you simply retype the number each time.

The site sets no cookies of its own. Cookies that do appear come from the advertising networks described below.

Advertising, cookies and personalisation

The site is funded by display advertising. Two networks run on it: Google AdSense, in automatic placements chosen by Google, and Adsterra, which fills one manually placed unit per page. Neither is given any information by us about who you are or what you typed into the balance checker.

Third party vendors, Google included, use cookies and similar technologies to serve ads based on your prior visits to this site and to other sites. Google's use of advertising cookies lets it and its partners show you ads across the web, and those partners may collect data such as your IP address, device type, approximate location and browsing activity. We do not receive that data, cannot query it and see only aggregate reporting of impressions and earnings.

You can switch personalisation off. Google's ad personalisation controls live in Google Ads Settings, reachable from myadcenter.google.com, and they apply across Google's own properties and its partner sites. For the wider set of advertising vendors, the industry opt out page at aboutads.info/choices lets you decline personalised ads from participating companies. Browser level controls are the third route: blocking third party cookies, or using tracking protection, works whatever the network chooses to do.

Personalisation controls do not remove the ads. They change how the ads are chosen, which is the honest description of what those controls do.

Server logs, fonts and analytics

The pages are served as static files, and the host that serves them keeps standard web server access logs the way every web server does: the requesting IP address, the browser user agent, the time and the page. Those logs exist to keep the site running and to investigate abuse, and they are not combined with anything from the balance checker, because the balance checker sends nothing to a server.

Every page loads the Inter typeface from Google Fonts, so your browser makes a request to fonts.googleapis.com and fonts.gstatic.com when a page opens. Google receives your IP address and user agent as part of that request. It is a real third party connection and we would rather name it than pretend the site is entirely self contained.

No visitor analytics product runs on this site as of the effective date above. There is no Google Analytics tag, no heatmap tool and no session recorder. If that changes, this section changes with it and the effective date at the top of the page moves.

No accounts, no comments, no mailing list

There is nothing to sign up for. The site has no user accounts, no login, no profile and no comment section, so there is no store of names, passwords or posts to lose. Every tool here runs in your browser on data that ships with the page.

The one way to send us anything is email, at hello@nolcardbalanceonline.com. A message you send sits in that mailbox and is used to reply to you. It is not added to a mailing list, because there is no mailing list, and it is not shared with advertisers. If you include a tag ID in an email, we cannot look it up and will not keep it. The contact page explains what we can and cannot help with.

Your choices, children and changes to this policy

Your controls are the practical ones: press Clear to drop the stored tag ID, clear site data to remove everything the site has written, block third party cookies to limit ad tracking, and use the two opt out routes above to switch off personalisation. None of them stops the tools working.

This is a public transport reference site, not a service directed at children, and it asks nobody for a name, an age or an address. We do not knowingly collect personal information from anyone, of any age, because the site is not built to collect it.

The effective date at the top of this page is real. It changes when the text changes, and the text changes when the site does. Questions about any of it go to hello@nolcardbalanceonline.com, and the disclaimer covers the separate question of how accurate the fares and timings on this site are.