Centauri Research Privacy Policy
Effective Date: October 5, 2026
This Privacy Policy is issued by Alpha Centauri Ventures Inc., operating as Centauri Research (“Centauri Research”, “we”, “us”).
1. Information We Collect
Centauri Research collects limited personal information to operate the Lake Digital Twin platform securely:
- Account Data: Email addresses, display names, and passwords managed securely via Firebase Authentication.
- Organization Affiliation: Municipality listings, NGO associations, or research scopes provided during onboarding to enforce database Row-Level Security (RLS).
- Usage Telemetry: Connection metadata, action logging, and API request audits to trace simulation executions and grab sample uploads.
- Access Requests: If you request access to a restricted feature (for example, road-salt modelling), we store your verified email address, the date of the request, and any note you choose to include. If your request is approved, your email address is also kept on the list of accounts allowed to use that feature. We keep access requests and the list of approved accounts until you ask us to delete them or your access is removed.
To ask us to delete an access request or remove your access, contact info@centauri-research.com.
2. How We Use Information
Your information is used strictly to enforce tenancy boundaries and deliver hydrological telemetry:
- To isolate database query scopes and prevent cross-tenant data leaks.
- To authenticate API endpoints and track researcher credits or simulation compute usage.
- To email critical telemetry alert warnings if registered thresholds (e.g. pathogen parameters) are breached.
- To review your access request, notify our team by email, and, if approved, grant and manage your access to the requested feature.
3. Data Sharing & Security
Centauri Research does not sell, lease, or monetize user data. Access is isolated at the database engine level via transaction-scoped Row-Level Security (RLS) policies. Shared simulations are only visible to specified organizations authorized via the `simulation_shares` schema.
4. Third-Party Integrations
The platform interfaces with the following subprocessors:
- Firebase Authentication: Identity provider and session tokens.
- Brevo (Sendinblue): Dispatch of transactional alert emails, recovery links and internal notices of access requests.
- Google Cloud Firestore: Storage of access requests and the list of approved accounts.
- Neon PostgreSQL: Relational and geospatial database hosting.