Security Overview
Version 1.0 · Effective 2026-08-08 · Last updated 2026-08-08
The security controls that are actually implemented in the platform.
Authentication
Accounts are managed by a managed authentication service. Passwords are never stored in the application database and are never held in plain text; they are stored as salted hashes by the authentication provider. Email/password and Google sign-in are supported, sessions use short-lived access tokens with refresh, and email confirmation is required for new email/password accounts. Password reset uses a single-use emailed link.
Access controls
Roles are stored separately from user profiles and are checked on the server. Designer workspaces distinguish workspace administrators from sales representatives, and retailer users are limited to their own retailer records.
Tenant isolation
Every business table enforces row-level security in the database. Queries run under the identity of the signed-in user, so a workspace can only read and write its own retailers, appointments, orders, collections, styles and files. Hiding UI is not used as an access control.
Server-side authorization
All privileged operations run through server functions that validate the caller's bearer token and re-check membership and role before touching data. Public endpoints are limited to a narrow, explicitly selected set of public showroom fields.
Input validation
Request payloads are validated with schema validation on the server. Database access uses parameterized queries through the data API, which prevents SQL injection. Rendered user content such as signatures is sanitized against an allowlist.
Data in transit and at rest
All traffic is served over HTTPS. Data is stored in a managed cloud database and object storage with encryption at rest provided by the hosting platform. Uploaded files live in private buckets accessed through short-lived signed URLs.
Monitoring and audit logging
Authentication events are recorded by the authentication provider. The platform additionally records an in-app audit log of important workspace actions, including sign-in, sign-out, password change, team and permission changes, retailer, order and collection changes, and privacy requests.
Backups
Database backups are provided by the managed hosting platform. Restoration is a platform-operator action, not a self-service feature.
Incident response
Reported or detected security issues are triaged by the platform operator, who investigates, contains, remediates and notifies affected customers where required by law or contract. Timeframes are not contractually guaranteed unless agreed in writing.
Data retention
Business data is retained while an account is active and afterwards only as needed for legitimate business and legal purposes. Deletion requests are processed through the privacy request workflow after identity verification.
Subprocessors
External providers that process customer data on our behalf are listed on the Subprocessors page and kept current.
Responsible disclosure
If you believe you have found a vulnerability, please email [SECURITY EMAIL] with enough detail to reproduce it. Please do not access other customers' data, degrade the service, or publicly disclose the issue before we have had a reasonable opportunity to remediate.
What we do not claim
We do not currently hold SOC 2, ISO 27001, HIPAA or PCI certification, and we make no such claims. This page describes only controls that are implemented today.
Report a security concern
Found something that looks wrong? Email security@amebsolutions.com with steps to reproduce. Please do not access other customers' data or publicly disclose the issue before we have had a chance to fix it.