relinked privacy policy

Privacy policy

Privacy policy

Last updated November 3, 2026.

What Relinked collects

Your Google account identity and email address from sign-in. Gmail metadata headers — the sender, reply-to address, recipients (including Bcc on mail you sent), subject, and date of a message, the headers that mark a message as an automatic reply, and Gmail’s own message and thread IDs — and never message bodies, snippets, attachments, or drafts. The profile and preference answers you give us. The contact graph derived from that mailbox: names, email addresses, email domains, employers, titles, how often and in which direction you corresponded, and the evidence behind a warm path. Subject lines are read in memory to sort a thread into a coarse type and are then discarded; the only facts Relinked keeps from a subject are the LinkedIn notification details and interview times described below.

Relinked also records the job pages you view on supported sites. That view is normally stored as a hash of the page address along with view counts and visible dwell time; if you choose “Apply anyway” after a warm-path prompt, the page address itself is kept in that audit record. Your actions in the product — tracked and dismissed companies, outreach status, interview notes — are stored too.

If you gift companies from your network to someone, Relinked stores their email address, the company names you chose, an optional note, and later intro requests (the company, the posting they opened, and an optional note). They see your name and those company names and can browse open roles there. Contact names, contact email addresses, and how many people you know at each company are never shared with them. You can revoke a gift, which ends their access.

To show whether a contact usually answers you, Relinked keeps, for each email thread you started with someone in your graph, the Gmail thread ID, when you first wrote, and when they first replied — not the subject or any content. Those facts belong to your account, are shown only to you, and are not combined with other users' data. When you start an outreach from a warm-path card, Relinked records whether you asked about the firm or asked for an intro, the card's position, and the relationship, evidence, and reply bands that card showed, so we can tell which kinds of asks get answered. Relinked also logs once a day which cards a company page showed you.

If you upload a LinkedIn data export (the zip LinkedIn emails, or Connections.csv), the extension reads only three files from it on your device: Connections.csv, and, when you included your Profile in the export, Positions.csv and Education.csv. From Connections it drops the email column there and sends names, profile URLs, companies, titles, and connection dates. Those rows are stored on a table that belongs to your account and never include an email address. They are used to match connections to people you already email, to fill in the current employer and title of a contact whose email does not show one, and to work out where a phone contact with the same name works. When an employer or title from them is recorded for someone you already email, it is stored on that person's shared record (see “People who are not Relinked users” below). From Positions and Education it sends your own employers, titles, schools, and dates, which are stored on your account and used only to tell you when a contact worked or studied where you did. Every other file in the export stays on your device.

Relinked also learns from LinkedIn's own emails in your Gmail. When LinkedIn emails you that someone accepted your invitation, started a new position, or has a work anniversary or birthday, the subject line names that person and sometimes their employer and title. Relinked keeps the name, company, and title the subject states, together with the date and Gmail ID of that notification. When LinkedIn emails you that someone messaged you or replied to your message, Relinked keeps the sender's name, whether it was a new message or a reply, the time, and the Gmail ID, and counts it toward how often you and that person are in touch. A sender who is not already one of your contacts becomes a contact on your account only. The subject line itself is not stored, and emails about pending invitations are not used. All of these rows are deleted when you disconnect Gmail; the connection rows are also deleted when you disconnect LinkedIn.

If you upload a phone or address book (an Apple Contacts vCard, or a Google or Outlook contacts CSV), the extension reads that file on your device and sends names, organisations, titles, email addresses, phone numbers, and — when the file has one — the city. Street addresses, postal codes, and the full formatted address are dropped on your device and are not uploaded. Every card with a name and a phone number or email is stored on a table that belongs to your account; nothing from the file is written onto the shared address list other users' graphs read. For each card Relinked works out a current employer from the card's own organisation field, or from a LinkedIn connection with the same name, so that a job posting at that company can show you a friend you can text. No phone number or name from that file is sent to a third party to look anyone up. If a supplied email already belongs to a different person in Relinked, that card is queued as a conflict and is not attached to them. If you tell Relinked the city you live in, that city is stored on your profile and used to flag contacts in the same city.

If you add a resume (a PDF, Word file, or pasted text) for the resume-fit check, the extension reads it on your device and keeps only the parsed result — employers, firm type and tier, titles, dates, the lines listed under each role, and credentials — in this browser's extension storage. The file itself and its full text are not kept. To compare it with a posting, the extension reads the posting text on the page you are viewing and keeps it in the same local storage alongside the current page. Signing out or deleting your account clears the parsed resume. For postings Relinked collects from job boards, the requirements a posting states (prior firm type, tier, years, credentials) and its qualification bullets are extracted when the posting is fetched and stored with it; the rest of the posting text is not.

