What SLATE reads, keeps and shares

Effective November 2, 2026

SLATE is a Chrome extension and dashboard that helps recruiting teams score LinkedIn profiles against their own role definition and example candidates. It also lets teams send email sequences from their own Gmail accounts. This policy covers the SLATE extension and the SLATE service behind it, run by Phoenix ("SLATE", "we").

In short:

SLATE reads LinkedIn profile, people search and Recruiter pages, and only what's already on your screen. On our own site, slate.you, its one job is letting the “Log in” button open your dashboard.
Profile text is sent to our AI provider, Anthropic, to produce a score. Anthropic doesn't train its models on it.
If you connect Gmail, SLATE sends your sequence emails from it and checks for replies from the people it emailed. It reads nothing else in your inbox. The start of each reply is kept so your team can read it, and sent to Anthropic to tag it as interested, not interested or neutral. Anthropic doesn't train its models on it.
Most of what SLATE keeps stays in your browser. Only your account, and the profiles your team chooses to save, are stored on our servers.
We don't sell data, show ads, or track you around the web.

Who uses SLATE

SLATE is by invitation only. A team admin invites each member by email, and nobody can create an account on their own. Two groups of people have information in SLATE. Users are the team members who sign in. Candidates are the LinkedIn members whose profiles users score. Both are covered below.

What SLATE collects

Your account

Your email address, the name and job title you enter, who invited you and when, and when you last signed in. Your password goes to our authentication provider, which stores it in hashed form. We never see or store it in plain text.

Profile content you score

When you score a profile, the extension reads the text of the LinkedIn page you're looking at: the person's name, headline, location, current and past roles, and About section. You score a profile by opening it with automatic scoring turned on, by clicking "Score this profile", or by clicking "Score all visible" on a search results page. Automatic scoring is on by default; you can turn it off in the extension's Settings, and then a profile is read only when you click to score it.

On LinkedIn, the extension runs only on www.linkedin.com profile pages, people search results and LinkedIn Recruiter pages. It doesn't read your messages, your connections or any other website. On our own site, slate.you, it only lets the “Log in” button open your SLATE dashboard, and reads nothing there. Apart from the profiles you score, it keeps no record of the pages you visit.

What your team adds

Role definitions, the example profiles you mark as good or poor fits, the scores SLATE returns, and feedback you give when you disagree with a score. When you click "Add to" on a profile, SLATE saves that profile and its score to your team's shared workspace. Notes, project stages and files you attach there are saved too.

Candidates' email addresses

The email address SLATE finds for a candidate, or that your team types in, is saved in your team's workspace. So are which service found it and what ZeroBounce said about it. SLATE keeps each service's answer, so it never asks or pays for the same person twice.

Usage records

For each AI request, our server records the type of request, the AI model, how many tokens it used, what it cost, your user and team IDs, and the time. These records don't contain profile content. We use them to enforce your team's monthly AI allowance. The dashboard's Costs screen also keeps a log in your browser. That log includes full request content only if you turn that option on in Settings.

Where it's stored

In your browser. Roles, example profiles, cached scores and extracted profile data, your saved list, feedback, the Costs log and your login session are kept in the extension's local storage on your computer. They stay there until you clear them or uninstall the extension. If you sign in to the web dashboard at slate.you/app, your login session and a copy of your team's roles, example profiles and scores are kept in that browser's storage for slate.you, until you sign out or clear site data.
On our servers. Your account, your team membership, your team's roles with their example profiles, the scores your team makes (each with the structured profile data it was scored from and a link to the person's LinkedIn profile photo, so teammates can see who was scored), the LinkedIn profile links your team imports to score, the profiles your team adds to its workspace (with their notes and attachments), and usage records are stored with our hosting provider, Supabase. Database rules restrict each team's records to that team's members.

Gmail

Any user can connect their own Gmail account through Google's sign-in. SLATE then sends the emails in that user's email sequences from that mailbox, on the schedule the user set.

What SLATE asks Google for

Your email address, so SLATE knows which mailbox you connected.
Permission to send email as you (gmail.send), to send your sequence emails.
Permission to read your email (gmail.readonly). SLATE uses it only to spot replies and bounces from the people SLATE emailed (in the threads SLATE started, or a new email from their address), to keep the start of each reply, and to read the ID of each email it sent so follow-ups land in the same thread.

SLATE doesn't read, store or index the rest of your inbox.

What SLATE stores

The connected email address and name.
An access token, encrypted on our servers, so SLATE can keep sending until you disconnect.
For each email SLATE sent: the recipient, subject, body, send time, and Gmail message and thread IDs.
Whether and when the person replied, or the email bounced.
For a reply: its first 500 characters or so, without the earlier emails it quotes, and its tag (interested, not interested or neutral) with a short quote from the reply explaining it. Out-of-office and other automatic replies aren't kept.

Emails go out as plain text. SLATE adds no tracking pixels and doesn't rewrite links.

Sending on someone's behalf

