@ever-co/legal 0.6.0 → 0.7.1

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 (98) hide show
  1. package/dist/content/aup/ever-async/en.json +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +2 -2
  3. package/dist/content/aup/ever-demand/en.json +2 -2
  4. package/dist/content/aup/ever-rec/en.json +2 -2
  5. package/dist/content/aup/ever-teams/en.json +2 -2
  6. package/dist/content/aup/ever-works/en.json +2 -2
  7. package/dist/content/aup/everiq/en.json +2 -2
  8. package/dist/content/aup/gauzy/en.json +2 -2
  9. package/dist/content/aup/githands/en.json +2 -2
  10. package/dist/content/aup/hust/en.json +2 -2
  11. package/dist/content/aup/traduora/en.json +2 -2
  12. package/dist/content/cookies/ever-async/en.json +2 -2
  13. package/dist/content/cookies/ever-corporate/en.json +2 -2
  14. package/dist/content/cookies/ever-demand/en.json +2 -2
  15. package/dist/content/cookies/ever-rec/en.json +2 -2
  16. package/dist/content/cookies/ever-teams/en.json +2 -2
  17. package/dist/content/cookies/ever-tech/en.json +2 -2
  18. package/dist/content/cookies/ever-works/en.json +2 -2
  19. package/dist/content/cookies/everiq/en.json +2 -2
  20. package/dist/content/cookies/gauzy/en.json +2 -2
  21. package/dist/content/cookies/githands/en.json +2 -2
  22. package/dist/content/cookies/hust/en.json +2 -2
  23. package/dist/content/cookies/traduora/en.json +2 -2
  24. package/dist/content/dpa/ever-async/en.json +2 -2
  25. package/dist/content/dpa/ever-demand/en.json +2 -2
  26. package/dist/content/dpa/ever-rec/en.json +2 -2
  27. package/dist/content/dpa/ever-teams/en.json +2 -2
  28. package/dist/content/dpa/ever-tech-services/en.json +2 -2
  29. package/dist/content/dpa/ever-works/en.json +2 -2
  30. package/dist/content/dpa/gauzy/en.json +2 -2
  31. package/dist/content/dpa/githands/en.json +2 -2
  32. package/dist/content/dpa/hust/en.json +2 -2
  33. package/dist/content/dpia/gauzy/en.json +2 -2
  34. package/dist/content/privacy/ever-async/en.json +2 -2
  35. package/dist/content/privacy/ever-corporate/en.json +2 -2
  36. package/dist/content/privacy/ever-demand/en.json +2 -2
  37. package/dist/content/privacy/ever-rec/en.json +2 -2
  38. package/dist/content/privacy/ever-teams/en.json +2 -2
  39. package/dist/content/privacy/ever-tech/en.html +90 -24
  40. package/dist/content/privacy/ever-tech/en.json +4 -4
  41. package/dist/content/privacy/ever-works/en.json +2 -2
  42. package/dist/content/privacy/everiq/en.json +2 -2
  43. package/dist/content/privacy/gauzy/en.json +2 -2
  44. package/dist/content/privacy/githands/en.json +2 -2
  45. package/dist/content/privacy/hust/en.json +2 -2
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-corporate/en.json +2 -2
  48. package/dist/content/refund/ever-demand/en.json +2 -2
  49. package/dist/content/refund/ever-rec/en.json +2 -2
  50. package/dist/content/refund/ever-teams/en.json +2 -2
  51. package/dist/content/refund/ever-tech-services/en.json +2 -2
  52. package/dist/content/refund/ever-works/en.json +2 -2
  53. package/dist/content/refund/gauzy/en.json +2 -2
  54. package/dist/content/refund/githands/en.json +2 -2
  55. package/dist/content/refund/hust/en.json +2 -2
  56. package/dist/content/refund/traduora/en.json +2 -2
  57. package/dist/content/security/ever-async/en.json +2 -2
  58. package/dist/content/security/ever-corporate/en.json +2 -2
  59. package/dist/content/security/ever-demand/en.json +2 -2
  60. package/dist/content/security/ever-rec/en.json +2 -2
  61. package/dist/content/security/ever-teams/en.json +2 -2
  62. package/dist/content/security/ever-tech/en.html +21 -2
  63. package/dist/content/security/ever-tech/en.json +9 -4
  64. package/dist/content/security/ever-works/en.json +2 -2
  65. package/dist/content/security/gauzy/en.json +2 -2
  66. package/dist/content/security/githands/en.json +2 -2
  67. package/dist/content/security/hust/en.json +2 -2
  68. package/dist/content/security/traduora/en.json +2 -2
  69. package/dist/content/subprocessors/ever-async/en.json +2 -2
  70. package/dist/content/subprocessors/ever-corporate/en.json +2 -2
  71. package/dist/content/subprocessors/ever-demand/en.json +2 -2
  72. package/dist/content/subprocessors/ever-rec/en.json +2 -2
  73. package/dist/content/subprocessors/ever-teams/en.json +2 -2
  74. package/dist/content/subprocessors/ever-tech/en.html +27 -12
  75. package/dist/content/subprocessors/ever-tech/en.json +4 -4
  76. package/dist/content/subprocessors/ever-tech-services/en.json +2 -2
  77. package/dist/content/subprocessors/ever-works/en.json +2 -2
  78. package/dist/content/subprocessors/everiq/en.json +2 -2
  79. package/dist/content/subprocessors/gauzy/en.json +2 -2
  80. package/dist/content/subprocessors/githands/en.json +2 -2
  81. package/dist/content/subprocessors/hust/en.json +2 -2
  82. package/dist/content/subprocessors/traduora/en.json +2 -2
  83. package/dist/content/tos/ever-async/en.json +2 -2
  84. package/dist/content/tos/ever-corporate/en.json +2 -2
  85. package/dist/content/tos/ever-demand/en.json +2 -2
  86. package/dist/content/tos/ever-rec/en.json +2 -2
  87. package/dist/content/tos/ever-teams/en.json +2 -2
  88. package/dist/content/tos/ever-tech/en.html +25 -10
  89. package/dist/content/tos/ever-tech/en.json +4 -4
  90. package/dist/content/tos/ever-tech-services/en.json +2 -2
  91. package/dist/content/tos/ever-works/en.json +2 -2
  92. package/dist/content/tos/everiq/en.json +2 -2
  93. package/dist/content/tos/gauzy/en.json +2 -2
  94. package/dist/content/tos/githands/en.json +2 -2
  95. package/dist/content/tos/hust/en.json +2 -2
  96. package/dist/content/tos/traduora/en.json +2 -2
  97. package/dist/index.json +105 -100
  98. package/package.json +52 -52
