Privacy Policy

1. What this covers

Two things: this website, luuqo.com, and the Luuqo application your business signs in to.

They behave very differently, so they are described separately. The website holds almost nothing. The application holds your business records.

2. This website

This site sets one cookie and makes no attempt to identify you.

• One cookie, named lk_lang. It records whether you chose Bahasa Malaysia or English, so the next page you open is in the language you picked. It holds two letters and is kept for a year. Nothing else is stored in it.
• No analytics, no advertising, no tracking pixels, no session recording, no heat maps, no cross-site identifiers.
• Nothing on these pages is loaded from another company. The fonts, the images, the styles and the scripts are all served from this site, so opening a page here does not tell anybody else that you did.
• No form on this site collects anything. There is nowhere to type your name, and no message is stored or forwarded from here — the contact page gives an email address instead.

Our host keeps ordinary server logs — the address a request came from, the page asked for and the time — for the usual purposes of keeping a website running and defending it from abuse.

3. The application: your account

When your business registers, we hold:

• Your business name, the business code Luuqo generates for you, your country and time zone, and your business registration number if you choose to enter one.
• Your name, your email address and the username you sign in with. A six-digit code is emailed to that address at sign-up so we know it reaches you.
• Your password, stored only as a bcrypt hash. It cannot be read back or reversed. Nobody at Luuqo can tell you what your password is, and nobody at Luuqo will ever ask you for it.
• A contact phone number and a billing address, if you enter them in your settings.
• The staff accounts you create, the roles you put them in, and which pages each role may open.

4. The application: your business records

Whatever the modules you install record. Depending on which ones you take, that means:

• Your item catalogue — names, codes, units, selling prices, costs and photographs.
• Your outlets, and how much of each item each one is holding; every stock movement in, out, adjusted, taken or transferred between them, with who did it.
• Sales rung up at the counter, line by line, with the payment method, any discount, the tax rates you had configured at the time, the cashier, the shift where you use shifts, and any refund or void raised against the sale afterwards.
• Sales recorded in Buku Jualan Gerai — the items, the amount, the payment method and the time — including sales held on the phone before they are sent, and expenses if you record them.
• Bookings, and the settings of the booking page.
• Each module's settings, including things like your receipt footer and any image you upload for it.

These are your business's records. We hold them so that the software can show them to you; we do not use them to build a profile of your business, and we do not use them to train anything.

5. The application: your customers, and your guests

Some modules collect details about people who are not our customers but yours. You decide whether to collect them; we hold them on your behalf, and you are responsible for telling those people what you are doing with them.

What that can include:

• A customer you add or attach to a sale — their name, and an email address or phone number where you record one.
• If you turn on the public booking page: a guest's name, phone number, identity-card number, the dates they booked, the image or document they upload as proof of payment, and the bank details they give when they ask for a security deposit back.
• An identity-card number is sensitive, and the booking page asks for one because the guest uses it together with their phone number to look up or cancel their own booking without an account. That also means anyone holding both can do the same, so treat the list of your bookings the way you would treat a guest register.

6. The application: the activity log, and what is not in it

The application keeps a record of changes so that you can see who did what in your own business.

• It records changes to your items, customers, sales, bookings, staff, roles and module subscriptions — the action, who did it, when, and the address and browser it came from.
• It is deleted after 30 days. Nothing older than that survives, for you or for us.
• It is a record of CHANGES, not a security log. There is no sign-in history: the application does not record when you signed in, when you signed out, or where from — successfully or otherwise. An owner asking "who logged in last night" cannot be answered from Luuqo.

7. Where it is stored, and how it is protected

• Your data lives in one managed PostgreSQL database, reached only over an encrypted connection, run for us by a hosting provider on infrastructure OUTSIDE Malaysia. If your data staying inside Malaysia matters to your business, that is the fact you need before you sign up, and it is why it is stated here rather than left out.
• It is one shared database, not one per business. Separation is enforced by the application: every read and every write is scoped to your business before it reaches the database. You do not get your own database, and we do not claim database-level isolation that is not there.
• Passwords are stored as bcrypt hashes. Sign-in sessions use cookies the browser will not hand to a script, and they are marked secure over HTTPS. Repeated failed sign-in attempts are throttled.
• We make no claim about encryption at rest, about backups, or about how quickly anything could be restored. Whatever a hosting provider does by default is not a promise Luuqo has earned in its own voice, and we will not present it as one.

8. Who else can see it

We do not sell your data, we do not rent it, and we do not share it for advertising. It is passed on in four situations and no others:

• To take a payment. When a bill is raised we pass your business name, your contact email address and the amount to Billplz, the payment provider, who takes the payment on their own pages. Your card or online-banking details are entered there and never reach Luuqo.
• To send you an email. Verification codes, staff invitations, payment links and notifications are delivered through an email provider on our behalf. It handles the address the message is going to and the message itself.
• To run the service at all. Our hosting and database provider necessarily stores the data described above, under contract, in order to host it.
• Luuqo's own support staff. Someone at Luuqo can open your account to help you with a problem. Where that happens, the activity log shows the action as taken by "Luuqo support" rather than by that person's name.

We will also disclose data where the law requires us to. If we are compelled to hand over your records, we will tell you unless we are forbidden from doing so.

9. How long it is kept

• Your business records are kept while your account is open.
• Unsubscribing from a module does not delete what that module recorded. The data stays so that reinstalling gives it back to you.
• The activity log is deleted after 30 days.
• If you take a module on a trial and do not subscribe, the records that module created may be deleted a short while after the trial ends. You are warned in the application before that happens.
• When you ask us to close your account, we delete your data. Bills already raised are kept as long as we are required to keep them.

10. Your rights under the PDPA

The Personal Data Protection Act 2010 gives you rights over personal data we hold about you. In practice:

• To SEE and CORRECT your own details: your business and contact information are on the Settings screen in your account and you can change them there.
• To get a COPY: Settings has an Export Data button, and it is important to be exact about what it produces. It returns your business profile, your account settings and your customer list — name, email and the date each was added. It does NOT return your items, your sales or your bookings. If you need those, write to us and ask; do not plan around that button doing more than this paragraph says.
• Most lists inside the application have a Download CSV button — stock balances, movements, valuations, requisitions, bookings, the activity log, your billing payments. There is none on the sales counter.
• To have your data DELETED: write to us and ask us to close the account.
• To WITHDRAW consent: write to us. Some of what you withdraw consent for is what the service runs on, so this may mean closing the account.

We do not charge for any of this, and we will not ask you why.

11. Cookies, in full

There are three, all of them necessary, and none of them used to track you across other sites.

• lk_lang, on this website. Your chosen language. One year.
• The sign-in session cookie, in the application. It is what keeps you signed in. Thirty days, not readable by scripts, marked secure over HTTPS.
• A "remember me" token, in the application, so you are not signed out on a device you use every day. Thirty days. Only a hash of it is stored on our side, so a copy of our database could not be used to mint one. Signing out clears it.

There are no advertising cookies and no third-party cookies, on either the website or the application.

12. Changes, and how to reach us

If this policy changes, the new version is published here with a new date, and where a change materially affects you we will tell you by email.

Ask us anything about your data, or make any of the requests in section 10, by writing to us. A person reads it.

The name, registration details and registered address of the party responsible for the data described here are to be inserted before this document is adopted. They are deliberately not filled in with a guess.