Privacy during
development.

Sign-in information

Sign-in is handled through Auth0. When you choose Google, Google shares the basic identity information you permit, such as your name, email and profile information, through Auth0. The current flow requests basic sign-in, profile and email information, not access to Gmail, Drive or Calendar.

Cabasis uses the validated identity to recognise your account. A suitable name can create your initial account record; otherwise you are asked to supply a display name. Matching email addresses do not automatically combine different sign-in identities. Email/password entry happens on the secure sign-in page; Cabasis HTML and JavaScript do not collect or store your password.

Your profile

Cabasis stores your account reference and display name. Suitable names and contact email may be filled from sign-in information. You can add or edit optional given/family names, date of birth, contact email, phone and postal address. Your contact email is separate from the verified sign-in email snapshot.

The private personal record is available to you and the project operator. Business team lists show display names and roles, not these private details. A business Owner role does not give access to the project operator's private account-management tools.

Plans and business access

Your sign-in identity, Cabasis profile, plan and business permissions are separate. Signing in does not activate Business or verify a payment. The prototype records manual plan decisions and business membership separately; this website does not collect payments.

Hosted test records

The hosted test account service runs on Render in Singapore (Southeast Asia). Cabasis account and profile records for this test are stored in Neon PostgreSQL in Sydney, Australia (ap-southeast-2). Auth0 handles identity separately, and Google handles its own sign-in information when you choose Google. These account-storage locations do not describe every provider's processing location.

The hosted test dataset is separate from retained local preview records. Earlier local accounts, plans, business memberships and desktop/module data are not automatically migrated or shared with it. This hosted signup test does not establish a shared desktop or business-data environment.

Sign-in uses cookies to maintain your session and protect requests. Hosted customer sign-in is separate from local project-operator tools. Signing out ends your Cabasis test sign-in session, but does not delete saved account records or necessarily sign you out of Google or the identity provider.

Use test information and avoid real customer or sensitive project data. For questions during testing, speak to the person who shared the Cabasis preview with you. This page does not establish production availability, completed provider verification or production data-migration arrangements.