Safety and Privacy: What Happens to Your Leave Data
A technical privacy explainer for Aussie Leave Calculator: what runs locally, what is not stored, and what share links and analytics can expose.
The direct answer
Your leave plan is calculated in your browser. The site does not ask for your name, employer, email address, payroll details, manager, salary, medical information, or travel plans. It does not create an account for you, and it does not store a database record of the leave dates the calculator recommends.
That is the most important privacy design choice in the project. The calculator does not need a backend service to do its work. A static data file supplies public holidays. JavaScript in your browser does the arithmetic. The result is rendered on the page you are already viewing.
What information the calculator uses
The calculator needs four main inputs: your state or territory, your available leave days, your preferred strategy, and whether you want school holidays considered. Those inputs are not highly sensitive by themselves, but they can still feel personal because they describe how someone might use time away from work. The safest pattern is to avoid collecting more than the tool needs.
No employer details are requested. No approval chain is requested. No login is requested. No leave balance document is uploaded. The tool is intentionally shallow in the best sense: it asks only enough to create a useful calendar plan.
Static site architecture
Aussie Leave Calculator is a static website. That means the public pages, JavaScript, CSS, and data files are served as files. There is no application server receiving a form submission when you click Calculate. The button triggers local JavaScript. The public holiday files are read by the browser because the calculator needs dates, not because the site is saving your answers.
This architecture has practical safety benefits. Fewer moving parts means fewer places to leak or mishandle data. There is no user table to breach, no password reset flow to secure, and no stored plan history to delete later. Static sites are not magically secure, but for this kind of utility they are a sensible low-risk design.
What share links reveal
The calculator can create a shareable URL. That URL may include simple parameters such as state, leave days, strategy, and the school-holidays option. This is useful when you want to reopen the same plan later or send it to someone else. It also means the URL itself contains those choices.
That is not the same as storing a plan in a database, but it is still worth understanding. If you paste a share link into an email, chat app, social network, or workplace system, that destination can see the URL. Anyone who receives the link can see the parameters in the address bar. For most users this is low-risk, but it is not invisible.
For that reason, share links should be treated like any other planning note. They are convenient, not secret. If a leave plan is sensitive because of workplace politics, travel timing, or personal circumstances, copy the dates into your own private notes instead of sharing the URL widely.
Analytics and query-string minimisation
The site uses Google Analytics to understand aggregate traffic patterns: which pages are visited, whether people find the guide pages useful, and whether the calculator is being discovered through search. Analytics is not required for the calculator to produce results.
Because share links can contain plan parameters, the analytics snippet has been configured to send the page location without the query string. In plain English: the analytics page view should record that someone visited the calculator page, not the exact ?state=qld&days=20&strategy=maximum values in the address bar. This is a practical privacy improvement, not a promise that every third-party destination on the internet will strip parameters if you share a link elsewhere.
Advertising status
The site is prepared for Google AdSense verification, but it is not currently serving display advertisements while approval is pending. If ads are enabled later, advertising scripts may use cookies or similar technologies according to Google's advertising systems and user settings. The calculator itself still does not need to send your leave plan to an ad server to calculate dates.
This distinction matters. A website can be private in its core tool design while still being transparent that third-party analytics or advertising scripts may operate on page visits. The privacy policy should describe both parts rather than pretending the web page exists in a vacuum.
What is not retained
There is no saved account profile. There is no stored leave history. There is no server-side copy of generated leave requests. Printing uses your browser. Calendar export creates a file on your device. Copy buttons use your browser clipboard. If you close the page and do not keep a share URL, the generated plan is not retained by this site.
The strongest privacy pattern is data minimisation: do not collect what you do not need. For a leave calculator, the best database is no database at all.
What users should still do
Privacy is shared work. Do not paste a share link into a public place if the dates are sensitive. Do not put medical, family, or employment explanations into any field, because the calculator does not need them. Confirm final dates in your employer's official leave system, and treat any copied leave request text as a draft you can edit before sending.
The goal is straightforward: make planning easier without turning a simple calendar tool into an unnecessary collector of personal information.
Related reading
Leave Maxing · Holiday Leave Theories · How We Calculate · Why You Need a Holiday · Long vs Short Breaks
For date-specific planning, start with the complete annual leave guide.