@@ -1,6 +1,6 @@
1
1
  <h1 id="privacy-policy" tabindex="-1">Privacy Policy</h1>
2
2
  <p><strong>Ever Tech</strong> — <a href="https://ever.tech">ever.tech</a></p>
3
- <p>Version 1.1.0 · In force from 2026-10-25</p>
3
+ <p>Version 1.2.1 · In force from 2026-11-19</p>
4
4
  <p>This notice explains what we do with personal data when you use the Ever Tech website and the websites,
5
5
  applications and application programming interfaces we make available at <a href="https://ever.tech">ever.tech</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,
@@ -497,13 +497,17 @@ and the database behind it, the enquiry and trial forms, the links to the market
497
497
  hired, and the people we publish.</p>
498
498
  <h3 id="the-talent-application-and-the-database-behind-it" tabindex="-1">The talent application, and the database behind it</h3>
499
499
  <p>The multi-step form at <a href="https://ever.tech/join-us">https://ever.tech/join-us</a> is not a &quot;send us your CV&quot;
500
- mailbox. When you submit it, three things happen in order.</p>
500
+ mailbox. When you submit it, three things happen in order — and a fourth where you asked to join our
501
+ talent network.</p>
501
502
  <ol>
502
503
  <li>The form is checked against our bot-protection provider.</li>
