The short version: the app collects nothing

Data in the application

Everything you type into MFAHHIQ ERP — customers, suppliers, invoices, stock, staff records, payroll, the ledger — is written to one JSON database file on the computer running the app. There is no server component at all: the interface reads and writes that file over an internal bridge that never touches a network interface, so nothing it does is reachable from your network, let alone the internet.

Where the file lives

• Windows — %APPDATA%\MFAHHIQ ERP\
• macOS — ~/Library/Application Support/…
• Linux — ~/.config/…

The database is also mirrored, on a throttle, to Documents/MFAHHIQ ERP Restaurant/. That copy sits deliberately outside the application folder, so it survives an uninstall. The files there are plain and human-readable, and you can copy them to another machine yourself without asking us for anything.

It never leaves the machine

There is no telemetry, no crash reporting, no usage analytics, no licence check-in and no automatic update that phones home. The app has no account system and nothing to log in to online. The only way data leaves the computer is if you move it: an export from the File menu, a copy of the Documents mirror, or a file you send to someone yourself.

We cannot access it

We run no server for this product, hold no copy of your database and have no remote access to your machine. If you email us asking why a figure looks wrong, we cannot go and look — you would have to tell us, or send us an export. That is inconvenient once or twice a year and worth it the rest of the time.

You are the controller of your own records

Because the records are yours and they sit on your equipment, you are the controller of the customer, employee and payroll data inside them. The duties that come with that — telling people what you hold, keeping it accurate and secure, and answering their requests — sit with your business. We are not a processor of that data, because we never receive it.

Data on this website

Every marketing page on this site — the ones you are reading now — is a static HTML, CSS and JavaScript file with no server behind it. Every asset — the stylesheet, the script, the logo — is served from this domain. Nothing is pulled from a content delivery network, a font service, a video host or a social platform. The one part of the site that talks to a real server is the demo's sign up and log in pages, covered on their own below.

• No analytics, measurement or session recording of any kind.
• No advertising pixels, remarketing tags or tag manager.
• No third-party scripts, fonts or images. The page loads only from this domain.
• No tracking cookie. The only cookie, and the only account, come from starting the 5-day demo — see below.

If you only read the site, one thing is stored in your browser: your light or dark theme preference, saved under the key meezan-theme in local storage. It stays in your browser, it is not a cookie, it is never sent to us, and clearing your browser data removes it.

Whoever hosts the site will keep standard server access logs — IP address, timestamp, the page requested and the browser user agent. That is how web hosting works everywhere. Those logs belong to the host, are used to deliver the site and deal with abuse, and we do not build profiles from them or join them to anything else.

The 5-day browser demo

Starting the demo is the one thing on this site that involves a real server and a real account. It is worth being exact about what that means, because the demo runs a full accounting application and you may well put real figures into it.

Signing up creates an account. The sign up page asks for your name, email, company and a password, so that the same free account works whether you are starting a demo or, later, signing in to a licence we have set up for you — see log in. That is new: earlier versions of the demo needed no account at all, and this page said so. It no longer does.

What we store on our server, against your account:

• your name, email address and company, as you typed them;
• your password — never in plain text. It is put through bcrypt, a one-way hashing function, before it is stored. We cannot read your password back, and if our database were ever stolen, the hashes are not reversible into the original passwords.
• your demo's start and end dates, and whether you have activated a paid licence;
• a link to your company's subscription, if one has been set up for you — nothing about that account's own data, just the fact that it exists.

It is kept for up to three years so a spent demo cannot silently be restarted, and you can ask us to delete your account and everything above at any time.

What still stays in your browser and never reaches us: the application itself. The chart of accounts, invoices, customers, staff, payroll and journal you enter once the demo is running are written to this browser's own local storage on this device, exactly as before — signing in only unlocks the application, it does not change where its data lives. We cannot read it, cannot recover it and do not have a copy.

What the demo stores in your browser, beyond the application itself:

• the application's database, under meezan_restaurant_v1 — everything you type into it;
• your session, under mz.demo.state.v1 — the name, email and company on your account, when the demo started and when it ends, and your activation code if you have entered one;
• a list of which addresses have already used a demo in this browser, under mz.demo.seen.v1, and a copy of the same list in a cookie named mz_demo_seen that lasts up to 400 days;
• a timestamp under mz.demo.clock.v1, so that setting the computer's clock backwards does not extend the demo.

