Terms and limitations

Bounded first version. This version provides the two workflows described here. The broader WebUT product remains in construction. Advertising is disabled.

The image workflow removes the selected supported metadata containers without resizing or re-encoding image pixels. Information visible in the pixels and unsupported or retained metadata may remain. A successful cleanup does not establish anonymity.

Image cleanup accepts up to 20 PNG, JPEG or WebP files with at most 50 MiB combined source bytes, subject to the stated structural limits. Unsupported features or an invalid member refuse the complete batch. Removing EXIF from an image with nontrivial orientation is refused.

Strict JSON formatting preserves numeric token spelling and object member order. Duplicate decoded member names, comments and trailing commas are refused. Schemas, queries and general JSON editing are outside this workflow.

JSON input and complete output are each limited to 25 MiB of UTF8 data, 128 nesting levels and 250,000 nodes. Formatting can exceed the output limit even when the input fits. Unsupported or oversized work is refused as a whole; output is not truncated.

Keep original files and inspect downloads in the application where they will be used. Downloaded files remain on the device after application work is cleared. Application cleanup is not a physical memory-erasure guarantee.

These are bounded workflows. Results do not certify anonymity, legal rights, security or compatibility with every receiving application. The broader WebUT product remains in construction. Advertising is disabled.

Keep original files and check downloads in the intended application. The supported finite workflows do not complete the full WebUT catalogue, regional commitments or language and document requirements.