Local first. Clear about connected data. Local register functions work offline. Enrolling a device enables Cloud synchronization; printing sends slips to the printer you choose.
Who this policy covers
DSA Software Corporation provides PeakPOS Lite, an Android point-of-sale app, and its connected PeakPOS Lite Cloud service. This policy explains information handled by the app, the connected service, and this website. Stores control the information they enter about their staff and business operations.
Core sales, inventory and reporting can be used on the Android device without Cloud enrollment. Connecting a store enables the additional data transfers described below.
Information on your Android device
The app stores owner and cashier names, local user identifiers, roles, salted PIN hashes, products, selected product photos, stock movements, sales, cash amounts, order slips, void reasons and business audit history in its private device storage. PINs are checked locally. The app does not send local PINs or PIN hashes to PeakPOS Lite Cloud.
Local retail receipt lines, cash tendered, change, reconciliation notes and locally selected product photos are not part of the app’s Cloud synchronization. Product photos you choose are read through Android’s image picker and stored in the app. Distributor catalog images are downloaded separately.
Local store-owner and cashier profiles operate on the device. They are separate from Cloud portal accounts issued by DSA.
What connecting to Cloud sends
Enrollment sends your activation code, a generated installation identifier, the device’s public authentication key and app, database and protocol versions. The service associates the device with an existing retailer. Authenticated requests include device and key identifiers, a request identifier, timestamp and cryptographic signature. The device’s private authentication key stays in Android Keystore.
Connected devices download linked distributor catalogs, product images and delivery updates. They upload completed delivery references, line references, received quantities, completion status and time.
The app also uploads daily sold and voided quantities, sale-line counts, stock quantities, low-stock thresholds, product references, business dates and measurement times for distributor-managed products. These records are associated with the store and device; they are not anonymous. Enrollment enables continuing synchronization, including background work when Android permits. The app currently has no separate switch for these metrics.
The retailer-owner dashboard additionally supports private whole-store daily sales and void totals, transaction counts, and product inventory snapshots including names, barcodes, categories, units, selling prices and costs. Supported Android versions can also send daily sales and void totals grouped by local register user, with the user's stable local identifier and display name. These transfers require an Android version with the corresponding reporting support and its updated disclosure; older versions do not send them. The dashboard shows missing reports as awaiting synchronization, not as zero sales. This feed contains no customer information, cashier PINs, PIN hashes, payment details or retail receipt lines.
Cloud enrollment is optional for local store operations. Contact DSA if an enrolled device needs to be revoked or its store connection needs to be changed. Revocation does not itself erase records already sent.
How information is used and who can access it
DSA uses service information to operate the register connection, authenticate devices and portal users, deliver catalogs and delivery records, provide distributor quantity and stock reports, support stores, and investigate service or security problems. Authorized DSA personnel have access according to their administrative role.
Linked distributors can view delivery information and reports for their own products at currently linked stores. Removing a store link removes that distributor’s access to the store’s current and historical quantity reports through the service. It does not erase the underlying records or copies previously obtained by the recipient.
The retailer-owner dashboard is restricted to the signed-in owner’s store. Its whole-store sales amounts, cashier breakdowns and names, retail prices, costs and locally created products are not exposed through distributor reporting. The installable dashboard requires a connection for fresh reports; its offline fallback does not store sales or inventory reports on the phone.
The service uses hosting infrastructure to store and process Cloud records. Connection and operational logs can include IP address, time, requested path, response status, browser or app information and error details. Portal sign-in uses essential session and security cookies. Administrative audit records identify the acting account or device, affected records, action and time.
The Android app contains no advertising SDK. Google Code Scanner handles diagnostic and usage information as described below. Information deliberately sent to a printer or to support is handled in the following sections.
Activation QR scanner and Google services
Starting with Android version 1.0.2, you can scan an activation QR code using Google Code Scanner, provided through Google Play services. Camera scanning starts when you choose Scan activation QR. Google processes the camera images on the device and returns the scanned code to PeakPOS Lite; Google states that images and scan results are not sent to its servers or stored by Google. You can still enter the activation code manually.
The scanner SDK sends diagnostic and usage metrics to Google. These can include device model and software information, app package and version, device or installation identifiers, performance measurements, SDK settings, feature and download events, and error codes. Automatic zoom also reports a temporary scanning-session identifier, zoom changes and the predicted position of a barcode within the camera image. These positions are image coordinates, not the device's geographic location.
Google uses these metrics to operate, troubleshoot, improve and protect its APIs under Google's Privacy Policy. SDK data is transmitted using HTTPS. Scanner components can download or initialize before a scan, and Cloud enrollment choices do not control this SDK's diagnostic collection. DSA does not receive the camera images. Contact DSA about information held by PeakPOS Lite; Google's policy explains its handling of the SDK metrics.
Printing and nearby devices
When you choose to print or reprint, the app sends an order slip directly to the selected Bluetooth or USB printer. A slip can include staff names, product descriptions, quantities and prices, transaction references and time, totals, cash and change. A voided slip can include the approving staff member’s name and entered reason.
The app stores the selected printer’s name and connection identifiers to reconnect. Android may request nearby-device permission or permission to use an attached USB printer. Printer transfers use the printer connection, not Cloud HTTPS. You and your store control the printer, printed copies and who can access them.
Security
Cloud API and catalog-image connections use HTTPS. Device requests are signed using an Android Keystore key. Local PINs are salted and hashed. Cloud portal passwords are hashed, and portal sessions have expiry, revocation and security checks. These measures do not guarantee that every device, printer or transmission is secure.
Keep the Android device and printer under the store’s control, use a device screen lock, and do not share PINs or activation codes. The app uses Android’s private app storage; this policy does not claim separate encryption of the local database or end-to-end encryption of printer output.
Retention and deletion
Local business records remain in app storage until removed from that storage. Deactivating a cashier prevents sign-in but preserves the cashier record and trading history. The current app does not automatically purge trading records or provide a complete store backup or export.
Clearing Android app storage or uninstalling can permanently remove local business records and the device identity. Cloud synchronization is not a full backup of local sales, users, photos or cash reports. Do not clear or uninstall a working store installation without first arranging how its records will be preserved.
Cloud device records, deliveries, receipts, product metrics and administrative audit history are not automatically erased when a device is revoked, a cashier is deactivated, or a distributor link is removed. Records are retained for the service’s operational, transaction-history, security and recordkeeping purposes. Deletion of local data does not delete Cloud records, backups or printed copies.
You can ask DSA about access, correction or deletion of information held by the service using the contact below. Identify the store and the information concerned, but do not include a PIN, password or activation code. A request concerning a store’s records may require confirmation of identity and authority. Records required for transaction integrity, security or applicable recordkeeping obligations may need separate handling; request the applicable retention and deletion details from DSA.
Support, questions and privacy requests
Email info@dsasoftwarecorp.com.ph and identify PeakPOS Lite. If you send a support request, the address, message and attachments you provide are used to respond and investigate the issue. Share only the information needed; remove unrelated personal or business details from screenshots.
For information controlled solely by your employer or store, contact the store owner as well. You may raise personal-data concerns with the Philippine National Privacy Commission. This policy does not remove rights available under applicable law.
Intended use and policy changes
PeakPOS Lite is a business tool for store owners and authorized staff in the Philippines. It is not designed as a service for children. Do not enter unnecessary sensitive personal information into product names, staff names or free-text business notes.
Updates to this policy will be published on this page with a revised effective date. Review it when connecting a device or when the service changes.