Privacy Policy

Lamuki is designed with a privacy-first approach. The normal file workflow is handled directly in your browser. Lamuki does not require an account, does not use analytics, and does not send your files to Lamuki's servers for processing or storage.

When you upload or create files in a Lamuki workspace, the file data is handled locally by your browser. File processing and operations are performed on your device rather than on Lamuki's servers.

• Uploaded files are processed directly in your browser.

• File contents are stored locally in your browser when required by the workspace.

• Lamuki's servers do not receive your file contents during the normal file-processing workflow.

• You do not need to create an account or provide personal information to use Lamuki's workspaces.

Lamuki uses browser storage to provide certain features. This data is stored on your device and is not stored on Lamuki's servers.

• LocalStorage: Lamuki uses LocalStorage to store Override settings, such as your theme and workspace preferences.

• IndexedDB: Lamuki uses IndexedDB to store file contents during workspace use. By default, this file data is cleared when the page is reloaded.

• Persist over reload: If you enable the Persist over reload option, Lamuki can keep your files and additional workspace information such as computed outputs and metadata in IndexedDB so that your workspace can be restored after a reload.

Persist over reload is an optional feature that allows Lamuki to keep workspace information in your browser after a page reload. This information remains stored locally until it is cleared according to the behavior of the feature or removed by the user.

• When Persist over reload is disabled, persisted workspace data is cleared on the next page reload.

• Disabling the option does not immediately remove the existing data from the current workspace.

• You can also remove locally stored Lamuki data by clearing the relevant browser data.

File downloads are handled directly by your browser. Lamuki does not need to upload your files to a server in order to prepare a download.

• Individual files are prepared locally in the browser before downloading.

• When multiple files are downloaded together, Lamuki may create a ZIP archive in your device's memory before starting the download.

• The download process does not require your file contents to be sent to Lamuki's servers.

When you delete files from Lamuki, the corresponding locally stored file data is removed from the browser's IndexedDB storage. Lamuki does not maintain a server-side backup of those files.

• Deleting a file removes its stored data from Lamuki's browser storage.

• Clearing the workspace removes the corresponding locally stored file data.

• After the deletion request is made, the actual storage cleanup is handled by the browser and operating system.

Lamuki does not maintain a separate server-side backup of your locally stored workspace files. If you clear Lamuki's browser or site data, the locally stored file-related information will be lost and Lamuki will start again with its default state.

Lamuki currently does not require users to provide personal information to use the website or its workspaces.

• Lamuki does not require an account, registration, or email address.

• Lamuki does not currently use analytics services.

• Lamuki does not currently use cookies.

• Lamuki does not have a contact or feedback form that sends information to us.

• Lamuki does not currently use automatic error or crash reporting services.

Lamuki is currently delivered as a statically generated website. The server provides the website resources required by your browser. Lamuki's normal workspace workflow does not send your file contents to Lamuki's servers.

• Uploading a file does not send the file contents to Lamuki's server.

• Running an operation does not send the file contents to Lamuki's server.

• Downloading a file does not require sending the file contents to Lamuki's server.

Lamuki currently does not use third-party services to process, store, or analyze your file contents. Lamuki may use third-party resources in the future where necessary for website functionality. Any future feature that changes how user data is handled will be reviewed and reflected in this Privacy Policy where applicable.

Lamuki may use browser APIs that are necessary to provide its functionality, such as APIs for working with files and browser storage. Information obtained through these APIs is used locally by Lamuki and is not intentionally transmitted to Lamuki's servers or third-party services as part of the current application workflow.

Lamuki does not currently use a separate personalization or tracking system. Some user experience preferences, such as theme and workspace settings, can be stored locally through the Override system.

Lamuki does not currently provide a contact form or feedback form. Users can voluntarily contact Lamuki using the email address provided on the Contact page. Information included in an email is provided voluntarily by the user and is not collected through the Lamuki application itself.

Lamuki does not currently require an account or personal information to use its workspaces. Lamuki is not currently restricted to a particular age group. Users should use Lamuki in accordance with the laws and requirements applicable to them.

Because Lamuki processes and stores workspace data in your browser, the security of that locally stored information also depends on the security of your device, browser, and operating system. Users should keep their devices and browsers appropriately secured.

Lamuki may update this Privacy Policy when the website, its features, or its data-handling practices change. When this policy is updated, the Last Updated date at the top of this page will be changed accordingly.

If you have questions about this Privacy Policy or how Lamuki handles information, you can contact Lamuki using the email address provided on the Contact page.