Skip to content

Central Node POS for Android — Privacy Policy

Last updated: November 3, 2026

This policy applies to the Central Node POS app for Android (package com.centralnode.androidpos, shown on the device as “Central Node Pos”), published by Central Node LLC (“Central Node”, “we”, “us”). The app is a point-of-sale terminal for businesses that already use Central Node. It is used by that business’s staff, not by the public. Our website is covered by the general Privacy Policy; use of the service is governed by our Terms of Service.

1. Who is responsible for the data

The business that owns the register decides what is sold, to whom, and which employees use the app; it is the controller of its sales and customer records. Central Node processes that data on the business’s behalf to run the service, and is the controller of the device, sign-in and diagnostic data described below.

2. Data the app collects

  • Device registration. A register hash, checksum and PIN that your business issues in Central Node to bind this device to one cash register, and a device name and identifier for it. Stored on the device and on our servers.
  • Employee sign-in. The employee ID and the employee PIN typed to sign in. The PIN is sent to our server over HTTPS to be verified.
  • Business data entered in the app. Shifts (opening and closing time, cash amounts), sales and return receipts (items, quantities, prices, totals, payments, time, the employee who made them) and, if the cashier selects one, the customer attached to a sale (name and contact details your business holds). The app also reads your business’s product catalogue, stores and price lists.
  • Push notification token. A Firebase Cloud Messaging token, so the server can deliver notifications to this device.
  • Diagnostics. Crash reports and basic usage events (app version, Android version, device model, screens opened, crash stack traces) collected through Firebase Crashlytics and Google Analytics for Firebase. The advertising ID is not collected.
  • Technical data. IP address and request logs on our servers.

The app does not ask for or collect your location, contacts, camera, microphone, photos, files, SMS or call history, and shows no advertising. The only permission it asks you to grant is notifications (Android 13+). Its other permissions are the standard ones the notification and network libraries need: internet and network state, keeping the device awake briefly to receive a message, and receiving messages after a restart. It does not use the advertising ID.

3. How we use it

  • To register the device, sign employees in and keep the register’s shift, sales and receipts in sync.
  • To show the business its own receipts, shift reports and stock.
  • To send service notifications to the device.
  • To find and fix crashes, keep the service secure, prevent abuse and improve the app.
  • To meet legal, accounting and tax obligations that apply to the business and to us.

We do not sell personal data and do not use it for advertising or profiling.

4. Who receives it

  • The business that owns the register, including its owners and the employees it authorises, sees the sales, shift and receipt data produced on its registers.
  • Central Node servers and our hosting providers, which store and process the data to run the service, under confidentiality and security obligations.
  • Google (Firebase): Cloud Messaging delivers notifications; Crashlytics and Analytics receive the diagnostic data in section 2. See Google’s Privacy Policy.
  • Authorities, where the law requires it, and a successor, if Central Node is merged or sold.

No one else receives data from the app.

5. Security

Data between the app and our servers is sent over HTTPS. Access to a register needs both the registered device and an employee PIN, and a device can be revoked by the business at any time. No system is perfectly secure, and we cannot guarantee absolute security.

6. Retention

Sales, receipt and shift records are kept for as long as the business’s account is active and for the period that accounting and tax law requires afterwards. Device and sign-in data is deleted when the device is removed from the register or the account is closed. Diagnostic data is kept by Google for the period set in Firebase. Logging out of the app removes the signed-in employee from the device.

7. Your choices and deleting data

  • Log out from the menu on the home screen to remove the signed-in employee from the device.
  • Uninstalling the app removes everything stored locally on the device.
  • Notifications can be switched off in Android settings without affecting the app.
  • To access, correct or delete data held on our servers, or to close an account, email centralnodebusiness1@gmail.com with the business name and register. Employees and customers of a business should ask that business first; we will help it respond. Records we must keep by law are kept for the legal period and then removed.

8. Children

The app is for business use and is not directed to children under 16. We do not knowingly collect their data.

9. International transfers

Our servers and Google’s services may be located outside your country. Where data is transferred, we rely on appropriate safeguards such as standard contractual clauses.

10. Changes

If we change this policy we will post the new version here and update the date above. If the change is material, we will also tell businesses using the app.

11. Contact

Central Node LLC — centralnodebusiness1@gmail.com or +374 41 21 14 21.