Legal
Privacy Policy
This privacy policy outlines how ReefNetAI approaches account privacy, project visibility, cookies, and operational data handling.
1. Overview
This page explains how ReefNetAI approaches account data, project information, uploaded imagery, and platform usage data.
Our goal is to treat research and conservation communities with respect while giving teams enough control over how their work, profiles, and project materials are shared.
2. Information We Collect
Depending on how ReefNetAI is used, we may collect account information such as name, email address, affiliation, organization details, and workspace role information.
We may also collect project data and operational content submitted to the platform, including uploaded reef imagery, annotations, monitoring context, project notes, metadata, and communications sent through support channels.
- Account and profile information
- Project, survey, and monitoring data
- Uploaded imagery and derived annotations
- Usage, session, and support information
3. Project and Data Visibility
Some ReefNetAI content may be intended for private collaboration, while other content may be meant for broader sharing across research, restoration, or public-facing programs. Visibility settings should be configured according to the needs of each project.
If a project, dataset, or workspace is configured for limited access, we intend access to be restricted to authorized collaborators. If a project is intentionally published or shared more broadly, certain images, labels, metadata, or summary information may be visible to a wider audience.
4. User Profile Privacy
Basic profile details may be visible within ReefNetAI workspaces so collaborators can understand who is participating in a project. Profile visibility may vary depending on platform configuration and account settings.
The email address associated with an account should not be displayed publicly unless the account holder intentionally publishes it through profile or contact information fields.
5. How We Use Information
We use collected information to operate the platform, support authentication and access control, maintain project workspaces, improve product usability, respond to support requests, and communicate relevant updates about ReefNetAI.
We may also use aggregated or operational information to improve model performance, workflow design, platform reliability, and research-supporting features, provided that such use is aligned with project permissions and product expectations.
6. Cookies, Sessions, and Analytics
ReefNetAI may use cookies or similar technologies for login sessions, account security, basic preferences, and other core application functions.
If analytics or monitoring tools are enabled, ReefNetAI may also collect limited usage information to help us understand product performance, diagnose issues, and improve the user experience.
7. Sharing and Disclosure
We do not intend to sell personal information. Information may be shared with authorized collaborators inside a workspace, with service providers supporting the operation of the platform, or when required to comply with legal obligations.
Where a user or organization chooses to publish project outputs, selected content may become visible outside the immediate workspace according to the project’s sharing configuration.
8. Security and Data Retention
We aim to use reasonable administrative and technical measures to protect ReefNetAI data. However, no online system can guarantee absolute security, and use of the platform always carries some degree of risk.
We retain information for as long as it is reasonably needed to operate ReefNetAI, maintain project continuity, meet support and operational needs, or satisfy legal and contractual obligations.
9. Policy Updates and Contact
This privacy policy may change as ReefNetAI evolves. When it does, the updated version should be posted on this page with a revised effective date or update notice.
For questions about privacy, account access, or project data handling, contact ReefNetAI through the help center, Slack community, or the designated support email used by the platform team.