# Why does Whalesync create a database user? ### Why does Whalesync need to create a user in my Supabase project? The password you set when creating a new project can't be retrieved via the Supabase API. We could ask you to provide that password when setting up a sync, but then the only way for you to revoke our access would be to rotate that password, potentially breaking your app. Instead, we create a new login role with the same privileges as the `postgres`role, and set our own password. This role is fully controllable by you using standard Postgres commands, and can be deleted if you want to remove Whalesync's access to your project. ### What is the user called? The user is named `whalesync_service_account_[ID]`, where ID is a string of hex digits unique to the sync. If you set up multiple syncs to the same Supabase project, you may see multiple users being created by Whalesync. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.whalesync.com/connectors/supabase/why-does-whalesync-create-a-database-user.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.