The mz_demo_seen cookie exists only to stop one address quietly taking a second demo on this browser. It is not a tracking cookie: it holds a short non-reversible digest of the address rather than the address itself, it is never sent anywhere except back to this domain, and it is used for nothing else. Clearing your site data deletes all of it — including the books you entered. Logging in again restores your account and its demo status, but not the books, which only ever lived in that one browser.

The demo does not report on what you do inside it. There is no telemetry, no usage tracking, no error reporting and no record of which screens you opened. Logging in and out is the only activity our server sees.

The contact form

The contact form has no backend. Nothing is posted to a server while you fill it in, and there is nothing on our side listening for it.

When you submit, the page assembles what you typed into a message and opens it in your own email client, addressed to info.mfahhiq@gmail.com. Nothing is transmitted to us until you press send in your own email app. If you change your mind and close the draft, we never see a word of it.

If the device has no email client configured, the form cannot hand the message over. In that case, email us directly at the address above.

Email we receive

When you email us, we receive whatever you put in the message: your name, your email address, usually a company name, sometimes a phone number, and whatever you choose to tell us about your business.

We use it to:

• Answer your question.
• Send a quotation, an invoice or a receipt.
• Issue, re-issue and renew licences.
• Arrange a demo, an installation or a support session.

We keep support correspondence for as long as it is useful for supporting you, and we keep licence and sales records for as long as we are required to keep accounting records under Saudi law. An enquiry that went nowhere can be deleted on request — ask and we will remove it.

We do not sell, rent or share your email address. You are not added to a mailing list because you wrote to us, and we do not pass your details to anyone for marketing.

Licensing data

To issue an activation code we need the machine code shown on the activation screen — something in the form MZR-DE07-EB9C-0099-17AA-7118. It is derived from a stable identifier on that computer. It is not a name, an address, a location or an account. On its own it identifies a machine rather than a person, and it cannot be turned back into the hardware details it came from, so we do not treat it as personal data.

Against a licence we store:

• the machine code you sent us;
• the licence period and its expiry date;
• the activation code we issued in return;
• the company name and the email address that bought it, so we can check who we are re-issuing to.

The activation code is an Ed25519 signature over machineCode|expiry. Only the public key ships inside the app; the private key never leaves us. All of the signing happens on our side, offline. The app itself never contacts us to check a licence, before activation or after it.

A licence for the browser demo works the same way with one substitution. A browser has no machine code, so a demo licence is signed over email|expiry instead — your email address takes the place of the machine identifier. Against one we store that address, the licence period, and the code we issued. The same rule applies: the signing happens offline on our side, and the page never contacts us to check a licence once you have entered one.

Third parties

In the product there are none. No analytics library, no error reporting service, no advertising network, no payment code, no embedded browser components calling out. That is not a policy we promise to keep — it is what the software does, and it is why the app runs perfectly well on a machine with no network card.

On our side, the only processors involved are the company that hosts this website and the company that provides our email. The first handles the site's access logs; the second handles our mailbox. If that ever changes — if we add a payment provider, for instance — this page will say so before it happens.

Your rights

For anything you have emailed us, you can ask us to:

• tell you what we hold about you;
• correct it if it is wrong;
• send you a copy of it;
• delete it;
• stop using it to contact you.

To ask, email info.mfahhiq@gmail.com and say what you want. Our response target is one business day, within support hours of Sunday to Thursday, 9:00 to 18:00 AST. We may ask you to write from the address the records are held under, so that we are not handing your details to somebody else.

One honest limit: we cannot act on data inside your own installation, because we never have it. Removing a customer or an employee from your database is something you do in the app, on your machine.

Children

MFAHHIQ ERP is business software sold to companies. It is not designed for children, not marketed to them and not intended to be used by them, and we do not knowingly collect anything about them. If a restaurant employs staff under 18 and records them in payroll, that data sits in the employer's own database on the employer's own machine and never reaches us.

Changes to this policy

If this policy changes, the new version is published on this page and the date at the top is updated. Anything material will be described plainly rather than folded quietly into a paragraph. Because the product collects nothing, changes here are far more likely to be about how we run our website and our inbox than about the app.

Contact

Questions about this policy, or a request about data you have sent us:

Email

info.mfahhiq@gmail.com

Address

MFAHHIQ ERP, Riyadh, Saudi Arabia

Support hours

Sunday to Thursday, 9:00 to 18:00 AST

Response target

Within one business day