Client-Side Tool Processing

ORIXIVA’s free browser-based tools are designed around a privacy-first, client-side processing model for supported workflows. This means the user’s browser can read and transform the selected file instead of sending the working file to an ORIXIVA processing server.

How Client-Side Processing Works

When you choose a supported local workflow, the browser loads the tool interface and any required code or processing library, reads the selected file locally, performs the supported operation, creates the result in browser memory, and provides the result for download. The current free architecture is intentionally designed not to create a permanent ORIXIVA database of users’ working files.

  • Upload/select the file in your browser.
  • Process the supported task locally on your device.
  • Generate the output in browser memory.
  • Preview or download the result.
  • Temporary browser objects may be released after use or when the session is reset.

What ORIXIVA Does Not Promise

Client-side processing does not mean that the webpage itself has zero network activity. The browser may need to download the interface, JavaScript libraries, model files, fonts, advertising resources, or other third-party assets. The important distinction is that supported local workflows are designed not to upload the user’s working file to an ORIXIVA processing server.

Free + Zero Server File Load Architecture

Core privacy model
Free tools first use browser-side processing for supported operations. No permanent user-file archive is intended to be created on the ORIXIVA WordPress server as part of the current free architecture.

Examples of Supported Local Tool Categories

  • PDF workflows such as supported merging, rendering, extraction, text search, and document preparation.
  • SVG and icon workflows such as sanitization, optimization, recoloring, resizing, inspection, and export.
  • Image workflows such as conversion, resizing, compression, and image-to-PDF.
  • Office and data workflows such as supported DOCX, XLSX, CSV, JSON, XML and PPTX extraction/conversion.
  • OCR workflows for images and scanned documents where the browser OCR engine is used.
  • ZIP and file-analysis workflows where processing is implemented locally.

Browser and Device Performance

Because processing occurs on the visitor’s device, speed depends on the device’s CPU, GPU support, available memory, browser implementation, file size, document complexity, and the specific workflow. OCR, large PDFs, spreadsheets, and media conversion can require substantially more resources than simple text or image tasks.

Heavy Libraries and Third-Party Resources

Some advanced workflows may load processing engines only when the user selects them. These libraries may come from third-party content-delivery services. Their presence does not by itself mean that the user’s working file is uploaded, but the associated network resources are subject to the provider’s infrastructure and policies.

Server-Side or External Processing in the Future

If ORIXIVA later adds a workflow that requires server-side processing, cloud storage, an external AI service, or another remote processor, the relevant page and privacy disclosures should clearly state that fact before or when the feature is used. The local-processing statement in this policy applies only to supported client-side workflows.

Security and Responsible Use

Users should still avoid placing highly sensitive information into any online service unless they understand the applicable processing model. ORIXIVA recommends keeping browsers updated, using trusted devices, and downloading results to a secure location. No website can guarantee absolute security.

Children’s Privacy

ORIXIVA is not directed to children under 13, and the tools are not intentionally designed as services targeted at children under 13.

Contact

For privacy questions, requests, or concerns, please use the contact method provided on the ORIXIVA website’s Contact Us page. Do not send passwords, payment-card numbers, or other unnecessary sensitive information through ordinary email or contact forms.

ORIXIVA | Privacy and Website Data Policies