Every network call, what it sends and how to turn it off
The tools make no network calls. The app makes three, all to offpaste.com. None of them sends what you paste. Here is each call, before you install.
The three calls
The app sends each call from its Rust code, only to the hosts below. It refuses any other host, also when a config file names one.
Update checkOn by default
- Sent to
updates.offpaste.com. Updates download only fromdownloads.offpaste.com.- When
- At most once in 24 hours, at start and while the app is open. “Check now” in Settings checks at once.
- What it sends
- The app version, the OS, the CPU architecture and the update channel (stable or beta).
first_this_week=1on the first check of each week. We count these flags to know how many installs are active each week. A lost response can count an install twice, so the count is approximate.
- What it never sends
- No ID, and nothing that you paste.
- How to turn it off
- Settings → Updates, or
updates.check = falseinsettings.toml. The app asks before it installs an update, and it checks the signature of each update.
AnalyticsOff until you say yes
- Sent to
events.offpaste.com- When
- Once a day. Offline days wait up to 30 days, then the app deletes them.
- What it sends
- How many times you opened each tool that day, by tool ID.
- A random install ID (UUIDv4). The app makes it when you turn analytics on. Nothing links it to you or to your machine, but it is the same ID in each batch, so we do not call it anonymous.
- What it never sends
- No input, output, options, snippet names or file paths.
- How to turn it off
- The first-launch prompt, or Settings → Privacy. When you turn analytics off, the app deletes the ID, the counts that wait, and the ID in each row of the sent log.
Crash reportsOff until you say yes
- Sent to
events.offpaste.com, which forwards the report to Sentry.- When
- When a tool fails, the error bar offers “Send crash report”. When the app itself crashes, it sends the report at the next start. A report that waits more than 30 days is deleted.
- What it sends
- The stack as raw memory addresses, plus the name, the debug ID and the size of each loaded module. Sentry turns them into function names.
- The file and line in the OffPaste source where the crash happened, the app version, the OS and the CPU architecture.
- For an error in the app window: the error type and the file, line and column in the OffPaste code. At most 5 reports per session.
- What it never sends
- No error message, no input, no ID, no computer name, no full file paths, no memory dump and no history of what you did before the crash. Each of these can hold what you pasted.
- How to turn it off
- The first-launch prompt, or Settings → Privacy. It has its own switch, apart from analytics.
Read what was sent
The app keeps a log of each analytics batch and each crash report, exactly as sent. Open it from Settings → Privacy → “Show sent log”. The app keeps each row for 90 days.
When you turn analytics off, each row shows “ID removed” in place of the install ID.
What stays in memory
Input and output stay in memory only, also the last input of each tool. Nothing you paste reaches the disk unless you save it.
The app writes to disk only your snippets, your settings, the options that each tool remembers, and the files that you save. A remembered option is never free text: the app keeps the flags of a regex, not its pattern.
Logs never hold input, output or file contents. The app never reads the clipboard. It only writes to it when you copy the output.
Two things are outside our control: the swap file of your OS, and any clipboard manager that you run.
Spell check and writing tools are off
The editors and each text field in the app turn off spell check, autocorrect, autocomplete and writing suggestions. Thus macOS Writing Tools and text suggestions do not read what you paste.
Only official builds make calls
Our release workflow adds the hosts and the updater key when it builds the app. Any other build, such as a build from source or a fork, makes no network calls. Its settings show “Updates are not available in this build”.
The hosts and the updater public key are public. A fork that builds with our updater key and our official-build flag gets our updates, and its update checks count as our installs.
Who sees your IP address
Cloudflare runs the three hosts, and GitHub hosts the release page. Both see the IP address of each call and each download, as for any website.
Our code on Cloudflare removes the IP address before it counts a check, stores a batch or forwards a report. It keeps no IP address and writes no request logs.