Data and security

How to read this page

Everything below describes how the service works today. It is not a legal promise and not a certificate: for the formal text see the privacy policy and the terms. If something here and in the policy differs, the policy wins and we fix this page.

Where data is collected

Business listings are collected on your computer by the Pinsonar extension for Chrome. When your account gives it a job, the extension opens its own work tabs on Yandex Maps, Google Maps or 2GIS and reads the public listings that the job names. It does not read your browsing history, your other tabs, cookies, passwords or forms. The first time it starts it shows what it reads and sends and does nothing until you agree. You can pause it in its window or remove it at any time; removing it deletes everything it stored.

What the extension sends and keeps

It sends the listings it read, a random installation identifier, its version, the connection token you pasted and a signature of each request. On first start it creates a key pair on your device and registers only the public key in your account; the private key never leaves the device. The server accepts data only from devices registered in your account. The token, the key and your choices stay in the extension storage on your computer.

What the server stores

Account: your e-mail, an optional name and a bcrypt hash of your password. A password is never stored as text.
Devices: the public key, the device kind, the version and the time it was last seen.
Business listings: public information about companies from the maps (name, address, phones, website, rating, public reviews). It forms a shared database of public business data and is not personal data of the account holder.
Your work: your campaigns, reports and your personal notes, statuses, tasks and tags.

Who sees what

An ordinary account sees the businesses that came with its own reports. Your notes, statuses, tasks and tags on a listing are visible only to you: if another user found the same company, they have their own separate set. The people who run the service can see the data when they need it to support users and check data quality.

How it is protected

The service is served over HTTPS, and the browser is told to keep using it (HSTS).
The sign-in session is a cookie that page scripts cannot read, marked secure in production, and it ends when you sign out. Sign-in, registration and password reset are protected by limits on repeated requests and by a captcha.
The database and the task queue are not reachable from the internet: only the web server accepts public connections.
Database backups are encrypted with AES-256 before they are stored. Disk encryption belongs to the hosting provider; we do not promise it.
Error reports, when error tracking is switched on, are cleaned of passwords, tokens and cookies before they leave the server.

Cookies and analytics

The application uses only the cookies it needs: the sign-in session and a short-lived value during Google sign-in. It sets no analytics or advertising cookies. The public site counts visits anonymously on our own server: no cookie, no IP address stored, no browser identification, no visitor identifier, and nothing is counted if your browser sends Do Not Track or Global Privacy Control. Details are in the privacy policy.

Deleting data

Write to privacy@pinsonar.com and we delete your account and the devices registered in it. In the application, "remove from me" hides a report and deletes your personal notes for companies that no other report of yours contains. Public business listings stay in the shared database.

What we do not claim

We do not claim certificates, audits or compliance marks, and we do not guarantee that the data is complete or exact.

Report a vulnerability

Write to security@pinsonar.com; the address is also in security.txt. Describe how to reproduce the problem and give us time to answer before you publish it.