SECURITY & PRIVACY · VERSION 2026-10-23
Practical protection. Clear limits.
This page describes BM’s standard service as reviewed on 23 October 2026. It is information about current controls, not an independent security certification or a guarantee against every incident.
Your company stays separate
Company access is checked on the server using memberships and roles. Records and files are scoped to the workspace; changing a company ID in a URL does not grant access. Owners manage their team. Drivers and technicians have restricted access to assigned work. Brighter administrator support access is time-limited and recorded.
Sign-in and permissions
Office users sign in using email and a password of at least 12 characters. Brighter platform administrators must use an authenticator. Driver access uses a company ID, sign-in name and four- or six-digit PIN, with persistent attempt limits. Passwords and PINs are hashed. Private invitation and recovery links expire. Password recovery revokes existing office sessions; resetting or disabling a driver PIN revokes that driver’s sessions. Company owners should review access regularly.
Documents and integrations
Business files are kept in private object storage and served after access checks. Retained documents are checked against recorded hashes. Some emailed documents use a random, seven-day link stored as a hash; treat that link as confidential because possession allows download until it expires. Email attachments and copies already downloaded cannot be recalled.
Connections use HTTPS. Xero tokens are encrypted and bound to the workspace; organisation selection is explicit. Stripe handles card entry and payment processing. BM does not store full card numbers. Integration credentials are kept server-side.
Recovery and continuity
Database point-in-time recovery is provided by Cloudflare D1. The paid service offers a 30-day history. BM also has a separate private recovery bucket and a scheduled file-copy process. These copies are in the same provider account, so they are not an independent off-provider disaster-recovery service.
Recovery checks include restoring database exports in isolation and checking retained-file references and hashes. A historical successful check does not guarantee recovery of every later change. File copying can lag or fail, and full production failover is not promised. No contractual recovery-time or recovery-point guarantee is included in self-service plans. Ask us about the latest recovery evidence or requirements before relying on a specific deadline.
Activity and incident handling
BM records important access, support, permission, billing and business changes. It also records queued-email status and processing failures. These are operational audit records, not a certified tamper-proof log of every view. We investigate reports, contain affected access, assess the information involved and coordinate notifications required by law.
Report a suspected security issue by emailing travis@brightertrading.com.au with “BM security incident” in the subject, or call 0435 458 275. Include the time, affected workspace and a short description. Do not send passwords, tokens or other customers’ records.
What we do not claim
We do not claim ISO 27001 or SOC 2 certification, a completed independent penetration test, Australian-only processing or complete WCAG 2.2 AA conformance. Accessibility and security testing are ongoing. Tell us if a barrier or vulnerability affects your use. Read support and data options or our Privacy Policy.
Contact Brighter
Travis John Gollan trading as Brighter Trading (sole trader), ABN 40 993 718 319
C/O Kootingal Post Office, Kootingal NSW 2352, Australia
travis@brightertrading.com.au · 0435 458 275
Published 23 October 2026. This version.