How we keep your data, and your customers' data, apart.
CartonLedger is made by a small company. We don't have a dedicated security team or any security certification yet. This page says plainly what protects your data today, and what is still planned.
At a glance
| Area | Today | Planned |
|---|---|---|
| Separation between warehouses | Enforced by the database itself, checked at start-up and by an automated test battery | Independent penetration test |
| Encryption in transit | HTTPS only, with HSTS | |
| Encryption at rest | By our database and hosting providers, and by the object storage that holds uploaded photos and files; your mail-server password also encrypted by us | |
| Sign-in | Hashed passwords, lockout after repeated failures, rate limits | Two-step sign-in, single sign-on |
| Roles | Administrator, staff, read-only, customer | Custom roles |
| Logs | Activity and error logs, kept by plan | Alerting, a separate log store |
| Availability | A single application instance with provider health checks | External monitoring, a status page, a second instance |
| Certifications | None | SOC 2 is on the roadmap |
Kept apart by the database, not just our code
Row-level security on every tenant table.
Every table holding a warehouse's data carries that warehouse's id, set by the database. A policy lets a query see and change only its own warehouse's rows.
A role that cannot bypass it.
The app runs its queries under a restricted database role. A query without a known warehouse sees no rows, and its writes are rejected.
Refuses to start without it.
At start-up the app checks it is running under the restricted role. In production, if the check fails, it does not start.
Tested: 274 checks.
An automated battery signs in as users of different warehouses and roles and tries to read or change the other warehouse's orders, photos, files, users, settings and billing. Every check must pass before a release.
Sign-in and roles
- Passwords are stored only as salted bcrypt hashes, never in a readable form.
- After 10 failed sign-ins in a row, password sign-in for that account is locked for 15 minutes. Sign-in attempts are rate-limited.
- People added by an administrator get a temporary password and must change it first.
- Sessions are kept on the server; the cookie can't be read by page scripts and is sent only over HTTPS.
- What a person can do comes from their role in the warehouse they're working in: administrator, staff, read-only or customer.
- Customers see only their own orders and only what is meant for them. Internal notes, billing details and staff names are removed before data reaches them.
Files, payments and logs
- Uploaded files are stored under names the server generates and served only after an access check. Photo uploads must be real images.
- A strict content security policy allows scripts only from our own domain.
- Card details go straight from your browser to Stripe; they never reach our servers.
- Every change made in the app is recorded in an activity log (administrators get the log screen on Growth and above). Logs are kept from 30 days to 2 years, depending on plan. Passwords, tokens and card fields are removed before anything is stored.
- Errors are logged in our own database, not sent to a third-party monitoring service.
Honest limits today
- No two-step sign-in or single sign-on yet.
- No security certification and no independent penetration test yet.
- No uptime guarantee, public status page or automatic outage alerts yet.
- We have not yet run a scheduled, documented restore test, so we don't state a tested recovery time.
Questions about any of this? Contact us.
Try it with your own data.
14 days free, no card. Routine exports come with paid plans, and the full export when you leave is on every plan.
14 days of Growth free · No card · Then the Free plan, never a locked screen