Paid plans include an AI detailed read of resume fit. When you click it, on a posting page or in the job board, the extension sends that posting (or its stored qualification bullets) and your parsed resume roles (employer, title, dates, and the lines under each role, but not your name, email, or phone) to Relinked's server, which passes them to Anthropic's Claude for the comparison and returns the answer to your browser. Relinked does not store the resume roles or the answer; it keeps only a daily count of checks.

Relinked does not store your card or bank details; Stripe holds those. We keep Stripe customer, subscription, and payment identifiers and your plan status. The Relinked website is hosted on Squarespace, which sets cookies needed to run the site and may record visitor statistics for us. Relinked adds no advertising pixel or session replay to the website, and the extension contains no analytics.

How Gmail and Calendar data is used

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements:

• Gmail metadata and Calendar attendee data are used solely to provide Relinked’s warm-path and job-search features.

• It is not used for advertising.

• It is not sold.

• It is not used to develop, improve, or train generalized AI or machine-learning models.

• People at Relinked do not read it, except with your permission, to investigate security issues or abuse, to comply with the law, or when it has been aggregated and anonymized for internal operations.

• It is transferred only as needed to provide those features: to the processors named below, and, when you choose to gift companies to someone, company names only to that person. Gmail message content is never transferred to anyone, because Relinked never requests it. No contact name or employer derived from Gmail metadata or Calendar attendees is sent to a data broker or enrichment vendor, and no contact name, contact email address, or message content is sent to an AI model. Company names and website domains, which can include employers Relinked identified from your contacts’ email addresses, are sent to Anthropic to classify the company, as described under “Where other data comes from”.

If you turn it on, Relinked can prepare a draft email from a fixed template, filling in a contact's first name, the company, and your first name. You review and send it in Gmail. Relinked never sends email and never writes to your Gmail Drafts. After you open a Gmail compose from Relinked, it checks the headers of your sent mail for a message to that contact and, when it finds one, marks the outreach sent; you can also mark it sent yourself. For outreach marked sent in the last 45 days, Relinked checks the headers of new mail for a reply from that contact, and may move the outreach to interview, offer, or declined based on the reply's subject line, which is not stored. It may also look up the sent message's thread so a follow-up can open in the same thread. It does not read any message body.

Google Calendar (optional)

You can separately connect Google Calendar from Settings. This is a second consent with its own read-only scope; signing in or connecting Gmail never asks for it. Relinked uses it for one thing: adding the people you meet in small meetings (ten or fewer people, including you) to your contact graph, and counting how often you met them, so someone you meet with weekly but rarely or never email does not look like a stranger. A person you have only met, and never emailed, becomes a contact on that basis, and their work-email domain is used to work out their employer the same way it is for an email correspondent. A card may then say “Met 4 times, last in March.”

The request to Google names exactly which fields may come back: each event’s ID, status, type, start time, whether you organized it, and for each attendee the email address, display name, response, and whether it is a room. Event titles, descriptions, locations, meeting links, and attachments are never transmitted to Relinked. All-day events, events you declined, events that have not happened yet, out-of-office and focus-time blocks, and any event with more than ten people are ignored. What is stored is one row per meeting per attendee (your account, the event ID, the person, the start time, whether you organized it), and per-contact counts and dates. Each attendee's email address and display name are matched to your contact graph the same way email correspondents are, and added to it if they are not already there. Calendar data is used only for your own account, is never used across users, and is never sent to a data broker or enrichment vendor.

Disconnecting Google Calendar revokes the calendar token on a best-effort basis, deletes it, deletes every meeting row, removes the meeting counts from your contacts and rescores them without meetings, and deletes any contact that existed only because you met them. It does not change your Gmail graph.

Where other data comes from

Relinked does not use a person or company enrichment vendor and does not send your contacts to one. Current employers and titles are worked out on Relinked servers: from a contact’s work-email domain, matched against companies Relinked already knows, a locally hosted copy of the Data Legion free company dataset (company data from Data Legion, datalegion.ai), or the employer’s own homepage; from a LinkedIn notification or your LinkedIn export, as described above; and, for a title, from a sender’s display name such as “Jane Smith | Vice President”. People who messaged you on LinkedIn are matched by unique full name against a locally hosted licensed Data Legion person file, which can add their current employer, title, and LinkedIn profile address. No Gmail-derived name, address, or domain is sent to Data Legion.

