Security Overview
At TAPOSna, we recognize that laundry counters handle sensitive customer contact numbers, daily cash totals, and confidential operational records. We treat security as an foundational operational requirement rather than an afterthought.
Our architecture combines modern cloud security standards with edge-first hardware communication, ensuring that customer records and financial balances remain private, authenticated, and resilient.
1. Encryption in Transit and at Rest
All interactions between counter tablets, attendant smartphones, customer tracking links, and TAPOSna services are protected by rigorous cryptography:
- Transport Layer Security (TLS 1.3): All HTTP traffic is strictly encrypted using modern cipher suites. Insecure HTTP connections are permanently redirected to HTTPS with HTTP Strict Transport Security (HSTS) headers enabled.
- Database Encryption at Rest: All stored database tables, transaction records, and cashier authentication tokens are encrypted using AES-256 standard encryption on physical storage volumes.
2. Tenant Isolation via Row-Level Security (RLS)
TAPOSna operates a secure multi-tenant architecture powered by PostgreSQL with granular Row-Level Security (RLS) policies:
Strict Shop Partitioning: Every query executed by the counter application or backend services requires an authenticated shop session. Database queries automatically scope results to the active shop tenant identifier.
Zero Cross-Tenant Leakage: Even in the event of an interface query anomaly, the database engine prohibits records belonging to Shop A from ever being exposed to Shop B.
3. Zero-Cloud Print Spooling Architecture
Many legacy POS solutions route sensitive receipt data to external third-party cloud print servers. TAPOSna takes an edge-first architectural approach:
- Local ESC/POS Bytecode Compilation: When an attendant clicks Print Stub, the raw 58mm printer instructions are formatted directly in the local browser memory sandbox.
- Direct Hardware Bluetooth Pairing: Bytecode streams directly from the tablet or laptop to the thermal printer via standard Web Bluetooth or USB Serial. Receipts are never proxied through intermediate cloud spoolers, preventing leakage of customer contact numbers or payment amounts.
4. Attendant PIN Locks and Role Permissions
Counter operations require distinct access boundaries between attendants and shop owners:
Restricted to weight intake, order status progression (wash, dry, fold), cash change computation, and claim stub printing. Prevented from altering base pricing or exporting customer lists.
Full control over base pricing configurations, kilogram minimum limits, attendant staff accounts, daily revenue reports, and historical shift audits.
5. Automated Backups and Disaster Recovery
Laundry counter continuity is vital. To guarantee disaster recovery:
- Continuous Point-in-Time Recovery: Database state write-ahead logs are synchronized continuously, allowing recovery to any minute of operation in the event of an outage.
- Daily Encrypted Snapshot Archives: Immutable daily backup archives are generated, encrypted, and distributed across geographically distinct cloud availability zones.
6. Responsible Vulnerability Disclosure Program
We welcome security researchers and developers to inspect our application security and report potential issues responsibly.
If you believe you have identified a security vulnerability in TAPOSna, please submit a detailed report to security@taposna.com. Please refrain from accessing or modifying user data without authorization, disrupting services, or publishing details prior to coordinated remediation.