@ever-co/legal 0.1.1 → 0.2.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 (162) hide show
  1. package/dist/content/aup/ever-async/en.html +778 -0
  2. package/dist/content/aup/ever-async/en.json +343 -0
  3. package/dist/content/aup/ever-corporate/en.html +2 -2
  4. package/dist/content/aup/ever-corporate/en.json +3 -3
  5. package/dist/content/aup/ever-demand/en.html +2 -2
  6. package/dist/content/aup/ever-demand/en.json +3 -3
  7. package/dist/content/aup/ever-rec/en.html +2 -2
  8. package/dist/content/aup/ever-rec/en.json +3 -3
  9. package/dist/content/aup/ever-teams/en.html +2 -2
  10. package/dist/content/aup/ever-teams/en.json +3 -3
  11. package/dist/content/aup/ever-works/en.html +2 -2
  12. package/dist/content/aup/ever-works/en.json +3 -3
  13. package/dist/content/aup/everiq/en.html +2 -2
  14. package/dist/content/aup/everiq/en.json +3 -3
  15. package/dist/content/aup/gauzy/en.html +2 -2
  16. package/dist/content/aup/gauzy/en.json +3 -3
  17. package/dist/content/aup/githands/en.html +2 -2
  18. package/dist/content/aup/githands/en.json +3 -3
  19. package/dist/content/aup/hust/en.html +11 -2
  20. package/dist/content/aup/hust/en.json +3 -3
  21. package/dist/content/aup/traduora/en.html +2 -2
  22. package/dist/content/aup/traduora/en.json +3 -3
  23. package/dist/content/cookies/ever-async/en.html +457 -0
  24. package/dist/content/cookies/ever-async/en.json +185 -0
  25. package/dist/content/cookies/ever-corporate/en.html +1 -1
  26. package/dist/content/cookies/ever-corporate/en.json +3 -3
  27. package/dist/content/cookies/ever-demand/en.html +8 -5
  28. package/dist/content/cookies/ever-demand/en.json +3 -3
  29. package/dist/content/cookies/ever-rec/en.html +8 -5
  30. package/dist/content/cookies/ever-rec/en.json +3 -3
  31. package/dist/content/cookies/ever-teams/en.html +6 -3
  32. package/dist/content/cookies/ever-teams/en.json +3 -3
  33. package/dist/content/cookies/ever-tech/en.html +3 -3
  34. package/dist/content/cookies/ever-tech/en.json +3 -3
  35. package/dist/content/cookies/ever-works/en.html +6 -3
  36. package/dist/content/cookies/ever-works/en.json +3 -3
  37. package/dist/content/cookies/everiq/en.html +1 -1
  38. package/dist/content/cookies/everiq/en.json +3 -3
  39. package/dist/content/cookies/gauzy/en.html +6 -3
  40. package/dist/content/cookies/gauzy/en.json +3 -3
  41. package/dist/content/cookies/githands/en.html +6 -3
  42. package/dist/content/cookies/githands/en.json +3 -3
  43. package/dist/content/cookies/hust/en.html +6 -3
  44. package/dist/content/cookies/hust/en.json +3 -3
  45. package/dist/content/cookies/traduora/en.html +1 -1
  46. package/dist/content/cookies/traduora/en.json +3 -3
  47. package/dist/content/dpa/ever-async/en.html +1848 -0
  48. package/dist/content/dpa/ever-async/en.json +640 -0
  49. package/dist/content/dpa/ever-demand/en.html +2 -2
  50. package/dist/content/dpa/ever-demand/en.json +3 -3
  51. package/dist/content/dpa/ever-rec/en.html +2 -2
  52. package/dist/content/dpa/ever-rec/en.json +3 -3
  53. package/dist/content/dpa/ever-teams/en.html +2 -2
  54. package/dist/content/dpa/ever-teams/en.json +3 -3
  55. package/dist/content/dpa/ever-works/en.html +2 -2
  56. package/dist/content/dpa/ever-works/en.json +3 -3
  57. package/dist/content/dpa/gauzy/en.html +2 -2
  58. package/dist/content/dpa/gauzy/en.json +3 -3
  59. package/dist/content/dpa/githands/en.html +2 -2
  60. package/dist/content/dpa/githands/en.json +3 -3
  61. package/dist/content/dpa/hust/en.html +2 -2
  62. package/dist/content/dpa/hust/en.json +3 -3
  63. package/dist/content/privacy/ever-async/en.html +1350 -0
  64. package/dist/content/privacy/ever-async/en.json +364 -0
  65. package/dist/content/privacy/ever-corporate/en.html +89 -6
  66. package/dist/content/privacy/ever-corporate/en.json +3 -3
  67. package/dist/content/privacy/ever-demand/en.html +102 -5
  68. package/dist/content/privacy/ever-demand/en.json +3 -3
  69. package/dist/content/privacy/ever-rec/en.html +113 -6
  70. package/dist/content/privacy/ever-rec/en.json +3 -3
  71. package/dist/content/privacy/ever-teams/en.html +100 -4
  72. package/dist/content/privacy/ever-teams/en.json +3 -3
  73. package/dist/content/privacy/ever-tech/en.html +89 -6
  74. package/dist/content/privacy/ever-tech/en.json +3 -3
  75. package/dist/content/privacy/ever-works/en.html +77 -8
  76. package/dist/content/privacy/ever-works/en.json +3 -3
  77. package/dist/content/privacy/everiq/en.html +110 -3
  78. package/dist/content/privacy/everiq/en.json +3 -3
  79. package/dist/content/privacy/gauzy/en.html +91 -6
  80. package/dist/content/privacy/gauzy/en.json +3 -3
  81. package/dist/content/privacy/githands/en.html +86 -5
  82. package/dist/content/privacy/githands/en.json +3 -3
  83. package/dist/content/privacy/hust/en.html +189 -40
  84. package/dist/content/privacy/hust/en.json +4 -4
  85. package/dist/content/privacy/traduora/en.html +96 -3
  86. package/dist/content/privacy/traduora/en.json +3 -3
  87. package/dist/content/refund/ever-rec/en.html +595 -0
  88. package/dist/content/refund/ever-rec/en.json +336 -0
  89. package/dist/content/refund/ever-works/en.html +2 -2
  90. package/dist/content/refund/ever-works/en.json +3 -3
  91. package/dist/content/refund/gauzy/en.html +2 -2
  92. package/dist/content/refund/gauzy/en.json +3 -3
  93. package/dist/content/refund/githands/en.html +2 -2
  94. package/dist/content/refund/githands/en.json +3 -3
  95. package/dist/content/refund/hust/en.html +2 -2
  96. package/dist/content/refund/hust/en.json +3 -3
  97. package/dist/content/security/ever-async/en.html +853 -0
  98. package/dist/content/security/ever-async/en.json +417 -0
  99. package/dist/content/security/ever-demand/en.html +1 -1
  100. package/dist/content/security/ever-demand/en.json +3 -3
  101. package/dist/content/security/ever-rec/en.html +1 -1
  102. package/dist/content/security/ever-rec/en.json +3 -3
  103. package/dist/content/security/ever-teams/en.html +1 -1
  104. package/dist/content/security/ever-teams/en.json +3 -3
  105. package/dist/content/security/ever-works/en.html +1 -1
  106. package/dist/content/security/ever-works/en.json +3 -3
  107. package/dist/content/security/gauzy/en.html +1 -1
  108. package/dist/content/security/gauzy/en.json +3 -3
  109. package/dist/content/security/githands/en.html +1 -1
  110. package/dist/content/security/githands/en.json +3 -3
  111. package/dist/content/security/hust/en.html +1 -1
  112. package/dist/content/security/hust/en.json +3 -3
  113. package/dist/content/subprocessors/ever-async/en.html +852 -0
  114. package/dist/content/subprocessors/ever-async/en.json +166 -0
  115. package/dist/content/subprocessors/ever-corporate/en.html +404 -10
  116. package/dist/content/subprocessors/ever-corporate/en.json +7 -3
  117. package/dist/content/subprocessors/ever-demand/en.html +444 -14
  118. package/dist/content/subprocessors/ever-demand/en.json +7 -3
  119. package/dist/content/subprocessors/ever-rec/en.html +494 -11
  120. package/dist/content/subprocessors/ever-rec/en.json +7 -3
  121. package/dist/content/subprocessors/ever-teams/en.html +436 -9
  122. package/dist/content/subprocessors/ever-teams/en.json +7 -3
  123. package/dist/content/subprocessors/ever-tech/en.html +444 -10
  124. package/dist/content/subprocessors/ever-tech/en.json +7 -3
  125. package/dist/content/subprocessors/ever-works/en.html +355 -14
  126. package/dist/content/subprocessors/ever-works/en.json +7 -3
  127. package/dist/content/subprocessors/everiq/en.html +485 -4
  128. package/dist/content/subprocessors/everiq/en.json +7 -3
  129. package/dist/content/subprocessors/gauzy/en.html +354 -21
  130. package/dist/content/subprocessors/gauzy/en.json +7 -3
  131. package/dist/content/subprocessors/githands/en.html +452 -14
  132. package/dist/content/subprocessors/githands/en.json +7 -3
  133. package/dist/content/subprocessors/hust/en.html +503 -13
  134. package/dist/content/subprocessors/hust/en.json +15 -3
  135. package/dist/content/subprocessors/traduora/en.html +462 -5
  136. package/dist/content/subprocessors/traduora/en.json +7 -3
  137. package/dist/content/tos/ever-async/en.html +1350 -0
  138. package/dist/content/tos/ever-async/en.json +687 -0
  139. package/dist/content/tos/ever-corporate/en.html +3 -3
  140. package/dist/content/tos/ever-corporate/en.json +3 -3
  141. package/dist/content/tos/ever-demand/en.html +3 -3
  142. package/dist/content/tos/ever-demand/en.json +3 -3
  143. package/dist/content/tos/ever-rec/en.html +40 -11
  144. package/dist/content/tos/ever-rec/en.json +5 -5
  145. package/dist/content/tos/ever-teams/en.html +3 -3
  146. package/dist/content/tos/ever-teams/en.json +3 -3
  147. package/dist/content/tos/ever-tech/en.html +3 -3
  148. package/dist/content/tos/ever-tech/en.json +3 -3
  149. package/dist/content/tos/ever-works/en.html +3 -3
  150. package/dist/content/tos/ever-works/en.json +3 -3
  151. package/dist/content/tos/everiq/en.html +3 -3
  152. package/dist/content/tos/everiq/en.json +3 -3
  153. package/dist/content/tos/gauzy/en.html +3 -3
  154. package/dist/content/tos/gauzy/en.json +3 -3
  155. package/dist/content/tos/githands/en.html +3 -3
  156. package/dist/content/tos/githands/en.json +3 -3
  157. package/dist/content/tos/hust/en.html +35 -11
  158. package/dist/content/tos/hust/en.json +11 -3
  159. package/dist/content/tos/traduora/en.html +3 -3
  160. package/dist/content/tos/traduora/en.json +3 -3
  161. package/dist/index.json +4506 -1316
  162. package/package.json +1 -1
