Doby Businlog
Start free trialTry free

Security & trust

Your company’s work, kept to your company

Every company on Do gets its own workspace address, its own certificate, its own app process and its own database. Here’s how that works, what we do to keep sign-in safe, and the controls your admins have, in plain English.

See how it works Report a problem
  • Its own database per company
  • HTTPS with HSTS
  • Passkey sign-in
  • Cards handled by Stripe
Two companies on Do Example names

Acme

acme.businlog.comIts own address and certificate
Its own app processRuns separately from other companies
Its own database and filesTasks, boards, files, rota

Brightwater

brightwater.businlog.comIts own address and certificate
Its own app processRuns separately from other companies
Its own database and filesTasks, boards, files, rota
Every company gets the same set-up. Workspace content is never kept in a shared database. Our account database holds owner and billing details, not your work.
1 database for each company
1 app process for each company
1 address and certificate for each company
5 ways to sign in, including passkeys

How we protect your workspace

Security, in plain English

What really happens behind the scenes, explained without jargon. Every point here describes how Do works today.

01

A separate workspace for every company

Your workspace isn’t a slice of one big shared database. Each company gets its own app process, its own database and its own folder of uploaded files, at its own address.

  • Its own address, like yourcompany.businlog.com, with its own certificate
  • Its own app process and its own database
  • Its own folder for uploaded files
  • Our account database holds owner and billing details, never your workspace content
  • Call rooms are named per workspace, so they can’t clash with another company’s
  • If a workspace pauses, for example after a trial, nothing in it is deleted
02

Encrypted connections and careful cookies

Everything between your browser and Do travels over HTTPS. Sign-in cookies are set so that page scripts can’t read them and they’re only sent over secure connections.

  • HTTPS for businlog.com and every workspace, with plain HTTP sent on to HTTPS
  • Certificates from Let’s Encrypt
  • HSTS tells browsers to use HTTPS for a year
  • Sign-in cookies are HttpOnly, Secure and SameSite=Lax
  • Every form that changes something on businlog.com carries a CSRF token
  • Account sign-ins on businlog.com end after 14 days
03

Passwords, passkeys and one-time codes

There are five ways to sign in to a workspace: a personal join link, email and passcode, email and password, a passkey, or a code sent by email. Pick the ones that suit your team.

  • Passwords are stored as PBKDF2-SHA256 hashes with a random salt, never in plain text
  • Passwords are at least 8 characters
  • Passkeys work with Face ID, Touch ID, a fingerprint or Windows Hello
  • A passkey only works on your workspace’s own address, and the device must check it’s you
  • Emailed sign-in codes are 6 digits, work once and expire after 10 minutes
  • Passcodes are short PINs for quick sign-in. A password or passkey is the stronger choice
04

Brakes on guessing and bots

Wrong guesses are slowed down and then stopped. Someone trying password after password, or code after code, soon runs out of tries.

  • In a workspace, 5 wrong tries in 15 minutes locks sign-in for 15 minutes
  • Emailed codes allow 5 tries, and at most 3 can go to one address every 15 minutes
  • Asking for a code gives the same reply whether or not the email has an account
  • Sign-in and sign-up on businlog.com are limited per network
  • Forms use a hidden trap field and a signed token to turn away bots
  • The sign-up confirmation code is kept only as a hash and expires after 15 minutes
05

Access you decide

Admins choose who sees what. People can be limited to the companies, projects or departments they work in, made read-only, or invited as guests with a link you can switch off.

  • Two roles, admin and member, and a workspace always keeps at least one admin
  • Limit a member to chosen companies, projects or departments
  • Read-only members can look but can’t change tasks or boards
  • Guest links can be view-only or edit, and can expire after 1 to 365 days
  • Files are only served to people who can see the space they’re in
  • Removing someone signs them out at once and closes their live connections
06

Safe files, and card details left to Stripe

