Data Loss Prevention Policy
Effective date: November 15, 2026
This policy describes the measures Lillo CX Inc. ("Lillo") applies so that data about merchants and their customers processed by the Lillo service (AI support, the support console, and our store-platform apps) is not disclosed, exfiltrated or lost without authorization.
1. We process only the data we need
- Store integrations request only the read access needed for support. For example, our Shopify app uses read-only access to orders, customers and products (read_orders, read_customers, read_products) and requests no write access.
- Order and shipping details are looked up in real time to answer a shopper's question in the chat. We do not store copies of orders or customer contact details. The only customer-related values we store from Shopify are the times of a customer's first and most recent order.
- Email addresses and phone numbers are partially masked in the support screens.
- We do not sell customer data.
2. Encryption in transit
- The service API, the support console and our website are served over HTTPS (TLS) only; HTTP requests are redirected to HTTPS. TLS for the API is terminated at a load balancer that accepts TLS 1.2 or later.
- The production database is configured to refuse unencrypted connections (require_secure_transport).
3. Encryption at rest
- The production database (Amazon RDS) has storage encryption (AES-256, AWS KMS) enabled. Its automated backups and snapshots are encrypted the same way.
- Integration credentials such as store access tokens are additionally encrypted by the application with AES-256-GCM before they are written to the database.
- Passwords are never stored in plain text; only bcrypt hashes are stored.
4. Access control
- Each workspace (merchant) has its own separate database. On every console request the server checks that the workspace in the sign-in token matches the requested workspace and that the user still belongs to it.
- The console sign-in screen offers an emailed one-time code (6 digits, valid for 5 minutes, invalidated after 5 wrong attempts, with send-rate limits), Google sign-in and Sign in with Apple. One-time codes are stored only as hashes.
- Console permissions are split into owner, admin, member and billing manager roles, and the server restricts actions such as settings changes and billing by role.
- At the network level, the production database accepts connections only from the security group of our application servers; it is not directly open to the internet.
- Access to production infrastructure (AWS) is limited to people we have issued accounts to, and we remove those accounts and permissions when someone leaves or changes role.
5. Secrets management
- Secrets such as API keys and database passwords are not stored in source code repositories. They are kept only in server environment files and in our deployment system's secret store, and the repositories are configured to exclude environment files.
- If a secret is exposed or suspected to be exposed, we rotate it immediately.
6. Logging and records
- Server logs are structured, and sensitive values such as authorization headers, cookies, passwords, tokens, one-time codes, card data, email addresses and phone numbers are automatically masked before they are written. In production, chat message bodies are not written to logs as-is.
- Server log files are rotated by size, and application event and usage log tables are automatically deleted after 90 days.
7. Separation of development and production
- Development and test environments use servers, databases and store-platform apps that are separate from production. We do not use production customer data for testing.
8. Backups
- The production database is backed up automatically every day, and automated backups are kept for 3 days. Backups are encrypted as described in section 3.
9. Retention and deletion
- When Shopify sends a customer redaction request (customers/redact), we delete that customer's order-time records. When Shopify sends a shop redaction request (shop/redact), we delete the integration tokens, the store details, order-time records and synced product data.
- When a merchant removes our Cafe24 app or disconnects it, we delete the tokens immediately and delete the member IDs, order data and integration data received from Cafe24 after 90 days.
- Merchants can delete their workspace from the console. A deleted workspace is kept for 14 days so it can be restored. We also accept deletion requests at hello@lillo.cx and delete the data without undue delay, except records we are required by law to keep.
- Retention periods are described in detail in our Privacy Policy.
10. Violations and changes
- Any confirmed data access or leakage outside this policy is handled under our Security Incident Response Policy.
- We review this policy when the service or infrastructure changes, and at least once a year, and publish changes on this page.
- Contact: hello@lillo.cx