gecko continuity — keeping australia running
Back to sign in
Security scanned daily · deep scan weekly · reviewed 18 September 2026

gecko continuity Trust Centre

Security and data-handling facts for the gecko continuity application. Claims on this page are limited to controls verified in the current product.

Request information

Security

Implemented controls

Encryption in transit

All connections to the application — including the sign-in page, workspace and API traffic — are encrypted using TLS (HTTPS). Unencrypted connections are not served.

Implemented

Encryption at rest

The database and its backups are encrypted at rest using AES-256, a widely adopted industry-standard cipher. Data is encrypted by the platform before it is written to disk, with no additional action required from your team.

Implemented

Row-level security

Access to business data is enforced inside the database itself using row-level security (RLS) policies. Every table — risks, activities, resources, dependencies, contacts, playbooks, policies and reports — is restricted so records can only be read or changed by members of the organisation that owns them. This protection applies even if application code were bypassed.

Implemented

Least-privilege database roles

The browser connects using a narrowly scoped, public-facing database role with no direct table access. Elevated privileges exist only in server-side functions, which verify the caller's role before performing privileged operations. Administrative database credentials are never present in the application or the browser.

Implemented

Authenticated access

Application workspaces require a signed-in account managed by the platform's authentication service. Sessions use short-lived signed tokens that expire automatically and are refreshed only for active sessions. Passwords are never stored in plain form.

Implemented

Input validation

Data sent from the browser is validated on the server before it reaches the database. Records are also constrained by database schema rules as a second layer, so malformed or unexpected data is rejected.

Implemented

Organisation-scoped access

Operational records are restricted by organisation membership. Signed-in users can access records only where their membership matches the record's organisation, and there is no cross-organisation visibility.

Implemented

Controlled invitations

Workspace invitations expire after 14 days. Only the person who created an invitation can view or remove it before acceptance.

Implemented

Managed backups

The database is backed up automatically by the hosting platform, and data storage is replicated so a single hardware failure does not affect availability.

Implemented

No third-party data sharing

Business data entered into gecko continuity is used only to operate the service for your organisation. It is not sold, shared for advertising, or used to train AI models.

Implemented

Data

Information handled

Account data

Name, email address, phone number and profile image when provided.

Organisation data

Business profile, team membership and outstanding invitations.

Operational resilience data

Risks, activities, resources, dependencies, contacts and disruption playbooks.

On-device data

Checklist completion state and the first-login welcome acknowledgement are stored in the browser on that device.

Infrastructure

Hosting and data location

Managed cloud infrastructure

Application infrastructure

gecko continuity runs entirely on a managed cloud platform that provides application hosting, managed authentication, an encrypted relational database and file storage. Infrastructure patching, capacity management and platform security updates are handled by the platform provider, and no servers are operated directly by gecko continuity.

Assurance

How we maintain these controls

Continuous security review

Security review is not a one-off exercise. Automated security scans run against the application and database every day, with deeper security scans performed weekly. Any issues these scans identify are tracked to resolution, and controls are re-verified as the product changes.

Secure by design

Security controls are built into the application and database rather than layered on afterwards. New tables are created with row-level security enabled and access restricted to authenticated, organisation-scoped roles before they can hold data.

Your data stays yours

Business data belongs to your organisation. You can export your continuity plan, risks and reports at any time, and workspace records are permanently removed when an organisation is deleted.

Kept current

The controls described on this page are actively maintained, not snapshots from a point-in-time audit. Platform security updates, patching and capacity management are handled by the underlying infrastructure provider.

Responsible disclosure

Report a security concern

Email what you observed, when it occurred and reproducible steps. Do not include another person’s sensitive information.

help@rqld.info