Privacy and publication terms
Service and responsibility
Klee Performance operates the OSiA platform and Library. Library is a beta service. These terms describe sharing, publication permissions and server records; your licence terms continue to apply.
Only server operations are recorded
We record operations requested from the platform: licence authentication, catalogue access, downloads, uploads, submissions, review, publication and permission changes. These records support service delivery, access control, security and publication accountability.
Records may include the verified licence email and fingerprint, reviewer or administrator identity, organisations and groups resolved at the time, item/version, date, result, truncated network address and client family. Audit records do not contain licence keys, passwords, access tokens, file contents or review comments.
No extension, workstation or OneStream usage telemetry, browser analytics, tracking beacon or background client-usage report is collected by this feature. Browser local storage holds preferences and file-resume references, not licence keys or file contents. Server upload state exists only to carry out the requested transfer, not for analytics.
Publication identity and audiences
The authenticated author email and reviewer identities remain in the signed provenance of each published version and are visible to its authorised audience. Erasing or pseudonymising an audit entry does not rewrite this signed provenance.
Public publications are available to every valid OSiA licence. Organisation/group publications require current membership or explicit administration rights. A valid licence is a bearer credential: sharing it also shares its identity and any associated permissions.
The publication owner controls who can submit later versions. Maintainer emails are shown only to people authorised to manage that owner. Ownership administration is separate from group membership and from the signed authorship of an existing version.
Audiences belong to a signed version. Changing them requires another reviewed and signed version. Withdrawal blocks new acquisition; copies already acquired, including offline copies, are not remotely erased or disabled.
What contributors and reviewers confirm
Submit only content you are authorised to redistribute, choose the appropriate audience and describe its origin and permissions. Do not include secrets or customer data that you are not authorised to share. Marketplace solutions remain restricted to the Klee audience.
Files must pass the configured structural and antivirus checks before publication. An unscannable file is not treated as clean. Automated checks do not replace human inspection of the exact files, their impact and redistribution permission. Every publication is validated by a reviewer before it is signed.
ZIP archives may total 5 GiB. Standalone files and individual archive entries must not exceed 1 GiB. Expanded archives are limited to 8 GiB and 10,000 entries. Encrypted, unsafe or unscannable content cannot be published.
Retention and deletion
Library usage audit records are normally retained for 180 days. Library contribution and administration audit records, approval envelopes and closed review packages are normally retained for 1,095 days, with daily cleanup. Approval links stop working after their seven-day validity. Unfinished submissions remain while processing. Unsubmitted upload bytes expire after 24 hours and are removed by the hourly cleanup.
Hub accounts, active permission assignments and general Hub account/security history are separate from Library review records and follow the Hub's account policy.
Publication content and its signed author/reviewer provenance remain for the lifetime of that version. Ownership and maintainer records remain while the identifier is allocated, to prevent another publisher taking it over. An authorised owner or administrator can change maintainer assignments; the publication-owner scope stays stable between versions.
Detailed analysis reports follow the associated review record; orphan reports are removed within seven days. Review-only quarantine copies are discarded when their submission is withdrawn, superseded or rejected and no active submission references them. Terminal upload metadata is removed after the closed-record retention period. Aggregated counters may remain, but small groups and precise dimensions can still identify people.
Audit removal uses pseudonymisation and may retain contextual identifiers; it is not a promise of irreversible anonymisation. Daily VM backups follow the operator's existing retention policy. Removal from the active service does not immediately remove older backup copies.
Access, correction and requests
You can ask Klee Performance for access to, correction of or removal of your personal records and permission assignments. Requests are verified before action. Signed publication provenance and records required for security or publication integrity are handled separately and the response explains any retained data.
Use your usual Klee Performance contact or the contact address below. Include your account email and relevant publication identifiers, not your licence key or password.