@@ -1,6 +1,6 @@
1
1
  <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
2
  <p><strong>Ever Hust</strong> — <a href="https://hust.so">hust.so</a></p>
3
- <p>Version 1.0.1 · In force from 2026-08-02</p>
3
+ <p>Version 1.0.2 · In force from 2026-08-02</p>
4
4
  <p>This notice explains what we do with personal data when you use the Ever Hust hosted service and the websites,
5
5
  applications and application programming interfaces we make available at <a href="https://hust.so">hust.so</a>
6
6
  (together, the &quot;<strong>Service</strong>&quot;). It tells you what we collect, why, who else sees it, how long we keep it,
@@ -606,25 +606,68 @@ copies somebody else's correspondence into our database, and our
606
606
  <h3 id="people-who-never-signed-up" tabindex="-1">People who never signed up</h3>
607
607
  <p>Three groups of people have data here without ever having dealt with us. Article 14 GDPR says they are
608
608
  entitled to be told, and this section is that notice as well as an explanation to you.</p>
609
- <p><strong>1. People named inside job postings.</strong> Listings are collected automatically from a large number of job
610
- boards, applicant tracking systems and company career pages. What comes back is the posting as its author
611
- wrote it, and postings routinely name a recruiter or a hiring manager and sometimes give a direct email
612
- address or telephone number. We did not ask for that, we do not go looking for it, and we do not build
613
- profiles of those people — but it arrives inside the description text and we store the description.</p>
609
+ <p><strong>1. People named inside job postings.</strong> This is the largest group of people in Ever Hust who never
610
+ agreed to anything, so it gets the most space.</p>
611
+ <p><strong>How many sources, and what they are.</strong> Listings are collected from <strong>1,832 sources</strong>: <strong>180 applicant
612
+ tracking systems</strong>, <strong>1,540 named employers' own career endpoints</strong>, and <strong>112 job boards, feeds and public
613
+ registries</strong>. The middle number is the one people do not expect — for well over a thousand named companies
614
+ we read that company's own careers endpoint directly, rather than waiting for a board to carry it.</p>
615
+ <p><strong>By what means.</strong> Not one method but several, and it is fairer to name them than to say &quot;automatically&quot;:
616
+ public REST, GraphQL and OData APIs; RSS, Atom, XML and JSON feeds; parsing the HTML of a careers page and
617
+ the structured data embedded in it; and, on a small number of sources, rendering the page in a headless
618
+ browser with the user agent and window size varied. <strong>This is scraping as well as API access, and we would
619
+ rather call it that.</strong> We do not operate a robots.txt check today. A board, an applicant tracking system or
620
+ an employer that wants us to stop reading its postings can say so at legal@ever.co and we will.</p>
621
+ <p><strong>What arrives, and what we then do to it.</strong> What comes back is the posting as its author wrote it, and
622
+ postings routinely name a recruiter or a hiring manager and give a direct email address or telephone
623
+ number. Two separate things then happen, and the second one is the one that needs stating plainly:</p>
614
624
  <ul>
