Skip to content

Commit 8a9af3e

Browse files
leecalcoteleecalcote
committed
add Privacy Notice and Sub-Processors pages for enhanced user transparency
Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
1 parent 1164195 commit 8a9af3e

2 files changed

Lines changed: 173 additions & 2 deletions

File tree

‎src/sections/Company/Legal/privacy/index.js‎

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,16 @@ const Privacy = () => {
1212
<Container>
1313
<Row>
1414
<Col $xs={12} $sm={12} $lg={12}>
15-
<h1>Layer5 Privacy Notice</h1>
1615
<p>
17-
Welcome to Layer5. We are Layer5, Inc., the company behind the cloud native management platform Meshery, the Layer5 Cloud service, and a vibrant global open-source community. We are committed to protecting your privacy and being transparent about how we handle your personal data.
16+
Welcome to Layer5. We are Layer5, Inc., the company behind the cloud native management platform Meshery, the Layer5 Cloud service, Kanvas, and a vibrant global open-source community. We are committed to protecting your privacy and being transparent about how we handle your personal data.
17+
</p>
18+
<p>
19+
This Privacy Notice explains what personal data we collect when you visit our websites, use our services, or participate in our community. It also describes why we collect it, how we use and protect it, and what rights you have regarding your personal data.
20+
</p>
21+
<p>
22+
For detailed information about the third-party service providers we work with to deliver our services, please see our <a href="/company/legal/sub-processors">Sub-Processors and Service Providers</a> page.
23+
</p><p>
24+
Welcome to Layer5. We are Layer5, Inc., the company behind the cloud native management platform Meshery, the Layer5 Cloud service, Kanvas, and a vibrant global open-source community. We are committed to protecting your privacy and being transparent about how we handle your personal data.
1825
</p>
1926
<p>
2027
This Privacy Notice explains what personal data we collect when you visit our websites, use our services, or participate in our community. It also describes why we collect it, how we use and protect it, and what rights you have regarding your personal data.

‎src/sections/Company/Legal/privacy/sub-processors.js‎

Lines changed: 164 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,164 @@
1+
2+
import React from "react";
3+
import { Container, Row, Col } from "../../../../reusecore/Layout";
4+
import PageHeader from "../../../../reusecore/PageHeader";
5+
6+
import TermsWrapper from "../terms.style";
7+
8+
const subProcessors = () => {
9+
return (
10+
<TermsWrapper>
11+
<PageHeader title="Sub-Processors and Service Providers" path="Terms > Sub-Processors and Service Providers" />
12+
<Container>
13+
<Row>
14+
<Col $xs={12} $sm={12} $lg={12}>
15+
<p>
16+
This document outlines the sub-processors and service providers that Layer5 works with to deliver our services. For comprehensive information about how we collect, use, and protect your personal data, please refer to our <a href="/company/legal/privacy">Privacy Policy</a>.</p>
17+
<p>
18+
To deliver our services effectively, Layer5, Inc. partners with various sub-processors, subsidiaries, and support providers. We may share customer data with the entities listed below to support our platform's functionality and performance.
19+
</p>
20+
21+
<h3>Third-Party Sub-Processors</h3>
22+
<p>We engage the third-party organizations listed below to host customer data and provide specific functionalities within the Layer5 platform. These partners are integral to our service delivery and infrastructure.</p>
23+
24+
<p>The hosting region for a sub-processor will typically align with your account's designated data region. For details on whether a specific sub-processor applies to your account's data region or service plan, please consult the Additional Information column in the list that follows.</p>
25+
<table className="simple">
26+
<caption id="tableCaption_01">Table 1: Sub-Processors, Subsidiaries & Support</caption>
27+
<thead>
28+
<tr>
29+
<th scope="col">Name</th>
30+
<th scope="col">Applicable Services</th>
31+
<th scope="col">Type of Service</th>
32+
<th scope="col">Data Shared</th>
33+
<th scope="col">Sub-Processor Hosting Regions</th>
34+
<th scope="col">Additional Information</th>
35+
</tr>
36+
</thead>
37+
<tbody>
38+
{/* <tr className="section">
39+
<td colSpan="4"><strong>When you browse our websites (layer5.io, getnighthawk.dev, meshery.dev, ) and applications (cloud.layer5.io, kanvas.new)</strong></td>
40+
</tr> */}
41+
<tr>
42+
<td>Amazon Web Services US</td>
43+
<td>Community Discussion Forum</td>
44+
<td>Cloud computing provider</td>
45+
<td>Community Discussion Forum user account data, posts, and comments therein.</td>
46+
<td>United States</td>
47+
<td>All accounts</td>
48+
</tr>
49+
<tr>
50+
<td>Equinix</td>
51+
<td>Layer5 Cloud</td>
52+
<td>Data center provider</td>
53+
<td>Layer5 Cloud user account data, including email addresses and hashed passwords.</td>
54+
<td>United States</td>
55+
<td>All accounts</td>
56+
</tr>
57+
<tr>
58+
<td>GitHub, Inc.</td>
59+
<td>Layer5 Cloud</td>
60+
<td>Code repository and version control</td>
61+
<td>Issue tracking</td>
62+
<td>United States</td>
63+
</tr>
64+
<tr>
65+
<td>Cloudflare, Inc.</td>
66+
<td>Layer5 Cloud, kanvas.new</td>
67+
<td>Content delivery network and DDoS mitigation</td>
68+
<td>Web traffic data</td>
69+
<td>United States</td>
70+
<td>All accounts</td>
71+
</tr>
72+
<tr>
73+
<td>Stripe</td>
74+
<td>Layer5 Cloud, kanvas.new</td>
75+
<td>Payment processing</td>
76+
<td>Payment information</td>
77+
<td>United States</td>
78+
<td>All accounts</td>
79+
</tr>
80+
</tbody>
81+
{/* <tfoot>
82+
<th scope="row">INTERNAL DOC#</th>
83+
<td>#gdpr-10c</td>
84+
<td>#gdpr-2</td>
85+
<td>#gdpr-9b</td>
86+
</tfoot> */}
87+
</table>
88+
<table>
89+
<caption id="tableCaption_02">Table 2: Service Providers Contact Information</caption>
90+
<thead>
91+
<tr>
92+
<th scope="col">Name</th>
93+
<th scope="col">Contact Information</th>
94+
<th scope="col">Data Protection Addendum</th>
95+
</tr>
96+
</thead>
97+
<tbody>
98+
<tr>
99+
<td>Amazon Web Services US</td>
100+
<td><a href="https://aws.amazon.com/contact-us/">https://aws.amazon.com/contact-us/</a></td>
101+
<td><a href="https://aws.amazon.com/compliance/data-privacy-faq/">https://aws.amazon.com/compliance/data-privacy-faq/</a></td>
102+
</tr>
103+
<tr>
104+
<td>Equinix</td>
105+
<td><a href="https://www.equinix.com/contact-us/">https://www.equinix.com/contact-us/</a></td>
106+
<td><a href="https://www.equinix.com/legal/data-protection-addendum/">https://www.equinix.com/legal/data-protection-addendum/</a></td>
107+
</tr>
108+
<tr>
109+
<td>GitHub, Inc.</td>
110+
<td>GitHub Privacy Office<br />
111+
88 Colin P. Kelly Jr. Street<br />
112+
San Francisco, California 94107 USA<br />
113+
dpo@github.com<br />
114+
<a href="https://support.github.com/contact">https://support.github.com/contact</a></td>
115+
<td><a href="https://docs.github.com/en/site-policy/privacy-policies/github-data-protection-addendum">https://docs.github.com/en/site-policy/privacy-policies/github-data-protection-addendum</a></td>
116+
</tr>
117+
<tr>
118+
<td>Cloudflare, Inc.</td>
119+
<td>
120+
101 Townsend Street<br />
121+
San Francisco, CA 94107<br />
122+
USA<br />
123+
Emily Hancock<br />
124+
Data Protection Officer<br />
125+
legal@cloudflare.com<br />
126+
<a href="https://www.cloudflare.com/contact/">https://www.cloudflare.com/contact/</a></td>
127+
<td><a href="https://www.cloudflare.com/terms/cloudflare-dpa/">https://www.cloudflare.com/terms/cloudflare-dpa/</a></td>
128+
</tr>
129+
<tr>
130+
<td>Stripe</td>
131+
<td>Stripe, Inc.<br />
132+
510 Townsend St.<br />
133+
San Francisco, CA 94103<br />
134+
USA<br />
135+
dpo@stripe.com<br />
136+
<a href="https://support.stripe.com/contact">https://support.stripe.com/contact</a></td>
137+
<td><a href="https://stripe.com/privacy">https://stripe.com/privacy</a></td>
138+
</tr>
139+
</tbody>
140+
</table>
141+
<h3>Data Hosting Locations</h3>
142+
<p>To provide our users with transparency about where their data is stored, Layer5 has defined primary hosting locations for its services. Data is stored in a specific region in the United States based on the service used.</p>
143+
144+
<p>Layer5 Cloud Account Data (cloud.layer5.io): All user account data is hosted in the United States at an Equinix datacenter in Dallas, Texas.</p>
145+
146+
<p>Layer5 Discussion Forum Data (discuss.layer5.io): All forum data is hosted in the United States within the Amazon Web Services (AWS) US East region.</p>
147+
148+
<p>Please note that in some cases, certain third-party services (sub-processors) that we use to deliver our services may operate and process data in additional regions.</p>
149+
<p>
150+
151+
<h3>Can I change my data region?</h3>
152+
153+
<p>Since data is physically stored in a predetermined location, once an account begins storing data it cannot be moved. If you want to switch to a different region, contact your local partner or Enterprise account manager to create a new account hosted in the region of your choice going forward.</p>
154+
155+
<i>Last Updated: Sept 25th, 2025</i>
156+
</p>
157+
</Col>
158+
</Row>
159+
</Container>
160+
</TermsWrapper>
161+
);
162+
};
163+
164+
export default subProcessors;

0 commit comments

Comments
 (0)