1. Security Overview
At TindahanGo, data security is central to our engineering, deployment, and infrastructure operations. We recognize that retail shops, mini groceries, and sari-sari stores trust us with their sales, stock, and credit ledgers. We implement layered, industry-standard security controls to protect your data from unauthorized access, accidental alteration, or leakage.
2. Data Encryption
We secure data both in-transit and at-rest:
- Encryption in Transit: The production public API uses HTTPS/TLS to protect data in transit.
- Password Hashing: We do not store plaintext passwords or cashier security PINs. Credentials are hashed using bcrypt before database storage.
- API Session Hashing: Access tokens utilize signed JSON Web Tokens (JWTs) to verify permissions statelessly on every request.
3. Database Isolation & Tenancy Security
TindahanGo operates as a multi-tenant platform. This means multiple stores share the same cloud database infrastructure, but are fully isolated:
- All transactional, customer, and cashier records are linked to a unique `companyId` (tenant key).
- Database queries are dynamically restricted in the REST API layers using company constraints, ensuring cashiers or owners from one company can never query or view records belonging to another company.
- Superadmins can review payment queues but operate under restricted access controls.
4. Backups & Disaster Recovery
We maintain recovery procedures and may maintain continuity backups. Backup schedules, locations, encryption, and deletion timing are operational controls and are not guaranteed by this public policy.
- Recovery: Recovery procedures are maintained for service-continuity incidents.
5. Monitoring, Logging, & Rate Limiting
We use bounded security and operational controls:
- Error monitoring: Sentry integration exists but is currently disabled in production because SENTRY_DSN is not configured.
- IP Rate Limiting: Auth endpoints enforce a rate limit map per IP address to block automated password scanning or cashier PIN brute-force attempts.
6. Security Incident Response
In the event of a verified database breach or security failure:
- We will investigate, contain, and remediate verified incidents using measures appropriate to the incident.
- We will notify affected Store Owners and authorities without undue delay where applicable law requires notification.
7. Responsible Disclosure Policy
We welcome reports from independent security researchers to make TindahanGo safer. If you find a security vulnerability:
- Email the details to admin@octechph.com.
- Allow our team reasonable time (e.g., 30 days) to resolve the issue before publishing details publicly.
- Do not attempt to access, download, or manipulate other tenants' data during your research.