Trust
Security
Last updated September 22, 2026
TerraLens uses practical security controls to help protect accounts, credentials and supported platform interactions. This page describes the security practices currently supported by the implementation.
Account access
TerraLens uses technical controls designed to help protect user accounts, credentials and applicable platform interactions. These controls reduce risk, but no internet-connected platform can be guaranteed to be completely secure.
For email and password sign-in, TerraLens stores passwords using one-way password hashing rather than plaintext. Credentials access checks require a verified email address and an active account before sign-in can complete.
Verified Google sign-in is supported when configured. TerraLens accepts Google sign-in only when the provider reports the account email as verified.
Verification and recovery
Email-verification and password-reset flows use randomly generated, time-limited tokens. Sensitive token values are stored in hashed form where these flows persist token records.
Applicable public confirmation and recovery flows also use token-gated access patterns so that sensitive recovery values are not stored as raw public records.
Restricted functionality
TerraLens applies server-side authorization controls to applicable restricted functionality. Enterprise Partnerships, for example, uses active-account checks together with role-based controls for the supported Partnerships management routes and APIs.
These controls are scoped to the functionality where they are implemented and should not be read as a claim of platform-wide role-based access control.
Backend credentials and integrations
Sensitive backend integration credentials are kept in server-side configuration. Applicable external API communication is routed through server-side boundaries rather than exposing backend credentials directly to browser code.
TerraLens error-handling paths are designed to avoid returning sensitive credential values to users when selected backend integrations are unavailable or fail.
Validation and error handling
TerraLens applies server-side input validation to applicable workflows before processing requests. Validation is used at selected API, authentication and operational boundaries where the current implementation supports it.
For selected account and integration flows, error responses are written to be useful without exposing passwords, raw tokens, provider secrets or backend credential values.
Contact
If you have a security concern about TerraLens or AI Home Group, contact us at hello@aihomegroup.com.au.