Who runs this
bettrConnect is run by Trissino Inc., a Delaware corporation. "We" and "our servers" on this page mean Trissino Inc. and the Steve application it runs. You sign in to the extension with a Steve account.
bettrConnect is independent. It is not affiliated with LinkedIn or Slack.
The extension on LinkedIn
On LinkedIn, the extension reads the posts, comments and profiles shown on the pages you open, so it can put its controls next to them. Post and comment text goes to our servers only for posts you pick or queue. Without a click, it sends the ids of posts on screen, the handle of a profile you open, your own profile, about once a day your own posts and comments of the last 90 days, and about once a day the names and LinkedIn ids of people who replied to comments you posted from our drafts.
What the extension reads on LinkedIn pages you open
- The posts and comments the page shows: the post's id and link, its text and image links, its reaction, comment and repost counts, and the name, headline, profile link and photo link of its author. For comments: the author's name, headline and public handle, and the text.
- On a person's profile: their public handle, from the page address. Their name, headline and photo link are read when you press Track.
- Your own LinkedIn name, headline, photo link and public handle, so a draft can be shown as you.
- LinkedIn's notifications page, only while we have that reader switched on (it is off on the date at the top of this page): who reacted to or commented on your posts or comments, and who accepted your invitation.
What it sends without a click from you
- The ids of the posts on screen, so we can show the drafts you already have for them. This happens while you are signed in and have a project selected. Nothing else about those posts is sent.
- When you open a person's profile: their public handle, so the extension can show what you have already done with them. Viewing a profile adds nothing to what we store.
- Your own name, headline, photo link and handle, at most once a day or when they change.
- About once a day, while Chrome is open and you are signed in to LinkedIn and to Steve, the extension re-reads, through your own LinkedIn session, the comments on posts where you posted one of our drafts in the last 14 days, at most 30 posts. For each reply by someone else to one of your comments, it sends the reply's id and time and the replier's name, LinkedIn profile id, member id and public handle. It also sends the ids of your comments it matched to our drafts. It never sends the text of a reply.
- About once a day, while Chrome is open and you are signed in to LinkedIn and to Steve, the extension reads, through your own LinkedIn session, your own posts and comments of the last 90 days: at most 200 posts and 500 comments, in at most 20 requests. It sends their text and time and, for each comment, the LinkedIn profile id and headline of the author of the post you commented on. It never sends that post's text or its author's name. From this we keep up to 8 of your texts as writing samples for drafts, how many people you commented on and how many of them more than once, and up to 20 of those headlines. The rest is not stored.
- Only while we have the notifications reader switched on (it is off on the date at the top of this page): while LinkedIn's notifications page is open, the name and public handle of each person who reacted to or commented on your posts or comments, with the post id and the approximate time, and of each person who accepted your invitation. The notification text is not sent. These wait in your browser and go to our servers at most once an hour.
- Two more readers exist and are off on the date at the top of this page: your most recent connections and your pending sent invitations, one page of each a day, with each person's name, LinkedIn profile id, member id, public handle and the date.
What it sends when you act
- When you press the bettrConnect button on a post or comment and choose to save or draft: that post, the comments you chose, and any instructions you typed. For a comment, that includes its author's public handle.
- For a post in your queue: the extension asks LinkedIn, from your browser and through your own LinkedIn session, for the comments and replies on that post. It sends them to our servers so replies can be drafted: each author's name, headline, LinkedIn profile id, member id and public handle, the text, the time, and which comments are yours.
- The result of each post attempt: posted, failed or skipped, with the id of the new comment.
- When you press Track: the person's public handle, name, headline and photo link.
- When you ask for an invitation note or a first message: the person's public handle. The draft is written from what we already hold about them.
- When you ask for a post draft: the topic you typed.
- When you open today's list of people to engage with, the extension asks our servers for it. Nothing about other people is sent with that request.
We store the posts you picked, the comments a draft answers, the drafts and your edits to them, and whether each one was posted.
We also keep, for each user, a record of the people you engage with. For each person: name, headline and photo link, and their LinkedIn profile id, member id and public handle, or for Slack their Slack user id. With it we keep whether you track them, each touch with its time and post (a comment, reply or Slack message posted from one of our drafts; their reply, reaction or comment), and each stage they reached with its time, such as invitation sent or connected.
A person is added to that record when you post a draft that answers them, when you press Track, or when the person your draft answered, or the author of the post, replies to your comment. Connections, invitations and notifications only update people already in the record; they never add new ones.
We also count each draft we write for you, with its kind and time, to apply plan limits.
There are two ways a comment gets posted. You choose in settings.
- "I click Post": the extension puts the draft in LinkedIn's own comment box and you press Post. In this mode the extension does not post in the background. New bettrConnect accounts start in this mode.
- "Post for me": after you approve a draft, the extension posts it from your browser, through your own LinkedIn session, one at a time with a pause between posts. It stops posting when LinkedIn shows a security check.
- If your setting is "I click Post", or the setting cannot be read, the extension refuses to post a draft in the background.
LinkedIn cookies: the extension checks that a LinkedIn session cookie exists, to know if you are signed in. It reads one more LinkedIn cookie, the request token LinkedIn asks for, and sends it back to LinkedIn only. Neither value is sent to our servers. The extension keeps a short debug log of step names in your browser, with cookie and token values removed.
The extension in Slack communities
Slack is off until you turn it on. The extension has no access to Slack when you install it. Chrome asks you for access to app.slack.com when you press Turn on in the extension, and Slack works only after that press. If Chrome holds that access without you having pressed Turn on, the extension gives it back to Chrome when it starts. Removing the access in Chrome clears your Turn on, so turning Slack on again takes a new press. It works on Slack in the browser only.
In Slack communities, the extension reads messages written by other members of the community, in the channels you ticked, and sends them to our servers to be scored. For each message that is the text, the sender's name and the sender's Slack user id.
How the reading works
- The extension reads only what the Slack page shows. It does not use Slack's internal interfaces, Slack's session token or Slack's local storage.
- About three times a day while Chrome is open, and when you press Check now, it opens one pinned Slack tab in the background, loads each channel you ticked, reads the latest screenful (at most 30 messages), and closes the tab.
- It does not read channels you did not tick, and it reads no history beyond that latest screenful.
- With each message it also sends the message time, the thread it belongs to, its link and its reply count. With each read it sends the channel id and name, and your own Slack user id and name when the page shows them. The screenful can include your own messages and bot messages. Our servers discard those, and very short messages, before scoring.
- Scoring compares the remaining messages with the topics you set and your company description. A scoring request carries the message text and the sender's name, with the community and channel names.
Only messages kept as opportunities, and notes you choose to save, are stored. A message you ask for a draft reply to is kept as an opportunity too. The rest are dropped after scoring.
What is stored, and what is not
- A kept opportunity holds the message text, the sender's name and Slack user id, the community and channel, the message link and time, and a one-line reason it was kept. Dismissing an opportunity deletes it.
- When you press the bettrConnect button on a message, the extension sends that message and the recent messages around it, so the draft has context. The surrounding messages and your instructions are used for the draft and are not stored. In a direct message, the recent messages of that conversation are sent the same way; the extension asks you to tick "I know this person or they asked me to message them" first when the community bans cold DMs.
- We store each draft with the message it answers, the text you inserted, and the time you inserted it.
- A note is the set of messages you picked with Save to Steve: for each, the sender's name and Slack user id, the time and the text. You can delete a note at any time.
- For a community you add, we store the workspace id and name, the rules you entered, and the ids and names of the channels sent when you pressed Add this community. Nothing about a workspace is sent before you press Add this community.
- When you add a community, the extension sends the ids and names of its public channels, and of a private channel only if you tick it to be read. Private channels are listed but never ticked for you. Group direct messages, direct messages and channels whose type the extension cannot tell are not listed and never sent.
- Only public channels named general, help or questions, or starting with ask-, start ticked, up to your channel limit. No private channel is ticked for you. You can untick any channel before you press Add this community.
- After a community is added, when you open that Slack workspace the extension sends the ids and names of public channels in your sidebar that the community does not list yet, so you can tick them in Steve. Private channels, group direct messages, direct messages and channels whose type it cannot tell are never sent this way.
- When you insert a draft reply or message, the person it answers is added to the record of people described under LinkedIn above, by Slack user id and name.
- Slack message text is not written to the extension's own storage or logs.
The extension never sends a Slack message for you. It puts a draft in Slack's own message box and you press send.
It does not click Slack's send button and it does not press Enter for you. There are no bulk actions and no member export.
AI model providers
Scoring and drafting are done by AI models run by other companies. Our servers send them the text needed for the task: the Slack messages being scored, or the post, comment or message a draft answers, with its context.
- Google: scoring of Slack messages.
- Anthropic, reached directly or through Amazon Web Services: drafts.
What stays in your browser
The extension keeps working data in Chrome's extension storage: what it is doing now, pacing timers, the time of its last profile sync, of its last daily read and of its last read of your own posts and comments, with a fingerprint of what that read sent, the Slack workspaces you answered Not now for, whether you pressed Turn on for Slack, and the progress of a Slack check (channel ids and names, counts).
For LinkedIn it also keeps: your comment counts per day, the public handles of people you commented on in the last 7 days with the times, how many invitation notes and first messages you drafted today, a copy of the handles you track (refreshed every 6 hours), the ids of the drafts you inserted in "I click Post" mode and the time of each (kept up to 15 days, at most 200), and, while the notifications reader is on, the names and handles waiting to be sent. Removing the extension removes all of it.
Sign-in is handled by Clerk. The extension uses your Steve sign-in session to talk to our servers.
This website
We measure how the site is used with PostHog, hosted in the United States. Requests go through our own domain first. We record page views, clicks on our buttons and links, which sections were seen and how far a page was scrolled. We never send text you type.
Two modes, by region
- In the EEA, the UK and Switzerland, and wherever we cannot tell your region, nothing is measured until you press Allow.
- Elsewhere, visits are measured from the start with nothing saved in your browser to recognise you later, and the notice lets you say no. Pressing Allow lets PostHog keep its own cookie and local storage entry so that a later visit counts as the same visitor.
- A Global Privacy Control or Do Not Track signal from your browser counts as No thanks. You are not asked.
- Session replay is off.
Cookies this site sets
- engage_analytics_consent: your answer to the measurement notice. Kept for one year.
- engage_consent_region: "eu" or "row", which decides the mode above. It is worked out from the country your request comes from. The country itself is not stored. Kept for one year.
- engage_jid: the join id described below. Set only after you press Allow. Kept for 30 days.
The join id: after you press Allow, links from this site to the Chrome Web Store and to sign-up carry your anonymous PostHog visitor id as a link parameter named ejid, and the same id is saved in the engage_jid cookie. Its one purpose is to connect a visit to this site with a later install or sign-up. It is not set if you never press Allow, if you press No thanks, or if your browser sends a privacy signal. Pressing No thanks removes the cookie.
Slop Check runs in your browser. The comment you paste is not sent to us. A share link holds a score and the names of the tells that were found, never the comment.
The launch list: if you leave your email, we receive it in our company Slack workspace with the role you picked, if any, the page you were on, the page you came from and your country. We use it to tell you when the product is ready.
Your choices
- Dismiss a Slack opportunity or delete a note in Steve and it is deleted.
- Pause a community in Steve, or untick a channel, and it is no longer read.
- Remove the extension's Slack access in Chrome's extension settings and it can no longer read Slack at all.
- Remove the extension and all reading stops.
- To get a copy of what we hold about you, or to have it deleted, write to taka@trissinoai.com.
If you are a member of a Slack community and think a message of yours was stored, write to the same address and we will find it and delete it.
Changes to this page
When the product changes what it reads, sends or stores, we change this page first and update the date at the top.