Collected
Products, stock changes, receipts, sales, payments, store settings, and consent choices.
Privacy transparency, not legal advice
FulPOS is built for kedai runcit owners who need a reliable POS and deserve clear control over their data. This deeper policy explains what Fulhive collects, why it is used, and how distributor access is controlled.
Products, stock changes, receipts, sales, payments, store settings, and consent choices.
Named store records, margins, contacts, and operating history stay private by default.
Area trends and category movement can be used without exposing store identity.
Distributor store-level access only happens after the retailer allows it.
FulPOS is a free point-of-sale product for Malaysian small retailers, built by Fulhive to help stores run checkout, inventory, receipts, and practical business workflows. This Privacy Policy explains how FulPOS collects, uses, protects, and shares information in language that is meant to be legally complete but still readable.
This policy is not formal legal advice and does not replace advice from a qualified lawyer. It is our operating privacy commitment for the FulPOS product and the Fulhive ecosystem.
This policy applies to the FulPOS website, the browser-based POS app, retailer accounts, distributor workflows, support communications, product photo features, inventory and transaction records, and related Fulhive services that link to this policy.
It does not cover third-party websites, payment terminals, messaging platforms, or distributor systems that Fulhive does not own or operate.
Where privacy law uses data controller, data user, processor, or operator wording, Fulhive generally acts as the operator of FulPOS and as the service provider that processes retailer POS data to deliver the product.
For account administration, platform security, product improvement, support, and anonymized or aggregated insights, Fulhive may determine the relevant business purposes and safeguards. Retailers remain responsible for the accuracy of the store, product, staff, and transaction information they enter into FulPOS.
Sales records, transaction line items, product catalogues, inventory changes, receipt settings, store profile details, account details, uploaded product photos, and distributor catalogue interactions may be collected when you use FulPOS.
We may also collect sign-in details, role information, support messages, basic device and browser information, approximate location information such as postcode or state, security logs, diagnostic events, and records of privacy choices such as distributor sharing consents.
We use information to provide checkout, barcode lookup, inventory tracking, product management, receipt printing, offline app behavior, account access, support, security monitoring, and retailer-facing recommendations.
We also use information to process distributor catalogues, suggest product matches, improve categorization, prevent misuse, debug reliability issues, and understand whether FulPOS is useful for real store operations.
Our legal and business purposes include providing the requested service, performing account and support obligations, protecting the platform, complying with applicable law, improving FulPOS, and operating the Fulhive distributor insight model in a privacy-respecting way.
When consent is required for a specific activity, such as store-level distributor access, we rely on that explicit retailer choice. When we use anonymized or aggregated information, we do so for market insight, product improvement, and distributor intelligence without exposing named store operating records.
FulPOS may use cookies, browser storage, service worker caching, and Firebase or Firestore local cache features to keep the app signed in, remember basic settings, improve reliability, and allow the POS to continue working when internet access is unreliable.
Firestore offline persistence means some POS data may be stored locally on the device through the browser so transactions, product lookups, and inventory workflows can continue offline and sync when the connection returns. Retailers should use trusted devices and sign out where shared computers are used.
FulPOS uses Firebase Auth, Firestore, Cloud Storage for Firebase, Cloud Functions, Firebase App Hosting, and related Google Cloud services to authenticate users, store POS records, keep uploaded files, run server-side workflows, host the app, and protect service reliability.
These providers process data for Fulhive under their applicable cloud terms and security controls. Fulhive may add other carefully selected processors for support, monitoring, analytics, communications, or AI-assisted product features when needed to operate the service.
Fulhive may use anonymized or aggregated insights from FulPOS to understand category demand, basket sizes, sales velocity, postcode-level trends, stocking gaps, and product opportunities across groups of stores.
These insights are designed to remove direct store identity and reduce the risk that a distributor can identify a specific retailer from ordinary market trend reporting. Fulhive may use and commercialize these anonymized or aggregated insights as part of the Fulhive business model.
Store-level distributor access requires explicit retailer opt-in for the specific distributor and sharing purpose. Fulhive does not give distributors named-store sales records, inventory records, product margins, contact details, or operating history by default.
Retailers should be able to see what categories of data are shared, who receives it, and how to turn that sharing off. Revoking consent may stop future sharing, but it may not fully delete information already received by a distributor where retention is legally or operationally required.
We keep information for as long as reasonably needed to provide FulPOS, maintain business records, support accounting and dispute handling, improve reliability, comply with law, and protect the security of the service.
Retention periods may differ by data type. For example, transaction records may be retained for store reporting and audit needs, support messages may be retained while a request is active, and local offline cache may remain on a device until cleared by the browser, app, or user.
Fulhive uses technical and organizational measures intended to protect FulPOS data, including authenticated access, role-based permissions, Firestore security rules, encrypted cloud services, logging, backups, and limits on who can access production information.
No system is perfectly secure. Retailers should protect their passwords, restrict staff access, secure POS devices, keep browsers updated, and contact Fulhive quickly if they suspect unauthorized access.
FulPOS may process and store information in Malaysia and in other countries where Fulhive, Google Cloud, Firebase, or other processors operate infrastructure or support teams.
When information is processed internationally, privacy and data protection laws may differ from those in your location. Fulhive relies on provider safeguards, contractual terms, access controls, and practical security measures to protect the information.
Depending on applicable law and your relationship with FulPOS, you may ask to access, correct, export, restrict, or delete certain personal information. Retailers can also manage store details, staff access, product information, and distributor consent choices inside the product where those controls are available.
Some requests may be limited by legal duties, security needs, backup retention, transaction integrity, or the need to keep accurate business records. We may need to verify your identity or store authority before acting on a request.
FulPOS is built for business use by store owners, staff, distributors, and administrators. It is not intended for children or minors, and minors should not create accounts or submit personal information without appropriate parent, guardian, or employer authorization.
If you believe a minor has provided personal information to FulPOS without proper authorization, contact us so we can review the situation.
Fulhive may update this Privacy Policy as FulPOS develops, new Firebase or cloud features are added, distributor workflows change, or legal and operational requirements evolve.
When changes are material, we will take reasonable steps to make the updated policy available and, where appropriate, provide additional notice in the product or through account communications.
For privacy questions, data access requests, correction requests, distributor consent questions, security concerns, or complaints, contact FulPOS at hello@fulpos.com.
You can also use the Contact us page to route retailer, distributor, partnership, or privacy requests. Please include enough detail for us to understand the store, account, or distributor relationship involved.