- Signing in
- You sign in with an email and password, or with a passkey. Passwords are never stored as typed; they are scrambled with a one-way method, so even we cannot read them. Repeated wrong attempts lock sign-in for a while.
- Two-factor authentication
- Not available for dashboard accounts yet; Account settings shows it as Coming Soon. A passkey is the strongest sign-in option today. Your customers can sign in to your shop with a one-time code texted to their phone.
- Signed-in devices
- Account settings lists every device signed in to your account. You can sign out one of them or all of the others, and changing your password signs you out everywhere else. The sign-in cookie is shielded from other code running in the browser, and we keep only a scrambled copy of it on our side.
- Keeping shops apart
- Every record is tagged with the shop it belongs to, and the system only returns records for the shop you are signed in to, even when a record is requested by its ID. A shop ID sent from a browser is never trusted as proof of access.
- Stored secrets
- The Google connection keys we hold for you are encrypted before they are stored. Everything else we store is protected by our hosting provider’s storage encryption.
- Backups and restore
- There is no separate, conventional backup copy kept somewhere else. Instead, each layer has its own protection. The product’s code is kept in version control, so any release can be rolled back. The database is kept by our hosting provider with restorable checkpoints, so it can be put back to any minute within about the past 30 days. Photos and files are kept on the provider’s durable file storage, built to keep files safe even when hardware fails. A database restore puts everything back to that moment for every shop at once, so it is a last resort rather than a per-shop undo. We have not yet published a tested restore exercise.
- Dashboard Copilot
- The Copilot can read your shop’s records but cannot change them on its own, and its view of orders leaves out customer contact details, addresses, and payment details. It can prepare a change for you, but only the shop owner can approve it, and the approved change goes through the same checks as one made in the dashboard. If you ask for a person, it drafts an email to support@cottagecms.com that is sent only after you approve it. There is no phone support.
- Reporting a security problem
- Email support@cottagecms.com and describe what you found. There is no separate security address or bug bounty program yet; reports go to the same inbox as other support email, which aims to reply within 24 hours. The same address is published for security researchers in the standard security.txt file at /.well-known/security.txt (also served at /security.txt).