Relinked also collects job postings from company career pages, Workday, Greenhouse, Lever, Ashby, iCIMS, investor portfolio job boards, and the licensed Coresignal job dataset, and reads public SEC filings to find named professional relationships. Those requests carry company, board, and posting information — not your identity, your contacts’ names, or their email addresses. The company whose postings we fetch can reflect that the company showed up in your graph.

To find public connections, Relinked collects the names and roles of people publicly listed at companies in your graph — officers named in SEC filings, members of a company’s public GitHub organization, and people named on a company’s own about or press pages — and looks up your own published works and co-authors in OpenAlex, a public index of research, by your account name. Those requests carry company names, GitHub organization names, company web addresses, and your name, never a contact’s name or email address. The public names are matched to your contacts on Relinked servers, and the collected lists are deleted after 90 days.

Relinked uses Anthropic’s Claude for three tasks. It sends a company’s name and website domain to classify its type, size, and sector; those companies can include employers Relinked identified from your contacts’ email addresses. It sends the title and text of job postings collected from public boards to extract the level, location, and stated requirements. And it sends the posting and resume roles described above when a paid user clicks the AI detailed read. No contact name, contact email address, or Gmail message content is sent to Anthropic.

Who we share with

Relinked uses these processors: Supabase (hosting, database, authentication, and scheduled jobs), Google (the Gmail and, if you connect it, Calendar access you authorize), Anthropic (the AI tasks described above), Coresignal (licensed job-posting data), Stripe (billing), Resend (email we send), and Squarespace (the Relinked website). Sentry error reporting is built in but inert unless a reporting key is configured for the deployment; when it is configured, reports are scrubbed of email addresses, tokens, and subject lines before they leave. Data Legion licenses datasets that Relinked hosts itself; nothing is sent to Data Legion.

Relinked does not sell personal information and has no advertising or data-broker integration.

Email we send you

Relinked emails you only if you turn it on in Settings and pick a cadence. It is off by default, and during alpha it is further limited to an explicit tester list. Resend delivers it to your own account email. A daily cadence lists new roles Relinked matched for you — company, job title, level, location, and the posting link — plus the name of your best contact at each company and that contact’s employer, and any job change you have already accepted in review. A weekly cadence is a Monday action list: up to three open roles, one outreach you sent that has not been answered, one dormant contact, and job changes you have already accepted when the new employer is a company you are targeting. Those names and employers are third-party personal data disclosed to Resend so it can deliver the message.

No contact email address is included, and the sending code refuses to transmit a message containing any email address other than your own. Relinked does not keep the message it sent, only a record that a send was attempted and its counts. Resend keeps its own delivery logs and message content under its contract with us. Relinked sends no other marketing email, and has no push notification or SMS channel.

Relinked also sends reminders to your own account email. If a subject line is an interview with a date — interview, phone screen, onsite, or superday — Relinked keeps the time and the Gmail message id, not the subject, and emails you once 24 hours after that time to send a thank-you, then once more 14 days later to ask for feedback. An interview round you log in the pipeline gets the same thank-you reminder, naming the company and the round. Before sending a thank-you reminder, Relinked checks the headers of your recent sent mail, and skips the reminder if you already wrote to the people or company from that interview. It keeps only that a thank-you was found and when. If a person emails you, Relinked emails you once that someone messaged you, without their name or address. If you mark a note sent and that person has not replied after seven days, and someone else at the company still qualifies, Relinked emails you once to apply if you have not and to try the next person. That message names the company and the role, not the contact. Newsletters and automated senders are skipped. During alpha these reminders use the same tester list as the digest. A late reminder is not sent: the thank-you and the unanswered-note reminder only go out in the two days after they are due.

If you gift companies to someone, Resend delivers the invitation to the address you enter, with your first name, how many companies you shared, and a link to accept. When they ask you for an intro, Resend delivers you an email with their first name and the companies and roles they asked about. Neither email names a contact. During alpha these emails use the same tester list as the digest.

Retention, disconnecting, and deletion

Relinked has no automatic age-based deletion of your account records. Account, graph, evidence, outreach, billing-reference, and audit records stay until you change them in the product or delete your account. Public names collected from company pages, GitHub, OpenAlex, and SEC filings are deleted after 90 days.

