UplixOS
Privacy Policy
UplixOS Privacy Policy for proportionate handling of limited B2B personal data.
- Effective date
- Last updated
- Version
- v1
Controller and contact
UplixOS is published by UPLIX, a French SAS with share capital of EUR 10,000, registered with the Paris Trade and Companies Register under number 891 839 573, VAT number FR32891839573.
The registered office is 11 bis rue Portalis, 75008 Paris, France. The publication director is Gwenaël Robert, CEO.
Legal, contractual, or privacy requests may be sent to contact@uplix.fr.
Uplix has not appointed a Data Protection Officer for UplixOS at this stage. Privacy requests may be sent to contact@uplix.fr.
Posture: limited B2B personal data
UplixOS primarily handles professional and company data, but some information linked to identifiable natural persons is limited B2B personal data.
This Policy therefore uses a proportionate posture: names, work emails, identifiers, logs, and usage data may fall within privacy rules depending on context.
Data categories
Possible categories include names, work emails, profile images, auth identifiers, organization and workspace memberships, workspace roles, audit logs, API usage, bug reports, comments, messages, user agents, analytics events, telemetry, support/admin data, technical logs, and security logs.
Generic company coordinates and company-level SEO/GEO datasets are not always personal data; professional contacts, individual accounts, authors, sole traders, and user-linked logs may be personal data.
Purposes
Data is used for account creation and authentication, workspace access control, product delivery, security, auditability, support, bug fixing, service improvement, analytics, cost and quota management, useful notifications, legal compliance, and B2B client relationship administration.
Legal bases
Likely legal bases include contract performance for SaaS access, legitimate interests for security, support, product improvement, and B2B operations, legal obligations where applicable, and consent where non-essential cookies or trackers require it.
Controller and processor roles
Uplix may act as controller for accounts, security, service administration, and customer relationship administration.
For some workspace content supplied or determined by a client, Uplix may act as a processor or service provider depending on the contract and actual purposes decided.
Recipients and processors
Recipient and vendor categories include hosting, database, authentication, analytics, observability, email, support or storage, Google services, GEO monitoring, and SEO/API providers used to provide UplixOS.
Internal access is limited to authorized Uplix teams for administration, support, security, operations, and customer relationship management.
International transfers
Transfers outside the European Economic Area depend on the actual vendors, regions, and contractual safeguards in use.
Where such transfers are necessary, Uplix relies on applicable contractual safeguards, including standard contractual clauses where required by the vendor relationship.
Retention
Account, role, and access data is retained for the duration of the customer relationship and authorized access, then for the periods needed for security, evidence, legal obligations, and contract administration.
Logs, analytics, support data, reports, messages, and backups are retained under proportionate criteria: security, auditability, incident resolution, customer support, service improvement, and technical backup constraints.
Individual rights
Depending on context, individuals may request access, rectification, erasure, restriction, objection, portability where applicable, consent withdrawal where applicable, and complaints to the competent supervisory authority.
Requests should be sent to contact@uplix.fr.
Security
UplixOS applies access controls, least privilege, audit logging, protections provided by hosted vendors, and responsible handling of credentials and incidents.
Cookies and trackers
Necessary, authentication, language, and security cookies are treated as functional cookies required for service operation.
Analytics or non-essential trackers, including PostHog or similar tools when active, require either valid consent or a documented exemption analysis.