WarmPath
log in

Privacy policy

Last updated 5 October 2026 · applies to warmpath-ys3g.onrender.com and any WarmPath workspace run from this code.

WarmPath finds warm introductions: it works out who in your team actually knows the person you need to reach, from the pattern of your email and calendar — who you corresponded with, and when. This page says exactly what WarmPath reads, what it keeps, who can see it, and how to remove it. Nothing is hidden from you: the Your data page shows the same facts live for your own account.

What WarmPath reads

What WarmPath stores

Never stored: message text, attachments, subject lines, or anything from a message beyond who, when and whether it was a reply. Contacts at personal email providers (Gmail, Yahoo, iCloud, Outlook.com and similar) are dropped by default, as are newsletters, notifications and other automated senders.

Who can see it

Google API Services — limited use

WarmPath's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to compute relationship scores and routes inside your workspace. It is never sold, never used for advertising, never used to train models, and never transferred to third parties except as needed to run the service (hosting) or as required by law.

Where it lives, and for how long

WarmPath runs on Render in the United States. Data is kept while your account exists. Monthly counts older than the lookback window you choose (two years by default) are dropped on each refresh. When you delete your account, everything tied to it — people, counts, scores, tokens, intro requests — is deleted immediately and is not recoverable.

Your controls

Contact

Questions or requests about your data: cael.tackett@uplabs.us.