What “local-first” means here
Request tabs, drafts, history, collections, settings and environments are designed to live in the Chrome browser profile on your device. You can start using the extension without creating a TruAPI account.
What still travels over the network
An API client must send the request you create to the endpoint you choose. The destination API, its infrastructure and network intermediaries may process that request according to their own policies. TruAPI's local-first claim describes the surrounding workspace; it does not mean an HTTP request can reach a remote server without network transmission.
How authentication values are treated
Authentication values are excluded from automatic tab, draft and history persistence. Developers should still use least-privilege credentials, rotate exposed secrets and avoid pasting production tokens into untrusted endpoints.
A privacy checklist for API tools
- Is an account required before the tool can be used?
- Where are requests, collections, environments and history stored?
- Are authentication values automatically persisted?
- Does the tool add developer-operated analytics around API payloads?
- Can you review a public privacy policy and Chrome Web Store disclosure?
- Do you understand the privacy terms of the API endpoint itself?