On behalf of each customer company, Kelo stores: the name, email and role of whoever has access; the record of who launched, closed and checked each production order; and the email of whoever requested each job.
This data exists because traceability is the product — knowing who did what is exactly what an ISO 9001 auditor will ask. There is no advertising, profiling or sharing with third parties for their own purposes.
The customer company is the data controller: it decides what data it enters and why. Kelo is the processor and handles it only on the company's instructions.
On servers in the European Union. Backups stay in the same jurisdiction and are kept for 14 days.
Each company's data is separated from everyone else's by the database itself, through row-level security policies, and not just by filters in the application. The application connects with a user that has no privilege to bypass those policies, and refuses to start if it finds that it does.
When the relationship with a customer ends, its data is deleted within 30 days, unless there is a legal obligation to keep it.
Anyone who wants to access, correct or delete their data should first speak to the company they work for or ordered the job from: it is the one that decides about it. Kelo answers requests forwarded by that company.
One session cookie, strictly necessary to keep you signed in, and two preference cookies that only store the user's choices: the language and the light or dark theme. There are no analytics or advertising cookies, and so there is no banner asking for consent to them either.