Steering a fixed-price project concentrates the most sensitive things an organization has: its margins, its contractual commitments, its leadership decisions, and how its teams feel. That data should not pass through a foreign jurisdiction.
Compliance obtained through an amendment remains subject to the law of the parent company. Where pylotik keeps your data follows from how the service is set up, not from a promise.
Data is kept in the European Union, with a hosting provider governed by French law and with no US parent company. The US Cloud Act allows a US authority to require data from a provider subject to US law, wherever that data is stored: our providers are not subject to that law because of their nationality or their ownership.
Backups always sit with a provider separate from the main host, also French (Scaleway, fr-par region). It is a direct lesson from the 2021 fire at the Strasbourg datacenter: a backup that burns together with production is not a backup.
Compliance is not a paragraph in the terms of service: it is functions that run.
Each user can export their data, delete it, and manage their consents from their own space.
A retention policy for each type of data: a duration in days and an action at expiry, whether deletion, anonymization, or archiving. Scheduled purge and anonymization jobs actually apply it.
Every access to sensitive fields (salaries, bank details, margins) is audited systematically, time-stamped, and attributed to a user.
Each organization is a sealed space. Sharing is not a right granted by hand: it is carried by the data itself, which references its supplier organization and its client organization. Each party's confidential information (internal team, margins, private milestones, HR alerts) stays strictly with its owner.
Password, TOTP two-factor authentication (mandatory for organization administrators), and a one-time code by email, which can be enabled organization by organization.
An organization's administrator mode is a separate context, activated explicitly and logged. The publisher's access to a user's account, for support, is read-only and audited.
HR log, project log (with the old value, the new value, and the context), and logs for reports, leave, monthly production, and the committee validation workflow. Everything is time-stamped, attributed, and replayable.
The publisher never steps into your client relationship. pylotik sits in the middle of the contractual link between a client and its supplier. That position is only worth something if it is structurally neutral: the supplier feeds the data, the client reads what concerns it and validates what is submitted to it, and no employee of the publisher ever takes part in the relationship.
That neutrality rests on technical properties (strict multi-tenant isolation, rights carried by each project, immutable historization, an audit log) and not on a moral commitment. This is what makes it enforceable, economical, and durable.
Public sector, local government, healthcare, defense, industry: we are happy to answer a security checklist or a procurement questionnaire point by point.