A teammate, usually the hiring manager, can be the sender of a sequence. Emails go from that person's Gmail only after that person approves them in SLATE. Nobody can send from a mailbox they didn't connect without the owner's approval.

Who can see it

Your teammates can see the emails sent from your team's sequences, whether each one got a reply, and the start of each reply with its tag. They can't see anything else in anyone's inbox.

Disconnecting

You can disconnect Gmail in SLATE at any time, or revoke SLATE's access at myaccount.google.com/permissions. Disconnecting deletes the stored token and stops all sends from that mailbox. The send history stays in your team's workspace until your team deletes it or closes its account.

How we use Gmail data

The only Gmail data sent to an AI provider is the start of a reply to one of your sequence emails, sent to Anthropic to tag it for your team. Gmail data is never used to train AI or machine-learning models, ours or anyone else's. We don't use it for ads, and we don't sell it. Nobody at SLATE reads it, except with your consent, when it's needed for security, or when the law requires it.

SLATE'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.

Who we share it with

Only the service providers SLATE needs to work, and only for that purpose:

Anthropic provides the AI that extracts and scores profiles. For each scoring request, our server sends Anthropic the profile text along with your role definition and example profiles. Anthropic processes this under its commercial terms, which don't allow it to train models on that content. When someone replies to a sequence email or LinkedIn message, our server also sends Anthropic the start of that reply so it can be tagged interested, not interested or neutral, under the same terms.
Google runs the Gmail API. If you connect Gmail, the emails you send through SLATE go through it, and SLATE uses it to check those threads for replies and bounces.
Unipile connects SLATE to LinkedIn for team members who connect their LinkedIn account. The member signs in to LinkedIn on Unipile's own page, so SLATE never sees their LinkedIn password, and Unipile keeps that connection for SLATE. Through it, SLATE reads the LinkedIn profiles your team imports, sends the invitations and messages in your team's sequences, and is told when someone replies. Unipile handles those profiles, messages and replies to do this.
Apollo, FullEnrich and ContactOut find candidates' email addresses. SLATE asks them for people your team adds to a role, or when someone on your team clicks Find email. For each person, SLATE sends the person's LinkedIn profile link. Apollo also gets the person's name and current company when SLATE has them. SLATE asks them one at a time, Apollo first, then FullEnrich, then ContactOut, and stops at the first address that passes ZeroBounce's check. No service is asked twice about the same person. They don't receive scores, notes or anything else from your workspace.
ZeroBounce checks that an email address can receive email before SLATE uses it. This covers addresses found by the services above and addresses your team types in or imports. SLATE sends ZeroBounce only the email address.
Supabase hosts SLATE's database, logins, file storage and server functions.
Our email provider delivers invite codes and password reset codes to your email address.
Google Fonts serves the typefaces on the SLATE dashboard. As with any web request, Google receives your IP address and browser details when the fonts load.
Your teammates can see your name and title, and everything saved to your team's workspace.

We may also disclose information if the law requires it.

What we don't do. We don't sell user data or candidate data. We don't use it for advertising, and SLATE has no analytics or tracking. We don't use or transfer data for any purpose other than scoring and organizing candidates, finding their email addresses, and sending your team's email and LinkedIn outreach. We don't use it to determine anyone's creditworthiness or for lending. Nobody at SLATE reads your team's data, except when you ask us for support, when it's needed for security, or when the law requires it.

If your profile was scored

If you're a LinkedIn member, a SLATE customer may have scored your profile using what LinkedIn showed them. The team that saved your profile decides what to keep. To find out whether we hold information about you, or to have it deleted, email phoenix@slate.you with your LinkedIn profile URL. We'll delete it from our servers and ask the team concerned to remove any copies they hold.

If you got an email through SLATE

If a SLATE user emailed you, the sender's team holds your email address and the messages sent to you. To have them deleted, email phoenix@slate.you with the address the email went to. We'll delete it from our servers and ask the team concerned to remove any copies they hold.

Keeping and deleting data

In your browser: until you clear it or uninstall the extension. Uninstalling deletes all of it.
Team workspace: until a team member deletes it, or your team asks us to close its account.
Gmail connection: the stored token is deleted when you disconnect. The send history is part of your team workspace and is kept or deleted with it.
Your account: your admin can remove you from the team at any time. To have your account deleted entirely, email us.

Security

All traffic between the extension and our servers uses HTTPS. Each team's data is separated by database access rules tied to your account. The keys that can bypass those rules exist only on our servers and never in the extension. Gmail tokens are encrypted, and only SLATE's server functions can read them. They never reach the extension or your browser. No system is perfectly secure, but we'll tell affected teams promptly if a breach exposes their data.

Children

SLATE is a workplace tool for recruiting teams. It isn't directed at children, and we don't knowingly collect information from anyone under 16.

Changes to this policy

If this policy changes, we'll update the date at the top. For changes that matter, we'll tell team admins by email before they take effect.

Contact

Questions or requests: phoenix@slate.you.