Back to Homepage
GAM Logo

Privacy Policy

Effective Date: September 22, 2026 · Last Updated: October 2026 · GAM (Gas Accounting Manager)

100% On-Premise Data Sovereignty

1. Introduction & Core Privacy Philosophy

Your privacy and the security of your business operations are paramount. GAM (Gas Accounting Manager) is intentionally engineered as an offline-first, on-premise desktop application.

Unlike web-based point-of-sale systems that transmit sensitive revenue, customer phone numbers, and operational records to cloud servers, GAM stores and processes all business data locally on your station's computer hardware.

We do not sell, monetize, track, mine, or share your business data with third parties or advertisers.

2. Information We Process Locally on Your Device

All information entered into GAM is stored in an embedded, local SQLite database (pos.db) residing on the station computer:

  • Operational & Sales Data: Sales transactions, fuel weights (kg), itemized amounts, payment methods (Cash, Card, Transfer), and timestamp sequences.
  • Inventory & Plant Records: Bulk Liquefied Petroleum Gas (LPG) storage pool levels, tank calibration entries, tanker delivery intake manifests, and retail accessories.
  • Cashier & Financial Records: Station expenses, shift close sheets, expected cash calculations, physical drawer tallies, cash discrepancies, and cryptographically salted password hashes.

None of this operational data is ever transmitted to NockForm Ltd, GAM Software Systems, or any external analytics platform.

3. Hardware & Local System Device Access

  • Thermal Receipt Printers (USB / Network / Spooler): GAM generates raw ESC/POS binary buffers to print customer receipts and shift close manifests directly to attached 80mm thermal printers. No printer telemetry leaves the computer.
  • Removable Media (USB Flash Drives): GAM can export verified snapshot backups and maintain automated secondary database mirrors on inserted USB drives for disaster recovery.

4. Network Communications & Licensing

  • Licensing Activation: During first-time activation, the desktop app pings our secure licensing endpoint to bind the product key to the terminal's hardware ID hash (CPU/motherboard UUID).
  • Zero Business Telemetry Transmitted: During update checks or license activation, no sales figures, financial totals, customer contacts, or plant ledger records are sent.
  • Web Portal & Google Sign-In: If you use Google OAuth on gampos.vercel.app, we request only your basic profile (email, name) to identify your license account. Payments are handled via Paystack without our servers ever seeing your raw card details.

5. Staff Authentication & Data Security

  • Local Password Hashing: Passwords are encrypted using one-way salted bcrypt algorithms before saving to the local database. Plaintext passwords are never stored.
  • Process Isolation: The user interface runs within a sandboxed Electron renderer using strict contextIsolation and disabled nodeIntegration.
  • Transactional Database Safety: The local SQLite database operates in Write-Ahead Logging (WAL) mode with atomic commits, preventing record corruption during sudden power loss.

6. Contact & Support

If you have questions regarding this Privacy Policy or data protection practices in GAM: