Mailspring
Mailspring shares data primarily with service providers to operate the platform.
Overview
Sells your data No
We will not share any PII that we have collected from or regarding you except as described below:
Shares with third parties Yes
Tracking levelModerate
Your Privacy Controls
Global Privacy Control (GPC)
Browser signal to opt out of data selling
UnknownDo Not Track (DNT)
Browser signal to opt out of tracking
UnknownHow Long Data Is Kept
Not clearly disclosed
Where Data Goes
Sent outside EU/EEAYes
US
Who Gets Your Data
Other Third Parties
Not clearly specified who receives your data
Other Third Parties
Not clearly specified who receives your data
Other Third Parties
Not clearly specified who receives your data
Other Third Parties
Not clearly specified who receives your data
Other Third Parties
Not clearly specified who receives your data
Tracking & Analytics
MixpanelGoogle Analytics
What Data Is Collected
26 types| Data Type | Category | Why |
|---|---|---|
| Name | Identity | Collected when a user creates an account to identify them. If you create an Account, we'll collect certain information that can be used to identify you (" PII"), such as your name and email address. |
| Email Address (Account) | Identity | Collected when a user creates an account to identify them and for communication. If you create an Account, we'll collect certain information that can be used to identify you (" PII"), such as your name and email address. |
| Credit Card Information | Financial | Collected for payment processing when using services that require it. We may also collect certain information that is not PII, because it cannot be used by itself to identify you, such as credit card information. |
| Linked Email Account Addresses | Identity | Addresses of email accounts linked by the user to the app, associated with Mailspring ID for features like read receipts. The addresses of the email accounts you link (eg: "bengotow@getmailspring.com") will be sent to our servers and associated with your Mailspring ID to enable application features such as read receipts. |
| Email Credentials (Passwords, Refresh Tokens) | Identity | Stored locally on the user's computer, but can be sent to servers with explicit opt-in for cloud sync features. We take the security of your email credentials (passwords, refresh tokens, etc.) seriously. This information is stored securely in your computer's keychain or keyring, and is never sent to our servers for any reason without your explicit consent. |
| Mail Data (Messages, Headers, Attachments) | Communications | Transferred off the user's computer only if 'thread sharing' or cloud sync features are explicitly enabled. Mailspring performs email sync locally on your computer and does not transfer mail data (messages, headers, attachments, etc.) or metadata derived from your mail data off of your computer unless you explicitly enable "thread sharing" features |
| Mail Metadata | Communications | Derived from mail data and transferred off the user's computer only if 'thread sharing' or cloud sync features are explicitly enabled. Mailspring performs email sync locally on your computer and does not transfer mail data (messages, headers, attachments, etc.) or metadata derived from your mail data off of your computer unless you explicitly enable "thread sharing" features |
| Calendar Contents | Communications | Scanned and cached if the user opts into cloud sync features. By approving this access, you're permitting Foundry 376, LLC to scan the contents of the applicable email inbox, calendar, and contact book, cache the contents as deemed necessary until you explicitly revoke our access |
| Contact Book Contents | Communications | Scanned and cached if the user opts into cloud sync features. By approving this access, you're permitting Foundry 376, LLC to scan the contents of the applicable email inbox, calendar, and contact book, cache the contents as deemed necessary until you explicitly revoke our access |
| Email Addresses of People You Email | Identity | Sent to servers when an optional feature to display expanded contact details is enabled. Enabling this feature sends the email address of the person(s) in the messages you view to our servers so that we can provide expanded contact details. |
| Cookies | Technical | Small text files placed on the device to identify login status, monitor usage, and customize services. "Cookies" are small text files that are placed on your device by a Web server when you access our Services. We may use both session Cookies and persistent Cookies to identify that you've logged in to the Services |
| Web Beacons (Pixel Tags, Clear GIFs) | Technical | Tiny graphics used to deliver/communicate with Cookies, track service performance, monitor visitors, and advertising effectiveness. "Web Beacons" (also known as Web bugs, pixel tags or clear GIFs) are tiny graphics with a unique identifier that may be included on our Services for several purposes, including to deliver or communicate with Cookies |
| Internet Protocol (IP) Address | Technical | Automatically recorded as part of Log Data to administer and improve services. Log Data may include information such as a User's Internet Protocol (IP) address |
| Browser Type | Technical | Automatically recorded as part of Log Data to administer and improve services. Log Data may include information such as ... browser type |
| Operating System | Technical | Automatically recorded as part of Log Data to administer and improve services. Log Data may include information such as ... operating system |
| Referring Web Page | Technical | Automatically recorded as part of Log Data, indicating the page visited before accessing services. Log Data may include information such as ... the web page that a User was visiting before accessing our Services |
| Pages or Features Browsed | Behavioral | Automatically recorded as part of Log Data to understand user interaction with services. Log Data may include information such as ... the pages or features of our Services to which a User browsed |
| Time Spent on Pages or Features | Behavioral | Automatically recorded as part of Log Data to understand user engagement with services. Log Data may include information such as ... the time spent on those pages or features |
| Search Terms | Behavioral | Automatically recorded as part of Log Data to understand user interests and improve services. Log Data may include information such as ... search terms |
| Clicked Links | Behavioral | Automatically recorded as part of Log Data to understand user interaction and navigation within services. Log Data may include information such as ... the links on our Services that a User clicked on |
| Other Usage Statistics | Behavioral | General statistics about how a person uses the services, recorded automatically. Log Data may include information such as ... and other statistics. |
| Mobile Device Identifier | Technical | Collected from mobile devices when using services to identify the device. We may collect certain information that your mobile device sends when you use our Services, like a device identifier |
| Mobile Device User Settings | Technical | Collected from mobile devices when using services. We may collect certain information that your mobile device sends when you use our Services, like a device identifier, user settings and the operating system of your device |
| Mobile Device Operating System | Technical | Collected from mobile devices when using services. We may collect certain information that your mobile device sends when you use our Services, like a device identifier, user settings and the operating system of your device |
| Mobile Device Usage Information | Behavioral | Information about how the user interacts with services on their mobile device. as well as information about your use of our Services. |
| Location Information | Technical | Collected and stored if the user permits, used to improve and personalize services. In some cases we collect and store information about where you are located, if you permit us to do so. |
Why Your Data Is Used
Core Service
- provide servicesThis explicitly states that email account addresses are used to enable specific features of the application, which is a core part of providing the service.The addresses of the email accounts you link (eg: "bengotow@getmailspring.com") will be sent to our servers and associated with your Mailspring ID to enable application features such as read receipts.
- provide servicesThis explicitly states that user-configured transmissions of mail data are used solely for the purpose of providing the service.If you do enable user-configured transmissions of your mail data to us, we do not use it for any purpose other than providing the service to you.
Deceptive Practices
Forced Consent
Roach Motel