Security
Protecting your account and information.
Research is available to everyone. Your company follows, reading history and account information stay private.
Security in the service
- Private account access. Signed-in requests are checked before account information is returned or changed.
- Separate publication. Public reports do not include private follows, reading history or internal research notes.
- Protected connections. Public pages and account requests use HTTPS.
- Source transparency. Research links back to identified sources and dates so you can inspect the underlying record.
No service can guarantee that an incident will never occur. This overview describes our approach; it does not claim an independent security certification or audit.
Help protect your account
Use a unique password, protect the email account used for sign-in, and sign out on shared devices. We will not ask you to send your password, private keys or sign-in links in a support message.
If you think someone else has accessed your account, use password recovery and contact support.
Report a vulnerability privately
Email [email protected] with the affected page or feature, a safe description, the likely impact and non-destructive steps to understand it. Redact account details and other people’s information.
Do not access, alter or download another person’s data to demonstrate an issue, disrupt the service or publish private details. Ask before testing beyond normal use. This page does not authorize intrusive testing or promise a bounty.
For account support, research corrections or privacy requests, use the relevant contact on our contact page.