Data Protection, Security & Retention

1. Core Data Protection Principles

Every operation involving personal data in BeställNu adheres to the following core tenets:

• Lawfulness, Fairness, and Transparency: Data is processed on valid legal bases and transparently disclosed to users.
• Purpose Limitation: Collected for explicit, specified purposes and never repurposed.
• Data Minimization: We collect only what is strictly necessary to run the platform.
• Accuracy: We keep records correct and updated.
• Storage Limitation: We delete or anonymize personal data when it is no longer required (except when overridden by tax/accounting statutes).
• Integrity and Confidentiality: Enforcing technical security to block unauthorized leaks or access.

2. Privacy by Design & Default

BeställNu integrates data protection directly into the application layer:

• Tenant Isolation: We enforce Row-Level Security (RLS) policies within our PostgreSQL databases (e.g. `order_tenant_isolation` utilizing `app.active_team_id`). This ensures a restaurant can never query or manipulate another restaurant's records.
• Credential Security: Passwords are cryptographically hashed using industry-standard algorithms (Argon2/Bcrypt) managed via Better Auth.

3. Data Processing Agreement (DPA)

For guest and employee records entered by restaurants, the restaurant acts as the Data Controller. BeställNu provides a standardized DPA defining our instructions, processing limits, and security obligations as the Data Processor.

4. Contact & Data Protection Officer

For any questions regarding our GDPR compliance, please contact our support team at support@bestallnu.com.

1. Infrastructure Security

• Cloud Hosting: Our architecture runs on Microsoft Azure within European Union jurisdictions (Sweden/Germany). Hosting centers utilize strict physical security controls, backup generators, and automatic DDoS mitigation.
• Network Isolation: Database clusters and internal microservices run behind enterprise firewalls and private Virtual Networks (VNets), blocking public web access.

2. Encryption

• In-Transit Encryption: All communications between client devices, browsers, and backend endpoints are encrypted via HTTPS and Secure WebSockets utilizing TLS 1.3 protocols.
• At-Rest Encryption: PostgreSQL databases utilize Transparent Data Encryption (TDE). Automated daily backups are encrypted prior to secure cloud storage.

3. Access Controls

• Least Privilege: Internal access to live environments is restricted to essential ops engineers. Access requires secure VPN tunnels, cryptographic keys, and mandatory Multi-Factor Authentication (MFA).
• POS App Security: Employees sign in via personal PIN codes. Role-Based Access Control (RBAC) restricts critical cashier permissions (e.g. initiating refunds, printing Z-reports) to authorized manager roles.

4. Vulnerability & Monitoring

• Continuous package audits (`bun audit`) and lint checks are executed to patch code flaws.
• Monitoring alerts are established via Azure Application Insights to instantly identify security anomalies or malicious request payloads.

1. Retention Schedule

2. Legal Override of GDPR Deletion Requests

Specific Swedish statutes mandate data retention. Under the Swedish Bookkeeping Act (Bokföringslagen), sales records, Z-reports, and cash register logs must be retained for 7 years. Therefore, guests or employees cannot request early deletion of fiscal transactions or staff logs under GDPR Article 17, as our legal compliance obligation overrides the right to erasure.

3. Destruction & Erasure Routines

• Automated Purges: Once a retention period expires, records are permanently dropped or anonymized from active database tables.
• Backup Cycles: Erased records may persist in encrypted system backups for up to 30 days before being automatically overwritten during normal backup rotation cycles.