Your Salesforce data never leaves your browser

OrgSprint is a Chrome extension that adds flow management, an object/record browser, a SOQL query builder, and a debug log viewer directly on top of your own Salesforce org. This page explains exactly what it touches and where that data goes.

Effective August 14, 2026

In short

No server of ours is involved. Every request OrgSprint makes goes straight from your browser to your own Salesforce org — the same org you're already logged into.
Nothing is sold, shared, or analyzed. There are no analytics, no trackers, and no third party who ever sees your data.
What little it remembers stays on your machine. A handful of UI preferences are saved locally in Chrome and never transmitted anywhere.
You are always logged in as yourself. OrgSprint reuses your existing Salesforce session — it never asks for or stores a separate password.

§1

What OrgSprint does

OrgSprint injects a panel into Salesforce pages (and Setup pages) that lets you browse and edit Flows, objects, and records; run SOQL queries with a visual field picker; and view Apex debug logs — all through Salesforce's own REST, Tooling, and Metadata APIs, called directly from your browser using your existing logged-in session.

It does not proxy your traffic, does not run on a server, and has no backend of any kind. If you looked at your browser's network activity while using it, every request would go to *.salesforce.com, *.force.com, or *.salesforce-setup.com — nowhere else.

§2

Permissions, and why each one is needed

Permission	What it's for
cookies	Reads your existing Salesforce session cookie so OrgSprint can call the Salesforce API as you, without a separate login.
host_permissions salesforce.com / force.com / salesforce-setup.com	Lets the panel appear on Salesforce pages and lets it call the Salesforce API for those same domains. OrgSprint has no reason to run anywhere else, and doesn't.
storage	Saves small UI preferences locally — see §3. Nothing here ever leaves your browser.

§3

What's stored, and where

Stored only in chrome.storage.local on your device

OrgSprint saves a short list of interface preferences using Chrome's built-in local storage, which lives only on your machine and is never transmitted:

The floating toggle button's on-screen position
Your recent and favorited Command Palette searches
Your recent SOQL query history
Panel and split-pane sizes you've dragged to resize

None of this is Salesforce record data — it's interface state. OrgSprint does not cache, log, or persist any Flow, object, or record data you view or edit; each query or edit talks to Salesforce live and the response is only held in memory while the panel is open.

§4

Data OrgSprint never collects

OrgSprint does not collect, transmit, or have access to any of the following, as defined by Chrome Web Store's data usage categories:

Health, financial, or authentication information (it reuses your session — it never sees or stores your password)
Browsing history or activity outside Salesforce domains
Location data
Any analytics, usage tracking, or telemetry of any kind

§5

Changes to this policy

If what OrgSprint touches ever changes in a way that affects this policy, this page will be updated and the "Effective" date above will change accordingly.