Your team's hours, pay rates and messages deserve straight answers. This page lists measures that are in place and running today. Nothing here is a plan.
Your data is kept apart
Each company has its own separate database, not a shared table with a company column. Each company also has its own signing keys, so a sign-in or a link made for one company means nothing at another. Automated tests run on every change to check that one company can't reach another's data.
Encryption
- All connections use TLS 1.2 or newer. Older versions are refused, plain HTTP redirects to HTTPS, and browsers are told to stay on HTTPS.
- Databases and files are encrypted at rest by our infrastructure provider, Cloudflare.
- Authenticator keys and tokens for connected services are sealed by us as well.
Signing in
- PINs and recovery codes are stored only as keyed hashes. We can't read them, and neither can anyone who gets hold of the database alone.
- Owners and admins need 8-digit PINs or an e-mail code. New PINs are generated by the server and shown once.
- Five wrong PINs lock web sign-in for that account for 15 minutes. Limits also apply per network and across a company, and they're built so that an attacker can't lock someone out of their own phone.
- Two-step sign-in with an authenticator app is available to everyone, and an Owner can require it for admins.
- A sign-in from a new device can alert the company. People can see and remove their own devices.
- Deleting a person, resetting a PIN or changing a role ends their sessions on the server at once, including live connections.
Inside your company
Roles and permissions are checked on the server for every request, not only hidden in the screens. An activity log records what admins do. Modules your Owner hasn't turned on don't just hide: their server routes refuse every request.
Every read of an uploaded file is checked against the person's permissions, and uploads are served so they can't run as web pages. Owners can hide message previews on lock screens and require an app lock with Face ID.
Our own staff
Only named staff can use our internal console. It lives at its own address, with its own sign-in: an e-mail code plus an authenticator app, always. Every sign-in and every change there is logged and kept for 3 years. Staff can't sign in as your people, and they get an e-mail when their account signs in.
If something breaks
- Backups. Every company's database is copied each night and kept 30 days. A company's database can also be restored to any moment in the last 30 days.
- Releases. New versions first go to a small share of traffic, and roll back on their own if errors rise.
- Monitoring. Errors, scheduled jobs and each module's availability are watched, and problems alert our staff. Anyone can see our status page.
- Breaches. If we learn of a breach affecting company data, we tell the affected Owners without undue delay, and within 72 hours.
What we don't claim
Plenty of software companies put badges on their sites. Here's where we stand.
- We don't hold SOC 2 or ISO 27001 certification. Cloudflare, which runs our infrastructure, holds its own, but those are Cloudflare's and don't cover PinkLinq. We'll say so here when ours exist.
- We don't sign HIPAA business associate agreements, and PinkLinq isn't for health records.
- We don't store payment cards. Stripe or Apple handle them.
- We haven't had an outside penetration test published yet. We test our own defences, and we'd welcome your findings.
- We can't promise you'll never be breached. No honest company can. We can promise to tell you quickly.
Your part
The strongest measures here fail if a shared PIN opens the door. Turn on two-step sign-in for Owners and admins, remove people the day they leave, give managers only the permissions they need, and keep kiosks somewhere you can see them.
Tell us about a security problem
If you think you've found a vulnerability, tell us through support@pinklinq.com. Please give us reasonable time to fix it before making it public, don't access or change data that isn't yours, and don't disrupt the Service. If you follow those rules, we won't take legal action against you for your research, and we'll thank you.