Useful tools.
Private by design.

Your files stay on your device.

PDF and image processing, formatting, and QR generation run in your browser. SIKITE does not upload, store, or retain the original or generated files. File names, JSON, SQL, QR content, and image pixels are excluded from generation logs.

Inputs and results live temporarily in browser memory. Leaving the tool releases its working references; refreshing or closing the page clears the session. Clicking a download saves an output to the location you choose. On supported devices, clicking Share file opens your device’s sharing options; you choose where to send it. SIKITE does not use browser databases or local storage to retain your content.

We record processing metadata.

When generation logging is configured, the server records the tool identifier, input and output byte counts, duration, success or failure, and timestamp. A trusted hosting provider may supply an approximate country and city. Unknown location is recorded as unknown.

We never request GPS or precise browser geolocation. Raw IP addresses are not stored in generation logs. A trusted edge’s address may be used transiently to derive a short-lived rate-limit identifier in server memory. Administrator views cover the most recent 90 days. The supplied database deployment removes older metadata hourly; other deployments must configure equivalent retention cleanup.

Logs have controlled access.

Generation logs are available only to an administrator signed in with an email and password. A super administrator can also browse paginated failed tool runs and application diagnostics, with individual detail views. Application diagnostics contain a fixed error code and timestamp; raw exception messages, stacks, credentials, content, filenames, and IP addresses are excluded. Persistent error records follow the same 90-day retention window.

Administrator access is separate from the public tools. A protected session cookie keeps the administrator signed in for up to one hour; signing out ends that session. Logging availability does not affect processing or downloads. When the database is unavailable, up to 1,000 safe application diagnostics are buffered temporarily in server memory and retried when storage recovers. That buffer clears on restart; logs are never saved to files as a fallback.

Understand each output.

PDF compression is a raster conversion intended for image-heavy documents. It removes selectable text, links, forms, and accessibility tags. Target size sets a maximum, not a guaranteed exact size. The tool tries several quality and resolution settings and shows whether the result meets your target. If the original already fits, or conversion would increase its size, your original bytes are returned. Keep your original for archival and editable use.

QR codes are static. The content you supply is encoded directly, with no redirect service, expiry, or scan tracking added by SIKITE. SQL is formatted as text and is never executed.

Hosting is a separate layer.

Your hosting provider may maintain standard infrastructure access logs under its own configuration. Configure those logs and their retention separately before making the website public. SIKITE’s application never sends document or image content to the server.

Public processing counts.

The homepage transparency chart shows only successful logged tool-run counts and UTC dates. Choose the last 90 days or all recorded history, grouped daily, monthly, or yearly. Daily aggregate totals are retained without an expiry so all-time history survives the cleanup of individual records. These totals contain no tools, sizes, duration, location, or user identifiers.

Historical totals begin with the records available when aggregate recording was introduced. Previously deleted records and unlogged runs cannot be recovered or estimated. Monthly and yearly totals cover the selected range, including partial periods. Individual records remain private. If logging is unavailable, the chart reports that state instead of estimating activity.