Privacy Policy

Effective date: 28 April 2026

Slipstream is a desktop application that uploads files from external drives to your own cloud storage. This page explains exactly what data Slipstream touches, where it goes, and what we do (and don't do) with it.

1. Who runs Slipstream

Slipstream is developed and operated by Rudra Pratap Singh ("we", "us"). Contact: rudra.ptp.singh@gmail.com.

2. The very short version

• Slipstream runs entirely on your device. We don't operate a server that holds your files.
• The only network destinations the app talks to are your own Google Drive account and Google's OAuth servers for sign-in.
• We don't see your files. We don't see what you upload. We don't have an analytics endpoint, a telemetry server, or any back-end you ever connect to.
• The Apple-notarized installer phones home to Apple's servers (this is a Gatekeeper requirement, not us).
• The in-app updater checks our official release manifest for new versions. The hosting provider sees the request; we do not.

3. Data Slipstream stores locally on your machine

To do its job, Slipstream keeps the following on your device only:

• OAuth tokens for the cloud provider you signed in with — stored in ~/Library/Application Support/com.rp.slipstream/slipstream_tokens.json on macOS. The app reads them locally to make API calls. They never leave your machine.
• Application settings (selected destination folder, OAuth client ID, last-used preferences) in slipstream_settings.json next to the tokens.
• A transfer queue database (slipstream_queue.db) recording each file's source path, size, SHA-256 hash, and transfer state. Used to resume after a crash or drive disconnect. Lives on disk only; deleted when you clear a session.
• A small in-flight buffer of file bytes currently being uploaded, deleted file-by-file as each upload completes.

4. Data Slipstream sends across the network

The only outbound traffic Slipstream generates is:

• OAuth sign-in requests to accounts.google.com and the relevant token endpoints (e.g. oauth2.googleapis.com).
• Drive API calls to www.googleapis.com to list folders, create folders, upload files, rename, and delete.
• Update checks to our release manifest at slipstreamapp.pages.dev. The server sees a generic "User-Agent: tauri-updater" request — no account info attached.

All of these go directly from your machine to the relevant third-party server. Slipstream has no intermediate proxy or relay.

5. Use of Google API services

Slipstream's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• The auth/drive scope is requested only to list folders, create folders, upload files you select, and (when you ask) rename or trash folders. We do not read the contents of files in your Drive.
• We do not transfer any data obtained from Google APIs to a server we operate. There is no Slipstream-side database of your files, file names, hashes, or folder structure.
• We do not use Drive data for advertising. We do not use Drive data to train AI/ML models.
• We do not allow humans to read this data. There is no support tool that lets us inspect any user's content.

6. Data we do not collect

• No analytics or product-usage telemetry.
• No crash reports sent to us. (If you encounter a crash, you can email rudra.ptp.singh@gmail.com.)
• No advertising identifiers, IP-address logs, or fingerprinting.
• No payment data is collected by the current version. (When billing is introduced, this policy will be updated and existing users will be notified.)

7. Revoking access

You can disconnect Slipstream from your Google account at any time via myaccount.google.com/permissions. Doing so invalidates Slipstream's stored token; the next time you open the app you'll be asked to sign in again.

Inside the app, the same effect is available via the Disconnect button on the Google Drive panel. This deletes the locally-stored token immediately.

8. Children

Slipstream is not directed at children under 13 and we do not knowingly collect any data from them.

9. Changes to this policy

Material changes will be reflected by an updated effective date above and we will give existing users reasonable advance notice before any change that affects how user data is handled.

10. Contact

Privacy questions or requests: rudra.ptp.singh@gmail.com.

---

The behaviour described above reflects how the current shipping version of Slipstream works. Feedback on inaccuracies is welcome at rudra.ptp.singh@gmail.com.