503
504
  <li>The application is emailed to an internal recruitment mailbox through our mail provider, <strong>with your
504
505
  CV attached</strong>.</li>
505
506
  <li><strong>A candidate record and an application record are written to our own content database</strong>, which runs
506
507
  on our own hardware in the European Union.</li>
508
+ <li><strong>Where you asked to join our on-demand talent network, your CV and part of your application are also
509
+ written to a private repository that GitHub hosts for us</strong> — outside our own hardware. What goes into
510
+ it, and how it comes out again, is set out below.</li>
507
511
  </ol>
508
512
  <p>What is stored in those records:</p>
509
513
  <ul>
@@ -512,7 +516,8 @@ number, location and the languages you speak.</li>
512
516
  <li><strong>Application</strong> — the role you are applying for, years of experience, the hourly rate you asked for,
513
517
  weekly availability, links to your GitHub and LinkedIn profiles, your skills, the tools you are
514
518
  familiar with, your specialisations, the past projects you described, education, degree, institution,
515
- year of graduation, certifications, preferred work type, time zone, earliest start date, the date and
519
+ year of graduation, certifications, how you asked to work with us (the on-demand talent network,
520
+ full-time, part-time), time zone, earliest start date, the date and
516
521
  time you submitted, whether you ticked the terms and privacy boxes, and the status we have given the
517
522
  application.</li>
518
523
  <li><strong>The CV file itself is stored inside the application record</strong>, not only emailed. It is held in our
@@ -523,27 +528,84 @@ second one, and adds a new application to it. That is what the address being the
523
528
  <p><strong>Our lawful basis is Article 6(1)(b) — steps taken at your request before entering into a contract</strong> —
524
529
  for handling your application, together with our legitimate interest in keeping a record of who applied
525
530
  and what we decided, so that we can answer a question about it later.</p>
526
- <p><strong>Twelve months after an application closes — when we accept or decline it — we anonymise it in place.</strong>
531
+ <p><strong>Twelve months after an application closes — when we accept or decline it — we anonymise it in place.
532
+ That is the rule for an application for a full-time or a part-time position. The one exception is our
533
+ on-demand talent network: where you asked to join it, on its own or alongside a position, we keep your
534
+ record for up to 36 months after the application closes, and anonymise it then.</strong>
527
535
  The CV and every field that identifies you are overwritten: your names, email address, telephone number,
528
536
  location, the links to your profiles, the projects you described, your education and your certifications.
529
537
  Once all of your applications have closed and been anonymised, the candidate record is anonymised the same
530
538
  way. What remains is a row with no one behind it — the role, the stage history and fields such as years of
