Security & control
Your company's work, kept safe.
Your conversations, files and people records stay private: kept apart from every other company, protected on the way, and seen only by the people you choose.
- Encrypted on the way Every page and file travels over HTTPS, and calls are encrypted between your device and our media server.
- Databases of your own Your workspace has its own databases, never rows in a table shared with another company.
- Passwords never readable Passwords are stored only as a one-way hash, and repeated wrong guesses lock the account for a while.
- Every action recorded Who did what, and when, is written to an audit log your administrators can read.
- Our team is held to it too Our staff sign in with two-factor codes, and every time support looks at your workspace it is logged.
- You decide who sees what Roles and sharing are yours to set. Leavers lose access the moment you suspend them.
In detail
Six ways we keep your work safe.
Every action is on the record
Actions are written to an audit trail as they happen — who did it, what they did it to, when, and from which address. Credentials, tokens and message bodies are redacted before anything is stored, and a failure to write the log can never fail the action that caused it.
- Authentication, administration, project, document and access events
- Filterable by person, by subject and by project
- Readable by administrators inside the workspace, not by request to us
Offboarding actually ends access
Suspending somebody closes four doors in one action, because closing three of them is the same as closing none. The row is marked suspended, every issued token is revoked, any live socket is disconnected, and the mailbox is locked.
- No waiting for a session to expire on its own
- A user in a call is removed from it, not left connected
- Reversible — reinstating restores access the same way
Roles, not a list of exceptions
Access is granted by role across every surface rather than per person per feature, so what someone can reach is a property of their job rather than of who remembered to tick a box.
- Roles and permissions applied consistently across chat, mail, projects and documents
- Documents and boards shared to people or to teams, with per-share permissions
- Access requests arrive as a message to the owner rather than an email to an admin
Outsiders get a door, not a key
People from outside your company reach exactly one thing and nothing else. There is no account to create, and therefore no dormant account to forget about later.
- Invite links carry a title and an expiry
- Guests joining a call knock and are admitted by a host
- A guest never appears in your directory and never counts as a seat
Your calls are your own traffic
Media runs on our media server rather than through a third-party meetings vendor, and moderation is enforced at the media layer — a force-muted participant stops producing audio rather than being asked politely by the interface to stop.
- No third-party conferencing provider in the path
- Mute and admission decided by the server, not the client
Your mail stays where it is
Oprex connects to the mailboxes you already own over IMAP and SMTP. Your mail server does not change, your addresses do not change, and migrating to Oprex does not mean migrating your mail.
- Same server, same addresses, same retention as today
- Read, sent and administered inside the workspace
Your data
Three questions, answered directly.
- Where it lives
- On our servers, in databases of its own: every workspace is kept apart from every other customer.
- Who reads it
- Your administrators, inside your workspace. Support access is not a standing permission.
- Who changes it
- Roles decide what each person may see and do, and an audit log records who did what, and when.
Questions about security? Ask us.
Send us your questionnaire or just your worry. A person answers, plainly, before you commit to anything.