Disconnecting Gmail revokes Relinked’s Google token on a best-effort basis and deletes the stored token, so no further mailbox reads happen. It also deletes what Relinked learned from LinkedIn emails in your mailbox, removes any contact that existed only because of a LinkedIn message notification, and clears any phone contact employer that came only from those emails. It does not delete the contacts, relationship statistics, scores, or evidence Relinked already derived from your mailbox; that graph stays in your account until you delete the account. Disconnecting LinkedIn deletes the rows matched from your Connections export, your own positions and schools read from the export, every stored Connections row (export and LinkedIn-email), clears phone contact employers that came from either, deletes the connection evidence and cached results the verifier produced and any remembered profile URLs, and turns off future verification consent. One record is kept: a log of how many LinkedIn pages were read and when, which is what enforces the daily reading limit. Clearing it would let disconnecting and reconnecting reset that limit. It holds no names or job titles and is deleted with your account. Disconnecting a phone or address-book upload deletes every stored card and any conflict queue from that file; it does not change your Gmail graph. Disconnecting Google Calendar is described above.

Deleting your account from Settings deletes your Stripe customer record, revokes the Google token on a best-effort basis, then deletes your login and every table that hangs off it: contacts, the email addresses and threads in your graph, scores, targets, evidence, job changes, LinkedIn rows, uploaded address-book rows, outreach and interview records, gifts you sent or accepted and their intro requests, settings, subscription state, audit events, and processing jobs. The extension clears its local storage once the server confirms. A canonical person record that no other user’s graph still references is removed with it, along with that person’s stored email addresses and employment history. Shared reference data that is not about you — companies, schools, recruiter firms, public job postings, and public filing metadata — is kept.

There is one deliberate exception. If someone has asked us not to enrich them or not to surface them, we keep the minimal record that identifies who the request applies to — their name, the address it was made about, and the request itself. Deleting it along with the graph would mean forgetting the request, and we would start processing them again the next time their address appeared in someone else’s mailbox. Honouring a standing objection requires remembering it.

One record survives deletion: a privacy-request receipt showing that a deletion was requested and completed, including the email address that requested it. Records of privacy requests have to be retained, so deletion is not the erasure of every trace of the account.

Relinked cannot delete what a third party holds on its own legal basis. Google keeps its own account and security records; Stripe keeps transaction and compliance records even after we delete the customer; Resend keeps delivery logs; Anthropic keeps API requests and responses under its own terms. Relinked sends no deletion request to Anthropic, Coresignal, LinkedIn, GitHub, OpenAlex, the SEC, or public job boards, and their retention is governed by their own contracts and policies.

California residents

You can export your data, edit your profile, and delete your account from Relinked Settings. The in-product download covers your account, profile, contacts, relationship and evidence records, outreach, and activity; it does not yet include every record we hold about you, so for a complete copy write to privacy@relinked.network and we will assemble it. Requests to know, correct, or delete are served at that address. Relinked does not sell or share personal information, so there is no sale or sharing to opt out of. Relinked is not directed to minors and does not knowingly collect minors’ data.

People who are not Relinked users

Your graph contains people who did not sign up. Relinked keeps that in two layers, and the two layers behave differently.

The relationship layer — that a person is your contact, how you corresponded, their score, the evidence behind a warm path, and your outreach — belongs to your account alone. Database row-level security enforces that: another user cannot read it and it never appears in another user’s product.

The identity layer — a person’s canonical record, with name, email addresses, and employment history — is shared infrastructure. It is keyed on the email address, which is globally unique, so when the same person appears in two users’ mailboxes both accounts point at one stored record rather than two copies. That deduplication is what keeps a person’s identity and employer history consistent. A current employer or title on that record, whether it came from a work-email domain, a LinkedIn notification, or a LinkedIn export, is therefore the same for every user whose graph includes that person. Those tables are backend-only: a signed-in user can read a person’s display-name record only when one of their own contacts points to it, and cannot read the email, employment, or education tables at all. Relinked does not publish a cross-user directory, does not tell one user that another user knows someone (a gift shares company names only, and only when the giver chooses), and does not sell any of it.

A person who is not a Relinked user can write to privacy@relinked.network to ask what we hold about them, to be excluded from enrichment, to stop being surfaced to users, or to have references to them removed. We handle those requests by email; there is no self-service form.

Contact

privacy@relinked.network

Contact

privacy@relinked.network