Permissions match responsibility.
Project managers, team leaders and members receive role-aware access. The aim is simple: people can act where they are responsible, not everywhere by accident.
Security by design
Your project data is not someone else’s product.
TinKan is being built for projects where evidence, responsibilities and institutional memory matter. Practical controls come first; vague reassurances do not.
Changes leave a trail.
Work reassignment and project activity are designed to remain understandable after the moment has passed.
No advertising-data bargain.
TinKan is designed around a straightforward premise: project information should support the project, not a hidden marketplace of behavioural data.
Data ownership
Data portability should be ordinary, not an escape room.
- Your operational data remains yoursA pilot is not a trap. Your team should understand what is held, why, and how to move it if TinKan is not right for you.
- Privacy is a product requirementExternal tracking and unnecessary data collection are treated as design choices, not inevitable background noise.
- Security evolves with the productSecurity documentation will be expanded as production deployment and customer requirements mature; no magical claims before the evidence exists.
Evaluate on the facts