615
- <li><strong>Source:</strong> publicly accessible job boards, applicant tracking system feeds and employers' own career
616
- pages. The categories are listed in the <a href="https://hust.so/subprocessors">Sub-processor List</a>.</li>
617
- <li><strong>Purpose:</strong> showing a job seeker a posting in the form it was published.</li>
618
- <li><strong>Legal basis:</strong> our legitimate interests, and those of the people using the product, in presenting a
619
- posting accurately. Weighed against the fact that the data was published by the employer for exactly this
620
- purpose, that we add nothing to it, and that we do not contact anyone named in it.</li>
621
- <li><strong>Retention:</strong> a posting is kept while it is live and for 12 months after we last saw it, then deleted.</li>
625
+ <li>we store the <strong>description as published</strong>, which is where names, telephone numbers and signature blocks
626
+ sit; and</li>
627
+ <li><strong>we run a pattern match over that description and pull every email address out of it into a structured
628
+ field of its own</strong>, which we store alongside the posting. So we do not merely happen to retain a
629
+ recruiter's address inside a wall of text — for a posting that contains one, we hold it as a discrete,
630
+ queryable value. Some applicant tracking systems also give us a named recruiter or contact person as a
631
+ field in their own right.</li>
632
+ </ul>
633
+ <p>We say this because the older version of this notice said we &quot;do not go looking for it&quot;, and that was not
634
+ an accurate description of what the software does.</p>
635
+ <p><strong>What we do not do with any of it.</strong> We do not contact anyone named in a posting. We do not build a
636
+ profile of them, enrich them against other sources, sell, rent or publish the addresses, or use them for
637
+ marketing of any kind. The addresses exist so that a posting can be shown and matched as its author wrote
638
+ it. Our <a href="https://hust.so/aup">Acceptable Use Policy</a> forbids a user from harvesting contact details out of
639
+ the postings we show them; we hold ourselves to the narrower promise above, and we would rather set the two
640
+ side by side here than let a reader find the asymmetry on their own.</p>
641
+ <ul>
642
+ <li><strong>Source:</strong> publicly accessible job boards, applicant tracking system feeds, public registries and
643
+ employers' own career pages — the 1,832 sources described above. They are <strong>sources we read from, not
644
+ sub-processors</strong>: nothing about any user is sent to them, so they receive nothing to process on our
645
+ behalf. The <a href="https://hust.so/subprocessors">Sub-processor List</a> explains that split and names the one
646
+ source we authenticate to.</li>
647
+ <li><strong>Purpose:</strong> showing a job seeker a posting in the form it was published, and matching it against what
648
+ they are looking for.</li>
649
+ <li><strong>Legal basis:</strong> <strong>our legitimate interests, and those of the people using the product</strong> (Article
650
+ 6(1)(f)), in presenting a posting accurately and completely. The balance rests on this: the data was
651
+ published by the employer, in public, for precisely the purpose of being read by job seekers; we show it
652
+ in the form it was published; we add nothing to it and infer nothing about the person named; and we never
653
+ contact them. Held against that is the extraction step above, which goes further than passive retention —
654
+ which is why the objection route below is deliberately easy and why we do not use the field for anything
655
+ other than displaying the posting. You can ask us for the balancing assessment.</li>
656
+ <li><strong>Retention:</strong> a posting and the raw payload behind it are deleted when the posting's own expiry date
657
+ passes, or once it is <strong>more than 90 days old and we have not seen it change for 90 days</strong>. An earlier
658
+ version of this notice published a 12-month figure; the software has always used the shorter rule and the
659
+ shorter rule is the one that binds us.</li>
622
660
  <li><strong>Notice:</strong> contacting each of these people individually would mean writing to everyone named in every
