Privacy Policy
Back to App
The short version MigrateStream does not collect, store, or transmit your personal data, your Salesforce files, or your Google Drive content to any server. Your Salesforce and Google access tokens live only in your browser's memory for the duration of your session. File content moves directly between Salesforce and Google Drive, through your browser only - it never passes through any server we run. We have no database, no user accounts, and no analytics. When you close the tab, everything is gone.

1. What We Do Not Collect

MigrateStream is designed with a zero-data-collection principle. We do not collect:

  • Your name, email address, or any personal information
  • Your Salesforce or Google credentials or passwords - you log in directly on each provider's own login/consent page
  • Your Salesforce or Google access/refresh tokens - held only in your browser's JavaScript memory and never written to any server database or log file
  • The content, names, or metadata of any file you migrate
  • Which Salesforce objects or files you choose to migrate, or the SOQL filters you use to narrow them down
  • Your migration report (the downloadable CSV is built and stays entirely in your browser)
  • Your license key, or how much of your license's data cap you have used
  • Usage analytics, page view counts, or behavioural tracking

2. How Your Salesforce and Google Sessions Work

When you log in with Salesforce or connect Google Drive, the following happens, once per provider:

Step 1 - You log in on the provider's own servers

Clicking "Login with Salesforce" redirects you to Salesforce's own login page (login.salesforce.com or test.salesforce.com). Connecting Google Drive opens a popup on Google's own consent screen. We never see your username or password for either.

Step 2 - The provider issues a one-time code

After you approve access, the provider sends a one-time authorisation code to a small server-side script of ours - one for each provider. This is standard OAuth 2.0 and is how every Salesforce- or Google-connected app works.

Step 3 - A token is handed to your browser and nothing else

Our server exchanges the code for an access token, using a client secret that never leaves the server. The token is passed straight to your browser and nothing else is retained - it is never written to a database, never written to a server log. From that point on, it lives only in your browser tab's JavaScript memory.

Step 4 - Your browser talks to Salesforce and Google directly

Unlike some Salesforce tools, MigrateStream does not proxy your data through our server. Once you hold a token, your browser calls the Salesforce REST API and the Google Drive API directly - listing files, running queries, downloading file bytes, and uploading them to Drive all happen browser-to-provider, with no server of ours in that path at all.

Our server's only job, for either provider, is the one-time code-for-token exchange above. It is never contacted again for the rest of your session.

3. Session Refresh Tokens

MigrateStream requests an OAuth refresh token alongside each access token (Salesforce and Google both) so it can automatically renew your session when it expires. Refresh tokens are handled identically to access tokens - handed to your browser once, held only in JavaScript memory, and never written to a database or server log. When you close your browser tab, both tokens are destroyed permanently.

4. Your License Key and Local Browser Storage

MigrateStream requires a signed license key to start. The key is verified entirely inside your browser (see the Architecture Deep Dive for exactly how) and, once verified, is kept in your browser's own local storage so you do not have to re-enter it on every visit. It is never transmitted to our servers to be checked.

A small local cache in your browser also keeps a lightweight record of files already migrated, purely to speed up resuming an interrupted migration. This is never authoritative - if it is missing, stale, or you switch machines, MigrateStream simply re-asks Google Drive directly and gets the same correct answer. None of this is transmitted to our servers either.

You can clear all of this at any time from within the app (the "Reset local app data" option), or by clearing your browser's site data for this page.

5. Server Logs

Our web hosting provider maintains standard web server access logs that record the IP address, timestamp, and URL of each request. These logs do not contain Salesforce or Google tokens, file content, or file metadata. They are maintained by the hosting provider for security and infrastructure purposes and are subject to their own privacy policy.

6. Cookies

MigrateStream does not set any cookies. Your theme preference (light or dark mode) and your verified license key are stored in your browser's local storage, not a cookie, and contain no personal information beyond what your license itself specifies.

7. Third-Party Services

MigrateStream loads fonts from Google Fonts (fonts.googleapis.com) and, when you use it, Google's own Picker UI (apis.google.com) for choosing a Drive destination folder - both standard, Google-hosted services subject to Google's own privacy policy. Beyond that, MigrateStream's only network activity is calling the Salesforce REST API and the Google Drive API directly with your own tokens, exactly as described in section 2. No analytics platforms or tracking scripts are loaded by MigrateStream.

8. Children's Privacy

MigrateStream is a professional Salesforce administration tool not intended for use by children under 13. We do not knowingly collect any information from children.

9. Changes to This Policy

If we make material changes to this privacy policy, we will update the "Last updated" date at the top of this page. Given that MigrateStream collects no personal data or file content, material changes are unlikely.

10. Contact

If you have questions about this privacy policy or MigrateStream's data practices, contact us at:

Satrang Technologies, Goregaon East, Mumbai, India