Privacy and your choices

This build is intended for demonstrations with fictional profiles or consenting test participants. Broader community access, retention periods and support ownership must be agreed before public membership opens.

Profiles and account access

Firebase handles sign-in and password recovery. Your account email and optional phone are private. Saving a profile does not publish it. Publishing shares selected details with signed-in members; seeking and identity audiences can be chosen independently. Accepting a connection does not share your email or phone.

Matching

Member-visible professional text is sent to Google Gemini to create numerical representations for matching. Identity fields, private and connection-only fields, account contacts, messages and fish appearance are excluded. A member-visible free-text field can still reveal information you type into it: review your previews before publishing.

Conversations and controls

Messages are stored for authorized participants. Removing a connection stops new messages while preserving history. Blocking hides the conversation from both participants; unblocking does not reconnect you. Unpublishing stops new messages and hides your profile. Requesting account deletion records a request for processing; it does not promise immediate erasure or removal from another participant’s retained history.

Office exploration

The office explorer loads Google Maps and initial DMV office listings when you open a page containing it. Google receives the network and browser information needed to provide its map. Office search uses the area and company name you enter; it does not request your location or send private member profiles or messages. Office results are transient provider content and are not a complete directory or evidence of hiring.

See Google’s Privacy Policy and Google Maps terms. Provider policy and key restrictions must be reviewed by the deploying project owner before enabling the explorer.

Local drafts

Unsaved text may be lost when you close or reload the page. Only a successful save confirms persistence. The application does not use message-body analytics or store unsaved contacts and messages in browser local storage.

Updated October 17, 2026. Terms and demonstration scope