Fieldbind
Privacy Policy
Last updated: 2026-08-09
Fieldbind is a browser extension that helps you work with your own Salesforce orgs, with optional Jira and Linear integrations. This policy explains exactly what data the extension touches, where it goes, how long it is kept, and how to delete it.
The short version
- Everything stays on your device. Fieldbind has no backend. The only network endpoints it talks to are Salesforce's APIs — and, if you connect them, Jira's and Linear's — on your behalf.
- No analytics, no telemetry, no tracking. Nothing is collected about you or your usage.
- You can delete all locally stored data at any time from Settings → Privacy & Data → "Clear all cached data".
What data Fieldbind accesses
-
Salesforce session cookies (
sid) — read live via the browser's cookie API to authenticate Salesforce API calls. Session ids are never persisted: they are held in memory only, for as long as the browser itself holds the cookie. - OAuth tokens — only if you explicitly connect Salesforce orgs, Jira, or Linear via OAuth. Tokens are stored encrypted (AES-GCM) in the extension's local storage and can be revoked per connection at any time.
- Org metadata — object describes, flows, permission sets, Apex classes, and similar metadata, fetched to power navigation, editing, and comparison features.
- Record data — the records you open, query, edit, import, or compare.
- Issue-tracker data — issues you search for and link to deployments; comments/status/label updates are sent only to issues you explicitly linked, on events you enabled.
What is stored locally, and for how long
All local storage lives in your browser profile (IndexedDB and extension storage). Nothing is uploaded anywhere.
| Data | Where | Retention |
|---|---|---|
| Metadata caches (describes, object lists, navigator metadata) | IndexedDB | 2–60 minutes TTL, auto-purged |
| Code file bodies (Apex/VF/LWC source) | IndexedDB | 24 hours TTL, auto-purged |
| Recent navigator items (labels + URLs) | IndexedDB | Capped at 100 per org |
| SOQL query history (query text + run stats, never result rows) | IndexedDB / extension storage | Capped (100–500 entries per org) |
| Compare snapshots (record field values from two orgs) | IndexedDB | Default 30 days; pinned snapshots kept until deleted |
| Deploy history (packages, component lists, linked issue keys) | IndexedDB | Capped at 50 deployments |
| Preferences (theme, keybindings, notification templates) | Extension storage | Until you change or reset them |
| OAuth tokens (Salesforce / Jira / Linear, opt-in) | Extension storage, AES-GCM encrypted | Until you disconnect |
| Salesforce session ids | Not stored | In-memory only |
How to delete your data
- Everything at once: Settings → Privacy & Data → "Clear all cached data".
- Connections: Settings → Connections → Disconnect (revokes tokens where the provider supports it).
- Completely: uninstalling the extension removes all of its storage.
What Fieldbind does not do
- No data is sent to any server other than the services you connect.
- No analytics, crash reporting, advertising, or fingerprinting.
- No sale or sharing of data with anyone — there is nothing to share.
Contact
Questions: open an issue on the GitHub repository.