Security

What protects your account, your designs and your shoppers today. Each point below is true of the product as it runs now; we add one only when it is.

1. Your data

• Each account's data is kept apart. Every customer table in our database enforces row-level security, so an account can read and change only its own rows, and every API route refuses a request that has no signed-in session or valid key.
• Card details never reach us. Payments run on Stripe. Card numbers go straight to Stripe and never touch our servers.
• Camera frames stay on the device. AR try-on reads the camera in the browser. Frames are analysed on the device and are never uploaded or stored.
• Your data, yours to take or delete. Owners and admins download everything in the account from Settings, or over the API, at any time. The owner can ask for the account to be deleted there; we confirm by email before anything is deleted. You can erase a shopper's leads yourself, in the dashboard or over the API, when they ask.

2. Access

• Roles for every team member. Owner, admin, member and viewer, so each person gets only what their work needs.
• API keys are kept only as hashes. A key is shown once, and we store only its SHA-256 hash. Each key has its own scopes and can be locked to your domains.
• New passwords are checked against known breaches. A new password is checked against public breach lists before it is accepted. Only the first five characters of its hash leave the browser, never the password.
• Protected share links and embeds. A password on a share link or an embed is stored as a scrypt hash, and an embed loads only on the domains you list.
• Staff actions are logged. Every change our staff make to a customer account is written to an audit log.

3. On the web

• HTTPS everywhere. Every page and API call is served over HTTPS with HSTS, so a browser never falls back to an unencrypted connection.
• Our pages cannot be framed. The app refuses to load inside another site's frame. Only embeds can, and only on the domains you allow.
• Prices are worked out on our server. A ring's price is recomputed on the server at every quote, cart and checkout, so nobody can change what is charged from the browser.
• Signed webhooks. Events we send to your systems carry an HMAC-SHA256 signature over a timestamp and the body, so you can check they came from us.

4. Report a problem

Found a security issue? Email info@3djewelrydesigner.comwith the details. Please don’t test against other customers’ data.