623
661
  posting we hold, which is not proportionate and for most of them not possible from what a description
624
662
  gives us. We rely on Article 14(5)(b) and publish this instead.</li>
625
- <li><strong>If that is you:</strong> write to privacy@ever.co with the posting or your name and we will remove your
626
- details from what we hold and, where we can, suppress them on re-collection. You do not have to be a
627
- customer, and you do not have to explain why.</li>
663
+ <li><strong>If that is you:</strong> write to privacy@ever.co with the posting, the address, or your name, and <strong>we
664
+ will delete your details both from the posting text and from the extracted address field.</strong> You do not
665
+ have to be a customer, you do not have to explain why, and we will confirm when it is done. You can also
666
+ object outright under Article 21, and for this group we will not argue compelling grounds — we will
667
+ simply remove you. <strong>One honest limit:</strong> the source keeps publishing the posting, so if we collect it
668
+ again the details can come back. Removing them again is a manual step we take, not yet an automatic one;
669
+ tell us if you see it recur, and ask the employer or the board to amend the posting at source, which is
670
+ the only fix that holds everywhere.</li>
628
671
  </ul>
629
672
  <p><strong>We never send anything to a person named in a posting.</strong> The product drafts outreach for a user to
630
673
  review, edit and send from their own account. Nothing leaves us addressed to a recruiter.</p>
