@ever-co/legal 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +667 -0
  2. package/dist/content/aup/ever-corporate/en.json +302 -0
  3. package/dist/content/aup/ever-demand/en.html +802 -0
  4. package/dist/content/aup/ever-demand/en.json +339 -0
  5. package/dist/content/aup/ever-rec/en.html +667 -0
  6. package/dist/content/aup/ever-rec/en.json +302 -0
  7. package/dist/content/aup/ever-teams/en.html +667 -0
  8. package/dist/content/aup/ever-teams/en.json +302 -0
  9. package/dist/content/aup/ever-works/en.html +667 -0
  10. package/dist/content/aup/ever-works/en.json +302 -0
  11. package/dist/content/aup/everiq/en.html +726 -0
  12. package/dist/content/aup/everiq/en.json +319 -0
  13. package/dist/content/aup/gauzy/en.html +715 -0
  14. package/dist/content/aup/gauzy/en.json +327 -0
  15. package/dist/content/aup/githands/en.html +864 -0
  16. package/dist/content/aup/githands/en.json +363 -0
  17. package/dist/content/aup/hust/en.html +781 -0
  18. package/dist/content/aup/hust/en.json +347 -0
  19. package/dist/content/aup/traduora/en.html +667 -0
  20. package/dist/content/aup/traduora/en.json +302 -0
  21. package/dist/content/cookies/ever-corporate/en.html +493 -0
  22. package/dist/content/cookies/ever-corporate/en.json +193 -0
  23. package/dist/content/cookies/ever-demand/en.html +633 -0
  24. package/dist/content/cookies/ever-demand/en.json +226 -0
  25. package/dist/content/cookies/ever-rec/en.html +564 -0
  26. package/dist/content/cookies/ever-rec/en.json +206 -0
  27. package/dist/content/cookies/ever-teams/en.html +549 -0
  28. package/dist/content/cookies/ever-teams/en.json +222 -0
  29. package/dist/content/cookies/ever-tech/en.html +469 -0
  30. package/dist/content/cookies/ever-tech/en.json +177 -0
  31. package/dist/content/cookies/ever-works/en.html +618 -0
  32. package/dist/content/cookies/ever-works/en.json +202 -0
  33. package/dist/content/cookies/everiq/en.html +437 -0
  34. package/dist/content/cookies/everiq/en.json +185 -0
  35. package/dist/content/cookies/gauzy/en.html +490 -0
  36. package/dist/content/cookies/gauzy/en.json +206 -0
  37. package/dist/content/cookies/githands/en.html +618 -0
  38. package/dist/content/cookies/githands/en.json +210 -0
  39. package/dist/content/cookies/hust/en.html +622 -0
  40. package/dist/content/cookies/hust/en.json +210 -0
  41. package/dist/content/cookies/traduora/en.html +580 -0
  42. package/dist/content/cookies/traduora/en.json +193 -0
  43. package/dist/content/dpa/ever-demand/en.html +1804 -0
  44. package/dist/content/dpa/ever-demand/en.json +628 -0
  45. package/dist/content/dpa/ever-rec/en.html +1963 -0
  46. package/dist/content/dpa/ever-rec/en.json +652 -0
  47. package/dist/content/dpa/ever-teams/en.html +1918 -0
  48. package/dist/content/dpa/ever-teams/en.json +648 -0
  49. package/dist/content/dpa/ever-works/en.html +1801 -0
  50. package/dist/content/dpa/ever-works/en.json +624 -0
  51. package/dist/content/dpa/gauzy/en.html +1836 -0
  52. package/dist/content/dpa/gauzy/en.json +632 -0
  53. package/dist/content/dpa/githands/en.html +1808 -0
  54. package/dist/content/dpa/githands/en.json +624 -0
  55. package/dist/content/dpa/hust/en.html +1804 -0
  56. package/dist/content/dpa/hust/en.json +632 -0
  57. package/dist/content/privacy/ever-corporate/en.html +1184 -0
  58. package/dist/content/privacy/ever-corporate/en.json +352 -0
  59. package/dist/content/privacy/ever-demand/en.html +1234 -0
  60. package/dist/content/privacy/ever-demand/en.json +364 -0
  61. package/dist/content/privacy/ever-rec/en.html +1250 -0
  62. package/dist/content/privacy/ever-rec/en.json +360 -0
  63. package/dist/content/privacy/ever-teams/en.html +1238 -0
  64. package/dist/content/privacy/ever-teams/en.json +368 -0
  65. package/dist/content/privacy/ever-tech/en.html +1127 -0
  66. package/dist/content/privacy/ever-tech/en.json +352 -0
  67. package/dist/content/privacy/ever-works/en.html +1284 -0
  68. package/dist/content/privacy/ever-works/en.json +364 -0
  69. package/dist/content/privacy/everiq/en.html +1172 -0
  70. package/dist/content/privacy/everiq/en.json +328 -0
  71. package/dist/content/privacy/gauzy/en.html +1281 -0
  72. package/dist/content/privacy/gauzy/en.json +356 -0
  73. package/dist/content/privacy/githands/en.html +1393 -0
  74. package/dist/content/privacy/githands/en.json +380 -0
  75. package/dist/content/privacy/hust/en.html +1359 -0
  76. package/dist/content/privacy/hust/en.json +368 -0
  77. package/dist/content/privacy/traduora/en.html +1146 -0
  78. package/dist/content/privacy/traduora/en.json +336 -0
  79. package/dist/content/refund/ever-works/en.html +595 -0
  80. package/dist/content/refund/ever-works/en.json +336 -0
  81. package/dist/content/refund/gauzy/en.html +595 -0
  82. package/dist/content/refund/gauzy/en.json +336 -0
  83. package/dist/content/refund/githands/en.html +647 -0
  84. package/dist/content/refund/githands/en.json +361 -0
  85. package/dist/content/refund/hust/en.html +595 -0
  86. package/dist/content/refund/hust/en.json +336 -0
  87. package/dist/content/security/ever-demand/en.html +900 -0
  88. package/dist/content/security/ever-demand/en.json +425 -0
  89. package/dist/content/security/ever-rec/en.html +768 -0
  90. package/dist/content/security/ever-rec/en.json +380 -0
  91. package/dist/content/security/ever-teams/en.html +768 -0
  92. package/dist/content/security/ever-teams/en.json +380 -0
  93. package/dist/content/security/ever-works/en.html +768 -0
  94. package/dist/content/security/ever-works/en.json +380 -0
  95. package/dist/content/security/gauzy/en.html +768 -0
  96. package/dist/content/security/gauzy/en.json +380 -0
  97. package/dist/content/security/githands/en.html +876 -0
  98. package/dist/content/security/githands/en.json +421 -0
  99. package/dist/content/security/hust/en.html +768 -0
  100. package/dist/content/security/hust/en.json +380 -0
  101. package/dist/content/subprocessors/ever-corporate/en.html +382 -0
  102. package/dist/content/subprocessors/ever-corporate/en.json +158 -0
  103. package/dist/content/subprocessors/ever-demand/en.html +452 -0
  104. package/dist/content/subprocessors/ever-demand/en.json +154 -0
  105. package/dist/content/subprocessors/ever-rec/en.html +439 -0
  106. package/dist/content/subprocessors/ever-rec/en.json +154 -0
  107. package/dist/content/subprocessors/ever-teams/en.html +477 -0
  108. package/dist/content/subprocessors/ever-teams/en.json +154 -0
  109. package/dist/content/subprocessors/ever-tech/en.html +335 -0
  110. package/dist/content/subprocessors/ever-tech/en.json +141 -0
  111. package/dist/content/subprocessors/ever-works/en.html +551 -0
  112. package/dist/content/subprocessors/ever-works/en.json +154 -0
  113. package/dist/content/subprocessors/everiq/en.html +296 -0
  114. package/dist/content/subprocessors/everiq/en.json +149 -0
  115. package/dist/content/subprocessors/gauzy/en.html +603 -0
  116. package/dist/content/subprocessors/gauzy/en.json +154 -0
  117. package/dist/content/subprocessors/githands/en.html +465 -0
  118. package/dist/content/subprocessors/githands/en.json +154 -0
  119. package/dist/content/subprocessors/hust/en.html +482 -0
  120. package/dist/content/subprocessors/hust/en.json +154 -0
  121. package/dist/content/subprocessors/traduora/en.html +362 -0
  122. package/dist/content/subprocessors/traduora/en.json +154 -0
  123. package/dist/content/tos/ever-corporate/en.html +973 -0
  124. package/dist/content/tos/ever-corporate/en.json +517 -0
  125. package/dist/content/tos/ever-demand/en.html +1598 -0
  126. package/dist/content/tos/ever-demand/en.json +783 -0
  127. package/dist/content/tos/ever-rec/en.html +1524 -0
  128. package/dist/content/tos/ever-rec/en.json +771 -0
  129. package/dist/content/tos/ever-teams/en.html +1551 -0
  130. package/dist/content/tos/ever-teams/en.json +779 -0
  131. package/dist/content/tos/ever-tech/en.html +762 -0
  132. package/dist/content/tos/ever-tech/en.json +421 -0
  133. package/dist/content/tos/ever-works/en.html +1552 -0
  134. package/dist/content/tos/ever-works/en.json +787 -0
  135. package/dist/content/tos/everiq/en.html +781 -0
  136. package/dist/content/tos/everiq/en.json +429 -0
  137. package/dist/content/tos/gauzy/en.html +1440 -0
  138. package/dist/content/tos/gauzy/en.json +755 -0
  139. package/dist/content/tos/githands/en.html +1542 -0
  140. package/dist/content/tos/githands/en.json +779 -0
  141. package/dist/content/tos/hust/en.html +1566 -0
  142. package/dist/content/tos/hust/en.json +787 -0
  143. package/dist/content/tos/traduora/en.html +1238 -0
  144. package/dist/content/tos/traduora/en.json +646 -0
  145. package/dist/index.json +26991 -0
  146. package/package.json +52 -0