531
- experience, the rate asked for and availability — which we keep for statistics about our hiring. The copy of the
532
- application in the recruitment mailbox, with the CV attached, is deleted at the same point. If you would
533
- rather stay on file for longer, tell us and we will — that is your consent, it is separate from applying,
534
- and you can withdraw it at any time.</p>
539
+ experience, the rate asked for and availability — which we keep for statistics about our hiring. The copy
540
+ of the application in the recruitment mailbox, with the CV attached, is deleted at the same point. The
541
+ entry in the talent network repository described below, where there is one, is deleted within 30 days of
542
+ it.</p>
543
+ <p><strong>The talent network is a talent marketplace, not a job opening, and joining it is not an application for
544
+ a job.</strong> Whichever of the three you ask for — a full-time position, a part-time position or the network —
545
+ we handle the application the same way: a person reviews it, and nobody is accepted without an interview.
546
+ What differs is what you are asking for. A job application is about one position: once we have
547
+ decided, there is little reason to go on holding it. Joining the network is a different thing. You ask to
548
+ be one of the people we match to projects — as a contractor, on demand and paid by the hour, whenever a
549
+ project fits what you do. No position is being filled, and joining is neither employment nor a promise of
550
+ work. <strong>We can only match people whose record we still hold, and that is why the period is longer.</strong></p>
551
+ <p><strong>If we accept you into the network, your profile becomes public.</strong> That is the main thing the choice
552
+ decides: whether we may list you. Once we have reviewed your application, interviewed you and accepted
553
+ you, we publish a profile of you in our talent marketplace, where anyone can read it — clients, other
554
+ visitors and search engines. That goes beyond the recipients listed under &quot;Who receives your personal
555
+ data&quot; below: a published profile has no fixed audience. <strong>We do not ask you again before we publish it.</strong>
556
+ A profile shows your name, your role, a short description, your skills, an hourly rate, the links to your
557
+ public profiles that you gave us and, where you give us one for the profile, your photograph. <strong>It never
558
+ shows your email address, your telephone number or your CV, unless you ask us to publish them.</strong> If you do
559
+ ask, we publish only what you named, and we take it down again when you tell us to. Until we accept you,
560
+ nothing about you is published, and if we decline you nothing ever is. A profile comes down when you leave
561
+ the network, and at the latest when your record is anonymised — 36 months after we accepted you, unless
562
+ you have asked to join again in the meantime. Applying only for a full-time or a part-time position never
563
+ puts you in our talent marketplace.</p>
564
+ <p><strong>The list of people who ask to join the network is kept in a private repository on GitHub, not on our
565
+ own hardware.</strong> When you send the form with the talent network selected, our server also writes three
566
+ things there: a file holding your name, your email address, the role you applied for, how you asked to
567
+ work with us, the links you gave and what you wrote in the form's free-text fields; your CV, where you
568
+ uploaded one; and a line in an index holding your name, the role, the date and a short code derived from
569
+ your email address, which is not the address itself. That happens when the form is sent, before anyone has
570
+ reviewed the application. GitHub, Inc., a Microsoft company in the United
571
+ States, hosts the repository as our processor, under the transfer safeguards named in the sub-processor
572
+ annex. <strong>The repository is private, and nothing in it is published</strong>: access is limited to the people who
573
+ review talent network applications and the administrators of our GitHub organisation. We count the
574
+ entries in the index — everyone who has asked to join, accepted or not — into the &quot;Talent Network&quot; figure
575
+ shown on the site, which is a number and identifies no one. <strong>We delete your entry from the repository
576
+ when you leave the network, when you ask us to, and in any case when your record is anonymised — within 30
577
+ days each time, because a person does it.</strong> Deleting a file from a repository leaves its earlier versions
578
+ readable in the repository's history, so we remove your file, your CV and your line in the index from that
579
+ history as well.</p>
580
+ <p><strong>Joining is a choice you make on the form, separately from applying for a position.</strong> The form asks how
581
+ you would like to work with us and sets the talent network next to full-time and part-time positions, with
582
+ what each one means; you can choose one of them or several. <strong>The talent network is already selected when
583
+ the form opens; deselect it before you send the form if you do not want to join, do not want your CV and
584
+ details copied to that repository, or do not want a public profile.</strong> Asking to join is how you ask us to
585
+ put you on the network's list, to keep your record for the longer period and to publish your profile once
586
+ we accept you — that is your consent, it is separate from applying, and you can withdraw it at any time by
587
+ writing to privacy@ever.co. We call that leaving the network, whether or not we have accepted you yet.
588
+ When you leave, we take your profile down, where there is one, and delete your entry from the network's
589
+ list. What someone has already copied from a public page, or what a search engine goes on showing for a
590
+ while, is beyond our reach. If you leave, or apply again without asking for the network, the twelve-month
591
+ period applies instead, counted from when each application closed; where that time has already passed, we
592
+ anonymise the record without delay.</p>
535
593
  <p><strong>No artificial intelligence screens, scores, ranks or filters applications.</strong> A person reads every one.</p>