@@ -673,23 +716,48 @@ scores, bands or gap lists to screen, rank or reject candidates, that is an auto
673
716
  its own obligations, and it is the organisation's to carry. Our terms require meaningful human review, the
674
717
  <a href="https://hust.so/dpa">Data Processing Addendum</a> annex sets out what else it must do, and we can switch the
675
718
  feature off for an organisation that ignores it.</p>
676
- <p>Separately, each posting carries a <strong>legitimacy and freshness signal</strong> — verified, likely or uncertain —
677
- with machine-generated reasons. <strong>That is an observation about the posting, not an accusation about the
678
- employer</strong>, it is deliberately kept out of the fit score, and an employer who disagrees with one can have
679
- it reviewed at legal@ever.co.</p>
680
- <h3 id="what-leaves-our-network-when-you-search" tabindex="-1">What leaves our network when you search</h3>
681
- <p>Job listings come from an aggregation service we operate ourselves. It is not reachable from the internet
682
- and it never receives your identity — no name, no email address, no CV, no account identifier.</p>
683
- <p>What does leave us, on each search, is <strong>your search terms — job title, keywords, location, distance,
684
- country and filters — together with our own server's IP address</strong>, sent out concurrently to a large number
685
- of job boards, applicant tracking systems and company career pages. With roughly a third of those sources
686
- we hold an API key or a publisher identifier, so those queries are identifiable as ours rather than
687
- anonymous; one public-sector source requires a contact email address of ours on every request. None of that
688
- identifies you to them.</p>
689
- <p><strong>Searches are stored.</strong> We keep a record of searches run through the product for 12 months, so that alerts
690
- work and so we can see which sources are producing results.</p>
691
- <p>We do not route this traffic through a commercial proxy pool. If that ever changes, the provider becomes a
692
- recipient of your search terms and it will be named in the
719
+ <p>Separately, a posting <strong>may carry</strong> a <strong>legitimacy and freshness signal</strong> — verified, likely or uncertain —
720
+ with machine-generated reasons. It is a setting rather than a fixture, it is not requested in every
721
+ environment, and where it is off a posting simply has no signal. <strong>Where there is one it is an observation
722
+ about the posting, not an accusation about the employer</strong>, it is deliberately kept out of the fit score,
723
+ and an employer who disagrees with one can have it reviewed at legal@ever.co.</p>
724
+ <h3 id="what-leaves-our-network-and-what-does-not" tabindex="-1">What leaves our network, and what does not</h3>
725
+ <p>There are two different things going on here and an earlier version of this notice ran them together, in
726
+ the direction that flattered nobody: it described your search fanning out to job boards. It does not. These
727
+ are separate paths and only one of them leaves our network at all.</p>
728
+ <p><strong>The aggregation engine is ours.</strong> Job listings are collected by <strong>Ever Jobs</strong>, a separate open-source
729
+ project of ours published under the MIT licence at
730
+ <a href="https://github.com/ever-jobs/ever-jobs">github.com/ever-jobs/ever-jobs</a>. <strong>We run it ourselves, inside our
731
+ own cluster.</strong> No third party operates it, it has no route in from the internet, it keeps nothing —
732
+ everything is in memory and the results are written into our own database — and <strong>it never receives your
733
+ identity: no name, no email address, no CV, no account identifier, not even a session.</strong> Because nobody
734
+ else runs it, there is no vendor to name for it in the
735
+ <a href="https://hust.so/subprocessors">Sub-processor List</a>, and you can read exactly what it does.</p>
736
+ <p><strong>Path one — scheduled collection, which does leave us, and carries nothing of yours.</strong> On a schedule, with
737
+ nobody present, the engine queries the 1,832 sources described above. What leaves us on each of those
738
+ requests is <strong>a generic job title taken from a fixed rotation of roughly thirty</strong> — &quot;software engineer&quot;,
739
+ &quot;product manager&quot;, &quot;data scientist&quot; and the like, chosen by the clock — together with a country and radius,
740
+ <strong>our own server's IP address</strong> and a browser-like user agent. <strong>Not one of those terms comes from a user.</strong>
741
+ No search you typed, no filter you set and nothing from your profile is ever part of that traffic.</p>
742
+ <p><strong>We are unauthenticated to all but one of them.</strong> An earlier version of this notice said we hold an API key
743
+ or publisher identifier with roughly a third of our sources, and that a public-sector source receives a
744
+ contact address of ours. Neither is true of what we run: <strong>exactly one source, Upwork, receives a credential
745
+ of ours</strong>, which makes those queries attributable to an account of ours rather than anonymous. It is named
746
+ in the <a href="https://hust.so/subprocessors">Sub-processor List</a> for that reason. Everything else is plain public
747
+ fetching.</p>
748
+ <p><strong>Path two — your search, which does not leave us at all.</strong> When you search in the product, <strong>that query
749
+ runs against our own database of already-collected postings.</strong> It is a query inside our own network. Your
750
+ search terms are not broadcast to job boards, not sent to an applicant tracking system, and not disclosed
751
+ to any source. The same is true of your alerts, which are matched against the same stored postings.</p>
752
+ <p><strong>Searches are still stored</strong> — we keep a record of searches run through the product for 12 months, so that
753
+ alerts work and so we can see which sources are producing results. That record is ours and stays with us.</p>
754
+ <p><strong>One outbound call is made for the postings themselves.</strong> As each newly collected posting is stored, our
755
+ backend sends its city, state and country to Google's geocoding service to turn that text into coordinates.
756
+ That runs on the collection schedule with nobody present, there is no setting that removes it, and it is
757
+ listed in tier 1 of the <a href="https://hust.so/subprocessors">Sub-processor List</a>. It carries a job's location,
758
+ never yours.</p>
759
+ <p>We do not route any of this traffic through a commercial proxy pool. If that ever changes, the provider
760
+ becomes a recipient of what we send and it will be named in the
693
761
  <a href="https://hust.so/subprocessors">Sub-processor List</a> before it is switched on.</p>
