Privacy Policy
Effective: 2 November 2026 · Applies to the StrataBase web application and associated cloud/archive services.
This Privacy Policy describes how StrataBase, a private-access geotechnical field and data platform, handles information. The application's administrator operates the platform; participating organisations are responsible for deciding which project data they are authorised to enter and share. Contact the administrator at stratabase.dev@gmail.com about this policy.
1. Information processed
- Account information. When you sign in with Google, StrataBase may receive your account identifier, email address, name and limited profile information needed to authenticate and identify you.
- Membership and access information. Your organisation, assigned role, authorisation status and related account identifiers are stored to manage permitted access.
- Project and field information. Authorised users enter project details, boreholes, test pits, geological and geotechnical measurements, structural observations, samples, associated locations, notes and other records. Some records may contain client-confidential information or personal information entered by users.
- Technical information. The application uses local device/browser storage for field records, session state and recovery checkpoints. Infrastructure providers may process standard network and security logs, such as request timestamps and IP addresses.
2. Why information is used
Information is used to authenticate users, apply organisation-based access controls, enable field logging and reporting, synchronise authorised records, generate recoverable backups, troubleshoot service errors and maintain the service. Do not upload personal or client-confidential material unless your organisation permits it.
3. Google sign-in and Drive access
Google sign-in is used to establish your identity through Supabase authentication. Signing in does not grant StrataBase access to your personal Google Drive.
A separately authorised administrator-controlled Google account may be used to create and retrieve organisation archives in a designated Google Drive folder. At the time of this policy, the backup connector uses the Google Drive scope that technically permits broad access to the connected backup account's Drive. The current archive workflow is designed to upload, list and download organisation backups in its configured folder, not to read ordinary users' personal Drive files. Drive authorisation credentials are held server-side rather than in the web app.
4. Where information is stored and shared
Field data is first stored on the authorised user's device, using browser-managed storage. When synchronisation is enabled and connectivity is available, authorised project data is transmitted to Supabase. Copies of selected project records may also be archived in Google Drive under the organisation's backup arrangement. Netlify serves the web application. These providers may process information to deliver the services under their applicable terms and data handling practices.
Project data is not made public through the StrataBase interface merely by being uploaded. Access is intended for approved organisation members. No advertising-based sale of Google user information is part of the described service.
5. Retention and deletion
Local records can remain in a browser profile after sign-out. Cloud records and separately created Drive archive copies may remain until an authorised user or administrator removes them, subject to operational recovery needs and applicable obligations. Deleting a record from the live workspace does not necessarily remove historical backup copies. A fixed automatic archive-deletion schedule is not yet represented as active in this application.
6. Security
StrataBase uses HTTPS, user authentication, organisation access checks and local-first storage. The operator aims to keep privileged cloud and Google Drive credentials on the server. No system can guarantee absolute confidentiality or availability. Protect your device, account and downloaded backup files, which may contain complete project datasets.
7. Your choices and rights
For requests concerning access, correction, deletion, or the use of your personal information, contact stratabase.dev@gmail.com. Depending on your relationship to an organisation and applicable law (including South Africa's Protection of Personal Information Act, where relevant), you may need to direct a request to the organisation responsible for the underlying project data. Requests will be assessed according to applicable obligations and the respective roles of the parties.
8. Changes
This notice may be updated as StrataBase's functionality, vendors, permissions or backup arrangements change. The effective date above indicates the most recent policy update.