Uploads are stored and served in a way that stops a booby-trapped file from running in your browser. When you pay, you enter card details on Stripe’s own pages, not ours.

  • Uploaded files are stored under random names
  • Files other than PDFs are served in a locked-down sandbox, and only safe types open in the browser
  • Rich text in docs and team mail is cleaned on the server, removing scripts, iframes and event handlers
  • Payments happen on Stripe Checkout and the Stripe billing portal
  • Businlog never handles your card details
  • No analytics or tracking scripts on businlog.com

Shared responsibility

What we do, and what you control

Security is a team effort. Here's the part Businlog looks after, and the part your workspace admins decide.

What Businlog does

Built in for every company. There's one plan, and it includes all of this.

  • Its own workspace for every company. Each company gets its own address, its own certificate, its own app process and its own database.
  • HTTPS everywhere. Connections use Let's Encrypt certificates, and browsers are told to stay on HTTPS for a year (HSTS).
  • Passwords stored as hashes. PBKDF2-SHA256 with a random salt, never in plain text.
  • Brakes on guessing. In a workspace, 5 wrong sign-in tries in 15 minutes locks sign-in for 15 minutes.
  • Safer files and documents. Uploads are stored under random names and served with strict safety headers. Rich text is cleaned on the server.
  • Card details go to Stripe. Payment happens on Stripe's own pages. We never see your full card number.

What your admins control

Settings inside your own workspace.

  • Who can see what. Limit people to chosen companies, projects or departments, or make them read-only.
  • Guest links. Pick the places a link opens, view-only or edit, and an expiry of 1 to 365 days. Switch links off at any time.
  • Ways in. Personal join links you can reset, passcodes you can set, passwords, passkeys, and emailed codes once your email is connected.
  • Signed-in devices. Everyone sees the devices they're signed in on and can sign any of them out. Admins can do it for anyone.
  • Leavers. Removing someone signs them out straight away and closes their live connections.
  • Admins. Roles are admin or member, and a workspace always keeps at least one admin.

For workspace admins

A quick security check

Six things worth doing once your team is in. Tick them off as you go.

Your ticks stay on this page. Nothing is saved or sent.

Questions

Security questions, answered straight

Is our data kept apart from other companies?

Yes. Each company has its own app process, its own database and its own folder of uploaded files, at its own address with its own certificate. Your tasks, boards, files and rota live in your workspace’s database, not in a shared one. To be precise: these are separate processes and databases, not separate servers or containers for each company.

Is our data encrypted?

Everything travelling between your browser and Do is encrypted with HTTPS, using Let’s Encrypt certificates, and HSTS tells browsers to stay on HTTPS. We don’t claim encryption at rest: your workspace database and files aren’t separately encrypted on disk. Passwords are stored as hashes, so they can’t be read back.

Do you support two-factor sign-in or single sign-on?

Not today. Do doesn’t have two-factor codes, or sign-in with Google, Microsoft or SAML. For stronger sign-in, add a passkey: it uses Face ID, Touch ID, a fingerprint or Windows Hello, and the device has to check it’s really you. Everyone can also see the devices they’re signed in on and sign out any they don’t recognise.

Who handles our card details?

Stripe does. When you pay, you enter your card on Stripe Checkout, and you manage it later in the Stripe billing portal. Businlog never handles your card details. You won’t be charged during the 30-day trial, and if you cancel before it ends you pay nothing.

Do you have security certifications, or use outside services?

Businlog doesn’t hold any formal security certifications, so this page tells you exactly how Do works instead. There are no analytics or tracking scripts on businlog.com. Inside a workspace, some features rely on outside services: Stripe for payments, Resend for email once you connect it, Google’s public server that helps calls connect, libraries that show file previews, Google Fonts, browser push services and a lookup that shows the approximate place of each signed-in device.

Found a security problem?

If you think you’ve found a security problem in businlog.com or a Do workspace, please email us privately with what you found and the steps to reproduce it, and we’ll look into it.

Email hello@businlog.com. Please don't post details in public until we've had a chance to fix it.

Email us Use the form

How we handle personal data is in our Privacy policy. The rules of the service are in our Terms.

Try it with your own team

Start a 30-day free trial. You won't be charged during the trial, and if you cancel before it ends you pay nothing.

Start your free trial Talk to us
Talk to us