@ever-co/legal 0.1.1 β 0.1.2
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.
- package/dist/content/aup/ever-corporate/en.html +2 -2
- package/dist/content/aup/ever-corporate/en.json +3 -3
- package/dist/content/aup/ever-demand/en.html +2 -2
- package/dist/content/aup/ever-demand/en.json +3 -3
- package/dist/content/aup/ever-rec/en.html +2 -2
- package/dist/content/aup/ever-rec/en.json +3 -3
- package/dist/content/aup/ever-teams/en.html +2 -2
- package/dist/content/aup/ever-teams/en.json +3 -3
- package/dist/content/aup/ever-works/en.html +2 -2
- package/dist/content/aup/ever-works/en.json +3 -3
- package/dist/content/aup/everiq/en.html +2 -2
- package/dist/content/aup/everiq/en.json +3 -3
- package/dist/content/aup/gauzy/en.html +2 -2
- package/dist/content/aup/gauzy/en.json +3 -3
- package/dist/content/aup/githands/en.html +2 -2
- package/dist/content/aup/githands/en.json +3 -3
- package/dist/content/aup/hust/en.html +2 -2
- package/dist/content/aup/hust/en.json +3 -3
- package/dist/content/aup/traduora/en.html +2 -2
- package/dist/content/aup/traduora/en.json +3 -3
- package/dist/content/cookies/ever-corporate/en.html +1 -1
- package/dist/content/cookies/ever-corporate/en.json +3 -3
- package/dist/content/cookies/ever-demand/en.html +3 -3
- package/dist/content/cookies/ever-demand/en.json +3 -3
- package/dist/content/cookies/ever-rec/en.html +3 -3
- package/dist/content/cookies/ever-rec/en.json +3 -3
- package/dist/content/cookies/ever-teams/en.html +1 -1
- package/dist/content/cookies/ever-teams/en.json +3 -3
- package/dist/content/cookies/ever-tech/en.html +3 -3
- package/dist/content/cookies/ever-tech/en.json +3 -3
- package/dist/content/cookies/ever-works/en.html +1 -1
- package/dist/content/cookies/ever-works/en.json +3 -3
- package/dist/content/cookies/everiq/en.html +1 -1
- package/dist/content/cookies/everiq/en.json +3 -3
- package/dist/content/cookies/gauzy/en.html +1 -1
- package/dist/content/cookies/gauzy/en.json +3 -3
- package/dist/content/cookies/githands/en.html +1 -1
- package/dist/content/cookies/githands/en.json +3 -3
- package/dist/content/cookies/hust/en.html +1 -1
- package/dist/content/cookies/hust/en.json +3 -3
- package/dist/content/cookies/traduora/en.html +1 -1
- package/dist/content/cookies/traduora/en.json +3 -3
- package/dist/content/dpa/ever-demand/en.html +2 -2
- package/dist/content/dpa/ever-demand/en.json +3 -3
- package/dist/content/dpa/ever-rec/en.html +2 -2
- package/dist/content/dpa/ever-rec/en.json +3 -3
- package/dist/content/dpa/ever-teams/en.html +2 -2
- package/dist/content/dpa/ever-teams/en.json +3 -3
- package/dist/content/dpa/ever-works/en.html +2 -2
- package/dist/content/dpa/ever-works/en.json +3 -3
- package/dist/content/dpa/gauzy/en.html +2 -2
- package/dist/content/dpa/gauzy/en.json +3 -3
- package/dist/content/dpa/githands/en.html +2 -2
- package/dist/content/dpa/githands/en.json +3 -3
- package/dist/content/dpa/hust/en.html +2 -2
- package/dist/content/dpa/hust/en.json +3 -3
- package/dist/content/privacy/ever-corporate/en.html +3 -3
- package/dist/content/privacy/ever-corporate/en.json +3 -3
- package/dist/content/privacy/ever-demand/en.html +3 -3
- package/dist/content/privacy/ever-demand/en.json +3 -3
- package/dist/content/privacy/ever-rec/en.html +3 -3
- package/dist/content/privacy/ever-rec/en.json +3 -3
- package/dist/content/privacy/ever-teams/en.html +3 -3
- package/dist/content/privacy/ever-teams/en.json +3 -3
- package/dist/content/privacy/ever-tech/en.html +3 -3
- package/dist/content/privacy/ever-tech/en.json +3 -3
- package/dist/content/privacy/ever-works/en.html +3 -3
- package/dist/content/privacy/ever-works/en.json +3 -3
- package/dist/content/privacy/everiq/en.html +3 -3
- package/dist/content/privacy/everiq/en.json +3 -3
- package/dist/content/privacy/gauzy/en.html +3 -3
- package/dist/content/privacy/gauzy/en.json +3 -3
- package/dist/content/privacy/githands/en.html +3 -3
- package/dist/content/privacy/githands/en.json +3 -3
- package/dist/content/privacy/hust/en.html +3 -3
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +3 -3
- package/dist/content/privacy/traduora/en.json +3 -3
- package/dist/content/refund/ever-works/en.html +2 -2
- package/dist/content/refund/ever-works/en.json +3 -3
- package/dist/content/refund/gauzy/en.html +2 -2
- package/dist/content/refund/gauzy/en.json +3 -3
- package/dist/content/refund/githands/en.html +2 -2
- package/dist/content/refund/githands/en.json +3 -3
- package/dist/content/refund/hust/en.html +2 -2
- package/dist/content/refund/hust/en.json +3 -3
- package/dist/content/security/ever-demand/en.html +1 -1
- package/dist/content/security/ever-demand/en.json +3 -3
- package/dist/content/security/ever-rec/en.html +1 -1
- package/dist/content/security/ever-rec/en.json +3 -3
- package/dist/content/security/ever-teams/en.html +1 -1
- package/dist/content/security/ever-teams/en.json +3 -3
- package/dist/content/security/ever-works/en.html +1 -1
- package/dist/content/security/ever-works/en.json +3 -3
- package/dist/content/security/gauzy/en.html +1 -1
- package/dist/content/security/gauzy/en.json +3 -3
- package/dist/content/security/githands/en.html +1 -1
- package/dist/content/security/githands/en.json +3 -3
- package/dist/content/security/hust/en.html +1 -1
- package/dist/content/security/hust/en.json +3 -3
- package/dist/content/subprocessors/ever-corporate/en.html +1 -1
- package/dist/content/subprocessors/ever-corporate/en.json +3 -3
- package/dist/content/subprocessors/ever-demand/en.html +1 -1
- package/dist/content/subprocessors/ever-demand/en.json +3 -3
- package/dist/content/subprocessors/ever-rec/en.html +1 -1
- package/dist/content/subprocessors/ever-rec/en.json +3 -3
- package/dist/content/subprocessors/ever-teams/en.html +1 -1
- package/dist/content/subprocessors/ever-teams/en.json +3 -3
- package/dist/content/subprocessors/ever-tech/en.html +1 -1
- package/dist/content/subprocessors/ever-tech/en.json +3 -3
- package/dist/content/subprocessors/ever-works/en.html +1 -1
- package/dist/content/subprocessors/ever-works/en.json +3 -3
- package/dist/content/subprocessors/everiq/en.html +1 -1
- package/dist/content/subprocessors/everiq/en.json +3 -3
- package/dist/content/subprocessors/gauzy/en.html +1 -1
- package/dist/content/subprocessors/gauzy/en.json +3 -3
- package/dist/content/subprocessors/githands/en.html +1 -1
- package/dist/content/subprocessors/githands/en.json +3 -3
- package/dist/content/subprocessors/hust/en.html +1 -1
- package/dist/content/subprocessors/hust/en.json +3 -3
- package/dist/content/subprocessors/traduora/en.html +1 -1
- package/dist/content/subprocessors/traduora/en.json +3 -3
- package/dist/content/tos/ever-corporate/en.html +3 -3
- package/dist/content/tos/ever-corporate/en.json +3 -3
- package/dist/content/tos/ever-demand/en.html +3 -3
- package/dist/content/tos/ever-demand/en.json +3 -3
- package/dist/content/tos/ever-rec/en.html +3 -3
- package/dist/content/tos/ever-rec/en.json +3 -3
- package/dist/content/tos/ever-teams/en.html +3 -3
- package/dist/content/tos/ever-teams/en.json +3 -3
- package/dist/content/tos/ever-tech/en.html +3 -3
- package/dist/content/tos/ever-tech/en.json +3 -3
- package/dist/content/tos/ever-works/en.html +3 -3
- package/dist/content/tos/ever-works/en.json +3 -3
- package/dist/content/tos/everiq/en.html +3 -3
- package/dist/content/tos/everiq/en.json +3 -3
- package/dist/content/tos/gauzy/en.html +3 -3
- package/dist/content/tos/gauzy/en.json +3 -3
- package/dist/content/tos/githands/en.html +3 -3
- package/dist/content/tos/githands/en.json +3 -3
- package/dist/content/tos/hust/en.html +3 -3
- package/dist/content/tos/hust/en.json +3 -3
- package/dist/content/tos/traduora/en.html +3 -3
- package/dist/content/tos/traduora/en.json +3 -3
- package/dist/index.json +144 -144
- package/package.json +1 -1
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "18262f49d38f0fc1bc4415459f58ed47058a6afb9ea2476d6cbc6b3f51533231",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/privacy/010-introduction-and-scope",
|
|
@@ -376,5 +376,5 @@
|
|
|
376
376
|
}
|
|
377
377
|
],
|
|
378
378
|
"path": "content/privacy/githands/en.html",
|
|
379
|
-
"markdown": "# Privacy Policy\n\n**GitHands** β [githands.com](https://githands.com)\n\nVersion 1.0.1 Β· In force from 2026-08-02\n\nThis notice explains what we do with personal data when you use GitHands Cloud and the websites,\napplications and application programming interfaces we make available at [githands.com](https://githands.com)\n(together, the \"**Service**\"). It tells you what we collect, why, who else sees it, how long we keep it,\nand what you can ask us to do about it.\n\nWe have written it to be read rather than to be defended. Where something is uncomfortable β data we hold\nthat you never gave us, or data your employer decides to collect through our software β we say so plainly\ninstead of burying it in a list.\n\n## What this notice covers\n\n- The website at [githands.com](https://githands.com) and the pages served from it.\n- The GitHands Cloud web application, together with any desktop application, mobile application or\n browser extension we publish for it.\n- The application programming interfaces and integrations we operate for it.\n- The emails, notifications and support conversations that go with it.\n\nA product-specific annex appears later in this notice. It adds detail for GitHands β what it\nactually collects, what is switched off by default, and which controls exist. It sits on top of this\nnotice rather than instead of it, and where it is more specific about GitHands, the annex governs.\n\n## What this notice does not cover\n\n**Other companies' products.** Other companies operate their own websites, products and services, and\npublish their own privacy notices. This notice covers only what is listed above. If a service is not on\nthat list, this notice does not apply to it β whatever it looks like, and whoever links to it.\n\n**Software you run yourself.** Some of our software is published as open source and can be installed on\nyour own infrastructure. **If you run your own deployment, you are the controller of the personal data in\nit β not us.** You choose its hosting, its storage, its email provider and every other component. We have\nno access to that data, we do not process it, we are not your processor for it, and nothing in this notice\ndescribes it. Telling your own users what happens in your deployment is your job, not ours.\n\n**Sites we link to.** The Service links out to third-party websites and services. Once you follow a link\naway from us, the operator of that site decides what happens to your data. We do not control those sites,\nwe do not receive what you do on them, and we are not responsible for them. Read their notices, not this\none.\n\n**Your organisation's own systems.** Where your employer or another organisation uses the Service, it also\nruns systems of its own. This notice covers our part. Its notice covers its part.\n\n## Who we are\n\nThe controller of the personal data described in this notice is **Ever Technologies LTD**, a company\nregistered in Bulgaria under company number 204599535, with its registered office\nat Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n\"Controller\" is the legal term for the organisation that decides why personal data is used and how.\nWherever this notice says we make that decision, **Ever Technologies LTD is the organisation accountable to\nyou** β and to the Commission for Personal Data Protection (ΠΠΎΠΌΠΈΡΠΈΡ Π·Π° Π·Π°ΡΠΈΡΠ° Π½Π° Π»ΠΈΡΠ½ΠΈΡΠ΅ Π΄Π°Π½Π½ΠΈ) (CPDP), which\nis our lead supervisory authority.\n\nEver Technologies LTD operates GitHands Cloud and is the company you contract with for it. There\nis no other operator behind us and no second company you have to chase to get an answer.\n\nYou can reach us about anything in this notice at privacy@ever.co, or by post at the registered office\nabove.\n\nThere are parts of this notice where we are deliberately **not** the controller: where a customer puts\npersonal data about its own people into the Service, that customer decides, and we act on its instructions.\nThat split matters, so it has its own section below.\n\n## Other companies in our group\n\nThere is one other company in our group, and its role is narrow enough to state in a sentence.\n\n**Ever Co. LTD**, a company registered in Israel under company number\n515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual\nproperty in the software. Ever Technologies LTD operates the Service under licence from it.\n\nThat is the entire relationship. Its consequences are worth stating positively rather than leaving you to\nwork them out:\n\n- **Ever Co. LTD does not access personal data held in the Service.** No administration console,\n no production database, no support tooling, no backups, no error reports.\n- It is **not a controller** of that data, **not a processor** of it, and **not a sub-processor**. It does\n not appear on our sub-processor list, because there is nothing for it to appear against.\n- **No personal data is transferred to it.** No international transfer to Israel arises out of\n your use of the Service, because none happens.\n\nOwning software is not the same as having access to the data that software holds, and we have kept the two\napart on purpose.\n\nIf that ever changes β if Ever Co. LTD were to take on any role involving personal data from the\nService β we would update this notice before it happened, name the role, disclose the transfer and the\nsafeguard we relied on, and add it to our sub-processor list. **Until you read that here, none of it is\nhappening.**\n\n## Data protection contact\n\n**We have not designated a Data Protection Officer.** Article 13(1)(b) of the GDPR asks a controller to\npublish a Data Protection Officer's contact details where one has been designated. None has been designated\nat Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a\nmailbox name imply otherwise. We keep the question under review, and if it changes we will publish the\ndetails here.\n\nWhat we do publish is a contact route that is monitored and acted on. **Privacy questions and requests to\nexercise your rights are handled through these addresses:**\n\n- **privacy@ever.co** β use this for anything about this notice, about the personal data we hold, or to\n make a request under any of your rights.\n- **dpo@ever.co** β an alias that reaches the same people. It exists because procurement forms,\n security questionnaires and privacy tooling routinely expect an address in that form. **It is a routing\n alias, not an office. Nothing about it means a Data Protection Officer has been designated.**\n\nYou can also write to us by post at the registered office given above.\n\nWe will acknowledge your message, and we will answer a request to exercise your rights within one month β\nthe deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may\nextend that by up to two further months. If we do, we will tell you inside the first month and explain\nwhy.\n\n## Who decides what: controller and processor\n\nData protection law splits responsibility in two. The **controller** decides why personal data is used and\nhow. The **processor** only acts on the controller's instructions. Which of the two we are is not a\nformality β it decides who you go to, who has to answer you, and who is accountable when something goes\nwrong.\n\nOur position depends on whose data it is. There are three cases. We set them out here, in the privacy\nnotice, rather than leaving them to a data processing agreement, because the person most affected by the\nsecond case is usually the person least likely to read a contract.\n\n### 1. Our own relationship with you β we are the controller\n\nWhere we decide, we are accountable. **We are the controller** for:\n\n- registration and account identity β the name, email address and credentials used to create and hold an\n account;\n- billing, payments, invoices, tax records and collections;\n- support conversations, including the tickets, emails, chats and attachments themselves;\n- security, fraud prevention, abuse handling and audit logging;\n- our own websites and their analytics, our newsletters, and our marketing to prospective customers; and\n- running our business β accounting, insurance, professional advice, and defending claims.\n\nEverything in this notice about purposes, legal bases, retention, transfers and your rights applies to this\nfirst case directly, and you exercise those rights against us.\n\n### 2. Personal data a customer puts into the Service about its own people β the customer is the controller\n\nWhen an organisation subscribes to the Service and uses it to run its business, the personal data it puts\nin is **its** data. It decides what to collect, which features to switch on, why, and for how long to keep\nit. **We process that data only on that organisation's instructions.** For it, the organisation is the\ncontroller and we are the processor.\n\nThis covers the ordinary contents of a workspace β employee and contractor records, contact details,\nprojects, tasks, documents and messages. It also covers the parts that matter most, where a product\nprovides them and the customer has enabled them:\n\n- **time-tracking data** β timers, timesheets, time entries and the records behind them;\n- **activity data** β how much keyboard and mouse activity occurred in a period, idle time, and which\n applications and websites were in use;\n- **screen and media capture** β periodic screenshots and, where separately switched on, webcam stills,\n audio recordings and screen recordings.\n\n**We do not decide to collect any of this. The customer does.** We build the features, we document what\neach one captures and what each control does, and we run them exactly as the customer configures them. We\ndo not use that data for our own purposes, we do not use it to train models, and we do not look at it\nexcept where we must in order to run, secure or support the Service.\n\nWhat GitHands can capture, what is off by default, and which controls exist is set out in the annex\nlater in this notice.\n\n### 3. Data a customer holds about its own clients and end users β the customer is the controller\n\nWhere a customer uses the Service to serve its own clients, members, applicants, patients or website\nvisitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the\nprocessor, and the customer owes those people the notice and the answers. If you have dealt with an\norganisation and want to know what it holds about you, ask that organisation.\n\n### If you are monitored at work, this part is for you\n\nWe would rather tell you directly than make you work it out from a contract you have never seen.\n\n**Your employer decides what is captured. We do not.** Screenshots, activity rates, application and website\nusage, webcam stills, audio, screen recordings β each of these is a setting your employer switches on or\nleaves off, for the organisation and, where the product allows it, for individual people. We cannot switch\nthem on for your employer, and we do not switch them on for ourselves.\n\n**Your employer is the controller of that data.** That means your employer, not us:\n\n- must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,\n which differs sharply from country to country;\n- must tell you, before it starts, what is captured, how often, why, and how long it is kept;\n- must carry out a data protection impact assessment where one is required, and act on what it finds;\n- must consult a works council, employee representatives or a trade union where its national law requires\n that; and\n- must answer your requests about that data.\n\n**We make no claim that monitoring employees is lawful across the European Union, because it is not.** Some\ncountries restrict it tightly, some require consultation before it starts, and some prohibit particular\nforms of it outright. Whether your employer's use of these features is lawful where you work is your\nemployer's responsibility. We require every customer to confirm to us that it has dealt with each of the\npoints above before it uses these features.\n\n**How to exercise your rights over monitoring data.** Send your request to your employer β it holds the\ndata and it has to answer you. If you send it to us instead, we will not ignore it:\n\n- we will forward it promptly to the customer whose workspace holds the data;\n- we will tell you that we have done so, and to whom, so you are not left waiting on silence; and\n- we will help that customer find, correct, export or delete the data, which is what our contract with it\n requires of us.\n\n**What we will not do is release one organisation's data to someone else on request.** We cannot verify an\nemployment relationship from the outside, and handing over a workspace's contents to a person the customer\nhas not authorised would be a breach in its own right. That restraint protects you as much as it\nconstrains you.\n\nIf you think your employer is monitoring you unlawfully, you can complain to the data protection authority\nin your own country, and to your national labour authority. You do not need our permission, and you do not\nneed to come through us first.\n\n## Personal data we collect\n\nWe group this by where the data comes from, because that is what determines what we know about you and what\nwe owe you.\n\nNot every category applies to every product, plan or user. This section describes the shape of what we\ncollect; the annex later in this notice lists what GitHands actually collects.\n\n### What you give us\n\n- **Account identity** β your name, username, email address, password (held only as a hash), profile\n picture, job title, preferred language and time zone.\n- **Organisation details** β the organisation you belong to, your team, your role and permissions within\n it, and who invited you.\n- **Contact details** β email address, telephone number and postal address, where you provide them.\n- **Billing details** β billing name and address, VAT or tax identification number, the plan you are on,\n invoices and payment history. **We do not receive or hold your full card number** β that goes straight to\n our payment processor.\n- **Support correspondence** β the tickets, emails, chat messages, screenshots and files you send when you\n ask for help, and our replies.\n- **Content you submit** β everything you or your organisation puts into the Service: documents, tasks,\n projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as\n processor, not as controller.\n- **Anything else you volunteer** β survey answers, feedback, event registrations, newsletter sign-ups, and\n whatever you choose to write to us.\n\n### What we collect automatically when you use the Service\n\n- **Device and browser data** β device type, operating system, browser and version, screen size, language,\n and the version of our application you are running.\n- **Connection data** β your IP address, and the approximate location it indicates. **That is\n city-or-region level, derived from the IP address**, and it is not satellite positioning. Where a\n specific feature collects precise location, it says so.\n- **Usage data** β pages and screens viewed, features used, actions taken, navigation paths, timestamps and\n the page that referred you.\n- **Logs** β server and application logs of requests, errors, response times, sign-ins, failed sign-ins and\n administrative actions, with the identifiers needed to tie an entry to an account.\n- **Diagnostics** β crash reports, stack traces and performance traces. These can incidentally contain\n whatever was in the request that failed.\n- **Cookies and similar technologies** β cookies, local storage, pixels, software development kit\n identifiers and comparable device storage. What each is for, and which ones need your consent, is in our\n [Cookie Policy](https://githands.com/cookies).\n\n### What we receive from other people\n\n- **Identity providers** β if you sign in with a third-party account, we receive that account's identifier,\n your email address, your display name and usually your profile picture, plus confirmation that the\n sign-in succeeded. **We never receive your password for it.**\n- **Payment processors** β whether a payment succeeded or failed, the payment method type, the last four\n digits and expiry of a card, the billing country, and any dispute or chargeback.\n- **Integrations you or your administrator connect** β whatever the connected service returns within the\n permissions granted. That varies by integration and is shown to you when you authorise it.\n- **Your organisation** β where an administrator creates your account, invites you, sets your role or\n imports records about you.\n- **Other sources**, where a particular product uses them. Those are set out in the next section and in the\n annex.\n\n### What you have to give us\n\nSome of it is unavoidable. Without account identity we cannot create an account for you; without billing\ndetails we cannot take payment for a paid plan; without certain records we cannot meet our own legal\nobligations. Where data is necessary in that sense, **not providing it means we cannot provide that part of\nthe Service** β but nothing worse follows.\n\nEverything else β an optional profile field, a newsletter subscription, an integration you could simply not\nconnect β is genuinely optional, and declining it costs you nothing.\n\n## Data we do not collect\n\nShorter than the previous section, and just as binding. These are commitments about how the Service is\nbuilt, not aspirations.\n\n- **We do not sell personal data.** Not to data brokers, not to advertisers, not to anyone β and not under\n the broader definitions of \"sell\" or \"share\" used outside the European Union.\n- **We do not buy marketing lists.** If we contact you about our products it is because you gave us your\n details, or because you are already a customer. We do not purchase your name from someone else in order\n to email you.\n- **We do not use your content to train machine-learning models** β not for our own purposes, and not for\n the benefit of other customers. Where a product has an AI feature, it processes your content to produce\n your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively\n choose, described before you choose it.\n- **We do not run advertising inside the Service.** No third-party advertising, no behavioural ad\n targeting, no cross-site advertising identifiers in the product.\n- **We do not record what you type.** Where a product measures keyboard and mouse activity, it counts\n events over a period. **There is no keylogger in our software. The content of your keystrokes is never\n captured, stored or transmitted.**\n- **We do not ask for special-category data** β health, racial or ethnic origin, religious or philosophical\n beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric\n data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is\n about what can end up inside a screenshot, and it has its own section below.\n- **We do not store full card numbers or card security codes.** Those are entered on our payment\n processor's systems and never reach ours.\n- **We do not collect precise location by default.** Where a product uses location at all, it is because a\n specific feature needs it, and that feature says so.\n\nIf you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it\nas a defect in the product, not as a disagreement about wording.\n\n## Where data comes from when it does not come from you\n\nNot all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it\ncame from, and this section does that.\n\n- **Your employer, or the administrator of your workspace.** Where an organisation subscribes to the\n Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies\n your name, work email address, job title, team, role and permissions, and whatever else the organisation\n chooses to hold about you in its workspace. **For that data the organisation is the controller**, as set\n out above.\n- **Identity providers.** If you sign in with a third-party account, that provider supplies the account\n identifier, your email address, your display name and usually a profile picture, and confirms the sign-in\n succeeded. It supplies nothing else, and never a password.\n- **Integrations you or your administrator connect.** A connected service supplies whatever the permissions\n you granted allow β for example issues and repositories from a code host, messages and channel names from\n a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when\n the connection is authorised, and it can be revoked in the same place.\n- **Payment processors and resellers.** They supply the outcome of a payment, the payment method type, the\n last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not\n pass us the card itself.\n- **Publicly available sources, where a product builds profiles from them.** Some products work with\n information people have published themselves β a public code-hosting profile, a public company page, a\n public professional listing. Where a product does this, the annex names the categories taken and the\n sources they came from, explains the basis we rely on, and says how to object. **If we hold a profile\n about you that you never gave us, you can object to it and we will act on that.**\n- **Service providers acting for us.** Fraud and abuse signals, delivery and bounce information from the\n systems that send our email, and security intelligence about addresses and networks.\n\nWhere we are the controller of personal data that did not come from you, we will tell you within a\nreasonable period and at the latest within one month of obtaining it β or, if we use it to contact you, at\nthat first contact. Where informing every individual separately would take disproportionate effort, this\nnotice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.\n\n## Why we use personal data, and on what legal basis\n\nArticle 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than\na general list of all six bases β you can check us against each line.\n\n| Purpose | Personal data used | Lawful basis |\n|---|---|---|\n| Providing GitHands Cloud: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you | Account identity, organisation and role, credentials, content you submit, device and connection data | **Contract** β Art 6(1)(b). Necessary to perform our agreement with you |\n| Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment | Billing details, plan and subscription data, invoices, payment outcomes | **Contract** β Art 6(1)(b) |\n| Keeping accounting, tax and invoicing records | Invoices, payment records, billing identity | **Legal obligation** β Art 6(1)(c), under tax and accounting law |\n| Support: answering your questions, investigating faults and reproducing problems you report | Support correspondence, account identity, logs and diagnostics, and whatever you point us at | **Contract** β Art 6(1)(b) where you are a customer. **Legitimate interests** β Art 6(1)(f) where you are not, so that we can answer anyone who writes to us |\n| Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure | Account identity, IP address, device data, request logs, sign-in and failed sign-in records | **Legitimate interests** β Art 6(1)(f) in keeping the Service and the people who use it safe |\n| Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups | Logs, diagnostics, usage data, account identifiers | **Legitimate interests** β Art 6(1)(f) in operating a reliable service |\n| Understanding how the Service is used, so we can improve it | Usage events, feature interactions, device and browser data, aggregated statistics | **Legitimate interests** β Art 6(1)(f). **Consent** β Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our [Cookie Policy](https://githands.com/cookies) |\n| Marketing to people who are not yet customers: newsletters, product announcements and events | Contact details, marketing preferences, whether you opened or clicked a message | **Consent** β Art 6(1)(a), which you can withdraw at any time |\n| Marketing our own similar products to an existing customer who gave us their address during a sale, with an opt-out in every message | Contact details, the products you already have | **Legitimate interests** β Art 6(1)(f), relying on the narrow existing-customer exception in the ePrivacy rules |\n| Meeting legal obligations: responding to lawful requests from authorities, sanctions and export-control checks, statutory record-keeping, and our own data protection duties | Whatever the specific obligation requires, and no more | **Legal obligation** β Art 6(1)(c) |\n| Establishing, exercising or defending legal claims, and handling complaints, disputes, audits, insurance and corporate transactions | Account and billing records, correspondence, and the logs relevant to the matter | **Legitimate interests** β Art 6(1)(f) in protecting our legal position |\n\nTwo things this table deliberately does not cover.\n\n**Where we act as processor**, the lawful basis is not ours to pick. The customer that put the data into\nthe Service decides the purpose and must have its own basis for it. See the controller and processor\nsection above.\n\n**Where we rely on your consent**, you can withdraw it at any time, and withdrawing it is as easy as giving\nit. Withdrawing consent does not make earlier processing unlawful β it stops the processing from that point\non.\n\n## The legitimate interests we rely on\n\nWhere the table above says \"legitimate interests\", the law requires us to tell you what that interest\nactually is β not simply to name the basis and move on. For each one we have asked three questions: what is\nthe interest, is the processing genuinely necessary for it, and is it fair to you. That last question is\nthe balancing test, and we keep a written record of it.\n\n### Keeping the Service and its users secure\n\n- **The interest:** preventing unauthorised access, account takeover, fraud, spam, denial-of-service and\n abuse of the Service.\n- **Why the processing is necessary:** you cannot see an attack without looking at the traffic. Sign-in\n records, IP addresses, device data and request logs are what make an intrusion visible at all.\n- **Why it does not override your rights:** the data is limited to what security work needs, it is kept for\n a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody\n reasonably expects a service to be run without security logging.\n\n### Keeping the Service running\n\n- **The interest:** operating a reliable service β monitoring, error tracking, debugging, capacity planning\n and backups.\n- **Why the processing is necessary:** faults surface in logs, and a crash report is only useful if it\n records what was happening when the crash occurred.\n- **Why it does not override your rights:** it is operational data, kept for short periods, used to fix\n software rather than to form views about people, and reachable only by the staff who need it.\n\n### Understanding how the Service is used\n\n- **The interest:** knowing which features are used, where people get stuck, and what to build or fix next.\n- **Why the processing is necessary:** the alternative is guessing. Aggregate usage data is the only\n practical way to see this without interrogating every user.\n- **Why it does not override your rights:** we analyse it in aggregate rather than to make decisions about\n you individually, and wherever cookies or similar device storage are involved we ask for your consent\n instead of relying on this interest at all.\n\n### Answering people who write to us without an account\n\n- **The interest:** replying to a question from someone who is not a customer.\n- **Why the processing is necessary:** we cannot answer you without keeping your message and your address.\n- **Why it does not override your rights:** you chose to contact us, we use it only to answer, and we keep\n it no longer than the matter and any follow-up require.\n\n### Telling existing customers about our own similar products\n\n- **The interest:** letting people who already buy from us know about the products next to the one they\n bought.\n- **Why the processing is necessary:** it uses the address they gave us during that sale, and there is no\n less intrusive way to reach them.\n- **Why it does not override your rights:** it is confined to our own similar products, every message\n carries a one-click opt-out, and an opt-out is acted on immediately and permanently.\n\n### Running and protecting our business\n\n- **The interest:** accounting, audit, insurance, professional advice, complaints, disputes, enforcing our\n terms, and evaluating or completing a corporate transaction.\n- **Why the processing is necessary:** these are ordinary obligations of operating a company, and each one\n needs the records that relate to it.\n- **Why it does not override your rights:** the data is confined to the matter in hand, access is narrow,\n and a great deal of it we are required to keep in any event.\n\n### Your right to object\n\n**You can object to any processing we base on legitimate interests, at any time, by writing to\nprivacy@ever.co.** Tell us which processing, and where you can, why β your particular situation is part\nof the balance. We will stop unless we can show compelling legitimate grounds that override your interests,\nrights and freedoms, or unless we need the data to establish, exercise or defend legal claims.\n\n**If you object to direct marketing there is no balancing at all. We stop.** That right is absolute.\n\nYou can also ask us for a summary of the balancing test behind any interest listed above, and we will give\nyou one.\n\n## Special categories of data\n\nSome personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic\norigin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,\nbiometric data used to identify someone, data concerning health, and data about a person's sex life or\nsexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.\n\n**We do not seek any of it.** We do not ask for it at sign-up, in billing or in support. There are no\nfields for it, we do not infer it, and we do not enrich profiles with it. Please do not send it to us in a\nsupport ticket either β if you need to show us something sensitive to get help, redact it first.\n\n### The honest caveat: incidental capture\n\nWhere a customer switches on screen capture, webcam capture or audio capture, **what gets captured is\nwhatever is there**. A screenshot taken while someone has a hospital appointment email open captures health\ndata. A webcam still can show a religious head covering. An audio recording can pick up a background\nconversation that has nothing to do with work.\n\nThat is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a\nscreen or a room on a timer, and it is true of every product that does it, ours included.\n\n### Whose responsibility it is\n\n**The customer that switches these features on is the controller of what they capture**, including anything\nspecial-category that comes with it. So the customer, not us:\n\n- decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;\n- must carry out a data protection impact assessment before starting, and act on what it finds β capture of\n this kind will normally require one;\n- must have a lawful basis, and where special-category data is realistically in scope must also satisfy\n Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between\n employer and employee;\n- must configure the product to reduce that risk rather than accept it; and\n- must deal with what has been captured, including deleting a capture that should never have been taken.\n\nWe are the processor for it. We do not decide to capture anything, we do not review captures for our own\npurposes, and we act on the customer's configuration and instructions.\n\n### The levers, and using them\n\nWhere a product offers screen or media capture, it also offers controls that materially reduce this risk.\nDepending on the product, those include:\n\n- switching capture off entirely, for the whole organisation or for an individual person;\n- switching off the more intrusive capture types β webcam stills, audio and screen recording β while\n keeping the rest;\n- reducing how often captures are taken;\n- blurring captured images;\n- shortening how long captures are kept, and deleting them automatically at the end of that period;\n- letting people see what has been captured about them; and\n- deleting an individual capture.\n\n**If you are a customer, these are yours to set, and the defaults are not a recommendation.** Choose the\nleast intrusive configuration that meets the purpose you actually have, and write down why you chose it.\nThat record is what a supervisory authority will ask for.\n\n**If you are being monitored and something sensitive has been captured, ask your employer to delete it.**\nYour employer can do that in the product. If you tell us instead, we will forward your request and help\nyour employer act on it, as described in the controller and processor section above.\n\nWhich of these controls GitHands provides, and what its defaults are, is set out in the annex later\nin this notice.\n\n## GitHands: the people in this Service who never signed up\n\nThis annex is unlike every other product annex we publish, and the reason is worth putting in the first\nline rather than the fifteenth. **Most of the personal data in GitHands Cloud is about developers\nwho have never used it.** They did not create an account, they did not agree to anything, and nothing they\ndid was addressed to us. We collected their data from public sources, we added inferences of our own to it,\nand some of them are then sent a message.\n\n**If you are reading this because you received an email you did not ask for, or because you found your own\nname on a GitHands page, this section is written for you and not for our customers.** It is the\nnotice Article 14 of the GDPR requires us to give you when we hold data about you that did not come from\nyou, and everything you need in order to make us stop is in it. Nothing below is behind an account.\n\n### What the Service does\n\nA customer names a public code repository, or writes a brief describing the kind of developer it wants to\nreach. The Service then:\n\n- **enumerates the people publicly associated with that repository** β the accounts that starred it or\n forked it, its contributors, the people who commented on its issues, reviewed its pull requests or joined\n its discussions, and the followers of the organisation that owns it. For a curated \"awesome list\" it does\n the same for the repositories the list points at;\n- **finds a contact address** for each person, by the routes set out below;\n- **builds a profile** of that person from their public activity, and adds scores and inferences we\n generate ourselves;\n- **drafts a message** with a language model, personalised to that person, and sends it β as one message or\n as a sequence spread over time; and\n- **records what happened to it** β whether it was delivered, opened, clicked, replied to, bounced or\n unsubscribed from.\n\n**For all of that, Ever Technologies LTD is the controller.** We are not acting on a customer's instructions\nwhen we decide to build this database, what to infer from it or how long to keep it β we decide that. So\nthe rights in this policy run against us directly, and you do not have to find out which of our customers\nholds your record before anyone will answer you.\n\n### Where your data came from\n\nEverything we hold about a person who is not a user came from one of these, and from nothing else:\n\n- **the public GitHub REST, GraphQL, Search and Events APIs**, and the equivalent public GitLab endpoints;\n- **public repository pages** β stargazer lists, fork lists, contributor lists, issue and pull-request\n participants, discussion participants, and organisation follower lists;\n- **public commit metadata** β the author and committer name, email address and date recorded in a public\n commit;\n- **public profile fields** β username, display name, avatar, biography, company, location, personal site,\n linked social handle, follower and repository counts, and the \"available for hire\" flag if you have set\n it; and\n- **public dependency manifests** in your public repositories, read to work out which technologies you use.\n\n**Every record carries a provenance flag saying which of those it came from.** If you ask us where we got\nyour data, we can tell you which route it arrived by rather than gesturing at \"public sources\".\n\nWe plan to add professional networking platforms as a further source. **We will not do so without updating\nthis annex first**, and the notice you receive at first contact will name the actual source your record\ncame from, not a general list.\n\n### Your email address, and how we got it\n\nThis is the part of the processing most people find surprising, so it gets its own section rather than a\nbullet. We look for a contactable address in four places, in this order, and stop at the first that works:\n\n1. **the email address published on your profile**, where you have chosen to publish one;\n2. **the author or committer address recorded in the commits of the repository being searched**, where you\n have committed to it;\n3. **the author or committer address in commits across your own most recently updated public repositories**;\n and\n4. **the address carried in the public push-event stream** for your account.\n\nWe discard the anonymised `noreply` addresses that GitHub issues, because contacting one is pointless.\nWe do not guess addresses, we do not generate permutations of a name against a company domain, and we do\nnot buy address lists.\n\n**An address you put in a commit was published so that your work could be attributed to you, not so that\nsomebody could sell to you.** We know that, and we are not going to pretend otherwise. Routes 2, 3 and 4\nabove take an identifier published for one purpose and use it for another, and that is the single hardest\npart of this processing to justify. We treat it accordingly: those records carry the provenance flag that\nsays so, we hold them to the same objection and deletion routes as everything else, and if you tell us to\nstop we do not ask you why.\n\n### What we work out about you\n\nAlongside what we collected, we generate our own assessments. These are ours, not yours, and none of them\nis verified:\n\n- an **engagement score** from 0 to 100 and a label for it β Champion, Hot, Warm or Cold;\n- an **intent tier**, estimating how likely you are to be looking for a tool of the kind being marketed;\n- an **influence score**, a network rank and a cluster, derived from a graph of relationships between\n accounts;\n- a **contributor class** and a contribution-depth score;\n- an **activity trend**, and any technology migrations we think we can see in your history;\n- a **technology fingerprint**, parsed from the dependency manifests in your public repositories;\n- a **numeric embedding** of your profile, which is what makes \"find developers similar to this one\"\n possible;\n- an **approximate time zone, a confidence figure for it, and your likely working hours**, inferred from\n the timestamps on your public commits; and\n- an **employment life stage** β job hunting, recently hired, exploring, building or settled β with a\n confidence figure.\n\nTwo of those deserve to be named rather than buried in a list. **Inferring your working hours from commit\ntimestamps is an inference about your daily routine and roughly where in the world you are.** And\n**inferring that you may be job hunting is an inference about your employment situation**, drawn from\npublic activity that you did not publish in order to say anything of the kind.\n\n**All of these are opinions produced by software from partial signals, and any of them can simply be\nwrong.** Our terms forbid a customer from treating them as facts about you, and forbid using them to decide\nanything about your employment, credit, insurance, housing or access to a service. The\n[Acceptable Use Policy](https://githands.com/aup) puts that in binding terms.\n\n### Why we think we are allowed to do this\n\nThe lawful basis for building and using this database is **our legitimate interests, Article 6(1)(f)**. The\nlaw requires us to weigh that interest against your rights, and to be able to show our working. Here it is\nin summary; ask privacy@ever.co and we will send you the full assessment.\n\n- **The interest.** Reaching the specific developers most likely to want a developer tool, instead of\n advertising it to everybody.\n- **Why the processing is necessary for it.** The signal that a person cares about a particular technology\n is their public activity around it. There is no less intrusive route to the same result β untargeted\n advertising is not a lesser interference with *you*, it is a larger interference with everyone else, and\n it does not work.\n- **Where the balance is thinnest, stated honestly.** Publishing code under your own name does not mean you\n expected to be marketed to, and a data protection authority has said as much about a comparable service.\n Our interest does not automatically win. What makes the balance defensible is the mitigations, not the\n purpose β which is why we treat them as commitments rather than as good intentions.\n- **The mitigations we rely on.** Business-context data only. Nothing from a private repository or a\n private profile. A provenance flag on every record so we can always tell you where it came from. A\n permanent, one-click, no-questions objection. Suppression that covers every customer and never expires.\n Retention limits that expire rather than renew. No special-category data, sought or inferred. No sale of\n the database to anybody.\n- **Our conclusion.** The interest is legitimate and the processing is proportionate **so long as the\n mitigations above actually work.** If one of them stops working, the balance fails β so treat any failure\n of one as something to report to us at privacy@ever.co, and we will treat it as a defect.\n\nWhere a customer imports its own contact list or connects its own CRM, the basis for that data is the\ncustomer's to establish, not ours. See the three flows at the end of this annex.\n\n### Article 14: how you are told, and where we rely on the exception\n\nArticle 14 requires us to tell you that we hold your data, where it came from and what we do with it. There\nare two situations and we handle them differently.\n\n**If we contact you, you are told individually, in that first message.** Every first outbound message\ncarries, in the message itself and not behind a link:\n\n- who the controller is β Ever Technologies LTD, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria, company number\n 204599535 β and how to reach us;\n- **the specific source your record came from**, in plain words: your public profile, the commits of a named\n repository, your own public repositories, or the public event stream;\n- what we hold, what we have inferred, and what the message is for;\n- that the basis is legitimate interests, and that you may object;\n- who receives the data and how long we keep it;\n- your rights, and your right to complain to a supervisory authority; and\n- **a one-click objection link that does not expire.**\n\nThat is Article 14(3)(b) β notice at the latest at the first communication. Because we are contacting you\nanyway, it costs us nothing, so there is no argument for doing less.\n\n**If we hold your record and nobody ever contacts you, this annex is the notice.** Here we rely on the\nexception in **Article 14(5)(b)** for disproportionate effort, and we want the reasoning on the record\nrather than asserted:\n\n- notifying a person we hold data about and do not intend to contact would mean **initiating contact for\n the sole purpose of telling them we exist** β which is the intrusion the notice is meant to protect them\n from, delivered to people we were otherwise going to leave alone;\n- so we do what Article 14(5)(b) requires instead: **we make the information public**, in this annex, at a\n stable address, in the same document as the removal route, with no account and no token needed to read\n it; and\n- **we do not claim this exception for anyone we actually email.** Their notice is individual, in the\n message, as above. The exception covers only the records that sit still.\n\nIf you think that reasoning is wrong in your case, say so at privacy@ever.co. You can also put it to a\nsupervisory authority, and you do not need to come through us first.\n\n### How to make us stop, and how to be removed\n\n**Objecting to direct marketing is absolute under Article 21(2). There is no balancing test, no condition,\nno time limit and nothing for us to weigh.** You do not have to give a reason, be a customer, hold an\naccount, or explain how you found us.\n\n**You were added to this database without doing anything at all, so removing yourself takes one action and\nno account.** Any of these works:\n\n- **the objection link in any message you received from us.** It never expires. A link that stops working\n after a few days is not an opt-out, and ours does not;\n- **the removal page at [https://githands.com/remove](https://githands.com/remove)**, which needs no token, no\n sign-in and no prior message from us. Give us the email address or the profile you want removed; or\n- **an email to privacy@ever.co**, which a person reads.\n\nWhat happens then:\n\n- **we act within 24 hours in the ordinary case, and within one month at the outside.** Sending stops\n immediately;\n- **the suppression is platform-wide and permanent.** It is not per-customer and it does not expire. No\n customer of ours can reach you afterwards through this Service, whatever project or account they use;\n- **your profile, your inferences, your scores and your engagement history are deleted**, and you are\n removed from any public page described below;\n- **we keep one thing, and only one: a one-way hash of your address and the date.** We cannot read your\n address back out of it, and its only function is to recognise you if the extraction pipeline encounters\n you again so that you are never re-added. Keeping it is what makes the objection stick, which is why the\n law lets us; and\n- **we tell the customers who already hold your record to delete or suppress it**, and our contract with\n them requires them to do it within five business days.\n\n**One limit, stated plainly because you should not discover it later.** If a customer had already exported\nyour details into its own CRM or mailing tool before you objected, that copy is in a system we do not\ncontrol, and **that customer is the controller of it**. We will tell you which customers we notified, so\nyou can go to them directly. Ask at privacy@ever.co and we will name them.\n\n### What we publish about you\n\nThe Service has public pages for a repository's community, showing named individuals β username, avatar and\nthe engagement score we generated for them β without a sign-in and open to search engines.\n\n**That is a different purpose from outreach, and we treat it as needing its own justification rather than\nriding on the one above.** Publishing an unverified judgement about a named professional is the part of\nthis product we are least comfortable with, and the rights below exist because of that discomfort:\n\n- **you can have your entry taken down** through any of the three routes in the previous section, and\n removal from the public page is immediate rather than queued;\n- **when we take an entry down we also ask the major search engines to drop the cached copy**, and we tell\n you when we have done so; and\n- **objecting to the public page does not require you to object to anything else**, and objecting to\n outreach removes you from the public page as well.\n\n### The tracking inside our messages\n\nMessages sent through the Service carry:\n\n- **an open-tracking image**, a single transparent pixel loaded from our servers, which tells us that the\n message was opened, when, and how many times; and\n- **click-tracking links**, which pass through our servers before going where they say they go.\n\nLoading either one discloses **your IP address, your user agent and the time** to us. That is how the\ntechnique works β there is no version of it that watches without seeing you.\n\nThis is access to information on your own device, so it is regulated separately from data protection, and\nconsent is the rule in the European Economic Area and the United Kingdom. **You did not give it.** So:\n\n- **open tracking is off by default for a recipient whose profile location or inferred time zone places\n them in the EEA or the United Kingdom**, and a customer cannot switch it on for them;\n- your mail client's \"do not load remote images\" setting defeats the pixel entirely, and we would rather\n tell you that than not; and\n- the [Cookie Policy](https://githands.com/cookies) annex covers the rest of what our own pages load.\n\n### Who else sees your data\n\nOur sub-processors are listed in full at\n[https://githands.com/subprocessors](https://githands.com/subprocessors), with what each one does and where it is.\nThree of them deserve to be named here rather than left to the table, because they are the ones a person in\nyour position is least likely to guess.\n\n- **The language-model provider.** Drafting a personalised message means sending your name, your username,\n your email address, your repositories and what we have inferred about you to a model provider, and it is\n forwarded on to the model that actually runs. Classifying your reply means sending the text of your reply.\n- **The AI observability service.** Every one of those prompts, and the completion it produced, is stored as\n a readable trace so we can debug quality and cost. Your data sits there in plain text.\n- **The email delivery provider**, which necessarily receives your address, the message and everything the\n tracking above records.\n\n**None of them is allowed to use your data for its own purposes, or to train models on it.** Most of them\nare established outside the European Economic Area, and the transfers section of this policy sets out the\nmechanism we rely on for each.\n\n### How long we keep it\n\n| What we hold | How long we keep it |\n|---|---|\n| A profile of a person who has never been contacted | **12 months** from when we last verified it against the source. Not renewed by re-finding you: if nothing new happens, it expires |\n| A profile of a person who has been contacted and did not respond | **24 months** from the last message |\n| Inferences, scores, technology fingerprints and embeddings | Deleted as soon as the signals behind them are stale, and in any event with the profile |\n| Message, delivery, open and click records | **24 months** from the send |\n| The text of a reply you sent us, and its classification | **24 months** from receipt, or until you ask us to delete it, whichever is first |\n| An entry on a public community page | For as long as the profile behind it exists, and removed immediately on objection |\n| A suppression record after you object | **Permanently**, as a one-way hash of your address plus the date, and nothing else |\n\n**We do not restart a retention period because your circumstances changed.** Changing employer, starring\nsomething new or pushing a commit does not renew our clock. Only re-verification of a record we are\nentitled to hold does, and only within the limits above.\n\n### Decisions about you\n\n**Nothing in this Service makes a decision that produces a legal effect for you, or that similarly\nsignificantly affects you, by automated means alone.** What it produces is a score, a label and a drafted\nmessage, all of which reach a human being at one of our customers before anything happens.\n\nThey are still profiling, which is why they are set out in full above rather than summarised. And they are\nfenced: our [Acceptable Use Policy](https://githands.com/aup) prohibits any customer from using this Service, or\nanything it outputs, to decide employment, credit, insurance, housing, benefits or eligibility for a\nservice. **We are not a recruitment database, we are not a background-check service, and a customer that\nuses us as one is in breach.**\n\n### What we do not do\n\n- **We do not touch private repositories, private profiles or anything behind a permission.** Only the\n official public APIs of the source platforms, and only what they serve to anybody.\n- **We do not scrape.** No unofficial endpoints, no headless-browser harvesting of pages the API does not\n serve, no circumvention of rate limits or technical protections.\n- **We do not seek or infer special-category data.** No health, beliefs, politics, union membership,\n ethnicity, sex life or sexual orientation. There are no fields for it and we do not want it.\n- **We do not sell the database.** Not to advertisers, not to data brokers, not to recruiters. A customer\n can export the records its own project produced, under contractual duties to honour objections and delete\n on notice; we do not licence the database as a product.\n- **We do not use it for consumer marketing.** This is business-context outreach to a person in their\n professional capacity, and customers are contractually restricted to that.\n\n### The source platforms' own rules\n\nGitHub's Acceptable Use Policies restrict what information gathered from GitHub may be used for, including\nsending unsolicited mail to its users and passing personal information to recruiters. GitLab has its own\nequivalents. Those rules bind the account that does the reading.\n\nSo the reading is done under the customer's own account, which the customer connects in its own name and\nwarrants that it is entitled to use for this purpose. Our [Terms of Service](https://githands.com/tos) annex\nsets out that obligation and the indemnity behind it. **We also reserve the right to retire a source,\nor a method of finding an address, at any time** β including because a platform asks us to β and we will do\nthat without waiting to be compelled.\n\n### If you are a customer: three flows, three roles\n\nWhich of us answers for what depends on where the data came from. There are three cases and they do not\noverlap.\n\n- **Data the Service extracts, enriches and scores from public sources.** **We are the controller.** We\n decide to collect it, we run the enrichment and the scoring, and we answer the objections. Your Data\n Processing Addendum does not cover it, and you cannot instruct us to re-add a person who has objected.\n- **Contacts you import by file, records you sync from your own CRM, and campaign content you write.**\n **You are the controller and we are your processor.** The [Data Processing Addendum](https://githands.com/dpa)\n annex sets out what you warrant about that data before you bring it in.\n- **Records you export, and messages you send.** **You become an independent controller** the moment data\n leaves the Service into your systems, and you are the sender of record for every message. Your own\n Article 13 and Article 14 notices, your own lawful basis, and your own obligation to honour objections\n all attach to you at that point.\n\n### If you run GitHands yourself\n\nThe software is open source and can be run on your own infrastructure. **In your installation we process\nnothing, we hold no data and we are not your processor** β you choose the database, the sending provider,\nthe model provider and the source credentials, and the obligations to the people in your database are\nyours alone.\n\nOne thing does reach us, and we would rather you heard it here than found it in a configuration file.\n\n- **An installation sends us an anonymous heartbeat roughly every 24 hours.** It contains an installation\n identifier, the version, the billing mode, the operating system, architecture, runtime and database\n versions, counts of organisations, users, campaigns, sends and AI calls, counts of errors by a fixed\n error class, which features are switched on, and optionally an operator contact address if you have set\n one.\n- **It contains no recipient data, no message content, no repository or organisation names, no model\n prompts or completions, no credentials and no raw IP addresses.**\n- **You can switch it off**, and switching it off is a supported configuration rather than a hack.\n- **Check the administrator alert address before you go live.** It defaults to an address at our domain, so\n until you change it, alerts about your campaign failures reach us. Set it to your own address.\n\n## Cookies and similar technologies\n\nCookies, local storage, pixels, software development kits and similar technologies get their own document,\nbecause they need more detail than a summary can carry. What each one is, what it does, how long it lasts,\nwho operates it and how to refuse it is set out in our [Cookie Policy](https://githands.com/cookies).\n\nIn short, we sort them into four categories:\n\n- **Strictly necessary** β needed to deliver what you asked for: signing you in, holding your session,\n routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against\n automated abuse. These are not optional, and we do not ask for consent to them.\n- **Preferences** β remember choices you have made, such as language, region and interface settings.\n- **Analytics** β help us understand how the Service is used so we can improve it.\n- **Marketing** β measure our campaigns and help us understand which organisations take an interest in us.\n\n**Nothing in the preferences, analytics or marketing categories is placed or read on your device until you\nagree to it.** You can accept everything, refuse everything, or choose category by category, and refusing\ntakes exactly as few clicks as accepting.\n\n### Changing your mind\n\nYour choices are not permanent. A **Cookie preferences** link sits in the footer of every page on\n[githands.com](https://githands.com) and reopens the same panel you saw the first time. Change a category\nthere and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing\nabout the Service is withheld from you for refusing.\n\nOne analytics tool runs without consent, because it is configured so that it stores and reads nothing on\nyour device and never builds a persistent identifier for you. That is a conditional position, not a\npermanent one: the [Cookie Policy](https://githands.com/cookies) names the tool, describes the exact\nconfiguration we rely on, and says what happens if any part of that configuration ever changes.\n\n## Who receives your personal data\n\nWe disclose personal data only to the categories of recipient below, and only as much as each one needs to\ndo the job it is there for.\n\n- **Service providers acting as our processors** β hosting and infrastructure, storage, content delivery,\n email delivery, error monitoring, product analytics, customer support tooling and similar. They act on\n our documented instructions under a written contract that meets Article 28 GDPR, they are bound to\n confidentiality and appropriate security, and **they may not use your data for their own purposes**.\n- **Payment processors** β to take payment, issue invoices and handle refunds and disputes. For their own\n regulated obligations β fraud prevention, anti-money-laundering, card-scheme rules β they act as\n controllers in their own right, and their own privacy notice governs that part.\n- **Professional advisers** β lawyers, accountants, auditors and insurers, bound by professional\n confidentiality, where we need advice or have to evidence that we have complied with something.\n- **Public authorities, courts and regulators** β where the law requires us to disclose, or where we need\n to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is\n no wider than it needs to be, we push back where it is not, and we tell you about it unless we are\n legally prohibited from doing so.\n- **An acquirer or successor** β if we are reorganised, merged or sold, or if part of the business changes\n hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this\n policy or by a notice at least as protective, and we will tell you before anything about the handling of\n your data changes.\n\n### The sub-processors we engage for the hosted Service\n\nThese providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your\ndata is most likely to reach.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | 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. | United States, with edge termination worldwide | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. | 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. | United States | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | 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. | United States | 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 |\n| OpenRouter, Inc. | 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. | United States, and onward to the selected model provider | 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 |\n| Langfuse GmbH | 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. | Germany | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. dba Sentry | 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. | United States | 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 |\n| PostHog, Inc. | 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. | United States | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | 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. | United States | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | 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. | United Kingdom | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | 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. | Not published by the provider | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n\nThe full and current list, including everything below, is published at\n[https://githands.com/subprocessors](https://githands.com/subprocessors), together with the notice period and\nobjection procedure that apply when we add or replace one.\n\n### Three tiers, and why the difference matters\n\nA single flat list of every vendor that appears anywhere in our software would be both inaccurate and\nmisleading, so the sub-processor page is split into three tiers. They mean genuinely different things.\n\n- **Always engaged.** The providers above. If you use the hosted Service, these are in the path.\n- **Engaged only if you turn something on.** Optional integrations, connectors and features. A provider in\n this tier is engaged only when you or your workspace administrator enables the specific feature or\n connects the specific account it belongs to. Enable nothing and it is never involved. The list says which\n feature or setting activates each one.\n- **Self-hosted deployments only.** Several of our products are published as open source and can be run on\n your own infrastructure. In that case **you** choose the database, object storage, email relay, AI\n provider and everything else, using your own credentials. Those providers appear in the list so you can\n see what the software can be pointed at β but they are **your** providers, not ours. **We process nothing\n in a deployment you run, we are not your processor for it, and the commitments in this policy do not\n describe it.**\n\n### We do not sell your personal data\n\nWe do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not\nsupply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to\nuse it to build advertising or interest profiles, on our sites or anywhere else.\n\n## Sending personal data outside the EEA\n\nMost of the personal data we hold stays inside the European Economic Area, on infrastructure we operate\nourselves. Some of it does not: a number of the providers we engage are established outside the EEA β\nprincipally in the United States β and some of them route, cache or store data on servers outside it.\n\nWhere that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the\nfollowing for every transfer, and the sub-processor page names the destination country and the mechanism\nprovider by provider.\n\n### Adequacy\n\nWhere the European Commission has decided that a country provides an adequate level of protection, the\ntransfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by\nthe Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as\npermanent.\n\n### Providers in the United States\n\nFor a US provider we rely on one of two things.\n\n- **The EUβUS Data Privacy Framework**, but only where that provider is *actively self-certified* under it\n for the type of data concerned. We check the official Data Privacy Framework list when we engage a\n provider and re-check it periodically. **We do not claim the Framework for a provider that has not\n certified, or whose certification has lapsed.**\n- **Standard Contractual Clauses** β the clauses approved by the European Commission in Implementing\n Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact\n assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the\n first place, contractual limits on onward disclosure, and a commitment from the provider to notify and\n where possible challenge a government access request.\n\n**We keep Standard Contractual Clauses in place as the standing mechanism**, including for providers that\nare also certified under the Framework. That is deliberate, and here is the honest reason.\n\nThe Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was\nchallenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in\n*Latombe* (Case T-553/23). **That is not the end of it** β an appeal is pending before the Court of\nJustice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the\nsame court. So we treat the Framework as a mechanism under review rather than a settled answer, and we\nkeep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not\nan interruption for you.\n\n### Other countries\n\nFor a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with\nthe same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,\nthe corresponding UK and Swiss additions are applied to those clauses.\n\nWe rely on an Article 49 derogation β for example, a transfer that is strictly necessary to perform a\ncontract you have asked us to perform β only in a specific, occasional case where no other mechanism fits.\nIt is not a routine mechanism for us, and we do not use it to run a regular data flow.\n\n### Getting a copy of the safeguards\n\nYou are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the\ntransfer you are asking about, and we will send you a copy of the relevant clauses and tell you which\nmodules apply. We may redact commercial terms such as pricing and service levels; we do not redact the\ndata protection terms, which are the part that concerns you.\n\n## How long we keep personal data\n\n\"As long as necessary\" is not an answer, so here are the actual periods. Each one runs from the event in\nthe middle column, and at the end of it we delete the data or irreversibly anonymise it.\n\n| What we hold | How long we keep it | Why that period |\n|---|---|---|\n| Account and profile data β name, email address, workspace membership, settings | For as long as the account is open, then deleted within **30 days** of closure | We need it to give you the account; after that we do not |\n| Content and files you put into the Service | For as long as the account is open; after it ends, available for export for **30 days**, then deleted | You decide what is in it β see below |\n| Invoices, payment records and the tax data attached to them | **10 years** from the end of the accounting year in which the transaction fell | Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request |\n| Record that you accepted our terms β version, date, method | **5 years** after the agreement ends | The general limitation period for a claim under the contract |\n| Support correspondence and tickets | **24 months** from the last message in the thread | Long enough to handle a recurring problem and a follow-up; not longer |\n| Security, access and audit logs | **12 months** | Investigating unauthorised access, and evidencing that we did |\n| Application and error logs, crash reports, diagnostics | **90 days** | Fixing what broke; they lose value quickly |\n| Marketing contact records and the evidence of your consent | Until you object or withdraw. We then remove you from the lists and keep only a suppression record β your email address and the date β so that we do not contact you again | An unsubscribe that forgets you is not an unsubscribe |\n| Cookie and consent choices | As stated in the [Cookie Policy](https://githands.com/cookies), which gives the lifetime of each entry | It belongs with the technology it describes |\n| Backups | Each backup ages out on its own rolling cycle, within **30 days** | Recovering from failure and ransomware, without becoming a second archive |\n| Anything we are required to preserve for a legal claim, investigation or regulatory request | Until the claim, investigation or request ends, including any appeal period | We are not allowed to delete evidence, and neither are you |\n\n### Data that belongs to one of our customers\n\nFor personal data held inside a customer's workspace β including anything the Service captures about that\ncustomer's own personnel β **the customer sets the retention period, not us**. We are their processor for\nit. The defaults and the limits of what they can configure are described in the product annex to this\npolicy.\n\nWe delete that data when the customer instructs us to, or at the end of the export window after their\nagreement ends, whichever comes first. If you are one of their people and you want their data about you\ndeleted sooner, ask them β see the section on your rights, which explains how we route that.\n\n### What \"delete\" means here\n\nDeletion is applied to live systems straight away. Backup copies are not individually edited β doing so\nwould defeat what a backup is for β so a deleted record persists in backups until that backup ages out on\nthe cycle above, at most 30 days. During that window the data is not used for anything, and **we do not\nrestore a backup to bring back data someone asked us to delete**; a backup is restored only to recover a\nwhole system after a failure.\n\nWhere we can keep something useful without keeping you identifiable, we anonymise instead of deleting β\naggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not\npossible for us to re-identify you from it.\n\n## How we protect personal data\n\nWe take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the\nrisk, reviewed as the risk changes. In practice that means the following.\n\n- **Encryption in transit.** Traffic to and from the Service travels over TLS. HTTPS is enforced, and\n plain HTTP requests are redirected rather than served.\n- **Encryption at rest.** The storage holding customer content, databases and backups is encrypted at\n rest, and particularly sensitive values β credentials, tokens and keys β are additionally encrypted at\n the application layer rather than stored in readable form.\n- **Access control and least privilege.** Access to production systems is limited to the people whose job\n needs it, granted by named individual accounts rather than shared logins, protected by multi-factor\n authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or\n someone leaves.\n- **Network segmentation.** Databases, storage and internal services sit on segmented internal networks\n and are not exposed to the public internet. Administrative interfaces are not publicly reachable.\n- **Logging.** Administrative and security-relevant events are logged, retained for the period in the\n retention section, and monitored so that unusual activity raises an alert rather than sitting unread.\n- **Backups.** Data is backed up regularly, held on separate infrastructure from the live systems, and\n restores are tested β an untested backup is a guess, not a control.\n- **Vulnerability management.** Dependencies are scanned, code is analysed automatically before it ships,\n security patches are applied on a defined schedule with a faster path for serious issues, and we operate\n a responsible disclosure route so that anyone who finds a problem can tell us.\n- **Personnel.** Everyone with access is bound by written confidentiality obligations that outlast their\n engagement, works on a need-to-know basis, and has access removed when it is no longer needed.\n- **Providers.** We assess a provider before we engage it, contract with it under Article 28 GDPR, and\n hold it to security obligations at least as strict as our own.\n\nOur [Security page](https://githands.com/security) sets out the detail, including which measure applies to\nwhich part of the Service, our incident response process, and the shared responsibility split between what\nwe secure and what you secure.\n\n### What we do not claim\n\n**We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.**\nIf anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came\nfrom. Where we describe a practice on this page or on the Security page, we describe something we actually\ndo; where we adopt a framework as a reference without being audited against it, we say so plainly rather\nthan implying a certification.\n\n### No system is perfectly secure\n\n**No service, ours included, can be made completely secure, and anyone who tells you otherwise is\nselling something.** What we can honestly promise is that we take the measures above seriously, that we\nkeep them under review, and that if a personal data breach affects you we will act on it: we notify the\nCPDP where the law requires it, within the deadline it sets, and we\ntell affected people directly without undue delay where the breach is likely to result in a high risk to\nthem.\n\nYour part matters too. Use a strong and unique password, turn on multi-factor authentication where it is\noffered, keep your devices patched, and do not share credentials or access tokens. If you think an account\nhas been compromised, tell us at privacy@ever.co immediately.\n\n## Your rights over your personal data\n\nWhere we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have\nto explain why you are using them, and using one costs you nothing.\n\n- **Access** β ask whether we hold personal data about you and, if we do, get a copy of it together with\n the information in this policy about how it is used. (Article 15)\n- **Rectification** β have inaccurate data corrected and incomplete data completed. Much of this you can\n do yourself in your account settings, which is faster than asking us. (Article 16)\n- **Erasure** β have data deleted where we no longer need it for the purpose we collected it for, where\n you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)\n- **Restriction** β have us pause processing while a dispute is sorted out: while we check an accuracy\n challenge, for example, or while we consider an objection. We keep the data but stop using it.\n (Article 18)\n- **Portability** β receive the data you gave us, in a structured, commonly used, machine-readable format,\n and have it sent to another provider where that is technically feasible. This applies to data processed\n by automated means on the basis of your consent or a contract with you. (Article 20)\n- **Objection** β object to processing we base on our legitimate interests. We then stop unless we can\n demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless\n we need the data for a legal claim. (Article 21(1))\n- **Objection to direct marketing** β **absolute, and there is nothing to weigh.** If you tell us to stop\n using your data for direct marketing, including any profiling connected to it, we stop. No balancing\n test, no grace period, no exceptions. (Article 21(2))\n\nYou also have the right to withdraw consent where consent is what we rely on, which has its own section\nbelow, and the right to complain to a supervisory authority, which has the section after that.\n\nSome of these rights have limits written into the law itself. Erasure does not override an obligation to\nkeep invoices for the statutory accounting period, and portability does not extend to data we inferred or\ngenerated rather than received from you. **Where we cannot do all of what you ask, we will tell you which\npart we cannot do and why**, rather than declining as a whole.\n\n### How to make a request\n\nWrite to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find\nthe right records β the email address on the account is usually enough. You can also write to us by post\nat the address at the end of this policy.\n\n- **It is free.** We charge nothing for a request. If a request is manifestly unfounded or excessive,\n particularly because it repeats one we have already answered, the law lets us charge a reasonable fee\n based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you\n how to challenge that decision.\n- **We answer within one month** of receiving the request. Where a request is complex, or where you have\n made several, we may extend that by up to two further months β and if we do, **we will tell you within\n the first month, and tell you why**.\n- **We check who you are** before we hand over personal data, because the alternative is handing your data\n to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the\n email address already on the account. We ask for an identity document only where nothing lighter works,\n and anything you send us for verification is used for that and nothing else, then deleted.\n\n### If your data sits in a customer's workspace\n\n**This is the most important paragraph on this page for many of the people who read it.**\n\nA large part of the personal data in the Service was put there by one of our customers β your employer,\nthe organisation whose workspace you belong to, or the operator of a site built on our platform. Where the\nService captures data about how an organisation's own personnel work, that data belongs to that\norganisation's workspace.\n\n**For that data the customer is the controller and we are only their processor.** We process it on their\ndocumented instructions and for no purpose of our own, so the law directs your request to them, not to us.\nPractically:\n\n- **Send your request to that organisation.** They decide it, and they are the ones who have to answer you\n within the deadline.\n- **If you send it to us instead, we will not ignore it.** We will forward it to the relevant customer\n promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum\n requires.\n- **We will not decide the request ourselves, and we will not delete, correct or hand over data from a\n customer's workspace without their instruction** β unless a law that applies to us requires it. That is\n not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely\n what a processor is not allowed to do.\n\nIf you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell\nyou, and point you to the right organisation if it is not us.\n\n## Withdrawing your consent\n\nWhere we rely on your consent for something, **you can withdraw it at any time, and withdrawing is as easy\nas giving it**. You do not have to give a reason, and we do not ask you to justify it.\n\nWithdrawing consent stops the processing from that point onwards. **It does not make what we did before\nunlawful** β processing carried out while your consent was in force stays lawful, and withdrawal does not\nundo it. What it does mean is that we stop, and that we do not start again unless you tell us to.\n\n### How to withdraw, purpose by purpose\n\n- **Cookies and similar technologies** β open the **Cookie preferences** link in the footer of any page on\n [githands.com](https://githands.com), turn off the categories you no longer want, and save. The change\n takes effect immediately. Details are in our [Cookie Policy](https://githands.com/cookies).\n- **Marketing emails** β use the unsubscribe link at the bottom of any message we send you, or write to\n privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require\n you to sign in or find your password first.\n- **Optional features and integrations you switched on** β turn the feature off, or disconnect the\n connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we\n will turn it off for you.\n\nIf you have consented to something not listed here, write to privacy@ever.co naming it, and we will\nact on it the same way.\n\n### What happens next\n\nWe stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep\nthe minimum record needed to show that you consented and that you withdrew, because being able to evidence\nconsent is itself a legal requirement β for how long, see the retention section.\n\n**We will not quietly move the same processing onto a different legal basis to keep it running.** If some\npart of what you asked us to stop genuinely rests on another basis as well β an invoice we are required to\nkeep, for example β we will tell you which part and why, rather than leaving you to discover it.\n\nMost of what we do is not based on consent at all. It rests on performing our contract with you, on legal\nobligations, or on legitimate interests. **Withdrawing consent therefore does not close your account or\nswitch off the Service** β it affects only the things you consented to.\n\n## Complaining to a supervisory authority\n\nIf you think we have handled your personal data badly or unlawfully, **you have the right to complain to a\ndata protection supervisory authority**. That right is yours regardless of anything else in this policy.\n\nWe would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and\nwe will look into it and come back to you. In most cases that is the quickest way to get the outcome you\nactually want. **You are not required to do this, and it is not a condition of complaining** β you can go\nstraight to an authority, and you can do it at any point, including while we are still dealing with your\ncomplaint.\n\n### Our lead supervisory authority\n\nWe are established in Bulgaria, so our lead authority is the\n**Commission for Personal Data Protection (ΠΠΎΠΌΠΈΡΠΈΡ Π·Π° Π·Π°ΡΠΈΡΠ° Π½Π° Π»ΠΈΡΠ½ΠΈΡΠ΅ Π΄Π°Π½Π½ΠΈ)** β the CPDP. Its website,\nincluding its complaint form and current contact details, is at\n[https://www.cpdp.bg/](https://www.cpdp.bg/).\n\n### You can also complain closer to home\n\nUnder Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:\n\n- where you live;\n- where you work; or\n- where the thing you are complaining about took place.\n\nYou do not have to use ours, and you do not need our agreement to use another one. If you complain to your\nlocal authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this\nsituation, so nothing is lost by choosing whichever is easiest for you.\n\nYou also have the right to an effective judicial remedy β against a supervisory authority's decision, and\nagainst us directly β in the courts of the country where you live or where we are established. Complaining\nto an authority does not use up that right.\n\n## Automated decision-making and profiling\n\n**We do not make decisions about you that produce legal effects concerning you, or that similarly\nsignificantly affect you, based solely on automated processing.** No algorithm of ours decides whether you\nare hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a\ndecision of that kind is made about you by an organisation using the Service, a person at that\norganisation makes it.\n\nWe do use automated rules to detect fraud, spam, abuse and attacks against the Service β rate limits,\nanomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one\nof them affects you, write to privacy@ever.co and a person will review it.\n\n### Where a customer turns on AI features, be aware of this\n\nThis is the part worth reading carefully, because it is easy to misunderstand.\n\nSome of our products capture activity data on behalf of a customer β an employer, typically β and some of\nthem offer optional AI features on top of it. **Where a customer enables those features, the Service can\ngenerate automated assessments of the activity it captures.** The clearest example: classifying whether\nthe content of a captured screen appears to be work-related. Other examples include scoring or summarising\ncaptured activity and grouping it into categories.\n\nFour things follow, and we would rather state them plainly than let them be discovered later.\n\n- **The output goes to the customer, not to us.** It is presented to the organisation whose workspace the\n data belongs to. **That organisation is the controller of it, and we are only its processor.**\n- **The customer decides what, if anything, to do with it.** We do not act on these assessments, we do not\n use them for any purpose of our own, and we do not share them with anyone else.\n- **These outputs are not decisions, and must not be used as if they were.** An automated assessment is an\n input to a human judgement. **Our terms require the customer not to treat an output of the Service as an\n automated decision about a person, and to apply meaningful human review before acting on one.** Whether\n any particular use is lawful where that customer operates β including the lawful basis for it, the\n notices it has to give, any impact assessment it has to carry out, and any consultation with employee\n representatives it has to run β is that customer's responsibility to determine, not ours.\n- **They can be wrong.** A classifier reading a screen has no idea what your job is. It can label genuine\n work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it\n as a rough signal, and we say so to our customers as well as to you.\n\n### If an assessment about you has been generated\n\nAsk the organisation whose workspace holds the data β normally your employer. You can ask them for human\ninvolvement, for an explanation of how the assessment was reached, to express your point of view, and to\ncontest the result. They are the controller, so they are the ones who have to answer.\n\nIf you send that request to us, we will forward it to them promptly, tell you we have done so, and assist\nthem in answering it. See the routing paragraph in the section on your rights, which explains why we\ncannot decide it ourselves.\n\n## Children\n\n**The Service is not directed at children, and we do not knowingly collect personal data from them.** It\nis a business product, bought by organisations and used by the people who work in them. We do not design\nit for children, we do not market it to them, and we do not offer accounts to them.\n\nWhere consent is the basis for an online service offered directly to a child, the GDPR sets the age at\nwhich the child can consent alone. **In Bulgaria that age is 14.** Other EU and EEA countries set\nit anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.\nBelow that age, consent has to come from β or be authorised by β a holder of parental responsibility.\nBecause we do not offer the Service to children, we do not operate a parental consent mechanism, and a\nchild under the applicable age should not create an account or submit personal data to us.\n\n### If a child's data has reached us\n\nTell us. Write to privacy@ever.co with enough detail for us to find the record β an email address, an\naccount name, or the page where the data was submitted. You do not need to prove anything first, and you\ndo not need to be the child's parent to report it.\n\nWe will check, and where we confirm that we hold personal data collected from a child without proper\nauthorisation, **we will delete it without undue delay**, keeping only what a law that applies to us\nrequires us to keep.\n\nIf the data sits inside one of our customers' workspaces rather than in our own records, the customer is\nthe controller of it. Tell them as well, and tell us β we will forward your report to them and press for\nit to be dealt with, as the routing paragraph in the section on your rights describes.\n\n## Links and content from other sites\n\nOur websites and the Service link to services we do not run, and some pages embed content that other\npeople host β videos, maps, code repositories, documentation and similar.\n\nFollowing a link takes you somewhere this policy does not reach. Loading embedded content means the\nprovider hosting it receives data directly from your browser, typically your IP address, your device and\nbrowser details, and the page you were on, and it may set its own cookies.\n\n**We do not control those services, and this policy does not apply to them.** What they collect and what\nthey do with it is governed by their own privacy notice, which is the one to read before you use them.\nWhere embedded content is not strictly necessary to deliver a page, we load it only once you have agreed\nto the relevant cookie category β see our [Cookie Policy](https://githands.com/cookies).\n\nA link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we\nwould like to know at privacy@ever.co so we can reconsider carrying it.\n\n## Changes to this policy\n\nThis policy changes when the Service changes, when we engage or replace a provider, or when the law moves.\nWe would rather update it than let it drift out of date and quietly stop being true.\n\nEvery version carries a version number and the date it takes effect, shown at the top of the page. **This\nis version 1.0.1, in force from 2026-08-02.**\n\n### How we tell you\n\n- **Minor changes** β clarifying wording, correcting a mistake, adding a provider of a kind already\n described β are published with a new version number and a new effective date. We do not send a separate\n notice for these.\n- **Material changes** β a new purpose, a new category of personal data, a new category of recipient, a\n longer retention period, a change to how you exercise your rights, or a change to the legal basis we\n rely on β are notified **at least 30 days before they take effect**, by email to account holders and by\n a notice on the site. That gives you time to read them and to act before they apply.\n- **Changes that need your consent** are not made by publishing a new version. We ask you, and we treat\n silence as a no.\n\nThis policy is a notice, not a contract. **We do not ask you to accept it**, and continuing to use the\nService is not us collecting your agreement to it. Where we genuinely need your agreement to something, we\nask for it separately and record it.\n\n### Previous versions stay available\n\nWe do not overwrite the past. **Every version of this policy that we have published remains available**,\nwith the dates it was in force, from the version history linked at the foot of\n[https://githands.com/privacy](https://githands.com/privacy). If you want to know what we said about your data on a\nparticular date, that is where to look β and if you cannot find it, ask us at privacy@ever.co and we\nwill send it to you.\n\n## How to contact us\n\nThe controller for the personal data described in this policy is **Ever Technologies LTD**, registered in\nBulgaria under company number 204599535, with its registered office at\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n- **Privacy questions, and any request about your personal data** β privacy@ever.co\n- **Data protection correspondence** β dpo@ever.co\n\nBoth addresses are monitored by the same people, and either will reach us. By post, write to the registered\noffice above and mark the letter for the attention of the privacy team. We correspond in English.\n\n**We have not designated a Data Protection Officer under Article 37 GDPR.** The dpo@ever.co address is\na contact channel, not a designation, and we will not describe it as one. If that position changes, this\npolicy will say so and will give the designated office's contact details.\n\nIf your question is about personal data held inside one of our customers' workspaces, that customer is the\ncontroller and the request goes to them β see the routing paragraph in the section on your rights. Write to\nus anyway if you are unsure, and we will tell you who to ask.\n\nThis document is version 1.0.1 of the Privacy Policy for\n[githands.com](https://githands.com), in force from 2026-08-02. Earlier versions, with the\ndates they applied, are at [https://githands.com/privacy](https://githands.com/privacy)."
|
|
379
|
+
"markdown": "# Privacy Policy\n\n**GitHands** β [githands.com](https://githands.com)\n\nVersion 1.0.2 Β· In force from 2026-08-02\n\nThis notice explains what we do with personal data when you use GitHands Cloud and the websites,\napplications and application programming interfaces we make available at [githands.com](https://githands.com)\n(together, the \"**Service**\"). It tells you what we collect, why, who else sees it, how long we keep it,\nand what you can ask us to do about it.\n\nWe have written it to be read rather than to be defended. Where something is uncomfortable β data we hold\nthat you never gave us, or data your employer decides to collect through our software β we say so plainly\ninstead of burying it in a list.\n\n## What this notice covers\n\n- The website at [githands.com](https://githands.com) and the pages served from it.\n- The GitHands Cloud web application, together with any desktop application, mobile application or\n browser extension we publish for it.\n- The application programming interfaces and integrations we operate for it.\n- The emails, notifications and support conversations that go with it.\n\nA product-specific annex appears later in this notice. It adds detail for GitHands β what it\nactually collects, what is switched off by default, and which controls exist. It sits on top of this\nnotice rather than instead of it, and where it is more specific about GitHands, the annex governs.\n\n## What this notice does not cover\n\n**Other companies' products.** Other companies operate their own websites, products and services, and\npublish their own privacy notices. This notice covers only what is listed above. If a service is not on\nthat list, this notice does not apply to it β whatever it looks like, and whoever links to it.\n\n**Software you run yourself.** Some of our software is published as open source and can be installed on\nyour own infrastructure. **If you run your own deployment, you are the controller of the personal data in\nit β not us.** You choose its hosting, its storage, its email provider and every other component. We have\nno access to that data, we do not process it, we are not your processor for it, and nothing in this notice\ndescribes it. Telling your own users what happens in your deployment is your job, not ours.\n\n**Sites we link to.** The Service links out to third-party websites and services. Once you follow a link\naway from us, the operator of that site decides what happens to your data. We do not control those sites,\nwe do not receive what you do on them, and we are not responsible for them. Read their notices, not this\none.\n\n**Your organisation's own systems.** Where your employer or another organisation uses the Service, it also\nruns systems of its own. This notice covers our part. Its notice covers its part.\n\n## Who we are\n\nThe controller of the personal data described in this notice is **Ever Technologies LTD**, a company\nregistered in Bulgaria under company number 204599535, with its registered office\nat Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n\"Controller\" is the legal term for the organisation that decides why personal data is used and how.\nWherever this notice says we make that decision, **Ever Technologies LTD is the organisation accountable to\nyou** β and to the Commission for Personal Data Protection (ΠΠΎΠΌΠΈΡΠΈΡ Π·Π° Π·Π°ΡΠΈΡΠ° Π½Π° Π»ΠΈΡΠ½ΠΈΡΠ΅ Π΄Π°Π½Π½ΠΈ) (CPDP), which\nis our lead supervisory authority.\n\nEver Technologies LTD operates GitHands Cloud and is the company you contract with for it. There\nis no other operator behind us and no second company you have to chase to get an answer.\n\nYou can reach us about anything in this notice at privacy@ever.co, or by post at the registered office\nabove.\n\nThere are parts of this notice where we are deliberately **not** the controller: where a customer puts\npersonal data about its own people into the Service, that customer decides, and we act on its instructions.\nThat split matters, so it has its own section below.\n\n## Other companies in our group\n\nThere is one other company in our group, and its role is narrow enough to state in a sentence.\n\n**Ever Co. LTD**, a company registered in Israel under company number\n515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual\nproperty in the software. Ever Technologies LTD operates the Service under licence from it.\n\nThat is the entire relationship. Its consequences are worth stating positively rather than leaving you to\nwork them out:\n\n- **Ever Co. LTD does not access personal data held in the Service.** No administration console,\n no production database, no support tooling, no backups, no error reports.\n- It is **not a controller** of that data, **not a processor** of it, and **not a sub-processor**. It does\n not appear on our sub-processor list, because there is nothing for it to appear against.\n- **No personal data is transferred to it.** No international transfer to Israel arises out of\n your use of the Service, because none happens.\n\nOwning software is not the same as having access to the data that software holds, and we have kept the two\napart on purpose.\n\nIf that ever changes β if Ever Co. LTD were to take on any role involving personal data from the\nService β we would update this notice before it happened, name the role, disclose the transfer and the\nsafeguard we relied on, and add it to our sub-processor list. **Until you read that here, none of it is\nhappening.**\n\n## Data protection contact\n\n**We have not designated a Data Protection Officer.** Article 13(1)(b) of the GDPR asks a controller to\npublish a Data Protection Officer's contact details where one has been designated. None has been designated\nat Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a\nmailbox name imply otherwise. We keep the question under review, and if it changes we will publish the\ndetails here.\n\nWhat we do publish is a contact route that is monitored and acted on. **Privacy questions and requests to\nexercise your rights are handled through these addresses:**\n\n- **privacy@ever.co** β use this for anything about this notice, about the personal data we hold, or to\n make a request under any of your rights.\n- **dpo@ever.co** β an alias that reaches the same people. It exists because procurement forms,\n security questionnaires and privacy tooling routinely expect an address in that form. **It is a routing\n alias, not an office. Nothing about it means a Data Protection Officer has been designated.**\n\nYou can also write to us by post at the registered office given above.\n\nWe will acknowledge your message, and we will answer a request to exercise your rights within one month β\nthe deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may\nextend that by up to two further months. If we do, we will tell you inside the first month and explain\nwhy.\n\n## Who decides what: controller and processor\n\nData protection law splits responsibility in two. The **controller** decides why personal data is used and\nhow. The **processor** only acts on the controller's instructions. Which of the two we are is not a\nformality β it decides who you go to, who has to answer you, and who is accountable when something goes\nwrong.\n\nOur position depends on whose data it is. There are three cases. We set them out here, in the privacy\nnotice, rather than leaving them to a data processing agreement, because the person most affected by the\nsecond case is usually the person least likely to read a contract.\n\n### 1. Our own relationship with you β we are the controller\n\nWhere we decide, we are accountable. **We are the controller** for:\n\n- registration and account identity β the name, email address and credentials used to create and hold an\n account;\n- billing, payments, invoices, tax records and collections;\n- support conversations, including the tickets, emails, chats and attachments themselves;\n- security, fraud prevention, abuse handling and audit logging;\n- our own websites and their analytics, our newsletters, and our marketing to prospective customers; and\n- running our business β accounting, insurance, professional advice, and defending claims.\n\nEverything in this notice about purposes, legal bases, retention, transfers and your rights applies to this\nfirst case directly, and you exercise those rights against us.\n\n### 2. Personal data a customer puts into the Service about its own people β the customer is the controller\n\nWhen an organisation subscribes to the Service and uses it to run its business, the personal data it puts\nin is **its** data. It decides what to collect, which features to switch on, why, and for how long to keep\nit. **We process that data only on that organisation's instructions.** For it, the organisation is the\ncontroller and we are the processor.\n\nThis covers the ordinary contents of a workspace β employee and contractor records, contact details,\nprojects, tasks, documents and messages. It also covers the parts that matter most, where a product\nprovides them and the customer has enabled them:\n\n- **time-tracking data** β timers, timesheets, time entries and the records behind them;\n- **activity data** β how much keyboard and mouse activity occurred in a period, idle time, and which\n applications and websites were in use;\n- **screen and media capture** β periodic screenshots and, where separately switched on, webcam stills,\n audio recordings and screen recordings.\n\n**We do not decide to collect any of this. The customer does.** We build the features, we document what\neach one captures and what each control does, and we run them exactly as the customer configures them. We\ndo not use that data for our own purposes, we do not use it to train models, and we do not look at it\nexcept where we must in order to run, secure or support the Service.\n\nWhat GitHands can capture, what is off by default, and which controls exist is set out in the annex\nlater in this notice.\n\n### 3. Data a customer holds about its own clients and end users β the customer is the controller\n\nWhere a customer uses the Service to serve its own clients, members, applicants, patients or website\nvisitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the\nprocessor, and the customer owes those people the notice and the answers. If you have dealt with an\norganisation and want to know what it holds about you, ask that organisation.\n\n### If you are monitored at work, this part is for you\n\nWe would rather tell you directly than make you work it out from a contract you have never seen.\n\n**Your employer decides what is captured. We do not.** Screenshots, activity rates, application and website\nusage, webcam stills, audio, screen recordings β each of these is a setting your employer switches on or\nleaves off, for the organisation and, where the product allows it, for individual people. We cannot switch\nthem on for your employer, and we do not switch them on for ourselves.\n\n**Your employer is the controller of that data.** That means your employer, not us:\n\n- must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,\n which differs sharply from country to country;\n- must tell you, before it starts, what is captured, how often, why, and how long it is kept;\n- must carry out a data protection impact assessment where one is required, and act on what it finds;\n- must consult a works council, employee representatives or a trade union where its national law requires\n that; and\n- must answer your requests about that data.\n\n**We make no claim that monitoring employees is lawful across the European Union, because it is not.** Some\ncountries restrict it tightly, some require consultation before it starts, and some prohibit particular\nforms of it outright. Whether your employer's use of these features is lawful where you work is your\nemployer's responsibility. We require every customer to confirm to us that it has dealt with each of the\npoints above before it uses these features.\n\n**How to exercise your rights over monitoring data.** Send your request to your employer β it holds the\ndata and it has to answer you. If you send it to us instead, we will not ignore it:\n\n- we will forward it promptly to the customer whose workspace holds the data;\n- we will tell you that we have done so, and to whom, so you are not left waiting on silence; and\n- we will help that customer find, correct, export or delete the data, which is what our contract with it\n requires of us.\n\n**What we will not do is release one organisation's data to someone else on request.** We cannot verify an\nemployment relationship from the outside, and handing over a workspace's contents to a person the customer\nhas not authorised would be a breach in its own right. That restraint protects you as much as it\nconstrains you.\n\nIf you think your employer is monitoring you unlawfully, you can complain to the data protection authority\nin your own country, and to your national labour authority. You do not need our permission, and you do not\nneed to come through us first.\n\n## Personal data we collect\n\nWe group this by where the data comes from, because that is what determines what we know about you and what\nwe owe you.\n\nNot every category applies to every product, plan or user. This section describes the shape of what we\ncollect; the annex later in this notice lists what GitHands actually collects.\n\n### What you give us\n\n- **Account identity** β your name, username, email address, password (held only as a hash), profile\n picture, job title, preferred language and time zone.\n- **Organisation details** β the organisation you belong to, your team, your role and permissions within\n it, and who invited you.\n- **Contact details** β email address, telephone number and postal address, where you provide them.\n- **Billing details** β billing name and address, VAT or tax identification number, the plan you are on,\n invoices and payment history. **We do not receive or hold your full card number** β that goes straight to\n our payment processor.\n- **Support correspondence** β the tickets, emails, chat messages, screenshots and files you send when you\n ask for help, and our replies.\n- **Content you submit** β everything you or your organisation puts into the Service: documents, tasks,\n projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as\n processor, not as controller.\n- **Anything else you volunteer** β survey answers, feedback, event registrations, newsletter sign-ups, and\n whatever you choose to write to us.\n\n### What we collect automatically when you use the Service\n\n- **Device and browser data** β device type, operating system, browser and version, screen size, language,\n and the version of our application you are running.\n- **Connection data** β your IP address, and the approximate location it indicates. **That is\n city-or-region level, derived from the IP address**, and it is not satellite positioning. Where a\n specific feature collects precise location, it says so.\n- **Usage data** β pages and screens viewed, features used, actions taken, navigation paths, timestamps and\n the page that referred you.\n- **Logs** β server and application logs of requests, errors, response times, sign-ins, failed sign-ins and\n administrative actions, with the identifiers needed to tie an entry to an account.\n- **Diagnostics** β crash reports, stack traces and performance traces. These can incidentally contain\n whatever was in the request that failed.\n- **Cookies and similar technologies** β cookies, local storage, pixels, software development kit\n identifiers and comparable device storage. What each is for, and which ones need your consent, is in our\n [Cookie Policy](https://githands.com/cookies).\n\n### What we receive from other people\n\n- **Identity providers** β if you sign in with a third-party account, we receive that account's identifier,\n your email address, your display name and usually your profile picture, plus confirmation that the\n sign-in succeeded. **We never receive your password for it.**\n- **Payment processors** β whether a payment succeeded or failed, the payment method type, the last four\n digits and expiry of a card, the billing country, and any dispute or chargeback.\n- **Integrations you or your administrator connect** β whatever the connected service returns within the\n permissions granted. That varies by integration and is shown to you when you authorise it.\n- **Your organisation** β where an administrator creates your account, invites you, sets your role or\n imports records about you.\n- **Other sources**, where a particular product uses them. Those are set out in the next section and in the\n annex.\n\n### What you have to give us\n\nSome of it is unavoidable. Without account identity we cannot create an account for you; without billing\ndetails we cannot take payment for a paid plan; without certain records we cannot meet our own legal\nobligations. Where data is necessary in that sense, **not providing it means we cannot provide that part of\nthe Service** β but nothing worse follows.\n\nEverything else β an optional profile field, a newsletter subscription, an integration you could simply not\nconnect β is genuinely optional, and declining it costs you nothing.\n\n## Data we do not collect\n\nShorter than the previous section, and just as binding. These are commitments about how the Service is\nbuilt, not aspirations.\n\n- **We do not sell personal data.** Not to data brokers, not to advertisers, not to anyone β and not under\n the broader definitions of \"sell\" or \"share\" used outside the European Union.\n- **We do not buy marketing lists.** If we contact you about our products it is because you gave us your\n details, or because you are already a customer. We do not purchase your name from someone else in order\n to email you.\n- **We do not use your content to train machine-learning models** β not for our own purposes, and not for\n the benefit of other customers. Where a product has an AI feature, it processes your content to produce\n your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively\n choose, described before you choose it.\n- **We do not run advertising inside the Service.** No third-party advertising, no behavioural ad\n targeting, no cross-site advertising identifiers in the product.\n- **We do not record what you type.** Where a product measures keyboard and mouse activity, it counts\n events over a period. **There is no keylogger in our software. The content of your keystrokes is never\n captured, stored or transmitted.**\n- **We do not ask for special-category data** β health, racial or ethnic origin, religious or philosophical\n beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric\n data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is\n about what can end up inside a screenshot, and it has its own section below.\n- **We do not store full card numbers or card security codes.** Those are entered on our payment\n processor's systems and never reach ours.\n- **We do not collect precise location by default.** Where a product uses location at all, it is because a\n specific feature needs it, and that feature says so.\n\nIf you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it\nas a defect in the product, not as a disagreement about wording.\n\n## Where data comes from when it does not come from you\n\nNot all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it\ncame from, and this section does that.\n\n- **Your employer, or the administrator of your workspace.** Where an organisation subscribes to the\n Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies\n your name, work email address, job title, team, role and permissions, and whatever else the organisation\n chooses to hold about you in its workspace. **For that data the organisation is the controller**, as set\n out above.\n- **Identity providers.** If you sign in with a third-party account, that provider supplies the account\n identifier, your email address, your display name and usually a profile picture, and confirms the sign-in\n succeeded. It supplies nothing else, and never a password.\n- **Integrations you or your administrator connect.** A connected service supplies whatever the permissions\n you granted allow β for example issues and repositories from a code host, messages and channel names from\n a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when\n the connection is authorised, and it can be revoked in the same place.\n- **Payment processors and resellers.** They supply the outcome of a payment, the payment method type, the\n last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not\n pass us the card itself.\n- **Publicly available sources, where a product builds profiles from them.** Some products work with\n information people have published themselves β a public code-hosting profile, a public company page, a\n public professional listing. Where a product does this, the annex names the categories taken and the\n sources they came from, explains the basis we rely on, and says how to object. **If we hold a profile\n about you that you never gave us, you can object to it and we will act on that.**\n- **Service providers acting for us.** Fraud and abuse signals, delivery and bounce information from the\n systems that send our email, and security intelligence about addresses and networks.\n\nWhere we are the controller of personal data that did not come from you, we will tell you within a\nreasonable period and at the latest within one month of obtaining it β or, if we use it to contact you, at\nthat first contact. Where informing every individual separately would take disproportionate effort, this\nnotice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.\n\n## Why we use personal data, and on what legal basis\n\nArticle 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than\na general list of all six bases β you can check us against each line.\n\n| Purpose | Personal data used | Lawful basis |\n|---|---|---|\n| Providing GitHands Cloud: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you | Account identity, organisation and role, credentials, content you submit, device and connection data | **Contract** β Art 6(1)(b). Necessary to perform our agreement with you |\n| Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment | Billing details, plan and subscription data, invoices, payment outcomes | **Contract** β Art 6(1)(b) |\n| Keeping accounting, tax and invoicing records | Invoices, payment records, billing identity | **Legal obligation** β Art 6(1)(c), under tax and accounting law |\n| Support: answering your questions, investigating faults and reproducing problems you report | Support correspondence, account identity, logs and diagnostics, and whatever you point us at | **Contract** β Art 6(1)(b) where you are a customer. **Legitimate interests** β Art 6(1)(f) where you are not, so that we can answer anyone who writes to us |\n| Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure | Account identity, IP address, device data, request logs, sign-in and failed sign-in records | **Legitimate interests** β Art 6(1)(f) in keeping the Service and the people who use it safe |\n| Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups | Logs, diagnostics, usage data, account identifiers | **Legitimate interests** β Art 6(1)(f) in operating a reliable service |\n| Understanding how the Service is used, so we can improve it | Usage events, feature interactions, device and browser data, aggregated statistics | **Legitimate interests** β Art 6(1)(f). **Consent** β Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our [Cookie Policy](https://githands.com/cookies) |\n| Marketing to people who are not yet customers: newsletters, product announcements and events | Contact details, marketing preferences, whether you opened or clicked a message | **Consent** β Art 6(1)(a), which you can withdraw at any time |\n| Marketing our own similar products to an existing customer who gave us their address during a sale, with an opt-out in every message | Contact details, the products you already have | **Legitimate interests** β Art 6(1)(f), relying on the narrow existing-customer exception in the ePrivacy rules |\n| Meeting legal obligations: responding to lawful requests from authorities, sanctions and export-control checks, statutory record-keeping, and our own data protection duties | Whatever the specific obligation requires, and no more | **Legal obligation** β Art 6(1)(c) |\n| Establishing, exercising or defending legal claims, and handling complaints, disputes, audits, insurance and corporate transactions | Account and billing records, correspondence, and the logs relevant to the matter | **Legitimate interests** β Art 6(1)(f) in protecting our legal position |\n\nTwo things this table deliberately does not cover.\n\n**Where we act as processor**, the lawful basis is not ours to pick. The customer that put the data into\nthe Service decides the purpose and must have its own basis for it. See the controller and processor\nsection above.\n\n**Where we rely on your consent**, you can withdraw it at any time, and withdrawing it is as easy as giving\nit. Withdrawing consent does not make earlier processing unlawful β it stops the processing from that point\non.\n\n## The legitimate interests we rely on\n\nWhere the table above says \"legitimate interests\", the law requires us to tell you what that interest\nactually is β not simply to name the basis and move on. For each one we have asked three questions: what is\nthe interest, is the processing genuinely necessary for it, and is it fair to you. That last question is\nthe balancing test, and we keep a written record of it.\n\n### Keeping the Service and its users secure\n\n- **The interest:** preventing unauthorised access, account takeover, fraud, spam, denial-of-service and\n abuse of the Service.\n- **Why the processing is necessary:** you cannot see an attack without looking at the traffic. Sign-in\n records, IP addresses, device data and request logs are what make an intrusion visible at all.\n- **Why it does not override your rights:** the data is limited to what security work needs, it is kept for\n a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody\n reasonably expects a service to be run without security logging.\n\n### Keeping the Service running\n\n- **The interest:** operating a reliable service β monitoring, error tracking, debugging, capacity planning\n and backups.\n- **Why the processing is necessary:** faults surface in logs, and a crash report is only useful if it\n records what was happening when the crash occurred.\n- **Why it does not override your rights:** it is operational data, kept for short periods, used to fix\n software rather than to form views about people, and reachable only by the staff who need it.\n\n### Understanding how the Service is used\n\n- **The interest:** knowing which features are used, where people get stuck, and what to build or fix next.\n- **Why the processing is necessary:** the alternative is guessing. Aggregate usage data is the only\n practical way to see this without interrogating every user.\n- **Why it does not override your rights:** we analyse it in aggregate rather than to make decisions about\n you individually, and wherever cookies or similar device storage are involved we ask for your consent\n instead of relying on this interest at all.\n\n### Answering people who write to us without an account\n\n- **The interest:** replying to a question from someone who is not a customer.\n- **Why the processing is necessary:** we cannot answer you without keeping your message and your address.\n- **Why it does not override your rights:** you chose to contact us, we use it only to answer, and we keep\n it no longer than the matter and any follow-up require.\n\n### Telling existing customers about our own similar products\n\n- **The interest:** letting people who already buy from us know about the products next to the one they\n bought.\n- **Why the processing is necessary:** it uses the address they gave us during that sale, and there is no\n less intrusive way to reach them.\n- **Why it does not override your rights:** it is confined to our own similar products, every message\n carries a one-click opt-out, and an opt-out is acted on immediately and permanently.\n\n### Running and protecting our business\n\n- **The interest:** accounting, audit, insurance, professional advice, complaints, disputes, enforcing our\n terms, and evaluating or completing a corporate transaction.\n- **Why the processing is necessary:** these are ordinary obligations of operating a company, and each one\n needs the records that relate to it.\n- **Why it does not override your rights:** the data is confined to the matter in hand, access is narrow,\n and a great deal of it we are required to keep in any event.\n\n### Your right to object\n\n**You can object to any processing we base on legitimate interests, at any time, by writing to\nprivacy@ever.co.** Tell us which processing, and where you can, why β your particular situation is part\nof the balance. We will stop unless we can show compelling legitimate grounds that override your interests,\nrights and freedoms, or unless we need the data to establish, exercise or defend legal claims.\n\n**If you object to direct marketing there is no balancing at all. We stop.** That right is absolute.\n\nYou can also ask us for a summary of the balancing test behind any interest listed above, and we will give\nyou one.\n\n## Special categories of data\n\nSome personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic\norigin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,\nbiometric data used to identify someone, data concerning health, and data about a person's sex life or\nsexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.\n\n**We do not seek any of it.** We do not ask for it at sign-up, in billing or in support. There are no\nfields for it, we do not infer it, and we do not enrich profiles with it. Please do not send it to us in a\nsupport ticket either β if you need to show us something sensitive to get help, redact it first.\n\n### The honest caveat: incidental capture\n\nWhere a customer switches on screen capture, webcam capture or audio capture, **what gets captured is\nwhatever is there**. A screenshot taken while someone has a hospital appointment email open captures health\ndata. A webcam still can show a religious head covering. An audio recording can pick up a background\nconversation that has nothing to do with work.\n\nThat is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a\nscreen or a room on a timer, and it is true of every product that does it, ours included.\n\n### Whose responsibility it is\n\n**The customer that switches these features on is the controller of what they capture**, including anything\nspecial-category that comes with it. So the customer, not us:\n\n- decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;\n- must carry out a data protection impact assessment before starting, and act on what it finds β capture of\n this kind will normally require one;\n- must have a lawful basis, and where special-category data is realistically in scope must also satisfy\n Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between\n employer and employee;\n- must configure the product to reduce that risk rather than accept it; and\n- must deal with what has been captured, including deleting a capture that should never have been taken.\n\nWe are the processor for it. We do not decide to capture anything, we do not review captures for our own\npurposes, and we act on the customer's configuration and instructions.\n\n### The levers, and using them\n\nWhere a product offers screen or media capture, it also offers controls that materially reduce this risk.\nDepending on the product, those include:\n\n- switching capture off entirely, for the whole organisation or for an individual person;\n- switching off the more intrusive capture types β webcam stills, audio and screen recording β while\n keeping the rest;\n- reducing how often captures are taken;\n- blurring captured images;\n- shortening how long captures are kept, and deleting them automatically at the end of that period;\n- letting people see what has been captured about them; and\n- deleting an individual capture.\n\n**If you are a customer, these are yours to set, and the defaults are not a recommendation.** Choose the\nleast intrusive configuration that meets the purpose you actually have, and write down why you chose it.\nThat record is what a supervisory authority will ask for.\n\n**If you are being monitored and something sensitive has been captured, ask your employer to delete it.**\nYour employer can do that in the product. If you tell us instead, we will forward your request and help\nyour employer act on it, as described in the controller and processor section above.\n\nWhich of these controls GitHands provides, and what its defaults are, is set out in the annex later\nin this notice.\n\n## GitHands: the people in this Service who never signed up\n\nThis annex is unlike every other product annex we publish, and the reason is worth putting in the first\nline rather than the fifteenth. **Most of the personal data in GitHands Cloud is about developers\nwho have never used it.** They did not create an account, they did not agree to anything, and nothing they\ndid was addressed to us. We collected their data from public sources, we added inferences of our own to it,\nand some of them are then sent a message.\n\n**If you are reading this because you received an email you did not ask for, or because you found your own\nname on a GitHands page, this section is written for you and not for our customers.** It is the\nnotice Article 14 of the GDPR requires us to give you when we hold data about you that did not come from\nyou, and everything you need in order to make us stop is in it. Nothing below is behind an account.\n\n### What the Service does\n\nA customer names a public code repository, or writes a brief describing the kind of developer it wants to\nreach. The Service then:\n\n- **enumerates the people publicly associated with that repository** β the accounts that starred it or\n forked it, its contributors, the people who commented on its issues, reviewed its pull requests or joined\n its discussions, and the followers of the organisation that owns it. For a curated \"awesome list\" it does\n the same for the repositories the list points at;\n- **finds a contact address** for each person, by the routes set out below;\n- **builds a profile** of that person from their public activity, and adds scores and inferences we\n generate ourselves;\n- **drafts a message** with a language model, personalised to that person, and sends it β as one message or\n as a sequence spread over time; and\n- **records what happened to it** β whether it was delivered, opened, clicked, replied to, bounced or\n unsubscribed from.\n\n**For all of that, Ever Technologies LTD is the controller.** We are not acting on a customer's instructions\nwhen we decide to build this database, what to infer from it or how long to keep it β we decide that. So\nthe rights in this policy run against us directly, and you do not have to find out which of our customers\nholds your record before anyone will answer you.\n\n### Where your data came from\n\nEverything we hold about a person who is not a user came from one of these, and from nothing else:\n\n- **the public GitHub REST, GraphQL, Search and Events APIs**, and the equivalent public GitLab endpoints;\n- **public repository pages** β stargazer lists, fork lists, contributor lists, issue and pull-request\n participants, discussion participants, and organisation follower lists;\n- **public commit metadata** β the author and committer name, email address and date recorded in a public\n commit;\n- **public profile fields** β username, display name, avatar, biography, company, location, personal site,\n linked social handle, follower and repository counts, and the \"available for hire\" flag if you have set\n it; and\n- **public dependency manifests** in your public repositories, read to work out which technologies you use.\n\n**Every record carries a provenance flag saying which of those it came from.** If you ask us where we got\nyour data, we can tell you which route it arrived by rather than gesturing at \"public sources\".\n\nWe plan to add professional networking platforms as a further source. **We will not do so without updating\nthis annex first**, and the notice you receive at first contact will name the actual source your record\ncame from, not a general list.\n\n### Your email address, and how we got it\n\nThis is the part of the processing most people find surprising, so it gets its own section rather than a\nbullet. We look for a contactable address in four places, in this order, and stop at the first that works:\n\n1. **the email address published on your profile**, where you have chosen to publish one;\n2. **the author or committer address recorded in the commits of the repository being searched**, where you\n have committed to it;\n3. **the author or committer address in commits across your own most recently updated public repositories**;\n and\n4. **the address carried in the public push-event stream** for your account.\n\nWe discard the anonymised `noreply` addresses that GitHub issues, because contacting one is pointless.\nWe do not guess addresses, we do not generate permutations of a name against a company domain, and we do\nnot buy address lists.\n\n**An address you put in a commit was published so that your work could be attributed to you, not so that\nsomebody could sell to you.** We know that, and we are not going to pretend otherwise. Routes 2, 3 and 4\nabove take an identifier published for one purpose and use it for another, and that is the single hardest\npart of this processing to justify. We treat it accordingly: those records carry the provenance flag that\nsays so, we hold them to the same objection and deletion routes as everything else, and if you tell us to\nstop we do not ask you why.\n\n### What we work out about you\n\nAlongside what we collected, we generate our own assessments. These are ours, not yours, and none of them\nis verified:\n\n- an **engagement score** from 0 to 100 and a label for it β Champion, Hot, Warm or Cold;\n- an **intent tier**, estimating how likely you are to be looking for a tool of the kind being marketed;\n- an **influence score**, a network rank and a cluster, derived from a graph of relationships between\n accounts;\n- a **contributor class** and a contribution-depth score;\n- an **activity trend**, and any technology migrations we think we can see in your history;\n- a **technology fingerprint**, parsed from the dependency manifests in your public repositories;\n- a **numeric embedding** of your profile, which is what makes \"find developers similar to this one\"\n possible;\n- an **approximate time zone, a confidence figure for it, and your likely working hours**, inferred from\n the timestamps on your public commits; and\n- an **employment life stage** β job hunting, recently hired, exploring, building or settled β with a\n confidence figure.\n\nTwo of those deserve to be named rather than buried in a list. **Inferring your working hours from commit\ntimestamps is an inference about your daily routine and roughly where in the world you are.** And\n**inferring that you may be job hunting is an inference about your employment situation**, drawn from\npublic activity that you did not publish in order to say anything of the kind.\n\n**All of these are opinions produced by software from partial signals, and any of them can simply be\nwrong.** Our terms forbid a customer from treating them as facts about you, and forbid using them to decide\nanything about your employment, credit, insurance, housing or access to a service. The\n[Acceptable Use Policy](https://githands.com/aup) puts that in binding terms.\n\n### Why we think we are allowed to do this\n\nThe lawful basis for building and using this database is **our legitimate interests, Article 6(1)(f)**. The\nlaw requires us to weigh that interest against your rights, and to be able to show our working. Here it is\nin summary; ask privacy@ever.co and we will send you the full assessment.\n\n- **The interest.** Reaching the specific developers most likely to want a developer tool, instead of\n advertising it to everybody.\n- **Why the processing is necessary for it.** The signal that a person cares about a particular technology\n is their public activity around it. There is no less intrusive route to the same result β untargeted\n advertising is not a lesser interference with *you*, it is a larger interference with everyone else, and\n it does not work.\n- **Where the balance is thinnest, stated honestly.** Publishing code under your own name does not mean you\n expected to be marketed to, and a data protection authority has said as much about a comparable service.\n Our interest does not automatically win. What makes the balance defensible is the mitigations, not the\n purpose β which is why we treat them as commitments rather than as good intentions.\n- **The mitigations we rely on.** Business-context data only. Nothing from a private repository or a\n private profile. A provenance flag on every record so we can always tell you where it came from. A\n permanent, one-click, no-questions objection. Suppression that covers every customer and never expires.\n Retention limits that expire rather than renew. No special-category data, sought or inferred. No sale of\n the database to anybody.\n- **Our conclusion.** The interest is legitimate and the processing is proportionate **so long as the\n mitigations above actually work.** If one of them stops working, the balance fails β so treat any failure\n of one as something to report to us at privacy@ever.co, and we will treat it as a defect.\n\nWhere a customer imports its own contact list or connects its own CRM, the basis for that data is the\ncustomer's to establish, not ours. See the three flows at the end of this annex.\n\n### Article 14: how you are told, and where we rely on the exception\n\nArticle 14 requires us to tell you that we hold your data, where it came from and what we do with it. There\nare two situations and we handle them differently.\n\n**If we contact you, you are told individually, in that first message.** Every first outbound message\ncarries, in the message itself and not behind a link:\n\n- who the controller is β Ever Technologies LTD, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria, company number\n 204599535 β and how to reach us;\n- **the specific source your record came from**, in plain words: your public profile, the commits of a named\n repository, your own public repositories, or the public event stream;\n- what we hold, what we have inferred, and what the message is for;\n- that the basis is legitimate interests, and that you may object;\n- who receives the data and how long we keep it;\n- your rights, and your right to complain to a supervisory authority; and\n- **a one-click objection link that does not expire.**\n\nThat is Article 14(3)(b) β notice at the latest at the first communication. Because we are contacting you\nanyway, it costs us nothing, so there is no argument for doing less.\n\n**If we hold your record and nobody ever contacts you, this annex is the notice.** Here we rely on the\nexception in **Article 14(5)(b)** for disproportionate effort, and we want the reasoning on the record\nrather than asserted:\n\n- notifying a person we hold data about and do not intend to contact would mean **initiating contact for\n the sole purpose of telling them we exist** β which is the intrusion the notice is meant to protect them\n from, delivered to people we were otherwise going to leave alone;\n- so we do what Article 14(5)(b) requires instead: **we make the information public**, in this annex, at a\n stable address, in the same document as the removal route, with no account and no token needed to read\n it; and\n- **we do not claim this exception for anyone we actually email.** Their notice is individual, in the\n message, as above. The exception covers only the records that sit still.\n\nIf you think that reasoning is wrong in your case, say so at privacy@ever.co. You can also put it to a\nsupervisory authority, and you do not need to come through us first.\n\n### How to make us stop, and how to be removed\n\n**Objecting to direct marketing is absolute under Article 21(2). There is no balancing test, no condition,\nno time limit and nothing for us to weigh.** You do not have to give a reason, be a customer, hold an\naccount, or explain how you found us.\n\n**You were added to this database without doing anything at all, so removing yourself takes one action and\nno account.** Any of these works:\n\n- **the objection link in any message you received from us.** It never expires. A link that stops working\n after a few days is not an opt-out, and ours does not;\n- **the removal page at [https://githands.com/remove](https://githands.com/remove)**, which needs no token, no\n sign-in and no prior message from us. Give us the email address or the profile you want removed; or\n- **an email to privacy@ever.co**, which a person reads.\n\nWhat happens then:\n\n- **we act within 24 hours in the ordinary case, and within one month at the outside.** Sending stops\n immediately;\n- **the suppression is platform-wide and permanent.** It is not per-customer and it does not expire. No\n customer of ours can reach you afterwards through this Service, whatever project or account they use;\n- **your profile, your inferences, your scores and your engagement history are deleted**, and you are\n removed from any public page described below;\n- **we keep one thing, and only one: a one-way hash of your address and the date.** We cannot read your\n address back out of it, and its only function is to recognise you if the extraction pipeline encounters\n you again so that you are never re-added. Keeping it is what makes the objection stick, which is why the\n law lets us; and\n- **we tell the customers who already hold your record to delete or suppress it**, and our contract with\n them requires them to do it within five business days.\n\n**One limit, stated plainly because you should not discover it later.** If a customer had already exported\nyour details into its own CRM or mailing tool before you objected, that copy is in a system we do not\ncontrol, and **that customer is the controller of it**. We will tell you which customers we notified, so\nyou can go to them directly. Ask at privacy@ever.co and we will name them.\n\n### What we publish about you\n\nThe Service has public pages for a repository's community, showing named individuals β username, avatar and\nthe engagement score we generated for them β without a sign-in and open to search engines.\n\n**That is a different purpose from outreach, and we treat it as needing its own justification rather than\nriding on the one above.** Publishing an unverified judgement about a named professional is the part of\nthis product we are least comfortable with, and the rights below exist because of that discomfort:\n\n- **you can have your entry taken down** through any of the three routes in the previous section, and\n removal from the public page is immediate rather than queued;\n- **when we take an entry down we also ask the major search engines to drop the cached copy**, and we tell\n you when we have done so; and\n- **objecting to the public page does not require you to object to anything else**, and objecting to\n outreach removes you from the public page as well.\n\n### The tracking inside our messages\n\nMessages sent through the Service carry:\n\n- **an open-tracking image**, a single transparent pixel loaded from our servers, which tells us that the\n message was opened, when, and how many times; and\n- **click-tracking links**, which pass through our servers before going where they say they go.\n\nLoading either one discloses **your IP address, your user agent and the time** to us. That is how the\ntechnique works β there is no version of it that watches without seeing you.\n\nThis is access to information on your own device, so it is regulated separately from data protection, and\nconsent is the rule in the European Economic Area and the United Kingdom. **You did not give it.** So:\n\n- **open tracking is off by default for a recipient whose profile location or inferred time zone places\n them in the EEA or the United Kingdom**, and a customer cannot switch it on for them;\n- your mail client's \"do not load remote images\" setting defeats the pixel entirely, and we would rather\n tell you that than not; and\n- the [Cookie Policy](https://githands.com/cookies) annex covers the rest of what our own pages load.\n\n### Who else sees your data\n\nOur sub-processors are listed in full at\n[https://githands.com/subprocessors](https://githands.com/subprocessors), with what each one does and where it is.\nThree of them deserve to be named here rather than left to the table, because they are the ones a person in\nyour position is least likely to guess.\n\n- **The language-model provider.** Drafting a personalised message means sending your name, your username,\n your email address, your repositories and what we have inferred about you to a model provider, and it is\n forwarded on to the model that actually runs. Classifying your reply means sending the text of your reply.\n- **The AI observability service.** Every one of those prompts, and the completion it produced, is stored as\n a readable trace so we can debug quality and cost. Your data sits there in plain text.\n- **The email delivery provider**, which necessarily receives your address, the message and everything the\n tracking above records.\n\n**None of them is allowed to use your data for its own purposes, or to train models on it.** Most of them\nare established outside the European Economic Area, and the transfers section of this policy sets out the\nmechanism we rely on for each.\n\n### How long we keep it\n\n| What we hold | How long we keep it |\n|---|---|\n| A profile of a person who has never been contacted | **12 months** from when we last verified it against the source. Not renewed by re-finding you: if nothing new happens, it expires |\n| A profile of a person who has been contacted and did not respond | **24 months** from the last message |\n| Inferences, scores, technology fingerprints and embeddings | Deleted as soon as the signals behind them are stale, and in any event with the profile |\n| Message, delivery, open and click records | **24 months** from the send |\n| The text of a reply you sent us, and its classification | **24 months** from receipt, or until you ask us to delete it, whichever is first |\n| An entry on a public community page | For as long as the profile behind it exists, and removed immediately on objection |\n| A suppression record after you object | **Permanently**, as a one-way hash of your address plus the date, and nothing else |\n\n**We do not restart a retention period because your circumstances changed.** Changing employer, starring\nsomething new or pushing a commit does not renew our clock. Only re-verification of a record we are\nentitled to hold does, and only within the limits above.\n\n### Decisions about you\n\n**Nothing in this Service makes a decision that produces a legal effect for you, or that similarly\nsignificantly affects you, by automated means alone.** What it produces is a score, a label and a drafted\nmessage, all of which reach a human being at one of our customers before anything happens.\n\nThey are still profiling, which is why they are set out in full above rather than summarised. And they are\nfenced: our [Acceptable Use Policy](https://githands.com/aup) prohibits any customer from using this Service, or\nanything it outputs, to decide employment, credit, insurance, housing, benefits or eligibility for a\nservice. **We are not a recruitment database, we are not a background-check service, and a customer that\nuses us as one is in breach.**\n\n### What we do not do\n\n- **We do not touch private repositories, private profiles or anything behind a permission.** Only the\n official public APIs of the source platforms, and only what they serve to anybody.\n- **We do not scrape.** No unofficial endpoints, no headless-browser harvesting of pages the API does not\n serve, no circumvention of rate limits or technical protections.\n- **We do not seek or infer special-category data.** No health, beliefs, politics, union membership,\n ethnicity, sex life or sexual orientation. There are no fields for it and we do not want it.\n- **We do not sell the database.** Not to advertisers, not to data brokers, not to recruiters. A customer\n can export the records its own project produced, under contractual duties to honour objections and delete\n on notice; we do not licence the database as a product.\n- **We do not use it for consumer marketing.** This is business-context outreach to a person in their\n professional capacity, and customers are contractually restricted to that.\n\n### The source platforms' own rules\n\nGitHub's Acceptable Use Policies restrict what information gathered from GitHub may be used for, including\nsending unsolicited mail to its users and passing personal information to recruiters. GitLab has its own\nequivalents. Those rules bind the account that does the reading.\n\nSo the reading is done under the customer's own account, which the customer connects in its own name and\nwarrants that it is entitled to use for this purpose. Our [Terms of Service](https://githands.com/tos) annex\nsets out that obligation and the indemnity behind it. **We also reserve the right to retire a source,\nor a method of finding an address, at any time** β including because a platform asks us to β and we will do\nthat without waiting to be compelled.\n\n### If you are a customer: three flows, three roles\n\nWhich of us answers for what depends on where the data came from. There are three cases and they do not\noverlap.\n\n- **Data the Service extracts, enriches and scores from public sources.** **We are the controller.** We\n decide to collect it, we run the enrichment and the scoring, and we answer the objections. Your Data\n Processing Addendum does not cover it, and you cannot instruct us to re-add a person who has objected.\n- **Contacts you import by file, records you sync from your own CRM, and campaign content you write.**\n **You are the controller and we are your processor.** The [Data Processing Addendum](https://githands.com/dpa)\n annex sets out what you warrant about that data before you bring it in.\n- **Records you export, and messages you send.** **You become an independent controller** the moment data\n leaves the Service into your systems, and you are the sender of record for every message. Your own\n Article 13 and Article 14 notices, your own lawful basis, and your own obligation to honour objections\n all attach to you at that point.\n\n### If you run GitHands yourself\n\nThe software is open source and can be run on your own infrastructure. **In your installation we process\nnothing, we hold no data and we are not your processor** β you choose the database, the sending provider,\nthe model provider and the source credentials, and the obligations to the people in your database are\nyours alone.\n\nOne thing does reach us, and we would rather you heard it here than found it in a configuration file.\n\n- **An installation sends us an anonymous heartbeat roughly every 24 hours.** It contains an installation\n identifier, the version, the billing mode, the operating system, architecture, runtime and database\n versions, counts of organisations, users, campaigns, sends and AI calls, counts of errors by a fixed\n error class, which features are switched on, and optionally an operator contact address if you have set\n one.\n- **It contains no recipient data, no message content, no repository or organisation names, no model\n prompts or completions, no credentials and no raw IP addresses.**\n- **You can switch it off**, and switching it off is a supported configuration rather than a hack.\n- **Check the administrator alert address before you go live.** It defaults to an address at our domain, so\n until you change it, alerts about your campaign failures reach us. Set it to your own address.\n\n## Cookies and similar technologies\n\nCookies, local storage, pixels, software development kits and similar technologies get their own document,\nbecause they need more detail than a summary can carry. What each one is, what it does, how long it lasts,\nwho operates it and how to refuse it is set out in our [Cookie Policy](https://githands.com/cookies).\n\nIn short, we sort them into four categories:\n\n- **Strictly necessary** β needed to deliver what you asked for: signing you in, holding your session,\n routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against\n automated abuse. These are not optional, and we do not ask for consent to them.\n- **Preferences** β remember choices you have made, such as language, region and interface settings.\n- **Analytics** β help us understand how the Service is used so we can improve it.\n- **Marketing** β measure our campaigns and help us understand which organisations take an interest in us.\n\n**Nothing in the preferences, analytics or marketing categories is placed or read on your device until you\nagree to it.** You can accept everything, refuse everything, or choose category by category, and refusing\ntakes exactly as few clicks as accepting.\n\n### Changing your mind\n\nYour choices are not permanent. A **Cookie preferences** link sits in the footer of every page on\n[githands.com](https://githands.com) and reopens the same panel you saw the first time. Change a category\nthere and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing\nabout the Service is withheld from you for refusing.\n\nOne analytics tool runs without consent, because it is configured so that it stores and reads nothing on\nyour device and never builds a persistent identifier for you. That is a conditional position, not a\npermanent one: the [Cookie Policy](https://githands.com/cookies) names the tool, describes the exact\nconfiguration we rely on, and says what happens if any part of that configuration ever changes.\n\n## Who receives your personal data\n\nWe disclose personal data only to the categories of recipient below, and only as much as each one needs to\ndo the job it is there for.\n\n- **Service providers acting as our processors** β hosting and infrastructure, storage, content delivery,\n email delivery, error monitoring, product analytics, customer support tooling and similar. They act on\n our documented instructions under a written contract that meets Article 28 GDPR, they are bound to\n confidentiality and appropriate security, and **they may not use your data for their own purposes**.\n- **Payment processors** β to take payment, issue invoices and handle refunds and disputes. For their own\n regulated obligations β fraud prevention, anti-money-laundering, card-scheme rules β they act as\n controllers in their own right, and their own privacy notice governs that part.\n- **Professional advisers** β lawyers, accountants, auditors and insurers, bound by professional\n confidentiality, where we need advice or have to evidence that we have complied with something.\n- **Public authorities, courts and regulators** β where the law requires us to disclose, or where we need\n to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is\n no wider than it needs to be, we push back where it is not, and we tell you about it unless we are\n legally prohibited from doing so.\n- **An acquirer or successor** β if we are reorganised, merged or sold, or if part of the business changes\n hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this\n policy or by a notice at least as protective, and we will tell you before anything about the handling of\n your data changes.\n\n### The sub-processors we engage for the hosted Service\n\nThese providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your\ndata is most likely to reach.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | 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. | United States, with edge termination worldwide | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. | 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. | United States | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | 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. | United States | 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 |\n| OpenRouter, Inc. | 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. | United States, and onward to the selected model provider | 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 |\n| Langfuse GmbH | 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. | Germany | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. dba Sentry | 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. | United States | 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 |\n| PostHog, Inc. | 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. | United States | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | 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. | United States | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | 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. | United Kingdom | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | 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. | Not published by the provider | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n\nThe full and current list, including everything below, is published at\n[https://githands.com/subprocessors](https://githands.com/subprocessors), together with the notice period and\nobjection procedure that apply when we add or replace one.\n\n### Three tiers, and why the difference matters\n\nA single flat list of every vendor that appears anywhere in our software would be both inaccurate and\nmisleading, so the sub-processor page is split into three tiers. They mean genuinely different things.\n\n- **Always engaged.** The providers above. If you use the hosted Service, these are in the path.\n- **Engaged only if you turn something on.** Optional integrations, connectors and features. A provider in\n this tier is engaged only when you or your workspace administrator enables the specific feature or\n connects the specific account it belongs to. Enable nothing and it is never involved. The list says which\n feature or setting activates each one.\n- **Self-hosted deployments only.** Several of our products are published as open source and can be run on\n your own infrastructure. In that case **you** choose the database, object storage, email relay, AI\n provider and everything else, using your own credentials. Those providers appear in the list so you can\n see what the software can be pointed at β but they are **your** providers, not ours. **We process nothing\n in a deployment you run, we are not your processor for it, and the commitments in this policy do not\n describe it.**\n\n### We do not sell your personal data\n\nWe do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not\nsupply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to\nuse it to build advertising or interest profiles, on our sites or anywhere else.\n\n## Sending personal data outside the EEA\n\nMost of the personal data we hold stays inside the European Economic Area, on infrastructure we operate\nourselves. Some of it does not: a number of the providers we engage are established outside the EEA β\nprincipally in the United States β and some of them route, cache or store data on servers outside it.\n\nWhere that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the\nfollowing for every transfer, and the sub-processor page names the destination country and the mechanism\nprovider by provider.\n\n### Adequacy\n\nWhere the European Commission has decided that a country provides an adequate level of protection, the\ntransfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by\nthe Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as\npermanent.\n\n### Providers in the United States\n\nFor a US provider we rely on one of two things.\n\n- **The EUβUS Data Privacy Framework**, but only where that provider is *actively self-certified* under it\n for the type of data concerned. We check the official Data Privacy Framework list when we engage a\n provider and re-check it periodically. **We do not claim the Framework for a provider that has not\n certified, or whose certification has lapsed.**\n- **Standard Contractual Clauses** β the clauses approved by the European Commission in Implementing\n Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact\n assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the\n first place, contractual limits on onward disclosure, and a commitment from the provider to notify and\n where possible challenge a government access request.\n\n**We keep Standard Contractual Clauses in place as the standing mechanism**, including for providers that\nare also certified under the Framework. That is deliberate, and here is the honest reason.\n\nThe Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was\nchallenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in\n*Latombe* (Case T-553/23). **That is not the end of it** β an appeal is pending before the Court of\nJustice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the\nsame court. So we treat the Framework as a mechanism under review rather than a settled answer, and we\nkeep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not\nan interruption for you.\n\n### Other countries\n\nFor a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with\nthe same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,\nthe corresponding UK and Swiss additions are applied to those clauses.\n\nWe rely on an Article 49 derogation β for example, a transfer that is strictly necessary to perform a\ncontract you have asked us to perform β only in a specific, occasional case where no other mechanism fits.\nIt is not a routine mechanism for us, and we do not use it to run a regular data flow.\n\n### Getting a copy of the safeguards\n\nYou are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the\ntransfer you are asking about, and we will send you a copy of the relevant clauses and tell you which\nmodules apply. We may redact commercial terms such as pricing and service levels; we do not redact the\ndata protection terms, which are the part that concerns you.\n\n## How long we keep personal data\n\n\"As long as necessary\" is not an answer, so here are the actual periods. Each one runs from the event in\nthe middle column, and at the end of it we delete the data or irreversibly anonymise it.\n\n| What we hold | How long we keep it | Why that period |\n|---|---|---|\n| Account and profile data β name, email address, workspace membership, settings | For as long as the account is open, then deleted within **30 days** of closure | We need it to give you the account; after that we do not |\n| Content and files you put into the Service | For as long as the account is open; after it ends, available for export for **30 days**, then deleted | You decide what is in it β see below |\n| Invoices, payment records and the tax data attached to them | **10 years** from the end of the accounting year in which the transaction fell | Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request |\n| Record that you accepted our terms β version, date, method | **5 years** after the agreement ends | The general limitation period for a claim under the contract |\n| Support correspondence and tickets | **24 months** from the last message in the thread | Long enough to handle a recurring problem and a follow-up; not longer |\n| Security, access and audit logs | **12 months** | Investigating unauthorised access, and evidencing that we did |\n| Application and error logs, crash reports, diagnostics | **90 days** | Fixing what broke; they lose value quickly |\n| Marketing contact records and the evidence of your consent | Until you object or withdraw. We then remove you from the lists and keep only a suppression record β your email address and the date β so that we do not contact you again | An unsubscribe that forgets you is not an unsubscribe |\n| Cookie and consent choices | As stated in the [Cookie Policy](https://githands.com/cookies), which gives the lifetime of each entry | It belongs with the technology it describes |\n| Backups | Each backup ages out on its own rolling cycle, within **30 days** | Recovering from failure and ransomware, without becoming a second archive |\n| Anything we are required to preserve for a legal claim, investigation or regulatory request | Until the claim, investigation or request ends, including any appeal period | We are not allowed to delete evidence, and neither are you |\n\n### Data that belongs to one of our customers\n\nFor personal data held inside a customer's workspace β including anything the Service captures about that\ncustomer's own personnel β **the customer sets the retention period, not us**. We are their processor for\nit. The defaults and the limits of what they can configure are described in the product annex to this\npolicy.\n\nWe delete that data when the customer instructs us to, or at the end of the export window after their\nagreement ends, whichever comes first. If you are one of their people and you want their data about you\ndeleted sooner, ask them β see the section on your rights, which explains how we route that.\n\n### What \"delete\" means here\n\nDeletion is applied to live systems straight away. Backup copies are not individually edited β doing so\nwould defeat what a backup is for β so a deleted record persists in backups until that backup ages out on\nthe cycle above, at most 30 days. During that window the data is not used for anything, and **we do not\nrestore a backup to bring back data someone asked us to delete**; a backup is restored only to recover a\nwhole system after a failure.\n\nWhere we can keep something useful without keeping you identifiable, we anonymise instead of deleting β\naggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not\npossible for us to re-identify you from it.\n\n## How we protect personal data\n\nWe take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the\nrisk, reviewed as the risk changes. In practice that means the following.\n\n- **Encryption in transit.** Traffic to and from the Service travels over TLS. HTTPS is enforced, and\n plain HTTP requests are redirected rather than served.\n- **Encryption at rest.** The storage holding customer content, databases and backups is encrypted at\n rest, and particularly sensitive values β credentials, tokens and keys β are additionally encrypted at\n the application layer rather than stored in readable form.\n- **Access control and least privilege.** Access to production systems is limited to the people whose job\n needs it, granted by named individual accounts rather than shared logins, protected by multi-factor\n authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or\n someone leaves.\n- **Network segmentation.** Databases, storage and internal services sit on segmented internal networks\n and are not exposed to the public internet. Administrative interfaces are not publicly reachable.\n- **Logging.** Administrative and security-relevant events are logged, retained for the period in the\n retention section, and monitored so that unusual activity raises an alert rather than sitting unread.\n- **Backups.** Data is backed up regularly, held on separate infrastructure from the live systems, and\n restores are tested β an untested backup is a guess, not a control.\n- **Vulnerability management.** Dependencies are scanned, code is analysed automatically before it ships,\n security patches are applied on a defined schedule with a faster path for serious issues, and we operate\n a responsible disclosure route so that anyone who finds a problem can tell us.\n- **Personnel.** Everyone with access is bound by written confidentiality obligations that outlast their\n engagement, works on a need-to-know basis, and has access removed when it is no longer needed.\n- **Providers.** We assess a provider before we engage it, contract with it under Article 28 GDPR, and\n hold it to security obligations at least as strict as our own.\n\nOur [Security page](https://githands.com/security) sets out the detail, including which measure applies to\nwhich part of the Service, our incident response process, and the shared responsibility split between what\nwe secure and what you secure.\n\n### What we do not claim\n\n**We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.**\nIf anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came\nfrom. Where we describe a practice on this page or on the Security page, we describe something we actually\ndo; where we adopt a framework as a reference without being audited against it, we say so plainly rather\nthan implying a certification.\n\n### No system is perfectly secure\n\n**No service, ours included, can be made completely secure, and anyone who tells you otherwise is\nselling something.** What we can honestly promise is that we take the measures above seriously, that we\nkeep them under review, and that if a personal data breach affects you we will act on it: we notify the\nCPDP where the law requires it, within the deadline it sets, and we\ntell affected people directly without undue delay where the breach is likely to result in a high risk to\nthem.\n\nYour part matters too. Use a strong and unique password, turn on multi-factor authentication where it is\noffered, keep your devices patched, and do not share credentials or access tokens. If you think an account\nhas been compromised, tell us at privacy@ever.co immediately.\n\n## Your rights over your personal data\n\nWhere we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have\nto explain why you are using them, and using one costs you nothing.\n\n- **Access** β ask whether we hold personal data about you and, if we do, get a copy of it together with\n the information in this policy about how it is used. (Article 15)\n- **Rectification** β have inaccurate data corrected and incomplete data completed. Much of this you can\n do yourself in your account settings, which is faster than asking us. (Article 16)\n- **Erasure** β have data deleted where we no longer need it for the purpose we collected it for, where\n you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)\n- **Restriction** β have us pause processing while a dispute is sorted out: while we check an accuracy\n challenge, for example, or while we consider an objection. We keep the data but stop using it.\n (Article 18)\n- **Portability** β receive the data you gave us, in a structured, commonly used, machine-readable format,\n and have it sent to another provider where that is technically feasible. This applies to data processed\n by automated means on the basis of your consent or a contract with you. (Article 20)\n- **Objection** β object to processing we base on our legitimate interests. We then stop unless we can\n demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless\n we need the data for a legal claim. (Article 21(1))\n- **Objection to direct marketing** β **absolute, and there is nothing to weigh.** If you tell us to stop\n using your data for direct marketing, including any profiling connected to it, we stop. No balancing\n test, no grace period, no exceptions. (Article 21(2))\n\nYou also have the right to withdraw consent where consent is what we rely on, which has its own section\nbelow, and the right to complain to a supervisory authority, which has the section after that.\n\nSome of these rights have limits written into the law itself. Erasure does not override an obligation to\nkeep invoices for the statutory accounting period, and portability does not extend to data we inferred or\ngenerated rather than received from you. **Where we cannot do all of what you ask, we will tell you which\npart we cannot do and why**, rather than declining as a whole.\n\n### How to make a request\n\nWrite to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find\nthe right records β the email address on the account is usually enough. You can also write to us by post\nat the address at the end of this policy.\n\n- **It is free.** We charge nothing for a request. If a request is manifestly unfounded or excessive,\n particularly because it repeats one we have already answered, the law lets us charge a reasonable fee\n based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you\n how to challenge that decision.\n- **We answer within one month** of receiving the request. Where a request is complex, or where you have\n made several, we may extend that by up to two further months β and if we do, **we will tell you within\n the first month, and tell you why**.\n- **We check who you are** before we hand over personal data, because the alternative is handing your data\n to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the\n email address already on the account. We ask for an identity document only where nothing lighter works,\n and anything you send us for verification is used for that and nothing else, then deleted.\n\n### If your data sits in a customer's workspace\n\n**This is the most important paragraph on this page for many of the people who read it.**\n\nA large part of the personal data in the Service was put there by one of our customers β your employer,\nthe organisation whose workspace you belong to, or the operator of a site built on our platform. Where the\nService captures data about how an organisation's own personnel work, that data belongs to that\norganisation's workspace.\n\n**For that data the customer is the controller and we are only their processor.** We process it on their\ndocumented instructions and for no purpose of our own, so the law directs your request to them, not to us.\nPractically:\n\n- **Send your request to that organisation.** They decide it, and they are the ones who have to answer you\n within the deadline.\n- **If you send it to us instead, we will not ignore it.** We will forward it to the relevant customer\n promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum\n requires.\n- **We will not decide the request ourselves, and we will not delete, correct or hand over data from a\n customer's workspace without their instruction** β unless a law that applies to us requires it. That is\n not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely\n what a processor is not allowed to do.\n\nIf you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell\nyou, and point you to the right organisation if it is not us.\n\n## Withdrawing your consent\n\nWhere we rely on your consent for something, **you can withdraw it at any time, and withdrawing is as easy\nas giving it**. You do not have to give a reason, and we do not ask you to justify it.\n\nWithdrawing consent stops the processing from that point onwards. **It does not make what we did before\nunlawful** β processing carried out while your consent was in force stays lawful, and withdrawal does not\nundo it. What it does mean is that we stop, and that we do not start again unless you tell us to.\n\n### How to withdraw, purpose by purpose\n\n- **Cookies and similar technologies** β open the **Cookie preferences** link in the footer of any page on\n [githands.com](https://githands.com), turn off the categories you no longer want, and save. The change\n takes effect immediately. Details are in our [Cookie Policy](https://githands.com/cookies).\n- **Marketing emails** β use the unsubscribe link at the bottom of any message we send you, or write to\n privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require\n you to sign in or find your password first.\n- **Optional features and integrations you switched on** β turn the feature off, or disconnect the\n connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we\n will turn it off for you.\n\nIf you have consented to something not listed here, write to privacy@ever.co naming it, and we will\nact on it the same way.\n\n### What happens next\n\nWe stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep\nthe minimum record needed to show that you consented and that you withdrew, because being able to evidence\nconsent is itself a legal requirement β for how long, see the retention section.\n\n**We will not quietly move the same processing onto a different legal basis to keep it running.** If some\npart of what you asked us to stop genuinely rests on another basis as well β an invoice we are required to\nkeep, for example β we will tell you which part and why, rather than leaving you to discover it.\n\nMost of what we do is not based on consent at all. It rests on performing our contract with you, on legal\nobligations, or on legitimate interests. **Withdrawing consent therefore does not close your account or\nswitch off the Service** β it affects only the things you consented to.\n\n## Complaining to a supervisory authority\n\nIf you think we have handled your personal data badly or unlawfully, **you have the right to complain to a\ndata protection supervisory authority**. That right is yours regardless of anything else in this policy.\n\nWe would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and\nwe will look into it and come back to you. In most cases that is the quickest way to get the outcome you\nactually want. **You are not required to do this, and it is not a condition of complaining** β you can go\nstraight to an authority, and you can do it at any point, including while we are still dealing with your\ncomplaint.\n\n### Our lead supervisory authority\n\nWe are established in Bulgaria, so our lead authority is the\n**Commission for Personal Data Protection (ΠΠΎΠΌΠΈΡΠΈΡ Π·Π° Π·Π°ΡΠΈΡΠ° Π½Π° Π»ΠΈΡΠ½ΠΈΡΠ΅ Π΄Π°Π½Π½ΠΈ)** β the CPDP. Its website,\nincluding its complaint form and current contact details, is at\n[https://www.cpdp.bg/](https://www.cpdp.bg/).\n\n### You can also complain closer to home\n\nUnder Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:\n\n- where you live;\n- where you work; or\n- where the thing you are complaining about took place.\n\nYou do not have to use ours, and you do not need our agreement to use another one. If you complain to your\nlocal authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this\nsituation, so nothing is lost by choosing whichever is easiest for you.\n\nYou also have the right to an effective judicial remedy β against a supervisory authority's decision, and\nagainst us directly β in the courts of the country where you live or where we are established. Complaining\nto an authority does not use up that right.\n\n## Automated decision-making and profiling\n\n**We do not make decisions about you that produce legal effects concerning you, or that similarly\nsignificantly affect you, based solely on automated processing.** No algorithm of ours decides whether you\nare hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a\ndecision of that kind is made about you by an organisation using the Service, a person at that\norganisation makes it.\n\nWe do use automated rules to detect fraud, spam, abuse and attacks against the Service β rate limits,\nanomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one\nof them affects you, write to privacy@ever.co and a person will review it.\n\n### Where a customer turns on AI features, be aware of this\n\nThis is the part worth reading carefully, because it is easy to misunderstand.\n\nSome of our products capture activity data on behalf of a customer β an employer, typically β and some of\nthem offer optional AI features on top of it. **Where a customer enables those features, the Service can\ngenerate automated assessments of the activity it captures.** The clearest example: classifying whether\nthe content of a captured screen appears to be work-related. Other examples include scoring or summarising\ncaptured activity and grouping it into categories.\n\nFour things follow, and we would rather state them plainly than let them be discovered later.\n\n- **The output goes to the customer, not to us.** It is presented to the organisation whose workspace the\n data belongs to. **That organisation is the controller of it, and we are only its processor.**\n- **The customer decides what, if anything, to do with it.** We do not act on these assessments, we do not\n use them for any purpose of our own, and we do not share them with anyone else.\n- **These outputs are not decisions, and must not be used as if they were.** An automated assessment is an\n input to a human judgement. **Our terms require the customer not to treat an output of the Service as an\n automated decision about a person, and to apply meaningful human review before acting on one.** Whether\n any particular use is lawful where that customer operates β including the lawful basis for it, the\n notices it has to give, any impact assessment it has to carry out, and any consultation with employee\n representatives it has to run β is that customer's responsibility to determine, not ours.\n- **They can be wrong.** A classifier reading a screen has no idea what your job is. It can label genuine\n work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it\n as a rough signal, and we say so to our customers as well as to you.\n\n### If an assessment about you has been generated\n\nAsk the organisation whose workspace holds the data β normally your employer. You can ask them for human\ninvolvement, for an explanation of how the assessment was reached, to express your point of view, and to\ncontest the result. They are the controller, so they are the ones who have to answer.\n\nIf you send that request to us, we will forward it to them promptly, tell you we have done so, and assist\nthem in answering it. See the routing paragraph in the section on your rights, which explains why we\ncannot decide it ourselves.\n\n## Children\n\n**The Service is not directed at children, and we do not knowingly collect personal data from them.** It\nis a business product, bought by organisations and used by the people who work in them. We do not design\nit for children, we do not market it to them, and we do not offer accounts to them.\n\nWhere consent is the basis for an online service offered directly to a child, the GDPR sets the age at\nwhich the child can consent alone. **In Bulgaria that age is 14.** Other EU and EEA countries set\nit anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.\nBelow that age, consent has to come from β or be authorised by β a holder of parental responsibility.\nBecause we do not offer the Service to children, we do not operate a parental consent mechanism, and a\nchild under the applicable age should not create an account or submit personal data to us.\n\n### If a child's data has reached us\n\nTell us. Write to privacy@ever.co with enough detail for us to find the record β an email address, an\naccount name, or the page where the data was submitted. You do not need to prove anything first, and you\ndo not need to be the child's parent to report it.\n\nWe will check, and where we confirm that we hold personal data collected from a child without proper\nauthorisation, **we will delete it without undue delay**, keeping only what a law that applies to us\nrequires us to keep.\n\nIf the data sits inside one of our customers' workspaces rather than in our own records, the customer is\nthe controller of it. Tell them as well, and tell us β we will forward your report to them and press for\nit to be dealt with, as the routing paragraph in the section on your rights describes.\n\n## Links and content from other sites\n\nOur websites and the Service link to services we do not run, and some pages embed content that other\npeople host β videos, maps, code repositories, documentation and similar.\n\nFollowing a link takes you somewhere this policy does not reach. Loading embedded content means the\nprovider hosting it receives data directly from your browser, typically your IP address, your device and\nbrowser details, and the page you were on, and it may set its own cookies.\n\n**We do not control those services, and this policy does not apply to them.** What they collect and what\nthey do with it is governed by their own privacy notice, which is the one to read before you use them.\nWhere embedded content is not strictly necessary to deliver a page, we load it only once you have agreed\nto the relevant cookie category β see our [Cookie Policy](https://githands.com/cookies).\n\nA link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we\nwould like to know at privacy@ever.co so we can reconsider carrying it.\n\n## Changes to this policy\n\nThis policy changes when the Service changes, when we engage or replace a provider, or when the law moves.\nWe would rather update it than let it drift out of date and quietly stop being true.\n\nEvery version carries a version number and the date it takes effect, shown at the top of the page. **This\nis version 1.0.2, in force from 2026-08-02.**\n\n### How we tell you\n\n- **Minor changes** β clarifying wording, correcting a mistake, adding a provider of a kind already\n described β are published with a new version number and a new effective date. We do not send a separate\n notice for these.\n- **Material changes** β a new purpose, a new category of personal data, a new category of recipient, a\n longer retention period, a change to how you exercise your rights, or a change to the legal basis we\n rely on β are notified **at least 30 days before they take effect**, by email to account holders and by\n a notice on the site. That gives you time to read them and to act before they apply.\n- **Changes that need your consent** are not made by publishing a new version. We ask you, and we treat\n silence as a no.\n\nThis policy is a notice, not a contract. **We do not ask you to accept it**, and continuing to use the\nService is not us collecting your agreement to it. Where we genuinely need your agreement to something, we\nask for it separately and record it.\n\n### Previous versions stay available\n\nWe do not overwrite the past. **Every version of this policy that we have published remains available**,\nwith the dates it was in force, from the version history linked at the foot of\n[https://githands.com/privacy](https://githands.com/privacy). If you want to know what we said about your data on a\nparticular date, that is where to look β and if you cannot find it, ask us at privacy@ever.co and we\nwill send it to you.\n\n## How to contact us\n\nThe controller for the personal data described in this policy is **Ever Technologies LTD**, registered in\nBulgaria under company number 204599535, with its registered office at\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n- **Privacy questions, and any request about your personal data** β privacy@ever.co\n- **Data protection correspondence** β dpo@ever.co\n\nBoth addresses are monitored by the same people, and either will reach us. By post, write to the registered\noffice above and mark the letter for the attention of the privacy team. We correspond in English.\n\n**We have not designated a Data Protection Officer under Article 37 GDPR.** The dpo@ever.co address is\na contact channel, not a designation, and we will not describe it as one. If that position changes, this\npolicy will say so and will give the designated office's contact details.\n\nIf your question is about personal data held inside one of our customers' workspaces, that customer is the\ncontroller and the request goes to them β see the routing paragraph in the section on your rights. Write to\nus anyway if you are unsure, and we will tell you who to ask.\n\nThis document is version 1.0.2 of the Privacy Policy for\n[githands.com](https://githands.com), in force from 2026-08-02. Earlier versions, with the\ndates they applied, are at [https://githands.com/privacy](https://githands.com/privacy)."
|
|
380
380
|
}
|
|
@@ -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.
|
|
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 "<strong>Service</strong>"). It tells you what we collect, why, who else sees it, how long we keep it,
|
|
@@ -1316,7 +1316,7 @@ would like to know at privacy@ever.co so we can reconsider carrying it.</p>
|
|
|
1316
1316
|
<p>This policy changes when the Service changes, when we engage or replace a provider, or when the law moves.
|
|
1317
1317
|
We would rather update it than let it drift out of date and quietly stop being true.</p>
|
|
1318
1318
|
<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.
|
|
1319
|
+
is version 1.0.2, in force from 2026-08-02.</strong></p>
|
|
1320
1320
|
<h3 id="how-we-tell-you" tabindex="-1">How we tell you</h3>
|
|
1321
1321
|
<ul>
|
|
1322
1322
|
<li><strong>Minor changes</strong> β clarifying wording, correcting a mistake, adding a provider of a kind already
|
|
@@ -1354,6 +1354,6 @@ policy will say so and will give the designated office's contact details.</p>
|
|
|
1354
1354
|
<p>If your question is about personal data held inside one of our customers' workspaces, that customer is the
|
|
1355
1355
|
controller and the request goes to them β see the routing paragraph in the section on your rights. Write to
|
|
1356
1356
|
us anyway if you are unsure, and we will tell you who to ask.</p>
|
|
1357
|
-
<p>This document is version 1.0.
|
|
1357
|
+
<p>This document is version 1.0.2 of the Privacy Policy for
|
|
1358
1358
|
<a href="https://hust.so">hust.so</a>, in force from 2026-08-02. Earlier versions, with the
|
|
1359
1359
|
dates they applied, are at <a href="https://hust.so/privacy">https://hust.so/privacy</a>.</p>
|