Skip to content

Security and privacy

Proof of work without the surveillance

eBRBe was rebuilt from scratch with privacy and security as defaults. Here is how we handle your data, and the principles behind it.

Principles

  • Evidence over surveillance

    We never log keystrokes, infer emotion or productivity scores, or capture screens by default. Anything captured is visible to, and deletable by, the person it's about before anyone else sees it.

  • AI drafts, people approve

    AI writes timesheets, reports and invoice lines. A person confirms anything that leaves the workspace or affects money. The AI only sees data the requesting person is allowed to see.

  • Honest and minimal

    We run on our own server and keep third parties to what the product needs: payments, AI and email. The subprocessor list names every one.

How we protect your data

  • Encryption in transit

    Every connection uses HTTPS with HSTS. Session cookies are HttpOnly, Secure and SameSite, and a strict Content Security Policy limits what pages can load.

  • Accounts and secrets

    Passwords are hashed with a memory-hard algorithm, two-factor authentication is available to everyone, and you can see and revoke your sessions. API keys are stored only as hashes, and third-party tokens are encrypted at rest.

  • Workspace isolation

    Every record belongs to a workspace, every query is scoped to it, and automated tests check that one workspace can never read another's data. Permissions are checked on the server for every page, action, API call and MCP tool.

  • Private files

    Uploads are never in a public folder. They are served only through signed links that expire, with type checks and size limits.

  • Backups

    The database and uploads are backed up every night. We keep 14 daily and 8 weekly copies, and test restores regularly.

Controls for larger teams

On the Business plan, rolling out workspace by workspace. Ask us to switch them on for yours.

  • Single sign-on with SAML 2.0 or OpenID Connect per workspace, on domains you verify with a DNS record; enforce it for everyone but owners (break-glass).
  • SCIM 2.0 user and group provisioning: people are added, updated and switched off from your directory, and groups map to roles.
  • Custom roles built from a permission catalogue, per-project overrides, rates and costs hidden from managers if you want, and guest access that expires.
  • Audit log search and export (CSV or JSON), with an optional signed webhook or syslog-over-TLS stream to your SIEM.
  • Data retention per workspace with daily purges, and legal hold that pauses every purge and deletion.
  • An IP allow-list for the web app, API and MCP server, required two-factor authentication, member session management and API key rotation reminders.
  • A full workspace export (JSON, CSV and files) at any time, and workspace deletion with a 30-day grace period.

Subprocessors

The companies that process customer data for us. We announce changes before they take effect; the subprocessor list is the authoritative version.

SubprocessorPurposeLocation
Stripe, Inc. and affiliatesSubscription billing and invoice payments (Stripe Billing and Stripe Connect)United States and EU
Anthropic PBCAI features: timesheet drafts, reports, quick add and Ask eBRBeUnited States
Cloudflare, Inc. (Turnstile)Bot protection on public forms (only when enabled)Global
GitHub, Inc.Importing commits and pull requests as evidence, and GitHub sign-in (only when enabled)United States
Google LLCGoogle sign-in (only when enabled)United States

GDPR and your rights

  • Export your data and delete your account yourself, at any time.
  • A Data Processing Addendum for customers who process personal data with eBRBe.
  • A public list of subprocessors, updated before changes take effect.
  • Retention settings for workspaces that need them (Business plan).
  • Only essential cookies, so there is no cookie banner. We don't use advertising or third-party tracking cookies.
  • A DPIA template for Business customers who turn on optional proof capture.

Responsible disclosure

Tell us privately through the contact form. Machine-readable details are in /.well-known/security.txt.

  • Report privately with enough detail to reproduce the issue. We acknowledge reports within 3 working days and keep you updated until it's fixed.
  • Test only against your own account and workspaces. Don't access, change or delete other people's data, and stop as soon as you reach someone else's.
  • No denial-of-service, spam, social engineering or physical attacks, and no automated scanning that degrades the service.
  • Give us 90 days (or until a fix ships, if sooner) before sharing details publicly. We'll credit you if you'd like.
  • If you follow these rules in good faith, we won't pursue or support legal action against you for your research.

Bill your next client for AI work

Free for up to 3 people, with the AI cost ledger included and a 14-day Pro trial. No card needed.