Who this notice covers
TPP Recruit is recruiting software operated by The Personality Project. Employers use it to publish jobs, receive applications, and manage hiring decisions. This notice describes what TPP Recruit does with personal data.
Two different groups appear in the service, and the relationship differs for each. Employers who license the service decide what candidate data they collect and how long they keep it; for that data they are the controller and we act on their instructions. For the accounts of the employer's own staff who sign in, and for the marketing pages on this site, we decide, and this notice governs directly.
TPP Employer is a separate assessment product with its own boundary. Where the two connect, the assessment record is held on the Employer side.
What the service collects
The service holds three broad categories.
- Account data for the employer's staff: name, work email address, organization membership, and role. This is what sign-in and permissions are built from.
- Candidate and application data, supplied by the candidate when they apply or imported by the employer from a previous system: contact details, the application form's answers, uploaded documents such as a CV or transcript, and the hiring record built around them - stage, interviews, scorecards, notes and offers.
- Connected mailbox data, described in its own section below, present only when a recruiter chooses to connect one.
Connected mailboxes, and Google user data
A recruiter may connect their own Gmail or Microsoft Outlook mailbox so that email they write to a candidate is sent from their own address rather than from ours. Connecting is optional, it is per person, and nothing about the rest of the service depends on it.
When a recruiter connects a Google mailbox, the service asks Google for four permissions, and a fifth only if reply sync is turned on, and stores nothing beyond what they allow:
- Send email on your behalf (gmail.send) - the permission that lets a message you wrote in TPP Recruit leave from your own mailbox and, if your employer picks your mailbox as a brand's automatic sender, the automatic email to candidates and to the employer's own hiring team.
- Your email address, your basic profile, and a sign-in identifier (userinfo.email, userinfo.profile, openid) - so the service can show you which mailbox is connected and attribute the message to you.
- Only if your employer has allowed reply sync and you turn it on for your own mailbox: read your mail (gmail.readonly, or Mail.Read for Outlook) - used only to bring in replies from candidates you wrote to through TPP Recruit, and bounce notices for those messages. This permission is asked for separately, after you have connected, and is never part of the first connection.
What connecting a mailbox does not give us
The send permission does not carry the ability to read mail. Unless you turn on reply sync, the service cannot open your inbox, read replies, list your messages, search your mail, or reach your contacts or calendar.
Reply sync is off unless two people choose it: an owner or admin of your employer's workspace allows it, and then you turn it on for your own mailbox. With it on, the service looks only for replies from candidates you wrote to through TPP Recruit, and bounce notices for those messages. It stores those and skips everything else: no other message is copied, kept or shown to anyone. The read permission is read only: the service never sends, moves, labels or deletes mail with it, and it never reaches your contacts or calendar.
These are not only undertakings. The database refuses to store a connection carrying the read permission unless the workspace has allowed reply sync, and when the workspace turns reply sync off the service stops reading at once. You can withdraw the permission yourself at any time by disconnecting the mailbox.
We do not use a connected mailbox for marketing campaigns. Messages sent to several candidates at once, and follow-up sequences, are written and started by a person at the employer and go out one candidate at a time.
TPP Recruit's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What is stored for a connected mailbox, and where
For each connection the service records the provider, your mailbox address, your Google account identifier, the permissions granted, the connection's status, and when its access expires. It also records a reference to the credentials.
The credentials themselves - the access and refresh tokens Google issues - are held encrypted in Supabase Vault and are reachable only by the backend service identity that sends mail. They are never returned to a browser, never exposed to any user of the service including you, and never written to logs. The stored row holds only an opaque reference to them.
For each message sent through a connected mailbox, the service stores the recipient address, the subject, the message body, the provider's identifier for the message, whether it sent, and when. That record is the employer's audit trail of what was said to a candidate, and it is what makes the hiring record complete. It is visible to members of that employer's organization and to nobody else.
Disconnecting, and what happens to the access
You can disconnect a mailbox at any time from Settings, Integrations. Disconnecting stops the service sending from it immediately.
The service then revokes the grant with the provider and deletes the stored credentials, so the permission you gave is withdrawn at Google rather than only forgotten by us. You can also revoke it yourself from your Google Account's third-party access settings, which has the same effect.
Messages already sent are not recalled - they are in the recipient's mailbox and in your own provider's Sent folder, neither of which we control. The record of those messages stays in the employer's hiring record, because deleting the account's history of what a candidate was told is not ours to do unilaterally.
Email between an employer and a candidate
If you are a candidate, the employer may write to you through TPP Recruit, and these emails come from a person at the employer or from the employer's name. What happens to your answers and to the email itself:
- Replies. When an employer chooses to receive replies in TPP Recruit, its emails ask you to reply to an address the service runs. Your reply, and any files you attach, are stored with your application so the employer's hiring team can read them.
- Opens and clicks. Only if the employer has turned this on, the service records when you opened one of its emails and which link in it you clicked. It does not record where you were or which device you used. Some mail apps open emails by themselves, so an open is not proof you read it.
- Mailboxes. An employer's staff may connect their own mailbox and allow the service to bring in your replies sent to them there, as described in the sections above.
How the data is used
Personal data in the service is used to run the service: to authenticate people, to show an employer its own hiring records, to receive and process applications, to send the messages a user asks to send, and to keep an audit of actions taken so an employer can account for its own hiring decisions.
We do not sell personal data. We do not use candidate data or Google user data to train machine-learning models. We do not use a connected mailbox's data for advertising or for any purpose other than sending the messages the recruiter writes and the automatic email the employer has chosen to send from it and, where reply sync is on, bringing in candidates' replies to them.
How long data is kept
Candidate and hiring records are kept for as long as the employer's account is active, because the employer decides its own retention and may be required to keep hiring records for a period. An employer can ask us to delete its data, and on account closure we delete it.
Connected mailbox credentials are the exception and are not kept: they are deleted when the connection is disconnected or revoked, whichever happens first.
Records that exist to show what the system did - audit entries and message delivery outcomes - are kept alongside the account they belong to.
Access, correction and deletion
If you are a candidate, the employer you applied to controls your application. Ask them first; we will support them in answering you, and you can also write to us at admin@thepersonalityproject.com and we will route it.
If you are a user of an employer's account, or you want to ask about a connected mailbox, write to admin@thepersonalityproject.com.
Depending on where you live you may have rights to access, correct, export, or delete your personal data, or to object to some processing. We will tell you what we can do and who holds the decision when the employer is the controller.
Security
Access to an employer's data is restricted to members of that employer's organization, enforced in the database itself rather than only in the application, so a request that escaped the interface still cannot read another organization's rows.
Mailbox credentials are encrypted at rest and reachable only by the backend identity that sends mail. Traffic is encrypted in transit.
No service is perfectly secure, and this notice does not constitute a security certification.
Changes to this notice
If this notice changes materially - in particular if the service ever asks for a broader mailbox permission than those described above - we will update the effective date and tell account holders before the change takes effect. A broader permission would also require you to grant it again.
Contact
Questions about this notice, or a request about your data: admin@thepersonalityproject.com.