You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 587f559
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,7 +199,7 @@ For example:
199
199
-`from WZIAtMx4LLhzit02`
200
200
201
201
> [!IMPORTANT]
202
-
> This is a best-effort action, and if some of the probes are no longer online, they will be missing from the new results. Additionally, as measurements expire (lifetime depends on user type), you should not hard-code measurement IDs, as new tests will break after a measurement expires.
202
+
> This is a best-effort action, and if some probes are no longer online, they will be missing from the new results. Additionally, as measurements expire after up to six months, you should not hard-code measurement IDs, as new tests will break after a measurement expires.
203
203
204
204
You can obtain the measurement ID through the "share" functionality. For example, use `--share` in the CLI, find the "Share URL" section at the bottom of the web results or receive it by calling the API directly.
205
205
@@ -330,6 +330,8 @@ Here are some tips:
330
330
331
331
### Things to keep in mind
332
332
333
+
Measurement parameters and results are public, may be accessed by anyone with the measurement ID, and may be published or made discoverable. Do not include credentials or other confidential information in measurement targets, options, or headers, and avoid including unnecessary personal data. Measurements are typically available for up to six months.
334
+
333
335
#### Probes share no UUIDs
334
336
Our probes don't expose unique IDs that you can use to target them explicitly. Instead, we recommend fine-tuning the probe selection by using and combining filters or specifying IDs from previous measurements, as described in the best practice section above.
Copy file name to clipboardExpand all lines: docs/terms/Privacy Policy.md
+20-16Lines changed: 20 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Privacy Policy
2
2
3
-
*Effective date: November 16, 2024*
3
+
*Effective date: September 16, 2026*
4
4
5
-
Volentio JSD Limited ("us", "we", or "our"), a company registered in England and Wales, operates the global.io ("Website") and the Globalping Service (collectively, the Services).
5
+
Volentio JSD Limited ("us", "we", or "our"), a company registered in England and Wales, operates the Globalping service under the globalping.io domain and the hosted Globalping Model Context Protocol (MCP) service at mcp.globalping.dev (collectively, the "Services"). This policy applies whether you access the Services directly or through ChatGPT, Codex, Claude, or another MCP client or integration.
6
6
7
7
When we collect, use and process personal data we are subject to the provisions of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. We are also subject to the EU General Data Protection Regulation (EU GDPR) in relation to personal data we collect, use and process in the European Economic Area (EEA).
8
8
@@ -20,23 +20,21 @@ Our Service may contain links to other sites that are not operated by us. If you
20
20
21
21
3.**we, us and our:** refers to Volentio JSD Limited and its directors;
22
22
23
-
4.**you and your:** refers to the person who is accessing our Website or Globalping and whose data is processed;
23
+
4.**you and your:** refers to the person who is accessing our Services and whose data is processed;
24
24
25
25
## 2. Information Collection
26
26
27
-
1. We collect the following types of information depending on which one of our Services you use or access:
27
+
1. We collect the following types of information depending on which Services you use or access:
28
28
29
-
1.2.1.1 Usage Data Globalping
29
+
1.**Service Usage Data:** We may collect information about how the Services are accessed and used. This may include your IP address, browser or client type and version, referrer domain, URLs visited on globalping.io, timestamps, unique device or request identifiers, and other diagnostic, security, and network data.
30
30
31
-
1. We may collect information how the Service is accessed and used ("Usage Data").
31
+
2.**Account and Contact Data:** When you create an account, we collect information such as your username, email address, and authentication credentials. We may also collect your email address and other information you provide when you contact us.
32
32
33
-
2. (ii) This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, referrer data (limited to domain), the URLs of our Service that you visit (limited to the globalping.io domain), the time and date of your visit, unique device identifiers and other diagnostic data. We never associate any gathered data with specific users or try to track their usage at any point and in any way.
33
+
3.**Measurement Data:** We collect the parameters submitted for a measurement and the results generated by it. These may include targets, requested locations, measurement options, custom HTTP headers, probe information, network paths, DNS responses, and other measurement output. Measurement Data is public by design, may be accessed by anyone with the measurement ID, and may be published or made discoverable. Do not include credentials or confidential information in Measurement Data, and avoid including unnecessary personal data.
34
34
35
-
2.Usage Data Website
35
+
4.**MCP Usage Data:** When you use our hosted MCP service, we may record tool names, information submitted to and returned by MCP tools (including Measurement Data), timestamps, duration, errors, MCP client name and version, User-Agent, request and network metadata, an internal session identifier, a generic authentication category, and the OAuth client ID where applicable. Request metadata may include IP, country, request, or session-related identifiers supplied by your client or our infrastructure. If you use the `get_more_tools` tool, we may also collect the missing-capability description submitted to that tool.
36
36
37
-
1. Registration information: We collect information such as your name and contact data, including username and email address, and credentials such as your password, during account creation.
38
-
39
-
2. Contact data: we may collect your email address when you contact us in relation to your use of the Services.
37
+
2. We exclude the authentication credentials provided in the transport-level MCP `Authorization` header from MCP Usage Data. We do not generally detect or remove secrets included in ordinary tool inputs, measurement targets, query values, custom headers, or results. You must not submit credentials or other confidential values in those fields.
40
38
41
39
## 3. Use of Data
42
40
@@ -48,15 +46,21 @@ Our Service may contain links to other sites that are not operated by us. If you
48
46
4. monitor the usage of our Services,
49
47
5. detect, prevent, and address technical issues.
50
48
51
-
2. Please note that our Services is not intended for use by children, and we do not knowingly collect or use personal information relating to children. If you are a parent or guardian and you are aware that your children have provided us with personal data, please contact us. If we become aware that we have collected personal data from children without verification of parental consent, we take steps to remove that information from our servers.
49
+
2. We use MCP Usage Data to understand which MCP tools and clients are used, diagnose failed or slow calls, improve tool descriptions, behavior, and reliability, understand requested capabilities, and protect and operate the Services. We do not use MCP Usage Data for advertising or sell it.
50
+
51
+
3. Please note that our Services are not intended for use by children, and we do not knowingly collect or use personal information relating to children. If you are a parent or guardian and you are aware that your children have provided us with personal data, please contact us. If we become aware that we have collected personal data from children without verification of parental consent, we take steps to remove that information from our servers.
52
52
53
53
## 4. Retention of Data
54
54
55
55
1. We will retain your personal data only for as long as is necessary for the purposes set out in this Privacy Policy.
56
56
57
57
2. We will retain and use your personal data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.
58
58
59
-
3. We will also retain non-aggregated Usage Data for internal analysis purposes, for example, to detect abuse of our Services. Non-aggregated Usage Data is retained for a shorter period of time until it is analyzed and deleted, except when this data is used to strengthen the security or to improve the functionality of our Service, or we are legally obligated to retain this data for longer time periods.
59
+
3. Measurement Data is public. We retain it to provide results and to operate and protect the Services. The current standard period for which measurements are available is stated in our [API documentation](https://globalping.io/docs/api.globalping.io). We may retain data longer where necessary to investigate abuse, resolve disputes, or comply with legal obligations. Anyone who accesses public Measurement Data may store a copy independently, potentially indefinitely; we cannot control or delete those copies. We may retain measurement-derived operational or aggregated statistics for longer; these do not contain MCP client or session details.
60
+
61
+
4. We retain MCP Usage Data for up to 60 days, unless a longer period is needed for a specific security investigation or legal obligation.
62
+
63
+
5. We retain other non-aggregated Usage Data only for as long as needed for operational analysis, abuse prevention, security, and service improvement, unless we are legally required to keep it longer.
60
64
61
65
## 5. Transfer of Data
62
66
@@ -89,15 +93,15 @@ For further information on cookies, when we will request your consent before pla
89
93
5. To request the deletion of personal data held about you;
90
94
6. You have the right to data portability for the information you provide to us. You can request to obtain a copy of your personal data in a commonly used electronic format so that you can manage and move it.
91
95
92
-
3.Please note that we may ask you to verify your identity before responding to such requests.
96
+
3.We may ask you to verify your identity and provide information that helps us locate the relevant personal data before responding to a request.
93
97
94
98
## 9. Sharing your data with others
95
99
96
-
1. We may employ third party companies and individuals to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services or to assist us in analysing how our Service is used.
100
+
1. We may employ third party companies and individuals, including hosting, content delivery, analytics, and observability providers, to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services or to assist us in analysing how our Service is used.
97
101
98
102
2. These third parties have access to your personal data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.
99
103
100
-
3. Content Delivery: We use third-party Service Providers to serve all of our traffic under the domain globalping.io. This means all of these providers have access to your IP address and other information sent by your web browser. This information is used for analytics and security purposes. Neither we nor our providers track any individual user.
104
+
3.**Content Delivery:** We use third-party Service Providers to serve traffic under the globalping.io domain. These providers have access to your IP address and other information sent by your browser or client. This information is used for service delivery, analytics, and security purposes.
0 commit comments