TSC private service

Privacy and Local Data Notice

This notice describes the current private TSC service and the proven Local-First Personal design. It is not a public-launch privacy notice. TSC is currently a private service. Each approved user has their own account-scoped encrypted Local Vault for genuine Personal employment and pay information. Private Members have separate Local Vaults, and the Owner cannot read another Private Member's Local Vault contents or passphrase. Unapproved and public users are not authorised.

Current boundary: each approved user may enter only their own genuine Personal employment and pay information in their own encrypted Local Vault. The Owner controls Private Membership approval but cannot read another Private Member's Local Vault contents or passphrase. A Private Member cannot invite, approve, suspend, revoke or manage other members. Do not enter bank details, tax identifiers, identity documents, medical details, signatures, addresses or business-confidential documents. Structured Personal employment, pay, timesheet, leave and pay-record information saved in TSC remains in the user's encrypted Local Vault and is not authorised for Base44 cloud storage. Payslip PDFs and full extracted payslip text are not stored in that vault. Creating a TSC account alone does not grant Private Membership or Local Vault access. Unapproved access, open public membership and public release remain blocked.

Who this notice applies to

This notice describes the private TSC service for people creating an account to request access and for approved users, including the Owner and Private Members. Creating an account does not grant Private Membership. Owner approval and activation are required before a Private Member can access the Personal workspace or Local Vault. Open public membership and public release remain blocked.

Operator identity pending final owner/legal confirmation

Privacy contact: Privacy contact pending final owner/legal confirmation

The operator identity and privacy contact are not yet final. TSC will not invent these details for the pre-launch notice.

Personal pay records and TSC account data are different

In the proven Local-First Personal flow, Personal employment and pay records are stored in an encrypted Local Vault in this browser on this device.

The proven Local-First Personal flow does not automatically sync Local Vault pay records to TSC or Base44 cloud storage.

TSC still uses Base44 for the hosted application and account access. Account identity, authentication/session information, access-control information, hosting requests, and security or technical service information may therefore be processed by Base44 and its service providers.

What the Local Vault contains

The Local Vault can contain Personal employment and pay records such as:

job and employer details
employment configuration and work pattern
Timesheets and Personal-recorded Leave
Expected Pay and Actual Pay
pay comparisons and structured review outcomes
monthly report snapshots

The Local-First design does not store a payslip PDF, full extracted payslip text, bank account details, tax identifiers or identity documents in the Local Vault.

What may still be handled through Base44

The current Base44 workspace records the app data region as the United States. Account and platform information handled through Base44 may therefore be processed outside Australia. The Local Vault pay records are designed to remain outside that cloud data path in Local-First mode.

Account and authentication information required to provide authorised access, and standard technical and security information required to operate and protect TSC, may still be handled through the hosted service. This means Local-First does not mean that every TSC interaction is network-free. It means the proven Personal employment and pay records are separated from the hosted account/platform path.

Encrypted backups

Encrypted TSC backups are created locally and are not automatically uploaded by the Local-First backup flow. You choose where to save, copy or store the backup file.

TSC does not store the Local Vault passphrase and cannot recover it for you. If you lose both access to the device vault and a usable encrypted backup or passphrase, Personal pay records may be unrecoverable.

Encrypted Local Vault backup files remain user-controlled.

Device and browser storage

Browser or device storage can be cleared, lost or unavailable. Persistent-storage requests can reduce some browser eviction risk where supported, but the browser decides whether to grant them and TSC cannot guarantee Local Vault retention.

Private or incognito browsing may remove Local Vault storage when the private session ends, and TSC cannot reliably detect every browser private mode.

After the hosted app is already loaded and the Local Vault is unlocked, proven Local Vault reads, writes and calculations can operate without network access. Initial app loading, sign-in and hosted account checks may still require internet access.

Signing out, account deletion and Local Vault deletion

Signing out of the TSC account does not by itself delete the encrypted Local Vault stored in this browser.

TSC account deletion and Local Vault deletion are separate actions. Deleting an account does not by itself erase an encrypted Local Vault already stored on the device.

Deleting the Local Vault, clearing the browser site data, or losing the device can remove the device copy. An encrypted backup can restore a Local Vault only when the backup and correct passphrase are available.

Security

Encryption and Local-First storage reduce exposure, but no browser, device or online service can be guaranteed to be completely secure.

TSC's Local-First design has been tested so that Personal pay records stay out of the normal network path during Local Vault operations after the app is loaded and the vault is unlocked. This does not protect against malware, malicious browser extensions, a compromised device or a malicious or compromised version of the app.

Access, correction and privacy complaints

TSC remains a private service. If it is ever considered for public release, the operator identity, privacy contact and any required public privacy process must be completed before that separate release decision.

Local Vault pay records are controlled on the user's device. Accessing or correcting those Local records is a different process from requesting access to account information held through the hosted service.

Retention

TSC does not set a server retention period for Local Vault pay records because the proven Local-First flow does not automatically upload those contents to TSC cloud storage. The user controls the device copy and any encrypted backup files they create.

A final retention and deletion position for TSC account, authentication, security, diagnostic and provider-held information remains subject to operator decisions and external legal/privacy review.

Hybrid AI privacy boundary

Hybrid AI is optional. When used, it must use the separately controlled outbound-summary, field-selection and per-request confirmation process.

TSC does not automatically send Local Vault files, full payslip files, full pay-record text, employer names, account email, bank information, tax identifiers, addresses or free-text notes through Hybrid AI. Outbound summary content is reviewed and confirmed by the user for each request.

TSC is not payroll, employer, tax or legal-entitlement authority

TSC calculates, records, compares and explains evidence. It does not process or approve payroll, move money, lodge statutory reports or determine legal employment entitlements.

TSC does not operate payroll or move money. TSC is not an employer, tax authority or legal-entitlement authority.

Terms Log in