EMSat Pty Ltd shares personal data with the third parties below to provide our service. Most of them process it on our behalf, under contract and only on our instructions. One — Microsoft — receives it as an independent controller, which its entry explains.
We keep this page current; it is referenced from our Privacy Policy.
Current subprocessors
Open any provider for what it receives, where it sits, and what it sets in your browser.
- Data involved
- Whatever contact details you include when you raise a support request.
- Location
- United States.
- Transfer basis
- Confirmation in progress.
- Cookies
None. We send support requests to Airtable from our own servers.
- Their terms
- Airtable Data Processing Addendum
- Data involved
- Account records, usage data, billing metadata.
- Location
- Australia (ap-southeast-2).Some services run in the United States.
- Transfer basis
- Standard Contractual Clauses, incorporated automatically by the AWS Service Terms.
- Cookies
None. AWS holds data on our servers and sets nothing in your browser.
- Their terms
- AWS Data Processing Addendum
- Data involved
- IP addresses, access logs, and single sign-on identities on gated hosts.
- Location
- Cloudflare's global edge network.
- Transfer basis
- Standard Contractual Clauses, part of the Cloudflare Self-Serve Subscription Agreement.
- Cookies
__cf_bmBot management. Around 30 minutes.cf_clearanceRecords that a challenge was passed. Session-scoped.Strictly necessary: the site cannot tell you from a bot without them.
- Their terms
- Cloudflare Customer DPA
- Data involved
- Email, display name, and the identifiers and metadata tied to how you sign in. If you sign in with Google or Microsoft rather than a password, that provider tells us your email address and name, and knows that you signed in to EMSat. It acts on its own behalf there, not ours, under its own privacy terms.
- Location
- United States and other Google regions.
- Transfer basis
- Standard Contractual Clauses, incorporated by the Firebase Data Processing Terms.
- Cookies
None. Your signed-in session is kept in your browser's local storage instead.
- Their terms
- Firebase Data Processing Terms
- Data involved
- Pages visited, referrer, browser and device type, and approximate location derived from your IP address.
- Location
- United States.
- Transfer basis
- Standard Contractual Clauses, incorporated by the Google Ads Data Processing Terms.
- Cookies
_gaDistinguishes one visitor from another. Up to 2 years._gidDistinguishes one visit from another. 24 hours.Set only if you accept analytics cookies. Change your mind any time through .
- Their terms
- Google Ads Data Processing Terms
- Data involved
- IP addresses on tile requests. Your browser calls Mapbox directly as you pan the map.
- Location
- United States.
- Transfer basis
- Standard Contractual Clauses, incorporated by the Mapbox Terms of Service.
- Cookies
None on our site.
- Their terms
- Mapbox Data Processing Addendum
- Their role
- Microsoft is an independent controller, not our processor. It decides its own purposes for this data and handles it under the Microsoft Privacy Statement rather than a contract with us, and it may use the data for its own purposes including advertising.
- Data involved
- Clicks, scrolls, cursor movement, pages visited, browser and device type, and approximate location derived from your IP address, recorded as session replays and aggregated into heatmaps. Text you type into form fields and drop-downs is never captured. In the application we run Clarity in its strict masking mode, so page text — including site names and estimation data — is masked in your browser and never reaches Microsoft. Recordings are available to us for 30 days.
- Location
- United States and other Microsoft regions.Stored in the Microsoft Azure cloud.
- Transfer basis
- No data processing agreement. Microsoft receives this data as a controller in its own right.
- Cookies
_clckKeeps a Clarity user ID for this site. First-party._clskJoins several page views into one recording. First-party.CLIDIdentifies when Clarity first saw this browser on any site using Clarity. Third-party.MUIDIdentifies a browser across Microsoft sites. Microsoft uses it for advertising, analytics and operational purposes. Third-party.ANONCHKFlags whether MUID is passed to an advertising cookie. Clarity always sets it to 0. Third-party.MRFlags whether MUID should be refreshed. Third-party.SMSynchronises MUID across Microsoft domains. Third-party.SRM_BMicrosoft advertising and analytics identifier, set alongside MUID. Third-party.Set only if you accept session-recording cookies. Change your mind any time through .
- Their terms
- Microsoft Privacy Statement
- Data involved
- Account identifiers and request context attached to error reports. In the application, Sentry may also record a short replay of the session around an error, with all text masked before it leaves your browser.
- Location
- United States.
- Transfer basis
- Standard Contractual Clauses, incorporated by the Sentry Data Processing Addendum (v5.1.0).
- Cookies
None.
- Their terms
- Sentry Data Processing Addendum
- Data involved
- Name, email and billing address. Card details go to Stripe directly and are never held by us.
- Location
- United States.
- Transfer basis
- Standard Contractual Clauses, part of the Stripe Services Agreement.
- Cookies
None on our site. Checkout runs on Stripe's own pages, where Stripe's cookie notice applies.
- Their terms
- Stripe Data Processing Agreement
Changes to this list
We update this page when we add or remove a provider. If you would like to be notified of changes, or you have a question about any provider listed here, contact us at privacy@emsat.com.
To report a security concern, contact security@emsat.com.