Security
Security at AftrBase: Encryption, Access & Retention
AftrBase handles data on every transaction your counters process. This page documents how we protect it and what you can hold us to.
Encryption
- Customer data is encrypted in transit (TLS) and at rest on AftrBase infrastructure.
- The receipt URL carries an unguessable tokenized path; no customer data appears in the URL itself.
Consent & DPDP
- Phone numbers are captured only with consent at the counter; the consent record is stored with a timestamp and the counter identity.
- Receipt-only mode (no marketing) is the default posture; marketing consent is separate and optional.
- Customers can request data deletion to the brand; the brand owner controls the customer data, and AftrBase processes it on their instruction.
Access control
- Role-based access for counter staff, managers and owners; sensitive views (full CRM, exports) are restricted by role.
- SSO and dedicated CSM are available on the Enterprise plan.
- Every action on customer data is logged for audit.
Data retention
- Customer purchase history is retained per your configuration (up to 6 years), so loyalty and CRM stay meaningful.
- On termination of a pilot or contract, customer data is exportable by the brand and deletable on request.
WhatsApp Business API
- Receipts are sent through the official WhatsApp Business API as transactional (utility) messages — no grey-route spoofing, no policy violations.
- Message templates comply with Meta's business-messaging policy; we handle the review, and you keep the number.
Questions about security or a specific deployment? Write to [email protected].