Privacy policy

Who is responsible

Olamide Olatayo Bello is identified as the operator of Global POS. This notice describes the current administration and storefront preview, including the installed web app. Each participating store controls the business and inventory information it provides.

Location and address searches

With browser permission, your coordinates are sent to the Global POS server to sort registered stores by distance. The application does not intentionally save shopper coordinates to its database or continuously track location. The current page requests location when opened and when you tap the location button; your browser may reuse a previously granted permission or a recent location reading.

Manual address searches compare your entry with registered stores in your browser. Your search text is not sent as a search query to the server. Store addresses, store coordinates, product names, stock and prices are public storefront information. Inventory inherits the store location, not the shopper location.

Product search

Nearby product search uses your device coordinates to rank matching merchant catalogs. When online search is selected, Global POS processes the product description and shares rounded location with the Overpass service to retrieve candidate store listings. Descriptions are used locally to filter listing categories and names; they are not sent in the external request. Search descriptions and rounded locations may be held in the in-memory discovery cache for 15 minutes. No product search starts a purchase. Opening a source-listed store website sends you to that independent service, whose terms and privacy practices apply.

Online store discovery

When device location is permitted and no registered store is within 500 metres, the page automatically searches online stores. Manual address selection avoids this lookup. Rounded coordinates (three decimal places) are sent to OpenStreetMap’s Overpass service to retrieve nearby shop listings. Results are cached in server memory for 15 minutes. Temporary Ansible job files are removed after the request. Accepted locations apply only to the current page; acceptance does not claim store ownership, publish inventory or authorize payments. Source providers may process network metadata under their own policies.

Administration data

Business signup creates a tenant administrator account and records acceptance of the terms and privacy versions in the audit trail. The service stores account email addresses, password hashes, user IDs, roles, store and tenant assignments, account status, hashed session tokens and expiry times. It also stores tenant, store and inventory records and audit events about administrative changes. Passwords are not written to the audit trail. Audit events may contain business details and identifiers submitted in forms.

Devices, logs and local storage

Hosting, web servers and network providers may process IP addresses, browser details, request URLs, errors and security logs. Location coordinates are currently included in discovery request URLs and may appear in infrastructure logs. Infrastructure access and retention must be reviewed before public launch.

The administration interface keeps its bearer session in page memory rather than persistent browser storage. The installed web app uses a service worker and browser Cache Storage for a small offline notice, stylesheet and icon. It does not intentionally cache API results, inventory, prices, credentials, payment status or private administration responses. Device and browser history remain under your browser's controls.

Purposes and recipients

Data is used to discover stores, publish inventory, manage authorized accounts and tenant access, investigate changes and operate the service. Hosting and infrastructure providers process data as necessary to deliver it. Authorized super admins can access administration records across tenants; other staff are scoped by assigned permissions. This release includes no advertising or analytics scripts, no marketing signup and no personal-data sale feature. This notice does not authorize a future sale, targeted advertising or unrelated marketing.

Public demo

Each demo login creates an isolated sample database, separate from production records. Demo data is available for one hour and expired demo databases are removed on the next demo login. Do not submit real personal information to the demo. The public demo credentials do not grant production access.

Marketplace, payments and integrations

Checkout records store/seller details, products, quantities, prices, totals, customer email, agreement acceptance, provider references and verified order status. The app stores a hash of the random order-access key; the browser keeps the original in tab session storage so it can reopen the order after a provider redirect. Integration API keys are displayed once and stored as hashes, prefixes, store scopes and expiry records.

For configured hosted checkout, necessary order details and the customer email are sent to the selected Stripe, Paystack or Flutterwave merchant integration. Payment-card details are entered on that provider’s website, not Global POS. Provider privacy and processing terms apply. The demo uses a local simulator and does not contact real providers. No camera images are collected. Location permission is not automatic-payment consent.

Request-throttling buckets retain hashes of origin addresses or integration-key IDs and expire on later requests. The reverse proxy may separately retain network logs. Production provider credentials are held in a private server environment file; the GUI stores reference names, not those secret values.

Retention and security

Sessions expire after one hour, and expired rows are removed at a later successful login. User, store, inventory, audit, order, agreement, integration-key and login-limit records currently remain until handled by an authorized operator; no automated retention or deletion schedule is configured. Backup and infrastructure retention periods are not yet configured in this notice. Operational schedules and a working rights-request process must be established before public commercial launch.

Current controls include password hashing, hashed session tokens, scoped access and application-level audit protection. No system can guarantee absolute security. Deployment must use HTTPS and restrict database and backup access.

Your choices and requests

You can deny or revoke location permission, use manual store selection, sign out, uninstall the app, and clear site storage through your browser. Clearing local storage does not delete server-side records. Ask your provisioning administrator to route account access, correction or deletion requests to the operator. Applicable rights and lawful record-retention duties vary by jurisdiction; this preview has no automated rights-request workflow.

International use, children and contact

Hosting regions and international transfer arrangements must be disclosed before enabling affected production services. Global branding does not mean services are approved in every country. This release is not directed to children. A direct public privacy email and operator postal contact are still pending; they must be supplied before public commercial launch.

Updates

The operator should publish a new dated version when practices materially change and provide any required notice or consent before new uses begin.