Loading page…
Loading page…
Understand the SDK license, local processing, and optional Cloud delivery.
File contents, previews, mapped records, and rejected records stay in your browser. Diakrio receives no file data, schema, key, or telemetry from the importer.
Your application receives accepted batches directly through the callback you configure. Opt-in saved progress keeps the source, corrections, and receipts in this browser for up to 24 hours; expiry is cleaned on the next importer opening, or immediately through Discard. Session tokens are not saved.
Your host application controls what its callback does with those records, including any transmission to your own services. Local mode means no data is sent to Diakrio.
Cloud v2 requires a short-lived session and publishable key. Accepted batches transit Diakrio and are relayed to the approved destination pinned by your backend. AI mapping is not available.
In widget delivery mode, Diakrio Cloud stores operational metadata such as import IDs, format, counts, status, duration, and delivery outcome—not filenames, raw rows, rejected values, tokens, or destination response bodies.
OCR downloads configured runtime and model assets for local image processing. Downloads are distinct from image uploads. Verified models may be cached on your device and can be cleared in the tool. A separately enabled, authenticated hosted OCR integration uploads images for transient CPU processing; the public tool remains local. Separately enabled asynchronous file processing stores input and output artifacts in private R2 under its configured retention and deletion policy. Anonymizer redacts supported content under selected profiles; misses and false positives remain possible. Neither redacted text nor extracted text sanitizes the source image or PDF, and no universal anonymity guarantee is provided.
The JavaScript distributions and public assets have separate release gates. See the product guides for availability and the support status.
Diakrio SDK packages are free for personal and commercial application use, including hosted applications, with no SDK per-user or per-record license fee. Bundling the runtime with your application is permitted with the license and notices retained.
New releases use a proprietary distribution license and keep development source private. Standalone rebranding and resale of the library are restricted. Diakrio Cloud and support services have separate terms.
Read the Free Distribution License and distribution notices. Earlier MIT releases and third-party components retain their existing license rights. The license included with your installed package governs that version.
Runtime distributions also include third-party Rust license notices.
Diakrio is provided as-is without warranties. Product telemetry, when enabled, is limited to privacy-safe operational measurements and does not include imported record values.
Retention, quotas, subprocessors, and security controls for hosted projects are documented on the security and data-flow page.