694
762
  <h3 id="how-long-we-keep-ever-hust-data" tabindex="-1">How long we keep Ever Hust data</h3>
695
763
  <p>These sit alongside the general retention table above; where both could apply, the shorter period wins.</p>
@@ -738,8 +806,8 @@ recipient of your search terms and it will be named in the
738
806
  <td>12 months</td>
739
807
  </tr>
740
808
  <tr>
741
- <td>Aggregated job postings and the raw payload behind them</td>
742
- <td>While the posting is live, and 12 months after we last saw it</td>
809
+ <td>Aggregated job postings and the raw payload behind them, including any recruiter email address extracted out of the posting text</td>
810
+ <td>Until the posting's own expiry date passes, or once it is more than 90 days old and has not changed for 90 days — whichever comes first</td>
743
811
  </tr>
744
812
  <tr>
745
813
  <td>Unused organisation invitations and referral records</td>
@@ -850,6 +918,7 @@ data is most likely to reach.</p>
850
918
  <th>Sub-processor</th>
851
919
  <th>Purpose</th>
852
920
  <th>Location</th>
921
+ <th>Transfer mechanism</th>
853
922
  <th>Personal data</th>
854
923
  </tr>
855
924
  </thead>
@@ -858,62 +927,142 @@ data is most likely to reach.</p>
858
927
  <td>Cloudflare, Inc.</td>
859
928
  <td>Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our network. Every request to the website and to the application passes through it.</td>
