SCB security statement

Version dated 17 November 2026. Effective on publication.

Stockroom Control Brisbane Pty Ltd (ABN 44 703 940 130). Report security concerns to support@stockroomcontrol.com.au. Postal contact: PO Box 471, Mount Gravatt QLD 4122.

Scope

This statement describes safeguards and their limits. It is not a certification, security warranty, uptime commitment or service-level agreement. Any agreed service commitments must be recorded in the applicable accepted service agreement or order. Security depends on configuration, operating practices and customer use as well as technical design. SCB currently offers services to customers in Australia; this does not mean all data handling stays in Australia.

Identity and access

SCB uses Supabase for identity and authenticator verification, with SCB permissions controlling access to customer workspaces and functions. An authenticator-app TOTP verification is required. After normal sign-in, SCB may reuse a successful verification for that account in the same browser for up to 24 hours. New browsers, sign-out, revoked sessions, account recovery or changed authenticator details require fresh verification. Sensitive actions may require a fresh code sooner. Signing in or matching an email domain does not by itself grant business access. Users must have assigned permissions. Administrators should give each person only the access needed and promptly remove access when it is no longer required.

For invited email accounts, passwords entered in the SCB form pass through the SCB server over HTTPS to Supabase. SCB does not maintain a local password database. When session continuity is enabled, encrypted Supabase access and refresh proofs are retained server-side to maintain active sessions and verify remembered multi-factor authentication; these provider tokens are not exposed to browser storage. Actual site input renews active sessions, while inactive access closes after 30 minutes. Remembered verification is limited to 24 hours from the actual authenticator check and ends on sign-out, session revocation or recovery. Separate authorised integrations, including Xero, may retain encrypted access and refresh tokens for their own operation. Clearing a local integration credential does not by itself prove revocation at the other service.

A suspected compromise requires review of both identity-provider access and SCB sessions and permissions. Support recovery must verify identity and business authority. Email possession alone must not bypass the authenticator requirement. Contact SCB if you lose access or suspect another person has obtained it.

Application and infrastructure safeguards

HTTPS protects browser connections. SCB session cookies are host-only, HttpOnly and Secure in production. Application permissions are checked on the server. Access controls, secure communications and application audit records support protection and investigation of account and business activity. Authorised SCB personnel and necessary providers may access relevant information for their duties; this is not end-to-end encryption that excludes the service operator.

SCB uses Cloudflare infrastructure, including D1 data services, and Supabase authentication. The observed D1 location is Oceania without an established Australia-only jurisdiction restriction. A Supabase Sydney region does not establish that support, subprocessors, logs or backups remain there. The privacy policy explains overseas handling. Provider certifications do not certify SCB as a whole.

Browser storage and integrations

The application does not store bearer tokens in localStorage, sessionStorage or an offline service-worker cache, and does not provide an offline count ledger. To recover an interrupted job setup, reviewed baseline inventory rows and non-secret setup details are saved in tab session storage for the initiating account and client. These drafts may survive a reload or browser session restoration. SCB clears these drafts after successful setup, a successfully resolved cancellation, explicit sign-out, or a verified switch to another account in that tab when browser storage is available, and warns if it cannot confirm clearance. Storage limits or failures can prevent local recovery; keep the source export and check existing jobs before starting a replacement. Signing out or clearing a draft does not delete an already-created server job or downloaded files. Information is also present in browser memory during use. On shared devices, sign out, close the tab, and protect or remove downloaded files; browser storage is not a private encrypted vault. Where site usage measurement is enabled, a random analytics tab identifier is kept in session storage. The privacy policy explains the recorded analytics fields, scheduled active-record retention and Do Not Track and Global Privacy Control choices. This analytics storage is separate from authentication and inventory storage.

Connect integrations only with the customer's authority and the permissions needed. Where calendar feeds are enabled, a subscription URL can provide access to published shifts and shared locations without an interactive sign-in. Keep it private and revoke or regenerate it if exposed. Revocation cannot remove copies already cached or imported elsewhere.

Logging and incident reports

Application audit and security records support investigation. Logging and scheduled cleanup code do not establish continuous monitoring or prove that every scheduled operation has succeeded. This statement does not promise continuous incident coverage or a fixed response or notification time.

Report suspected unauthorised access or vulnerabilities to support@stockroomcontrol.com.au with the affected page, approximate time and a safe description. Do not include passwords, recovery codes, session tokens, invitation or calendar links, or other customers' records. SCB will assess reports and coordinate appropriate containment, investigation and remediation. Any legally required notifications remain subject to applicable law. Contractual incident targets require a separate express agreement supported by an operational response process.

Backups and recovery

An on-demand encrypted backup download and an isolated restore have been tested. That test demonstrates the tested export and restore, not recovery of every service dependency or recovery during a production failure. A cloud-synchronised copy does not by itself establish that a usable backup can be downloaded and restored after loss of the original system.

This statement does not promise automated offsite backup operation, a fixed backup expiry, a maximum amount of lost work or a fixed recovery time. Customers should retain exports and source records needed for their own continuity and statutory duties. Contact SCB to agree the export and recovery arrangements needed for a particular service. Deletion, backup copies and provider retention are addressed in the privacy policy and any specifically agreed retention arrangements.

Customer responsibilities and limitations

Use updated devices with screen locks and individual accounts. Protect credentials, recovery methods and subscription links. Review permissions when staff join, change roles or leave. Revoke connections that are no longer needed. Use approved workflows for sensitive information, check report recipients and protect or remove downloads on shared devices.

No online service can guarantee absolute security. Local regression tests and a successful isolated restore are not an independent penetration test, certification or proof of hosted-provider recovery behaviour. Material service or security commitments must be expressly agreed, rather than inferred from feature availability or an individual test. Nothing in this statement excludes rights or obligations that cannot lawfully be excluded.