Menu

More

Enterprise
Language

Compliance Framework

Last Updated: June 13, 2026

Prokolpo Sathi is dedicated to building tools that respect user autonomy and satisfy the highest standards of data security and regulatory compliance. Since our core utility architecture is client-side, we minimize data risk by eliminating file retention entirely.

1. Digital Personal Data Protection (DPDP) Act, India

Under the DPDP Act of 2023, data fiduciaries are held to strict standards regarding processing personal data. Because Prokolpo Sathi processes your photos, signatures, identity details, and forms entirely in your local web browser, we do not collect, store, or transmit your personal documents. Your device serves as both the processor and storage, placing full data control directly in your hands.

2. GDPR & CCPA Data Minimization

We align with the principle of "Data Minimization" outlined in the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). Prokolpo Sathi collects only the minimum necessary metadata (such as anonymized browser analytics and page hit counts) to optimize performance. Your files (JPG, PNG, PDF) never touch our backend, ensuring compliance by architecture.

3. Local Secure Execution & Sandboxing

All core photo resizing, PDF merging/splitting, format conversion, and age calculation operations are executed within the browser's JavaScript engine sandbox. This execution context is isolated from external networks and processes, providing a self-contained environment that prevents cross-site leaks.

4. Third-Party Integrity

For any third-party transaction or analytical integrations (such as Stripe for Pro subscriptions or Google Analytics for platform improvement), all telemetry and communications are transmitted via industry-standard TLS 1.3 encryption. Financial tokens and payment card credentials never transit or store on Prokolpo Sathi servers.

5. Ephemeral Processing

Where backend processing is technically necessary (such as Background Removal APIs), files are stored strictly in temporary, volatile RAM. They are cleared automatically within seconds after the composite output is served back to your browser. No persistent log of these files is maintained.