The words we use in a fixed sense, in the Recruiter Terms of Service, the Developer Terms of Service, the Privacy & Security policy and the FAQ. Each entry links to the place that defines it; nothing here adds a rule.
Accounts and people
Account holder. Anybody who signs in with GitHub: a recruiter, a developer, or the same person as both. Privacy §1.
Recruiter. Somebody who signed in with GitHub and holds a recruiter subscription, paid or on its free trial. We do not verify employers. Developer Terms §12.
Developer. Somebody with a public GitHub account who made a Thleo developer account. Whether they are shown to anyone is their choice. Developer Terms §1.
Candidate. A developer as a recruiter sees them: a GitHub username searched, saved, noted or tagged in a workspace. Only an authorized developer ever becomes one. Recruiter Terms 8.2.
Sign-in address. The email address on your GitHub account, kept on your sign-in record. The one-time codes that authorize a charge go there and only there. Recruiter Terms 2.1.
Address for notices. Where we write to you about a new version of the documents you agreed to. Starts as your sign-in address; change it on your Account page. Recruiter Terms 2.2, Developer Terms 5.6.
Being findable
Hidden. A developer account nobody can find. Every new account starts here. A recruiter searching the username is told there is no profile, word for word as for a username that never existed. Nothing is deleted; the settings wait. Developer Terms 5.1.
Visible to recruiters. Findable by signed-in recruiters only, ever. Developer Terms 5.1.
Public. Findable by recruiters, and served on a page at thleo.app/developers/<username> that
anyone with the link can open without signing in. Same fields, same boxes, nothing more.
Developer Terms 5.1.
Authorization, the box. The checkbox on a developer's Account page whose wording is the consent to be shown to recruiters. Ticking it stores a receipt; unticking it stamps the withdrawal. It is a separate act from accepting the Terms, and nothing ticks it for you. Developer Terms 5.2.
Receipt. The record of the authorization: which wording version, when ticked, that the person was signed in through GitHub, and when withdrawn. Never deleted, even by a full deletion. Developer Terms 5.2.
The three conditions. An account, a findable visibility, and a current authorization. All three, at once, checked on every read; miss one and nothing is shown, counted or newly stored. Developer Terms §3.
Stopping
Going Hidden. Ends the showing and deletes nothing. The reversible one. Developer Terms §6.
Withdrawing. Unticking the authorization box. Ends the showing and empties our copy of the profile, in every recruiter's search history too, and deletes every switched-on link. The account and its settings stay, so ticking again brings you back. Developer Terms §6.
Deleting, erasure. The button on the developer's Account page. Removes the records themselves, the analyses, the notes recruiters wrote, and the account. Needs the GitHub sign-in; there is no email route. Developer Terms §7, Privacy 2.5.
Suppression list. Two columns kept after a deletion: the numeric GitHub account id and the date. It exists so the next search cannot bring a deleted person back; the database refuses the write underneath the whole product. Only the person can take their id off it, by signing in again and ticking the authorization box; a recruiter never can. Developer Terms 7.4.
Closing a recruiter account. Three steps in order: cancel the subscription, press Delete my account on the Danger Zone tab, revoke Thleo at GitHub. The button closes the account at once and a daily job deletes it thirty days later; signing in again before then restores it. Recruiter Terms 12.1.
Copies and time
Copy, cache. What Thleo keeps of a developer's public GitHub profile so a recruiter's page does not need a request to GitHub every time it loads. Holds only the fields the developer allows. Privacy 2.1.
Refresh, the refresh profile cycle. Re-reading the copy from GitHub. It happens only when somebody acts: the developer opens their Account or Explore page and the copy is older than six hours; a recruiter searches the username and it is older than an hour; a recruiter presses Refresh from GitHub on the card; a recruiter opens a collection the developer is in and the copy is older than fourteen days; or the developer presses their own Refresh button or changes any box. There is no timer. Developer Terms §2, Recruiter Terms 8.3, Privacy 2.4.
Version. Every document here is a dated file that is never edited after it goes live; a change is a new file beside the old one. The version you accepted is recorded with the date. Privacy §8.
Notice, deemed acceptance. A new version of a Terms or of the privacy policy is announced at least 14 days before it takes effect, by one email to the address for notices and a banner in the product. Accepting is one click; continuing to use Thleo after the date counts as acceptance and is recorded as such. The authorization box is the exception: it is consent, and only the person can tick it. Recruiter Terms §14, Developer Terms §11.
Workspaces and money
Workspace. Where a recruiter's data lives. The personal workspace is private to one person; a team workspace is shared by every active member and nothing moves between the two. Recruiter Terms §3.
Team, admin. A team exists when a recruiter pays for a team subscription in a company's name; that company is the customer, and the recruiter who paid is the team's admin and acts for it. The admin invites, removes, changes seats, and is the only one who reads the team's activity log. The role moves to another member on the company's request to support. Recruiter Terms §3.
Seat. One paid place in a team, held by an active member or a pending invitation, the admin included. Adding a seat is a charge confirmed by an emailed code; reducing seats lowers the next invoice. Recruiter Terms §5.
Free trial. Fourteen days, card given at checkout and charged when the trial ends unless cancelled first. Once on your first individual subscription and once on the first team you pay for, because they are two separate billing accounts; never a second time on the same one. Recruiter Terms §4.
Founding price. The price at checkout today, held for 24 months from your first subscription while it stays active; the regular price is printed beside it on the pricing page. Recruiter Terms §4.
Controller, processor. The two roles data-protection law names. Thleo is the controller for a developer's profile and for every sign-in record; for what a recruiter writes about a candidate, the recruiter's company is the controller and Thleo is its processor. Privacy 3.7, Recruiter Terms §16.
Collection. A named group of candidates or repositories in a workspace, with notes and tags. Personal and team workspaces have different caps per collection; the recruiter FAQ has the table. Recruiter FAQ.
Activity log. The append-only record of governance actions in a team. Written by the system, never edited afterwards by anyone. Recruiter Terms §3.