Privacy policy

Who is responsible

Saline Singularity operates this instance of Saline Singularity Hive and controls the data stored in it. The application is designed as single-team software; one team's database is not shared with another team.

Information we process

Account and sign-in information

When you sign in through a configured identity provider, the application receives a stable provider account identifier and a verified email address. It stores that identifier, the provider used, and the email address at the time the account is linked. Sign-in access and refresh tokens are not retained by the identity login flow.

Team information

The application stores the information needed for enabled team functions, such as membership, roles, meetings, training records, onboarding status, and audit history. Access is limited by role. Because robotics teams can include minors, the application is designed to minimize personal data and support deletion or anonymization when a member leaves.

Connected calendar information

When an authorized operator connects a team calendar, the application may read and write event titles, descriptions, dates and times, locations, recurrence details, visibility, attendee email addresses, event status, and provider event identifiers for that selected calendar. It uses this information only to create, update, cancel, and reconcile team meetings and training events.

The application stores the team's meeting or training record, the external event identifier, and synchronization state needed for reliable updates and retries. Calendar data read during reconciliation is processed transiently unless it is already part of a team record or is required as synchronization metadata.

How information is used

Information is used to authenticate authorized users, provide configured team workflows, keep the selected team calendar aligned with approved schedule changes, secure the service, and maintain required operational and audit records.

Information obtained through connected accounts is not sold, used for advertising, or used to train general-purpose artificial-intelligence models.

Sharing and service providers

Information is shared only with the instance operator, authorized team users, configured outside services when a team workflow requires it, and infrastructure providers needed to operate this instance. Event attendees may receive invitations and updates when an authorized user publishes a meeting or training event.

Use and transfer of information received from Google APIs follows the Google API user-data policy, including its applicable limited-use requirements.

Retention, deletion, and revocation

Linked identity records are retained while the associated platform account exists. Meeting, training, and audit records are retained according to the team's operational and safety needs; identifying membership data is deleted or anonymized when it is no longer needed. Connection credentials remain until they are replaced, disconnected, revoked by the provider, or removed by an authorized operator.

You can revoke a connected account through the provider's account-security controls. Revocation stops future access but does not automatically delete records already required for team operations. To request access, correction, or deletion of information held by this instance, contact [email protected].

Security and policy changes

The application uses role-based access controls and encrypts stored adapter credentials. No internet service can guarantee absolute security. Material changes to this policy will be posted on this page with an updated effective date.