Privacy policy for Research Connect
Research Connect by OliveTurn, inc
Privacy policy for Research Connect
The browser extension
- The browser extension fetches nothing until it is linked to your account. Our extension links only after a step from you in the extension: a click on its prompt, which says which account (for an account that only a download link names, its kind and, for a code account, the day it was made, never an email address), an account code you type into its popup, or a pairing code from your AI client that you confirm. In Firefox every install of an extension gets its own random address, so Research Connect cannot tell our extension from another one: a Firefox extension you installed yourself, with permission to use our site, can link itself to the account this browser is signed in to without a step from you. It then learns the account (the email address of an email account), receives the article requests of that account and can answer them with text of its own; for a code account it can also read the account code, open the dashboard and delete the account; for an email account it can pause and resume the search history. It can also end the link of our extension in that browser: an unlink applies to the whole browser session, so when we tried such an add-on and it unlinked itself, the connection of our extension was closed too and stayed closed until our extension was linked again. In Chrome only an extension whose id is on our list can link by the cookies of this browser, a download link or an account code; a pairing code from your AI client works from any program that holds it. There is one exception: when you install the extension from a Research Connect download link, on our pages or in a reply to your AI client, in this same browser, and the download link and this browser's own cookies name the same account, it links at once, shows you which account, and offers "Undo". A reply to your AI client that missed the full text of an article because no browser extension is linked to your account can carry such a download link, at most once in ten days per account. Your AI client's provider sees it as part of the reply. When the link carries a handoff, it works once, for at most 15 minutes, and in any other browser it links only after a click on the extension's prompt. That prompt does not show the email address of an email account that only the link names: it says the account comes from a download link. You can unlink it at any time from the extension popup, which deletes the link on the server as well. If Research Connect cannot be reached at that moment, the extension forgets the link anyway, and the link on our side ends when it expires, 30 days after the extension last used it.
- Anyone who holds a download link can use it: opened in their own browser, it lets them link that browser to the account with one click on the extension's prompt. From then on the extension in that browser can receive the account's article requests, and its popup shows the account: for an email account its address, and for a code account its account code, its dashboard, which opens with no password, and the deletion of the account; for an email account the popup can also pause the history. A program that opens the link before you do, such as a link preview, can use it up, because opening it is what spends it. The page then shows as the plain download page, and the next reply that missed full text, after the ten days, carries a new link.
- Before it is linked, each time you open its popup, and when you press "Link this browser" on one of our pages, the extension asks Research Connect which account this browser belongs to. The browser attaches Research Connect's own cookies to that request, as it does for any page of ours. They are our cookies only, never a publisher's, and the extension cannot read them. The account code you type, and the confirm of a link offer (the call that makes the link), are sent the same way. A pairing code is sent on its own, with no cookie. When a browser that is linked already links again, that confirm also carries the old link, so that we can remove it. A confirm links the extension to a browser session of your account. If this browser has no live session in that account, the confirm opens a new one, notes this browser's IP address on it, and may set our two cookies for it, but never over cookies that name another account. Its other calls to us, such as the check-in, carry no cookie of ours. Once it is linked, they carry the link. The connection it keeps open is not the same in every browser. It carries the link in a header of its opening request, never in its address. Chrome attaches none of our cookies to that opening request. Firefox may attach all three of them (the one that names your browser session, the one that remembers your account, and the one that checks that a form came from our own page); in our test of Firefox it did. The server reads no cookie on that request, so in Firefox they are sent and ignored.
- On Research Connect's own pages, the extension marks the page with three facts: that it is installed, whether it is linked to the account the page is for, and its version. That is how those pages know not to offer it to you again.
- When your AI client asks for an article that no open route can deliver, the extension opens that one article address in a browser linked to your account (and, when the publisher's article page loads its text from a second address on the same website, as ScienceDirect's does, that address too), using the accounts your browser is already signed in to, and sends the article text to Research Connect, which hands it to your AI client. For a publisher where your institution has a direct sign-in address, it can then open one page of the publisher's website that shows whether you are signed in and, unless that shows you are not, the direct sign-in address, which can reuse a sign-in you already have at your institution. Both addresses it opens are fixed by Research Connect for that publisher, are https addresses on a public host, and, where we know the publisher's domains, stay on them. It only ever reads pages: it submits no forms, types no password, buys nothing, and never bypasses a paywall or a sign-in page. A page that turns out to be a sign-in page, a paywall notice, a page for a different article, or a page that could not be confirmed as the complete article, is discarded, not delivered. If more than one browser is linked to your account, the request can go to the extension in any of them.
- What leaves your browser is the extracted article text, the scheme and host of the address the request ended at (never the path or query, which can carry sign-in tokens), the HTTP status, a label saying whether the page looked like an article, a sign-in page, a paywall, a page for a different article, a page that could not be confirmed as the complete article, or could not be told at all, and the extension version. The label can also say that the page was a robot check. For a page for a different article, it also says whether a sign-in page stood in the way. It also sends whether the page was redirected on the way, the type the website gave the page (its content type), the size in bytes of the text it extracted, and, when the fetch failed, a short error word saying why, such as an address that was not safe to open, a page that was not text, a page that was too large, or a network error. Your passwords and cookies never leave: the browser attaches them to the request itself, and the extension cannot read them.
- To prove a page really is the article you asked for, not just something that looks like one, the extension also sends: the version of the page rules it checked the page with, which publisher's website layout it recognized (or none), the ids of the checks that found the full text, that found the article withheld, or that could not run, whether the page's own DOI matched the one requested, what DOIs the page itself declared, which of the page's own tags carried the DOI, and the number of characters of text it extracted.
- The extension itself keeps a few things in your browser's extension storage, on your device: the link (its token, its id and when it expires), the Research Connect server address the link was made with (a setting), the account's label (for an email account the email, for a code account the words "your code account"), a tag that tells accounts apart, the kind of account, the day it was made, whether the server has refused the link, how often to check in, and, until the browser restarts or the extension is updated, a note that Research Connect refused this version of the extension. Unlinking removes the link, the account details and the check-in interval, and leaves the server address and that note. Choosing a different server address in its options also removes the link and that note. It keeps no article text, no page address and no list of what was fetched.
- Research Connect keeps the link (a hashed token that belongs to one browser session of your account, the extension version, whether it is connected, and timestamps) until it expires or you unlink. The extension's fetches are not tallied. Research Connect's own fetches from a publisher's website, made by our server and not by the extension, are counted by the domain of the address fetched: domain names, counts, and the first and the latest day, never content. Article text is held in the server's memory only long enough to hand it to your AI client, at most a few hours when a document is too large to pass in one piece, and is never written to disk or a database. Linking itself uses one-time tickets, kept only as a hash, each good for one use and for fifteen minutes at most.
- While it is linked, the extension keeps a connection to Research Connect and checks in every few minutes. Each of those tells us the IP address your browser is on now. That is the IP address the first part of this page describes.
- Usage records note that a fetch went through the extension and how it ended. They hold no page text and no address.
- The shared record notes that an article arrived through the extension, and so does the history of an email account. The article's DOI comes from your AI client's request, never from the page. The DOIs the page itself declares are checked against it and reported back to your AI client; they are not stored.
- Everything the extension sends travels over encrypted connections (HTTPS and WSS).
- The Research Connect browser extension's use of information received from your browser complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. That information is used only to deliver the article to the AI client you connected. It is not sold, not used for advertising, and not used for any purpose unrelated to that.