Businesses kept apart
Every record belongs to one business, and every request is checked against the business that is signed in. Another business's data is not reachable, and this is covered by tests.
Available now
Security and your data
We tell you what protects your information, and just as plainly what we do not claim. Everything below is something we can point to in our code, our tests or our operating notes.
Every request is checked against the business that is signed in
Protection in layers
Each item is in use on the platform today.
Every record belongs to one business, and every request is checked against the business that is signed in. Another business's data is not reachable, and this is covered by tests.
Available now
Owner and Team member access levels. Owners manage the team; the menu and the server both limit what a person can do.
Available now
A second step with an authenticator app or an e-mailed code. Passwords are stored only as salted hashes, and repeated wrong attempts are limited.
Available now
See where you are signed in and end any session you do not recognise, or every other one at once.
Available now
The platform is served over HTTPS and tells browsers to keep using it (HSTS).
Available now
Sign-in, two-step codes, password reset and forms are rate-limited. Public forms check for abuse, and every public write is validated and size-limited.
Available now
The portal sends a strict content security policy, cannot be framed by another site and refuses requests from foreign origins.
Available now
Changes are recorded with who made them and when. The early-access business operations area also keeps the values before and after.
Available now
The database is backed up every night, each backup is checked, and a restore is tested on every test run. The newest 14 are kept.
Available now
The platform watches its scheduler, backups, certificates and the websites it manages, and alerts WEKRAM staff by e-mail.
Available now
Keys and passwords the platform needs are kept outside the web folders with owner-only permissions, are not in the code and are not in database dumps.
Available now
Server logs never contain codes, tokens or passwords, and old logs are rotated away after 14 days.
Available now
Only the right people
You decide who has access. If a phone is lost or a colleague leaves, you can end their access yourself.
The people who can sign in to your business.
Team member: enquiries and requests. Owner: everything, including team, invoices and business details.
Where you are signed in. End any you do not recognise.
In development
An encrypted copy of the backups, kept on another computer and another drive, is built and tested, but it is not yet running on a schedule. Today the verified nightly backups are kept on the platform's own server. We will say so here when the second copy is switched on.
Ask us anything before you decide. We answer plainly, including when the answer is "not yet".