860
929
  <td>United States, with your connection terminated at the edge location nearest to you</td>
930
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
861
931
  <td>IP address, TLS and connection metadata, request URLs and headers, cookies in transit</td>
862
932
  </tr>
863
933
  <tr>
864
934
  <td>Stripe Payments Europe, Limited</td>
865
935
  <td>Subscription checkout, recurring billing, invoices, refunds and payment fraud checks. Engaged when you buy a plan. The free tier never reaches it, and we never receive your full card number.</td>
866
936
  <td>Ireland, with processing on Stripe infrastructure including the United States</td>
937
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
867
938
  <td>name, email address, billing address and country, card token and last four digits, tax identification number, subscription and invoice history, IP address at checkout</td>
868
939
  </tr>
869
940
  <tr>
870
941
  <td>OpenRouter, Inc.</td>
871
942
  <td>Routes the assistant's model requests. It carries your chat messages, job description text, your CV text and the prompts behind evaluations, cover letters, tailored resumes, interview preparation and outreach drafts — then forwards each request to the upstream provider of the model in use.</td>
872
943
  <td>United States, with onward processing by the upstream provider of the selected model</td>
944
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
873
945
  <td>chat messages, CV and profile text, job description text, generated output, user and session identifiers</td>
874
946
  </tr>
875
947
  <tr>
876
- <td>Anthropic PBC</td>
948
+ <td>Anthropic, PBC</td>
877
949
  <td>CV parsing. The full extracted text of a CV you upload is sent here on a direct call, outside the router above, to produce the structured profile. Also the default assistant model on paid plans.</td>
878
950
  <td>United States</td>
951
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
879
952
  <td>the full text of your CV, name, email address, telephone number, location, employment history, education, skills</td>
880
953
  </tr>
881
954
  <tr>
882
955
  <td>Langfuse GmbH</td>
883
956
  <td>Tracing and observability for the assistant. It receives complete model prompts and completions, which means CV text, job text and chat content, with the identifiers that tie a trace to a user.</td>
884
957
  <td>Germany (European Union)</td>
958
+ <td>None needed — established in the EEA</td>
885
959
  <td>model prompts and completions, CV, job and chat text contained in them, user and session identifiers</td>
886
960
  </tr>
887
961
  <tr>
888
962
  <td>Resend, Inc.</td>
889
963
  <td>Delivery of the email we send you — address verification, sign-in, password reset, job alerts, application reminders and billing notices. It does not send anything from your connected mailbox.</td>
890
964
  <td>United States</td>
965
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
891
966
  <td>recipient email address and name, message subject and body, delivery, bounce and complaint events</td>
892
967
  </tr>
893
968
  <tr>
894
969
  <td>Functional Software, Inc. d/b/a Sentry</td>
895
970
  <td>Error and performance monitoring. Error context carries your user identifier and email address, so this is not anonymous telemetry and we do not describe it as such.</td>
896
971
  <td>United States</td>
972
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
897
973
  <td>user identifier, email address, IP address, page or route, browser and device, stack traces and breadcrumbs</td>
898
974
  </tr>
899
975
  <tr>
900
- <td>GitHub, Inc.</td>
976
+ <td>GitHub, Inc. (a Microsoft Corporation company)</td>
901
977
  <td>Source code, build pipeline and container registry. This is how the Service is built and shipped rather than where your data lives, and it is disclosed because it is still a third party.</td>
902
978
  <td>United States</td>
979
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
903
980
  <td>none of your account or job-search data in the ordinary course, build and deployment metadata</td>
904
981
  </tr>
905
982
  <tr>
906
983
  <td>Automattic Inc.</td>
907
984
  <td>Gravatar avatar fallback. Where you have not set a profile picture, your browser asks Gravatar for one using a hash of your email address.</td>
908
985
  <td>United States</td>
986
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
909
987
  <td>a hash of your email address, IP address, browser and device</td>
910
988
  </tr>
911
989
  <tr>
912
- <td>Prospect One (jsDelivr)</td>
990
+ <td>Prospect One sp. z o.o. (jsDelivr)</td>
913
991
  <td>Public content delivery network serving the API reference viewer on the developer documentation pages. Your browser fetches those assets directly, so the request discloses your address to it.</td>
914
992
  <td>Poland, with delivery from edge locations worldwide</td>
993
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
915
994
  <td>IP address, browser and device, the page you were on</td>
916
995
  </tr>
