Fathom Pulse
How it works Pricing FAQ Privacy
Get it on Google Play

Privacy Policy

Last updated: [FILL IN DATE ON PUBLISH]

Fathom Pulse ("Fathom", "the app", "we") is developed by [YOUR NAME / COMPANY NAME]. This policy explains what data the app collects, what it doesn't, and how the third-party services it uses (Google Play Billing and Google AdMob) handle data on our behalf.

The short version: Fathom has no account system and no backend server of its own. The Postman collections, environments, and test results you work with are stored only in local storage on your device. The only network requests Fathom makes on your behalf are the actual HTTP calls your collection defines - sent straight to the URLs you configured, never to us.

1. Data stored locally, on your device only

The app stores the following in local, on-device storage, never transmitted to us:

  • Imported Postman collections and environments (requests, headers, bodies, scripts, variables)
  • Saved run configurations (which preset/settings you last used for a collection)
  • Test run results (latency, throughput, error rates, timestamps)
  • Dashboard pins and their auto-check preferences

Uninstalling the app, or clearing its storage from Android's Settings app, permanently deletes all of this. We have no copy of it anywhere else, because we never received it.

2. Network requests your collection defines

When you run a test, Fathom sends real HTTP(S) requests to whatever URLs your collection specifies - these go directly from your device to the target server you configured, not through any server of ours. You are responsible for those targets being ones you own or are authorized to test; see the Terms of Service.

3. Permissions

PermissionWhy
Internet / network stateTo run the load tests your collections define, and to check your device's network type before sizing a load preset.
Notifications (Android 13+)Only requested the first time you turn on periodic auto-check for a pinned flow - used solely to alert you if that flow starts failing.

Fathom does not request location, contacts, camera, microphone, or storage-wide access.

4. Advertising (AdMob)

Free and Plus both show ads served by Google AdMob - a banner on the dashboard, and an interstitial (full-screen) ad after a test run finishes, at most once every few minutes. AdMob may collect device identifiers (such as your advertising ID), IP address, and general device information to serve and measure ads, and may use this data for ad personalization depending on your region and settings. We do not receive or store this data ourselves - it is handled directly between your device and Google. See Google's ad policy and Google's Privacy Policy for detail. If you're in the EEA, UK, or another region where it applies, Google's own consent form (via Google's User Messaging Platform) appears before any ad is requested, letting you choose whether ads are personalized; declining doesn't block the app, it only affects which ads are shown. Upgrading to Pro removes ads entirely.

5. Payments (Google Play Billing)

The Plus and Pro subscriptions are billed and managed entirely through Google Play. We never see or store your payment card details - Google handles the transaction, and Play's own privacy policy governs that data. We only receive confirmation of which subscription, if any, is active, so the app can unlock the matching features.

6. Remote configuration (Firebase Remote Config)

Certain free-tier limits (how many past test runs are kept, how many flows you can pin to the dashboard) are controlled through Firebase Remote Config, so they can be adjusted without shipping an app update. This uses Firebase's Installations service, which assigns your app install an anonymous installation identifier - handled directly between your device and Google, we never see or store it ourselves. It has no access to, and never transmits, any of your collections, environments, or test results.

7. Slack integration (Pro, optional)

If you're on Pro and choose to configure a Slack Incoming Webhook, Fathom sends test summaries there - directly from your device to the webhook URL you entered, never through a server of ours. Each message includes only the run's label, verdict, and metrics (throughput, latency, error rate) and the weakest endpoint's name - never the actual request URLs, headers, bodies, or scripts in your collection. This is entirely opt-in: nothing is sent to Slack unless you add a webhook URL yourself, and Slack's own privacy policy governs the data once it reaches your workspace. Because the same webhook URL can be shared across several people's devices, each message also carries a sender label - your device's model name by default, or a custom name you choose to set instead - so your team can tell which device a message came from.

8. Backup and restore

Two separate mechanisms, both keep data within your own Google account, never a server of ours. First, Android's own Auto Backup: if it's turned on for your device (Settings > System > Backup), your collections, environments, templates, dashboard pins, past run results, and app settings are periodically copied to a private, hidden area of your Google account and restored automatically on reinstall or a new device signed into the same account - entirely Android's own mechanism, no Google sign-in inside this app, and it's invisible in your normal Drive file list. Second, "Export data"/"Import data" in Settings: a plain file you choose where to save (or open from) yourself, using Android's own file picker - nothing is uploaded anywhere unless you choose to save it somewhere that does, and this file doesn't include past run results, only your collections, environments, templates, dashboard pins, and settings. Neither mechanism includes your subscription status (Google Play restores your subscription on its own). If you've configured a Slack webhook (section 7), that URL is included in Auto Backup's "app settings" like any other setting - restored the same way, within your own Google account, never a server of ours.

9. PDF reports

For a Load Test result on Plus or Pro, "Share result" builds a PDF (verdict, charts, and the device's specs - CPU cores, RAM, network type) on your device and hands it to Android's own share sheet, so you pick whichever app you want to send it through - we never see the report or the device details in it. Below Plus, or for a Sanity Check, the same button shares a plain text summary instead. Nothing happens unless you tap this yourself.

10. What we don't do

  • We don't require an account, login, or any personal identifier to use the app.
  • We don't run our own analytics or crash-reporting SDK that profiles you.
  • We don't sell or share your collection/environment/result data - we never have it to begin with.

11. Children's privacy

Fathom Pulse is a developer/IT tool not directed at children, and we do not knowingly collect data from children under 13 (or the relevant age in your region).

12. Changes to this policy

If this policy changes, we'll update the date at the top of this page. Continued use of the app after a change means you accept the updated policy.

13. Contact

Questions about this policy: contact@fathompulse.app

© 2026 Fathom Pulse. All rights reserved.
How it works FAQ Privacy Policy Terms of Service