@@ -0,0 +1,465 @@
1
+ <h2 id="why-this-page-exists" tabindex="-1">Why this page exists</h2>
2
+ <p>When you use GitHands Cloud to process personal data, we act as your processor and you are the
3
+ controller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that
4
+ you must be told in advance when we intend to add or replace one so that you have a real chance to object.</p>
5
+ <p><strong>This page is that disclosure.</strong> It names every provider we engage to process personal data for the hosted
6
+ Service, says what each one does, where it does it, and what categories of data reach it. Our Data
7
+ Processing Addendum refers to this page, and your general authorisation to the providers listed here is
8
+ given through it.</p>
9
+ <p>It is also written for people who are not our customers — someone whose employer uses the Service, or
10
+ whose data ends up here for some other reason — because &quot;who else can see this&quot; is a fair question and the
11
+ answer should not be available only to the person paying the invoice.</p>
12
+ <h3 id="what-counts-as-a-sub-processor" tabindex="-1">What counts as a sub-processor</h3>
13
+ <p>A <strong>sub-processor</strong> is a third party we engage that processes personal data <strong>on our behalf and on our
14
+ instructions</strong>, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,
15
+ delivers your email, catches our errors or answers your support chat is a sub-processor.</p>
16
+ <p>Three things are not sub-processors, and lumping them in would make this page less accurate rather than
17
+ more complete:</p>
18
+ <ul>
19
+ <li><strong>A provider that never touches personal data.</strong> A design tool or an accounting package we use internally
20
+ is not in the path of your data.</li>
21
+ <li><strong>A company that decides its own purposes.</strong> A payment processor acting on its own regulated obligations
22
+ — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that
23
+ part, not our processor. Those recipients are described in the
24
+ <a href="https://githands.com/privacy">Privacy Policy</a> instead.</li>
25
+ <li><strong>Something we run ourselves.</strong> Our databases, object storage, secrets manager and container platform are
26
+ ours. There is no third party to disclose. The infrastructure section below explains what we operate and
27
+ what genuinely sits in front of it.</li>
28
+ </ul>
29
+ <h3 id="what-this-page-covers" tabindex="-1">What this page covers</h3>
30
+ <p>The <strong>hosted Service we operate</strong> at <a href="https://githands.com">githands.com</a>, for GitHands
31
+ specifically. Other products in our range have their own list on their own domain, and the providers differ
32
+ between them — do not read this one as covering a product it does not name.</p>
33
+ <p><strong>It does not cover a deployment you run yourself.</strong> If you install our open-source software on your own
34
+ infrastructure, you choose your own providers with your own credentials and contracts. The third tier below
35
+ exists to make that distinction visible rather than to blur it.</p>
36
+ <p>This page is versioned and dated. The version in force, and the date it took effect, are at the end.</p>
37
+ <h2 id="how-to-read-this-list" tabindex="-1">How to read this list</h2>
38
+ <p>The three tables that follow mean genuinely different things, and reading them as one flat list will give
39
+ you the wrong answer.</p>
40
+ <p>Here is why the split exists. Our products are open-source at their core and built to be connected to other
41
+ things, so <strong>more than 160 distinct third-party providers appear somewhere in our source code across our
42
+ whole range of products.</strong> The overwhelming majority of them are never engaged by us for anything. Some are
43
+ optional integrations that do nothing until somebody switches them on. Many are reachable only in a
44
+ deployment that somebody else runs, with their own account and their own credentials.</p>
45
+ <p>Publishing all of them as &quot;our sub-processors&quot; would be inaccurate, and inaccurate in the worst direction:
46
+ it would tell you your data reaches companies it never touches, while burying the handful that it actually
47
+ does. <strong>A list that is technically exhaustive and practically misleading is not a disclosure.</strong> So there are
48
+ three tiers.</p>
49
+ <h3 id="tier-1-always-engaged" tabindex="-1">Tier 1 — always engaged</h3>
50
+ <p><strong>If you use the hosted Service, these providers are in the path.</strong> There is no setting that removes them,
51
+ because they are part of how the Service is delivered to everyone.</p>
52
+ <p>This is the real Article 28 sub-processor list. It is the tier to use when you are completing a data
53
+ protection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.
54
+ It is short, and it is short because we run our own infrastructure rather than renting someone else's.</p>
55
+ <h3 id="tier-2-engaged-only-if-you-turn-something-on" tabindex="-1">Tier 2 — engaged only if you turn something on</h3>
56
+ <p><strong>A provider in this tier is engaged only when a specific feature, connector or integration is enabled.</strong>
57
+ Enable nothing and it is never involved, and no data of yours ever reaches it.</p>
58
+ <p>Who does the enabling depends on the feature:</p>
59
+ <ul>
60
+ <li><strong>You or your workspace administrator</strong>, by switching on a feature or connecting an account in the
61
+ product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository
62
+ connector.</li>
63
+ <li><strong>An individual user</strong>, by making a personal choice — signing in with a social account, for example, or
64
+ connecting their own third-party tool.</li>
65
+ </ul>
66
+ <p>The table names the feature or setting that activates each provider, so you can check your own
67
+ configuration against it rather than take our word for the current state. If you want to know precisely
68
+ which of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.</p>
69
+ <p><strong>Enabling one of these is a decision to send your data somewhere else</strong>, and it is yours to make. The
70
+ provider's own terms and privacy notice then apply to what it does, alongside our contract with it.</p>
71
+ <h3 id="tier-3-self-hosted-deployments-only" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
72
+ <p>Several of our products are published as open source and can be run on your own infrastructure. When you do
73
+ that, <strong>you</strong> choose the database, the object storage, the email relay, the AI provider and everything else,
74
+ using your own accounts and your own credentials.</p>
75
+ <p>The providers in this tier are listed <strong>only so that you can see what the software can be pointed at</strong>.
76
+ They are not our sub-processors, and they never become ours by appearing here.</p>
77
+ <p><strong>In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,
78
+ and nothing on this page or in our Data Processing Addendum describes it.</strong> You choose those providers, you
79
+ contract with them, you hold the credentials, and the obligations to your own users are yours alone. The
80
+ open-source section of our <a href="https://githands.com/tos">Terms of Service</a> sets out the same split.</p>
81
+ <p>If you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a
82
+ useful starting inventory. It is not your list — only you know which of these you actually configured.</p>
83
+ <h3 id="what-the-columns-mean" tabindex="-1">What the columns mean</h3>
84
+ <ul>
85
+ <li><strong>Sub-processor</strong> — the contracting legal entity, not the brand on the website. Where a provider has a
86
+ separate European establishment that contracts with us, that is the one named.</li>
87
+ <li><strong>Purpose</strong> — what it does for the Service, specifically enough to be checked. Not &quot;business operations&quot;.</li>
88
+ <li><strong>Location</strong> — where the processing takes place, or the provider's place of establishment where
89
+ processing is distributed. Where that is outside the European Economic Area, the transfer mechanism we
90
+ rely on for it is described in the international transfers section of our
91
+ <a href="https://githands.com/privacy">Privacy Policy</a>, and we will give you a copy of the safeguards for a named
92
+ provider on request.</li>
93
+ <li><strong>Personal data</strong> — the categories that reach that provider. Categories, not a promise about volume: a
94
+ provider that receives email addresses receives them for the people who trigger the feature, not for
95
+ everyone.</li>
96
+ </ul>
97
+ <h3 id="what-is-deliberately-not-in-the-tables" tabindex="-1">What is deliberately not in the tables</h3>
98
+ <ul>
99
+ <li><strong>Infrastructure we operate ourselves.</strong> Our databases, object storage, cache, secrets manager and
100
+ container platform are not sub-processors, because there is no third party involved. The next section
101
+ describes what we run and what really does sit in front of it.</li>
102
+ <li><strong>Recipients that are not processors</strong> — payment providers acting under their own regulatory
103
+ obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those
104
+ are covered in the <a href="https://githands.com/privacy">Privacy Policy</a>.</li>
105
+ <li><strong>Sites you choose to visit</strong> by following a link out of the Service. Once you are on someone else's
106
+ site, their notice applies.</li>
107
+ </ul>
108
+ <h2 id="annex-githands" tabindex="-1">Annex: GitHands</h2>
109
+ <h3 id="tier-1-always-engaged-1" tabindex="-1">Tier 1 — always engaged</h3>
110
+ <table>
111
+ <thead>
112
+ <tr>
113
+ <th>Sub-processor</th>
114
+ <th>Purpose</th>
115
+ <th>Location</th>
116
+ <th>Personal data</th>
117
+ </tr>
118
+ </thead>
119
+ <tbody>
120
+ <tr>
121
+ <td>Cloudflare, Inc.</td>
122
+ <td>Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our infrastructure. Every request to any GitHands hostname passes through it.</td>
123
+ <td>United States, with edge termination worldwide</td>
124
+ <td>IP address, connection and TLS metadata, full request URLs and headers, cookies in transit</td>
125
+ </tr>
126
+ <tr>
127
+ <td>GitHub, Inc.</td>
128
+ <td>Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams.</td>
129
+ <td>United States</td>
130
+ <td>the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity</td>
131
+ </tr>
132
+ <tr>
133
+ <td>Resend, Inc.</td>
134
+ <td>Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back.</td>
135
+ <td>United States</td>
136
+ <td>recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply</td>
137
+ </tr>
138
+ <tr>
139
+ <td>OpenRouter, Inc.</td>
140
+ <td>Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content.</td>
141
+ <td>United States, and onward to the selected model provider</td>
142
+ <td>developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant</td>
143
+ </tr>
144
+ <tr>
145
+ <td>Langfuse GmbH</td>
146
+ <td>Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form.</td>
147
+ <td>Germany</td>
148
+ <td>complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace</td>
149
+ </tr>
150
+ <tr>
151
+ <td>Functional Software, Inc. dba Sentry</td>
152
+ <td>Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report.</td>
153
+ <td>United States</td>
154
+ <td>IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed</td>
155
+ </tr>
156
+ <tr>
157
+ <td>PostHog, Inc.</td>
158
+ <td>Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser.</td>
159
+ <td>United States</td>
160
+ <td>IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer</td>
161
+ </tr>
162
+ <tr>
163
+ <td>Jitsu Labs, Inc.</td>
164
+ <td>A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated.</td>
165
+ <td>United States</td>
166
+ <td>IP address and user agent, in-product events and their properties, user identifier</td>
167
+ </tr>
168
+ <tr>
169
+ <td>Trigger.dev Ltd.</td>
170
+ <td>The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database.</td>
171
+ <td>United Kingdom</td>
172
+ <td>job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data</td>
173
+ </tr>
174
+ <tr>
175
+ <td>ui-avatars.com</td>
176
+ <td>Generated placeholder avatars, used where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser.</td>
177
+ <td>Not published by the provider</td>
178
+ <td>the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent</td>
179
+ </tr>
180
+ </tbody>
181
+ </table>
182
+ <h3 id="tier-2-engaged-only-when-a-feature-integration-or-consent-brings-them-in" tabindex="-1">Tier 2 — engaged only when a feature, integration or consent brings them in</h3>
183
+ <table>
184
+ <thead>
185
+ <tr>
186
+ <th>Sub-processor</th>
187
+ <th>Purpose</th>
188
+ <th>Location</th>
189
+ <th>Personal data</th>
190
+ </tr>
191
+ </thead>
192
+ <tbody>
193
+ <tr>
194
+ <td>Google LLC</td>
195
+ <td>Sign in with Google. Engaged only where an individual chooses that sign-in method.</td>
196
+ <td>United States</td>
197
+ <td>email address, name, profile picture URL, Google account identifier</td>
198
+ </tr>
199
+ <tr>
200
+ <td>LinkedIn Corporation</td>
201
+ <td>Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method.</td>
202
+ <td>United States</td>
203
+ <td>email address, name and profile fields, profile picture URL, LinkedIn member identifier</td>
204
+ </tr>
205
+ <tr>
206
+ <td>HubSpot, Inc.</td>
207
+ <td>Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected.</td>
208
+ <td>United States</td>
209
+ <td>contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection</td>
210
+ </tr>
211
+ <tr>
212
+ <td>Salesforce, Inc.</td>
213
+ <td>Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation.</td>
214
+ <td>United States</td>
215
+ <td>contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection</td>
216
+ </tr>
217
+ <tr>
218
+ <td>Slack Technologies, LLC</td>
219
+ <td>Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace.</td>
220
+ <td>United States</td>
221
+ <td>workspace, channel and user identifiers, the notification content we send</td>
222
+ </tr>
223
+ <tr>
224
+ <td>Stripe, Inc.</td>
225
+ <td>Payments and subscription billing. <strong>Not engaged today</strong> — the hosted Service is free, no payment method is collected and nothing is charged. Stripe becomes a sub-processor only if and when paid plans are switched on, and we will give notice before that happens.</td>
226
+ <td>United States</td>
227
+ <td>billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history</td>
228
+ </tr>
229
+ <tr>
230
+ <td>Twilio SendGrid</td>
231
+ <td>An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service.</td>
232
+ <td>United States</td>
233
+ <td>recipient email address and name, message content, delivery and engagement events</td>
234
+ </tr>
235
+ <tr>
236
+ <td>Sinch Mailgun</td>
237
+ <td>An alternative outbound sending provider. Not configured in the hosted Service.</td>
238
+ <td>United States, with an optional European region</td>
239
+ <td>recipient email address and name, message content, delivery events</td>
240
+ </tr>
241
+ <tr>
242
+ <td>Amazon Web Services, Inc.</td>
243
+ <td>Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service.</td>
244
+ <td>United States</td>
245
+ <td>recipient email address and name, message content, bounce and complaint events</td>
246
+ </tr>
247
+ <tr>
248
+ <td>ActiveCampaign (Postmark)</td>
249
+ <td>An alternative outbound sending provider. Not configured in the hosted Service.</td>
250
+ <td>United States</td>
251
+ <td>recipient email address and name, message content, delivery events</td>
252
+ </tr>
253
+ </tbody>
254
+ </table>
255
+ <h3 id="tier-3-self-hosted-deployments-only-1" tabindex="-1">Tier 3 — self-hosted deployments only</h3>
256
+ <p>If you run GitHands on your own infrastructure, you choose these providers and hold the
257
+ credentials. <strong>We are not a processor for anything in a deployment you run</strong>: we do not receive that data,
258
+ we cannot reach it, and we have no relationship with the providers you configure.</p>
259
+ <table>
260
+ <thead>
261
+ <tr>
262
+ <th>Sub-processor</th>
263
+ <th>Purpose</th>
264
+ <th>Location</th>
265
+ <th>Personal data</th>
266
+ </tr>
267
+ </thead>
268
+ <tbody>
269
+ <tr>
270
+ <td>The email sending provider you choose</td>
271
+ <td>A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay.</td>
272
+ <td>Wherever the provider you choose processes</td>
273
+ <td>recipient email addresses and names, message content, delivery and engagement events</td>
274
+ </tr>
275
+ <tr>
276
+ <td>The model provider you choose</td>
277
+ <td>Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it.</td>
278
+ <td>Wherever the provider you choose processes</td>
279
+ <td>prompts and completions, including any personal data your installation puts in them</td>
280
+ </tr>
281
+ <tr>
282
+ <td>The GitHub or GitLab account you connect</td>
283
+ <td>A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours.</td>
284
+ <td>The platform's own infrastructure</td>
285
+ <td>the queries your installation makes, your own account identity and access token</td>
286
+ </tr>
287
+ <tr>
288
+ <td>The database, object storage and job runtime you choose</td>
289
+ <td>You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself.</td>
290
+ <td>Wherever you deploy them</td>
291
+ <td>all application data in your installation</td>
292
+ </tr>
293
+ <tr>
294
+ <td>The error-monitoring and analytics projects you choose</td>
295
+ <td>Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account.</td>
296
+ <td>Wherever the provider you choose processes</td>
297
+ <td>error reports, console output, product analytics events and the identifiers attached to them</td>
298
+ </tr>
299
+ <tr>
300
+ <td>Mem0 AI, Inc.</td>
301
+ <td>Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own.</td>
302
+ <td>United States</td>
303
+ <td>stored agent conversation memory, which can contain customer and developer details</td>
304
+ </tr>
305
+ </tbody>
306
+ </table>
307
+ <h3 id="data-about-developers-who-are-not-our-users" tabindex="-1">Data about developers who are not our users</h3>
308
+ <p>Most of the personal data in GitHands is about people who never signed up. The sub-processors
309
+ above process that data on our instructions in the same way as any other — but two points follow that a
310
+ plain table does not convey.</p>
311
+ <ul>
312
+ <li><strong>The source platforms are not our sub-processors.</strong> GitHub, GitLab and similar platforms are where the
313
+ data comes from, not parties we send it to. Their terms govern what may be collected from them and what
314
+ may be done with it afterwards.</li>
315
+ <li><strong>We do not sell this data, and no provider above receives it for their own purposes.</strong> Every one of them
316
+ acts on our instructions under a written contract.</li>
317
+ </ul>
318
+ <p>If you are a developer whose data is here and you want it removed, you do not need to work out which
319
+ provider holds what. Use the objection route in the privacy annex and it is handled across all of them.</p>
320
+ <h2 id="hosting-and-infrastructure" tabindex="-1">Hosting and infrastructure</h2>
321
+ <p>The tables above are short for a reason, and the reason is worth stating plainly: <strong>we run our own
322
+ infrastructure.</strong> The Service is not a tenancy in a public cloud account. It runs on physical servers we
323
+ own, in facilities we control, <strong>inside the European Union</strong>, on a virtualisation and container platform we
324
+ operate ourselves.</p>
325
+ <p>The database, the object storage that holds your files, the cache and queue layers, the secrets manager and
326
+ the deployment system are all components we run. <strong>None of them is a third party, so none of them appears
327
+ as a sub-processor</strong> — there is nobody else to disclose. What we do with them is described on our
328
+ <a href="https://githands.com/security">Security page</a>.</p>
329
+ <h3 id="where-processing-actually-happens" tabindex="-1">Where processing actually happens</h3>
330
+ <ul>
331
+ <li><strong>Your data at rest, and the applications that process it, sit on our own hardware in the European
332
+ Union.</strong> That is the primary location for accounts, content, files and the databases behind them.</li>
333
+ <li><strong>Requests reach us through a global content delivery and security network.</strong> Traffic is terminated at
334
+ the edge location nearest to whoever is making the request, which can be anywhere in the world, before
335
+ being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the
336
+ transfer mechanism for it is described in our <a href="https://githands.com/privacy">Privacy Policy</a>.</li>
337
+ <li><strong>Off-site backup copies are held with an external object storage provider</strong>, encrypted by us before they
338
+ leave our network. That provider holds ciphertext and no key, and cannot read what it stores.</li>
339
+ <li><strong>Our source code, build pipeline and container images are hosted with a third-party provider.</strong> That is
340
+ how the Service is built and deployed rather than where your data lives day to day, but it is a genuine
341
+ third party and it is disclosed as one.</li>
342
+ </ul>
343
+ <h3 id="where-a-product-does-something-different" tabindex="-1">Where a product does something different</h3>
344
+ <p>A small number of products use a third-party managed database, managed storage or hosted platform for a
345
+ specific function instead of our own infrastructure. <strong>Where that is the case for GitHands, the
346
+ provider appears in the always-engaged tier above and the product annex says which data goes there.</strong></p>
347
+ <p>We are explicit about this because &quot;self-hosted&quot; is exactly the sort of claim that gets made once and then
348
+ stops being true for one product in the range. If your data for a given feature sits with someone else, the
349
+ table says so.</p>
350
+ <h3 id="the-regions-you-should-design-around" tabindex="-1">The regions you should design around</h3>
351
+ <p>If you are completing a transfer mapping or a data protection impact assessment, the honest summary is:
352
+ <strong>primary processing in the European Union on infrastructure we operate; edge termination worldwide; a
353
+ small number of named providers established outside the European Economic Area, each with its own transfer
354
+ mechanism.</strong> Every one of those providers is in the tables above, and the mechanism for each is in the
355
+ international transfers section of the <a href="https://githands.com/privacy">Privacy Policy</a>.</p>
356
+ <p>If you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which
357
+ modules apply — write to privacy@ever.co and we will send them.</p>
358
+ <h2 id="when-this-list-changes" tabindex="-1">When this list changes</h2>
359
+ <h3 id="the-notice-period" tabindex="-1">The notice period</h3>
360
+ <p><strong>We give at least 30 days' notice before a new or replacement sub-processor starts processing personal
361
+ data for the hosted Service.</strong> The 30 days run from the date the notice is published or sent, whichever
362
+ comes first, and they exist so that your objection right is a real one rather than a formality you learn
363
+ about afterwards.</p>
364
+ <h3 id="how-you-find-out" tabindex="-1">How you find out</h3>
365
+ <ul>
366
+ <li><strong>This page changes first.</strong> It carries the date it took effect and a dated record of what changed, so
367
+ the page itself is the notice.</li>
368
+ <li><strong>By email, if you ask for it.</strong> Write to privacy@ever.co and we will add your address to the
369
+ notification list. We then email you before each change, at the same time the page is updated. <strong>We
370
+ recommend a role address rather than an individual's</strong> — a notice sent to someone who has left your
371
+ organisation has been sent and not received.</li>
372
+ <li><strong>In the product</strong>, for changes that affect a feature you are using, through a notice to workspace
373
+ administrators.</li>
374
+ </ul>
375
+ <h3 id="what-the-notice-tells-you" tabindex="-1">What the notice tells you</h3>
376
+ <p>The provider's legal name, what it will do, where it is established, the categories of personal data it
377
+ will receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,
378
+ and whether it is a new provider or replaces one already on the list. If it replaces one, we say which.</p>
379
+ <h3 id="urgent-replacements" tabindex="-1">Urgent replacements</h3>
380
+ <p>Sometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its
381
+ service, loses the legal basis it relied on, or fails in a way that makes staying with it worse than
382
+ leaving.</p>
383
+ <p><strong>Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with
384
+ the reason we could not wait.</strong> Your right to object is not affected: it simply runs from the notice
385
+ instead of before the change. We do not use this route as a convenience, and a notice sent under it says
386
+ plainly why the normal period was not followed.</p>
387
+ <h3 id="changes-that-do-not-need-notice" tabindex="-1">Changes that do not need notice</h3>
388
+ <p>Removing a provider does not need a notice period — it reduces the number of people handling your data. A
389
+ provider changing its own name, or the group entity that contracts with us changing without a change in
390
+ where or how the processing happens, is recorded here as an administrative update rather than announced as
391
+ a new engagement. <strong>A provider moving its processing to a different country is not administrative, and gets
392
+ the full notice.</strong></p>
393
+ <h3 id="the-record" tabindex="-1">The record</h3>
394
+ <p>We keep the change history for this page so that you can reconstruct who was engaged during a given period.
395
+ That matters if you are updating your own records of processing, refreshing an impact assessment, or
396
+ answering a question about a period in the past. Ask privacy@ever.co if you need the state of the list
397
+ as it stood on a particular date.</p>
398
+ <h2 id="objecting-to-a-sub-processor" tabindex="-1">Objecting to a sub-processor</h2>
399
+ <h3 id="who-can-object" tabindex="-1">Who can object</h3>
400
+ <p>The customer — the organisation or person who contracts with us and acts as controller for the data in the
401
+ workspace. If you are an individual whose data we hold, this is not your route: your rights are in the
402
+ <a href="https://githands.com/privacy">Privacy Policy</a>, and if your data sits in an employer's workspace, your employer
403
+ is the controller and the request goes to them.</p>
404
+ <h3 id="how-to-object" tabindex="-1">How to object</h3>
405
+ <p>Write to <strong>privacy@ever.co</strong> within <strong>30 days</strong> of the notice, and tell us:</p>
406
+ <ul>
407
+ <li>which provider you are objecting to;</li>
408
+ <li><strong>your reasons, on data protection grounds</strong> — a transfer you cannot justify, a conflict with a
409
+ commitment you have given your own users, a regulator's position that applies to you, a documented
410
+ security concern;</li>
411
+ <li>which of your workspaces or environments the objection covers.</li>
412
+ </ul>
413
+ <p><strong>The reasons matter.</strong> This is a right to object on data protection grounds, not a veto over our choice of
414
+ suppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem
415
+ is and we can usually solve it.</p>
416
+ <h3 id="what-we-do-next" tabindex="-1">What we do next</h3>
417
+ <p>We acknowledge your objection within five business days and <strong>respond substantively within 30 days.</strong> In
418
+ between we look for a way to make the objection unnecessary:</p>
419
+ <ul>
420
+ <li><strong>A different provider</strong> for your workspace, where one exists that does the job.</li>
421
+ <li><strong>A different configuration</strong> — narrowing what is sent, changing a region, or turning off the feature
422
+ that needs the provider at all, if you can live without it.</li>
423
+ <li><strong>Excluding your workspace</strong> from the provider, where that is technically possible.</li>
424
+ <li><strong>Additional safeguards or contractual terms</strong> where your concern is about a specific risk rather than
425
+ the provider as a whole.</li>
426
+ </ul>
427
+ <p>Where it is technically possible to hold off, <strong>we will not start using the provider you have objected to
428
+ for your data while the objection is open.</strong> Where it is not possible — because the provider is part of how
429
+ the Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the
430
+ clock run out on you.</p>
431
+ <h3 id="if-we-cannot-resolve-it" tabindex="-1">If we cannot resolve it</h3>
432
+ <p>If we cannot offer you a solution you can accept, <strong>you may terminate the affected subscription by written
433
+ notice, without penalty, and we will refund the fees you have prepaid for the period after termination.</strong>
434
+ That is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.</p>
435
+ <p>Give us notice within 30 days of our final response, and we will keep your data available for export for
436
+ the usual 30-day window described in the <a href="https://githands.com/tos">Terms of Service</a> so that leaving does not
437
+ cost you the data.</p>
438
+ <p>If you are on a free tier there is nothing to refund, and the same route is simply to stop using the
439
+ Service and export your data.</p>
440
+ <h3 id="objecting-to-a-provider-already-on-the-list" tabindex="-1">Objecting to a provider already on the list</h3>
441
+ <p>You do not have to wait for a change. <strong>You can raise a concern about a provider already listed at any
442
+ time</strong>, using the same address and the same process, without the 30-day deadline. The realistic outcome
443
+ differs by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,
444
+ because it is part of how the Service works — and if the answer is going to be no, you will get it as a
445
+ straight no with the reason.</p>
446
+ <h2 id="how-to-reach-us-about-this-list" tabindex="-1">How to reach us about this list</h2>
447
+ <ul>
448
+ <li><strong>Questions about a provider, a request for the safeguards behind a transfer, or a request to join the
449
+ change notification list</strong> — privacy@ever.co.</li>
450
+ <li><strong>An objection to a sub-processor</strong> — privacy@ever.co, as set out above.</li>
451
+ <li><strong>The Data Processing Addendum, a due diligence request, or a security questionnaire</strong> —
452
+ legal@ever.co.</li>
453
+ </ul>
454
+ <p>We are <strong>Ever Technologies LTD</strong>, registered in Bulgaria under company number
455
+ 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our
456
+ own processing and your processor for the data in your workspace. By post, write to the registered office
457
+ and mark the letter for the attention of the privacy team. We correspond in English.</p>
458
+ <p>You may also complain to a data protection supervisory authority. Ours is the
459
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
460
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
461
+ to the authority for the country where you live or work.</p>
462
+ <p>This document is version 1.0.0 of the sub-processor list for
463
+ <a href="https://githands.com">githands.com</a>, in force from 2026-08-02. It lists the providers engaged
464
+ as at that date. Earlier versions, with the dates they applied, are at
465
+ <a href="https://githands.com/subprocessors">https://githands.com/subprocessors</a>.</p>