Skip to content
Privacy

Privacy policy

What this site does and does not do with your data. The short version: the tools run inside your browser and never send what you put into them anywhere, but the site does serve third-party ads and measure visits, and both of those use cookies.

Last updated 19 August 2026

What you put into the tools never leaves your device

Every tool on UtilifyHub runs entirely in your browser. The file you open, the text you paste, the invoice you fill in, the names and terms you type into an agreement — none of it is transmitted to us or to anyone else. There is no server to receive it.

Nearly every tool keeps working with your internet disconnected, which is the plainest demonstration of this that we can offer. There is one exception, and it is worth naming precisely: the word unscrambler downloads its dictionary the first time you use it. That is a fixed word list served as a static file from this site — the traffic goes one way, and nothing you typed is ever part of it. Once the file is cached, that tool works offline too.

This is an architectural fact rather than a promise about our conduct. The site is a set of static files; there is no backend, no database and no account system that could store your work even if we wanted it to.

What is stored in your browser

Some tools remember things so you do not have to set them up again. This uses your browser’s local storage: it stays on your device, it is never sent anywhere, and we cannot read it. You can clear all of it at any time through your browser’s "clear site data" or "clear browsing data" controls.

Rather than list every tool — that list would go stale the moment we add another — here is the rule each one follows:

  • If closing the tab would lose real work, the tool saves that work. A half-finished invoice, the week in a planner, the document open in the HTML editor, the monthly budget in the expenses and savings calculator, the proposal you are drafting, the résumé you are writing, the list you are about to print, the business card you are designing, the slide deck you are putting together, the receipt or delivery note you are writing up, the letterhead you are laying out, the certificate you are awarding, the badges you are printing for an event. It is kept so you can come back to it, and only ever on your device. Some of those hold things worth naming outright — figures about your household or your business, in a résumé your name, your phone number and where you have worked, and in a set of meeting minutes the names of the people who were there and what they agreed. All of it is written to this browser and read back by this browser, and it reaches us at no point, because there is nowhere for it to go. A photo added to a résumé is resized on your device and kept the same way. The badge maker is the exception and does it deliberately: it keeps the names and roles but strips the photographs out of its saved draft, so a shared computer is not left holding a set of faces.
  • If a tool only has settings, it saves the settings and not your input. The days calculator keeps your weekend and holiday choices but never the dates you typed; the image compressor keeps your quality preference but never the images.
  • Which form sections you have open is remembered on the longer forms. That is a handful of true/false switches, not anything you wrote.
  • Where the content is sensitive or throwaway, nothing is saved at all. The contract generator keeps no document content and no signature image, because an agreement carries the other party’s details and quietly writing those to a shared computer is not a decision we should make for you. The loan and mortgage calculators save nothing either — not the amount, not the rate, not the property price — because those figures describe what you earn and what you owe. The same goes for anything you paste into a converter, a counter or a formatter: it is gone when the tab closes.
  • Every key is namespaced under `utilifyhub:`, so clearing this site’s data removes all of it and nothing else.

Advertising

This site is funded by advertising. Google AdSense is loaded on every page and Google may set cookies or read existing ones in order to serve and measure ads. Google, as a third-party vendor, uses cookies to serve ads based on your prior visits to this and other websites.

Google’s use of advertising cookies enables it and its partners to serve ads based on your visit to this site and other sites on the internet. You can opt out of personalised advertising at Google Ads Settings (adssettings.google.com), and you can opt out of third-party vendor cookie use at aboutads.info/choices.

Third-party vendors, including Google, may also use cookies to serve ads based on someone’s prior visits to this website. We do not control what those vendors collect, and we never pass them anything you typed into a tool.

Analytics

We use Google Analytics 4 to count visits and see which tools people actually use. It sets cookies beginning with _ga to distinguish one visitor from another.

What is deliberately not sent: query strings and URL fragments are stripped before anything is reported, because tool state sometimes lives in the URL and that state is something you typed. Only the page path, the page title and the site origin are recorded. No form values, no file names, and no contents of any tool.

You can block this entirely with Google’s Analytics Opt-out Browser Add-on, or with any browser setting or extension that blocks analytics scripts. Nothing on this site stops working if you do.

Personal data under the PDPA 2010

UtilifyHub is operated by PIXEL & BORDERS SERVICES (SSM SA0519429-W), a business registered in Malaysia, which is the data user for the purposes of Malaysia’s Personal Data Protection Act 2010. That Act governs the processing of personal data in commercial transactions.

We do not collect, hold or process personal data ourselves. There is no account, no sign-up, no form on this site and no mailing list, and nothing you enter into a tool reaches us. The only personal data involved in simply visiting is what Google collects through the advertising and analytics cookies described above, processed by Google as an independent party under its own privacy policy at policies.google.com/privacy.

If you would rather no such data be processed at all, blocking cookies or using an ad and analytics blocker prevents it, and every tool on this site continues to work exactly as before.

For anything you want to raise about data on this site — including a request under the PDPA — write to the address below and it will reach a person.

dev@utilifyhub.my

When you contact us

Everything above describes simply using the site. Writing to us is different, and it is the only route by which personal data reaches us at all — so it is set out separately rather than left to be inferred.

If you send an email to the address on the Contact page, we receive what you chose to send: your email address, your name if your mail client includes it, and whatever is in the message. It is delivered through Cloudflare Email Routing into an ordinary mailbox and kept there like any other correspondence, used only to answer you and to fix what you reported. It is not added to any list, because there is no list, and it is not passed to anyone else.

The Contact page also links two external forms, for bug reports and tool requests. Those are Google Forms and they are not part of this site: what you submit goes to Google and then to us, under Google’s privacy policy rather than this one. Use email instead if you would rather not involve them. Either way, please do not attach the document, image or file that caused a problem — a description is what is actually useful, and we would rather not hold a copy of your invoice or your contract.

You can ask at any time for correspondence you have sent to be deleted, and it will be.

dev@utilifyhub.my

Children

This site is not directed at children and we do not knowingly collect anything from them. Since we collect nothing from anyone directly, there is nothing for us to delete on request — but the cookie controls above apply the same way.

Changes to this policy

If what the site does changes, this page changes with it in the same release. The date at the top is the date it last changed. There is no version where the site behaves one way and this page describes another.

Contact

Questions about this policy, about how the site handles data, or about anything else here can go to the address below. It is read by the person who builds this site, not a support queue.

dev@utilifyhub.my