Data Processing.
Browser-based processing notes and technical infrastructure
Browser-Based Processing Model
This document serves as a standard Data Processing Addendum between the User (Controller) and Docustitch (Service Provider). Unlike cloud-based competitors, our DPA is simplified because supported tools are designed to avoid a remote processing queue for document files.
1. Nature of the Service
Docustitch provides browser-side PDF processing utility tools. The technical nature of the software is "Client-Side Execution." Supported document workflows are designed to run in the end-user's browser session. Some future, API, or account-based workflows may require separate documentation.
2. Technical Privacy Controls
WASM Runtime
The processing engine is written in Rust/C++ and compiled to WebAssembly, ensuring strict memory isolation inside the browser sandbox.
No Backend API
Standard supported tools are designed around browser-side processing rather than a document upload endpoint.
3. Data Handling Obligations
In the event that you provide us with contact information (via support inquiries), we treat that data as "Operator Data" and process it strictly to fulfill your request. We do not sell or share user contact data with third parties for marketing purposes.
4. Security Measures
We implement industry-standard security measures to protect the integrity of the website code and ensure that the WASM modules served to your browser have not been tampered with.
- HTTPS/TLS 1.3: All asset delivery is encrypted.
- SRI (Subresource Integrity): Ensuring that script files match the intended cryptographic hash.
- CORS Policies: Restricting cross-origin access to the local browser context.
5. Geographic Transfers
For supported browser-side tools, document files do not need a remote processing queue. Website assets and analytics may still be served through ordinary web infrastructure. Website assets are served via a Global Content Delivery Network (CDN) to ensure low-latency access worldwide.