536
- <p>To have your record anonymised or deleted before the 12 months are up, write to privacy@ever.co from
537
- the address you applied with. We do not ask why.</p>
594
+ <p>To have your record anonymised or deleted earlier — before the 12 months or the 36 months are up — write to
595
+ privacy@ever.co from the address you applied with. We do not ask why.</p>
538
596
  <h3 id="applying-through-the-careers-pages-is-different" tabindex="-1">Applying through the careers pages is different</h3>
539
597
  <p>An application sent from the job listings at <a href="https://ever.tech/careers">https://ever.tech/careers</a> is
540
- <strong>emailed only</strong>. Nothing about it is written to the candidate database. It sits in the recruitment
541
- mailbox, and it is deleted 12 months after the application closes.</p>
598
+ <strong>emailed, and nothing about it is written to the candidate database</strong>. It sits in the recruitment
599
+ mailbox, and it is deleted 12 months after the application closes — or, where you asked on that form to
600
+ join our on-demand talent network, up to 36 months after it closes. That form offers the same choice in
601
+ the same way and with the same consequences — an entry in the talent network repository when you send the
602
+ form, and a public profile if we accept you into the network — and you can withdraw it, or ask for earlier
603
+ deletion, as described above.</p>
542
604
  <h3 id="please-do-not-send-us-special-category-data" tabindex="-1">Please do not send us special category data</h3>
543
- <p>We publish this site in thirteen languages, and CV conventions differ sharply between those markets. <strong>We
544
- do not need, and do not ask for, a photograph, date of birth, marital status, nationality, health
545
- information, religion, trade union membership or anything else Article 9 protects</strong>, and no field on any
546
- form asks for it. Please do not send criminal-record information either.</p>
605
+ <p>We publish this site in thirteen languages, and CV conventions differ sharply between those markets.
606
+ <strong>For an application we do not need, and do not ask for, a photograph, date of birth, marital status,
607
+ nationality, health information, religion, trade union membership or anything else Article 9 protects</strong>,
608
+ and no field on any form asks for it. Please do not send criminal-record information either.</p>
547
609
  <p><strong>Where any of it reaches us unbidden, it plays no part in the decision.</strong> We remove it where the record
548
610
  can be edited, and delete the document where it cannot.</p>
549
611
  <h3 id="other-people-named-in-what-you-send" tabindex="-1">Other people named in what you send</h3>
@@ -558,7 +620,7 @@ you.</p>
558
620
  <p>The contact and hire-us forms collect your name, email address, company, the subject, the reasons you
559
621
  selected, the message you wrote and any file you attach. <strong>They are emailed to us and nothing from them
560
622
  is written to the candidate database.</strong> We keep an enquiry for as long as we are dealing with it and for
561
- the correspondence period in the retention table above.</p>
623
+ the correspondence period in the retention table below.</p>
562
624
  <h3 id="trial-applications" tabindex="-1">Trial applications</h3>
563
625
  <p>The <strong>Request a free trial</strong> form on the hire-us page asks for your name, work email address and company,
564
626
  <strong>what you want the agent to do</strong>, and optionally a repository address, the chat and tracking tools you use
@@ -608,10 +670,14 @@ policy position</strong> — tell us and we will fix the cause, not just remove
608
670
  them, links to their public profiles. <strong>Our basis is our legitimate interest in showing who does the work
609
671
  for the role information, and consent for the photograph</strong> — consent that the person can withdraw,
610
672
  without needing a reason and without it counting against them. We remove an entry when someone leaves.</p>
673
+ <p><strong>Members of our talent network are published as well</strong>, each with a profile in our talent marketplace.
674
+ What a profile shows, when it is published and how to have it taken down are set out under the talent
675
+ application above. Membership and the profile go together: for a member, having the profile taken down is
676
+ leaving the network.</p>
611
677
  <p>The open-source contributor list is fetched by our own server from GitHub's public search API and shows
612
678
  public GitHub profile data as GitHub publishes it. We store no profile of those accounts and enrich
613
679
  nothing.</p>
