Privacy Policy

What the site collects

This website is static and loads no third-party fonts or embeds. Its hosting provider keeps the standard server logs any web server keeps. Beyond that, reading these pages produces nothing unless you accept analytics in the notice: accept and Google Analytics measures visits and receives request and browser information; decline and no measurement script is loaded at all. Your answer is a single localStorage entry, described in the Cookie Policy. The download link points at a storage host, which sees the download request the way any file server sees any request.

What the application collects

PowerOps is a desktop application and is separate from this site. Your profiles, their browser directories and their stored sessions live on your own machine. Credentials go to the operating system's credential store.

Cloud Sync is switched on by default. Nothing has to be pressed for it to start: once the application is signed in, a profile's cookies, Local Storage and IndexedDB are captured when the profile closes and encrypted on your machine, with a key that belongs to the workspace, before they are uploaded. An owner or admin of your organisation can switch Cloud Sync off for every workspace in it, in Settings, and any profile can be set so that its session is never uploaded. A single-holder lease decides which machine may write, so two machines never overwrite each other.

The workspace key is created on one of your devices, and the ArticleOps service keeps a copy so that it can give the key to another device when an account that belongs to the workspace signs in there. Because the service holds the key as well as the encrypted data, Cloud Sync is not end-to-end encryption: the service is technically able to decrypt synced data, although syncing never requires it to. Your ArticleOps account and the security of that service are what protect synced data.

The shared profile catalogue is a different kind of data from those encrypted browser-session backups. It does not depend on the Cloud Sync switch: it is kept in step with your workspace whenever the application is signed in, and it is not encrypted with the workspace key. For each profile it holds the name, folder, groups and tags, the platform, the fingerprint settings, the proxy configuration and the addresses of its open tabs. It also records when the profile was last used and its last connection: the IP address and country its browser came out on, the time, and the name of the computer that used it. For an account saved with a profile it holds the platform, the label, the login address, the cookie domains and the autofill settings.

Secrets travel with the catalogue, but they are encrypted with the workspace key on your machine first: proxy passwords, and a saved account's username, password, two-factor secret and notes. So the service stores three kinds of data: session backups and secrets, which are encrypted with the workspace key, and catalogue data, which is not.

Connected installations send operational health reports: installation, device and workspace identifiers; machine name, operating system and application version; profile and running-profile counts; sync and key availability status; timestamps; and up to 20 recent backup outcomes with profile identifiers and error codes. These reports help diagnose installation and sync problems. The reporting fields exclude passwords, cookie contents and full browsing history. Website cookie preferences do not control this desktop reporting.

Your data, your machine

The design position is plain. A profile's browser runs on your machine, and what it does there is written to that profile's own directory on your disk. Cloud Sync, which is on by default and can be switched off, uploads an encrypted copy of the session as described above, and the profile catalogue is shared with your workspace. Signing in uses your ArticleOps account and connected services process account, device and workspace information. Downloads, update checks and cloud features also make network requests. Local storage does not mean that the application never contacts a server.

Deleting local profiles and synced data

Archiving a profile keeps its data so it can be restored. Permanently deleting it removes that profile from this installation, including its stored account credentials and remembered tabs. Stop the profile before permanently deleting it.

When the application is signed in, deletion is also sent to the shared catalogue. Other devices archive their copies rather than automatically erasing local browser data. A local deletion is therefore not a request to erase every cloud backup, operational record or copy on another device, and it does not delete your ArticleOps account.

Contact

Questions about this policy go through the contact details on the about page.