Keep your work yours.
Getherness separates account identity from private project records.
Authentication
Account authentication is provided by Supabase. Passwords are handled by the authentication service and are not stored in Getherness workspace tables.
Workspace access
Private workspace tables enforce ownership with row-level security. Browser clients use the public anonymous key together with a signed-in user session, never a service-role key.
Local execution
The web application does not request SSH credentials, execute terminal commands, or install local software. Repository links do not grant Getherness permission to access your repository.
Report an issue
Use the contact form to report a security concern. Include a concise description and steps to reproduce, without exposing passwords or private tokens.