Permissions and privacy
If you're wondering why Briskine needs the permission to "Read and change all your data on the websites you visit" you're in the right place.
Why do we need such a permission in the first place?
We need it because it allows us to manipulate the content on the website you use Briskine for.
When you insert a template in a text field, it's considered a change to the website. For variables to work (for example, {{to.first_name}}), we have to read the contents of the website.
Why do we need this permission on all websites?
A lot of our customers use Briskine on their internal web services (CRMs, helpdesks, etc.). In fact, Briskine works on most websites and it would be impossible to enumerate them all.
To ensure Briskine works on any site you might need, this permission is requested once during installation.
Do we read your emails or your banking details?
No. Briskine only reads what it needs to find and insert your templates:
- Template shortcuts. When you press ⇥ Tab , or your own shortcut key, Briskine looks at the word right before the text cursor, to check if it's one of your template shortcuts. Nothing else you type is read.
- Variables. When you insert a template, Briskine reads the details your template variables need, like the sender, the recipients, and the subject. It doesn't read your messages.
- Page and site helpers. The
csshelper and the site helpers only read the parts of the page your template asks for. Password, card, and one-time code fields always read as empty.
Everything Briskine reads stays in your browser, and is only used to insert your template. It's never sent to Briskine or anyone else.
The only time text from a page leaves your browser is when you save selected text as a template from the context menu. Briskine then opens the Briskine Dashboard with the text you selected, so you can save it as a new template.
See our privacy policy for more details.
Do we record what you type?
No. A lot of text expanders record every key you type, so they can spot a shortcut as soon as you finish typing it.
Briskine works differently. It ignores every key except the shortcut key, and never records what you type. When you press the shortcut key, Briskine only looks at the word right before the text cursor, to check if it's one of your template shortcuts. It never does this in password fields.
Do we read your other open tabs?
Only when you insert a template that uses the site helpers, and only the tabs it asks for. What Briskine reads stays in your browser, and is never sent to Briskine or anyone else.
Websites you add to the Blocklist are never read, and templates you insert in a regular window never read tabs in private windows.
Can you block the extension from certain websites?
Yes. You can add a website to the Blocklist on the Settings page.
Can you allow the extension to run only on certain websites?
Yes. You can use your browser's extension settings page to make the extension run only on certain websites.
On Google Chrome, right-click the Briskine icon in the browser toolbar on the top-right, and press Manage Extensions.
In the Site access section, select On specific sites. You'll then be able to add sites where you want to use Briskine.
On specific sites mode requires you to also add https://app.briskine.com/ to the list - otherwise you won't be able to sign in to your Briskine account.
Briskine is open source
The Briskine browser extension is open source, licensed under the GPL-3. You can verify how it works, and what data it reads, by reviewing the source code available on GitHub.