Security
Security and privacy
How Team-Week is hosted, where your data lives, and who can read it. Each statement here is one the product does today.
Where it runs
Team-Week runs on one operator's own servers in a home lab, not on a public cloud. One person runs it. Traffic reaches it through Cloudflare.
Where your data lives
Each instance has its own PostgreSQL database. A second team never shares a database with yours.
Backups and restore
- Before every deploy the production database is dumped to disk.
- A separate encrypted copy of it is made every night and kept off site.
- An automated restore test runs every week: it restores that copy into a throwaway database.
Restoring a real database is done by hand, by the operator.
Encryption in transit
All traffic uses HTTPS (TLS 1.2 or newer), and browsers are told to always use it (HSTS). Team-Week hands email to its email provider only over an encrypted connection, and does not send it when that connection can't be encrypted.
Sign-in and sessions
- Passwords are stored as salted scrypt hashes, and common passwords are refused.
- Guessing is slowed down: an account locks for 15 minutes after 10 failed sign-ins, and so does a network address after 50.
- A session lasts 14 days by default (an owner can set 1 to 30), in a cookie that scripts on the page can't read and that is sent only over HTTPS.
- A password reset or removing a person signs them out everywhere.
Two limits, plainly: there is no multi-factor sign-in yet, and a session has no idle timeout.
Who can read what
- The reporting line.You see your own check-ins and feedback, and those of everyone below you in the reporting line.
- Admins.Admins see everyone except the people above them in the reporting line.
- Private notes.A person can lock a note so that only they and their manager at that moment can read it. Not other managers, not admins and not owners, unless that person is the manager it was locked to.
- The directory.Everyone signed in sees who is on the team: name, email, title, team, manager, admin flag and joined date. It holds no check-in text.
No AI, no trackers
No AI reads, summarises or scores a check-in. There are no analytics in the app or on this site, and no tracking pixels or link tracking in email. The only third-party script is Cloudflare's bot check on the sign-in and demo forms.
Export and deletion
Ask your operator, or write to [email protected], and your instance's data is exported or deleted. A person handles each request.