Keep proof and product history close to the thing you bought.

Choose a receipt photo, product image, or PDF when the useful details are easier to show than type. With cloud AI permission enabled, Kopti sends the selected content for parsing and prepares a candidate for review.

The candidate can propose an item, purchase or service event, document name, merchant, model, purchase date, cost, currency, and warranty information when those details are supported by the source.

Receipts can be faded, cropped, multilingual, or ambiguous. Kopti shows the extracted fields before saving so you can compare them with the source and correct the product, date, amount, model, or warranty term.

The original receipt and the issuer's warranty terms remain authoritative. A parsed field helps you find and use the information; it does not change the legal document.

The original file is sent for parsing and is not retained by Kopti's backend afterward. If you choose to keep proof, the iPhone app stores the original locally on that device while the backend stores document metadata.

A local file can be removed with its document record. Device-local storage also means you should keep another authoritative copy when losing the only receipt would matter.

A purchased item can accumulate service events, replacement parts, warranty details, and reminders without separating the product's history from its proof.

When a problem appears, the item timeline can help you retrieve the model, purchase, previous work, and locally stored receipt instead of rebuilding the story from email, photos, and calendar entries.

Kopti lets you correct or delete saved information. Account export creates structured data for profile settings, groups, items, maintenance, reminders, and document details, with chat history optional.

Account deletion removes server data through the documented deletion process. Deleting a Kopti account does not cancel an App Store subscription, which must be managed separately through Apple.