614
- <p><strong>If you are on either of those pages and want an entry corrected or taken down, write to
680
+ <p><strong>If you are on any of those pages and want an entry corrected or taken down, write to
615
681
  privacy@ever.co.</strong> We will do it, and we will not ask you to justify the request.</p>
616
682
  <h3 id="logs-error-reports-and-session-replay" tabindex="-1">Logs, error reports and session replay</h3>
617
683
  <ul>
@@ -624,7 +690,7 @@ media is blocked</strong> in the capture — what is reconstructed is the shape
624
690
  not the words. It is in the analytics category and it does not run unless you consent to that category.</li>
625
691
  </ul>
626
692
  <p>Access to all three is limited to the engineers who run the site, and each is kept for the period in the
627
- retention table above.</p>
693
+ retention table below.</p>
628
694
  <h3 id="the-supervisory-authority-for-this-processing" tabindex="-1">The supervisory authority for this processing</h3>
629
695
  <p>Everything on this site is processed by Ever Technologies LTD in Bulgaria, and the authority to
630
696
  complain to is the Commission for Personal Data Protection (Комисия за защита на личните данни) — https://www.cpdp.bg/. You
@@ -720,10 +786,10 @@ data is most likely to reach.</p>
720
786
  </tr>
721
787
  <tr>
722
788
  <td>GitHub, Inc. (a Microsoft Corporation company)</td>
723
- <td>Source hosting, continuous integration and the container registry the site is built and deployed from. It is also queried by our own server, once per page that shows the open-source contributor list, to read public repository and profile data from the GitHub search API.</td>
789
+ <td>Source hosting, continuous integration and the container registry the site is built and deployed from. It is also queried by our own server, once per page that shows the open-source contributor list, to read public repository and profile data from the GitHub search API. It also hosts the private repository of our talent network, which has its own row in tier 2.</td>
724
790
  <td>United States</td>
725
791
  <td>Standard Contractual Clauses (EU 2021/914)</td>
726
- <td>build, release and deployment metadata, developer and automation account identifiers, public GitHub usernames, avatars and profile links returned by the search API, no visitor data, because the call is made by our server and not by your browser</td>
792
+ <td>build, release and deployment metadata, developer and automation account identifiers, public GitHub usernames, avatars and profile links returned by the search API, no visitor data from that call, because it is made by our server and not by your browser, applicant data only in the talent network repository, as set out in its row in tier 2</td>
727
793
  </tr>
728
794
  <tr>
729
795
  <td>Cloudflare, Inc. (R2 object storage)</td>
@@ -1204,7 +1270,7 @@ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
1204
1270
  <p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
1205
1271
  We would rather update it than let it drift out of date and quietly stop being true.</p>
1206
1272
  <p>Every version carries a version number and the date it takes effect, shown at the top of the page. <strong>This
1207
- is version 1.1.0, in force from 2026-10-25.</strong></p>
1273
+ is version 1.2.1, in force from 2026-11-19.</strong></p>
1208
1274
  <h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
1209
1275
  <ul>
1210
1276
  <li><strong>Minor changes</strong> — clarifying wording, correcting a mistake, adding a provider of a kind already
@@ -1242,6 +1308,6 @@ policy will say so and will give the designated office's contact details.</p>
1242
1308
  <p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
1243
1309
  controller and the request goes to them — see the routing paragraph in the section on your rights. Write to
1244
1310
  us anyway if you are unsure, and we will tell you who to ask.</p>
1245
- <p>This document is version 1.1.0 of the Privacy Policy for
1246
- <a href="https://ever.tech">ever.tech</a>, in force from 2026-10-25. Earlier versions, with the
1311
+ <p>This document is version 1.2.1 of the Privacy Policy for
1312
+ <a href="https://ever.tech">ever.tech</a>, in force from 2026-11-19. Earlier versions, with the
1247
1313
  dates they applied, are at <a href="https://ever.tech/privacy">https://ever.tech/privacy</a>.</p>