The credential vault
Short answer: Every credential you give Build Perch (API keys, integration tokens, your license key) is stored in the Windows Credential Manager, the operating system’s own secure vault, not in an app file. Each secret is used only to reach the service you connected it to, and it’s never bundled into a settings or workspace export.
Where are my credentials stored?
Build Perch never writes secrets to a config file, a database, or anywhere on disk it manages. Every credential goes into the OS-native credential store (Windows Credential Manager), under a fixed set of entry names Build Perch defines: the app only ever reads or writes its own entries, and no settings or workspace export ever carries one. Each secret is used only to talk to the service you connected it to.
How do I add, rotate, or remove a credential?
- Open Integrations from the app menu to connect Gmail, Discord, Notion, or GitHub, or to add search/Ollama Cloud keys.
- Paste or type the credential once and save; the field shows a “configured” state afterward, never the value itself.
- To rotate a credential, replace it the same way; to remove access, disconnect the integration.
Good to know
- This is separate from Privacy Mode, which controls what happens to your prompts, not your credentials.
- Your license key is handled the same way: the app only ever works from your derived status (trial, active, or expired), never the raw key.
- None of this substitutes for securing your Windows account; the vault keeps your secrets out of app files and exports, not away from someone already signed in to your Windows session.