Beta waitlist information.
When you request beta access, Shifu stores your email address, the optional reason you select for joining, and the time of your request. We use this information to manage beta access and send beta-access emails you agree to receive.
You choose every connection.
Shifu shows the current access boundary for a source before you authorize it. Connect only sources you are allowed to use and that are relevant to the question you want to answer.
Coding-session syncs stay reviewed.
For supported coding harnesses, Shifu prepares a concise redacted summary locally and shows the exact unsynced segment before you confirm it is sent. Raw session transcripts are not uploaded.
GitHub access has a clear boundary.
During the current beta, the GitHub connection lets you connect your identity and choose repositories for future use. It does not read repository contents today.
You can remove access.
Use Sources in the dashboard to disconnect a GitHub account or revoke a coding-harness key. This stops the current connection from being used.
Generated work stays reviewable.
Shifu keeps the context behind summaries visible so you can check what is accurate and decide whether to use it. Source information remains in its original system, where any changes must be made.