LiOS is a local-first workspace with connected AI and data services. Local-first does not mean offline-only, and it does not mean every action stays on your device.
THREE DISTINCT BOUNDARIES
Your work. Your connections. Our portal.
Your desktop workspace
The desktop app is the working environment for your analytical files and tasks. Creating a website account is not an instruction to upload that workspace or hand your AI credentials to Limuria. Protect the device, its backups and any exports; local storage alone is not a claim that every file is encrypted or inaccessible to other software.
Providers you choose to connect
Using a connected AI model, data service or other integration can send prompts, selected content and authorised requests to that provider. Its own account permissions, retention rules, terms and charges apply. Consider the sensitivity of the material before submitting it, and revoke access at the provider when a connection is no longer needed.
The Limuria customer portal
Website account and organisation details belong to the vendor-operated portal, along with subscription and service records. Material you explicitly submit for a consulting engagement enters Limuria’s custody. That is a separate disclosure from working in your local app; it should be limited to what is necessary for the agreed brief.
SOFTWARE DISTRIBUTION
Metadata is not a signature.
The release centre displays publisher-provided version, commit, package size, SHA-256 and signing status only when the metadata meets its schema and configured HTTPS-host checks. Those checks do not verify the downloaded binary, certify its safety or establish the publisher’s identity cryptographically.
A checksum can detect a mismatch with a published value. A manifest signature needs a trusted public key obtained independently and verification by the desktop release authority. A key published next to its own manifest is not an independent trust anchor. This website does not replace that authority or generate a second release-signing key.
Apple Developer ID signing and notarization are different from a signed release manifest. Ad-hoc builds do not provide Developer ID notarization. Check the actual release’s declared status and macOS security result; do not turn off operating-system protections to make an unexpected package open.
FOR SENSITIVE WORK
Start with the boundary.
Use only data and documents you have the right to access and share. Do not submit client-confidential or regulated material without the necessary authority.
Use a supported AI connection and permissions appropriate to the task. Keep API keys, recovery codes and signing material out of email, screenshots and consulting submissions.
Confirm scope, handling requirements and any required confidentiality arrangements before sharing sensitive consulting material.
Keep independent backups and review outputs before relying on them. AI-generated work is not an assurance of accuracy or permission to take an irreversible action.
We make no SOC 2, ISO 27001, independent penetration-test or other certification claim on this page. No blanket “zero retention”, “everything encrypted” or “nothing leaves your device” promise is implied.
Raise a security concern.
Contact Limuria’s public service address with a brief, non-sensitive description, affected product or page, and safe reproduction steps. Do not attach credentials, customer data or a working exploit against someone else’s account. Ask for an appropriate channel before sending sensitive details.
This is the published corporate contact address, not a claim of a dedicated incident-response service, guaranteed response time or bug-bounty programme.