Security
How we protect your store and your customers.
Autofli handles store data, customer records, and payment flows. Here is how that data is secured, isolated, and kept private — in plain language.
Encryption
Your data is encrypted at rest and in transit.
At rest
AES-256
All data stored in our PostgreSQL database is encrypted at rest using AES-256. This includes your product catalog, customer records, order history, and store configuration.
In transit
TLS 1.3
All data in transit between your browser, our API, and third-party services is protected by TLS 1.3. HTTP connections are redirected to HTTPS. Internal service-to-service communication is encrypted.
Authentication
Secure sessions. No plaintext credentials stored.
Autofli uses secure session-based authentication. When you log in, a cryptographically signed session token is issued and stored in an HttpOnly cookie — inaccessible to JavaScript on the page, preventing XSS-based session theft.
Your password is hashed using bcrypt with a per-user salt before being stored. We never store plaintext passwords, and our infrastructure never has access to your plaintext credentials after they leave your browser.
API keys for third-party services you connect (ad platforms, supplier accounts) are encrypted at the application layer before being written to the database — they are not stored as plaintext even in the encrypted database.
Data isolation
Your store's data is strictly isolated.
Every store on Autofli operates as a fully isolated tenant. Your product catalog, customer records, order history, and store configuration are scoped to your store ID. No API endpoint can return data from a store other than the authenticated user's own stores.
Agent operations are also scoped per store. When an agent runs a task for your store — adjusting a price, placing an order, responding to a support ticket — it operates only on your store's data and can only affect your store's records.
Admin access to store data is logged and auditable. We do not access merchant store data for purposes other than operating the service and debugging issues you report.
HiveMind privacy
Aggregate signals, not raw store data.
HiveMind learns from performance signals across all stores on the platform. This is the source of its compounding advantage — niche-level benchmarks that no single store could generate alone.
The learning process is additive and anonymized. What enters HiveMind is statistical outcomes: conversion rate ranges, margin benchmarks, ad angle performance patterns. Your customer names, email addresses, order details, and product-specific data never enter the shared layer.
No other merchant can query your store's data through HiveMind or any other mechanism. The shared layer contains only derived statistical patterns — nothing that could identify your store, your customers, or your specific products.
Payment security
Stripe handles all payment data. We never see card numbers.
All payment processing for your storefront customers flows through Stripe. Autofli never handles, stores, or transmits raw cardholder data. Card numbers, CVVs, and full PAN data are captured directly by Stripe's PCI-compliant infrastructure — they never pass through our servers.
Our integration with Stripe uses their hosted Checkout Sessions and Payment Elements — both of which are certified PCI DSS Level 1 compliant. Autofli's own PCI scope is minimal by design.
What we store after a successful payment: a Stripe Payment Intent ID and the last 4 digits of the card used, for order reference. Nothing that could be used to process a payment or identify a full card number.
Infrastructure
How the platform is hosted and backed up.
Railway-hosted PostgreSQL
Our primary database runs on Railway's managed PostgreSQL service. Railway provides infrastructure-level encryption, isolated networking, and automated security patching.
Automated backups
The database is backed up automatically on a daily schedule with point-in-time recovery available. Backup retention covers 30 days, giving us the ability to restore from any point within that window.
Network isolation
The API server and database communicate over a private network and are not directly accessible from the public internet. The database accepts connections only from our API service, not from external IPs.
Dependency security
Dependencies are monitored for known vulnerabilities. Critical security patches are applied on a priority basis. We track upstream security advisories for the libraries in our stack.
Security reports
Found a vulnerability? Tell us.
If you discover a security issue in Autofli's platform, please disclose it responsibly. We review all reports and respond to critical issues within 24 hours.