996
+ <tr>
997
+ <td>Cloudflare, Inc. (R2 object storage)</td>
998
+ <td>Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network.</td>
999
+ <td>United States</td>
1000
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
1001
+ <td>client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold</td>
1002
+ </tr>
1003
+ <tr>
1004
+ <td>Google Ireland Limited (reCAPTCHA)</td>
1005
+ <td>Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made.</td>
1006
+ <td>Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC)</td>
1007
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
1008
+ <td>IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com</td>
1009
+ </tr>
1010
+ <tr>
1011
+ <td>Clerk, Inc.</td>
1012
+ <td>Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name.</td>
1013
+ <td>United States</td>
1014
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
1015
+ <td>name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored</td>
1016
+ </tr>
1017
+ <tr>
1018
+ <td>Tavily</td>
1019
+ <td>The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain.</td>
1020
+ <td>United States</td>
1021
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
1022
+ <td>search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata</td>
1023
+ </tr>
1024
+ <tr>
1025
+ <td>ui-avatars.com</td>
1026
+ <td>Generates placeholder avatars 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>
1027
+ <td>UNKNOWN - not published by the provider</td>
1028
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
1029
+ <td>the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent</td>
1030
+ </tr>
1031
+ <tr>
1032
+ <td>UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified</td>
1033
+ <td>Second permitted origin for the Lottie animation runtime on the ever-works login and register pages.</td>
1034
+ <td>United States (unverified)</td>
1035
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
1036
+ <td>IP address, user agent, referring page URL</td>
1037
+ </tr>
1038
+ <tr>
1039
+ <td>Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting.</td>
1040
+ <td>Handles subscription billing and invoicing for the hosted Gauzy service.</td>
1041
+ <td>United States / Netherlands</td>
1042
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
1043
+ <td>billing identity and address, plan, invoice and payment history</td>
1044
+ </tr>
1045
+ <tr>
1046
+ <td>Shopify International Limited</td>
1047
+ <td>Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records.</td>
1048
+ <td>Ireland (contracting) / Canada and United States (Shopify group)</td>
1049
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
1050
+ <td>customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront</td>
1051
+ </tr>
1052
+ <tr>
1053
+ <td>Upwork Global Inc.</td>
1054
+ <td>The one posting source in the whole catalogue that we authenticate to. Freelance and gig postings are pulled from Upwork's API under an OAuth credential of ours, so those queries run as an identified account rather than anonymously, and they run on every scheduled ingestion because Upwork is in the default source list. It is a source we read from - nothing about you is sent to it.</td>
1055
+ <td>United States</td>
1056
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
1057
+ <td>our own OAuth account identity with Upwork, not yours, a generic job-title search term from our fixed rotation, our egress server IP address, none of your account, profile, CV, search or application data</td>
1058
+ </tr>
1059
+ <tr>
1060
+ <td>Google Ireland Limited (Google Maps Platform)</td>
1061
+ <td>Server-side geocoding on the ingestion path. When a posting is newly collected, our own backend sends its city, state and country to the Geocoding API to turn that text into coordinates. This runs on a schedule with nobody present and there is no setting that removes it, which is why it sits here and not only in tier 2 with the browser-side map.</td>
1062
+ <td>Ireland and the United States</td>
1063
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
1064
+ <td>the city, state and country named in a job posting, our server's IP address and API key, none of your account, profile, CV or search data</td>
1065
+ </tr>
917
1066
  </tbody>
918
1067
  </table>
919
1068
  <p>The full and current list, including everything below, is published at
@@ -1316,7 +1465,7 @@ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1316
1465
  <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1317
1466
  We would rather update it than let it drift out of date and quietly stop being true.</p>
1318
1467
  <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1319
- is version 1.0.1, in force from 2026-08-02.</strong></p>
1468
+ is version 1.0.2, in force from 2026-08-02.</strong></p>
1320
1469
  <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1321
1470
  <ul>
1322
1471
  <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
@@ -1354,6 +1503,6 @@ policy will say so and will give the designated office's contact details.</p>
1354
1503
  <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1355
1504
  controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1356
1505
  us anyway if you are unsure, and we will tell you who to ask.</p>
1357
- <p>This document is version 1.0.1 of the Privacy Policy for
1506
+ <p>This document is version 1.0.2 of the Privacy Policy for
1358
1507
  <a href="https://hust.so">hust.so</a>, in force from 2026-08-02. Earlier versions, with the
1359
1508
  dates they applied, are at <a href="https://hust.so/privacy">https://hust.so/privacy</a>.</p>