AI & privacy
Useful AI with permission, review, and explicit storage boundaries.
Kopti uses AI to reduce form-filling, not to make an invisible record on your behalf. Cloud processing is permission-based, every candidate is reviewable, and the original attachments you submit are not retained by Kopti's backend by default.
- Permission
- Cloud AI can be allowed or withdrawn per account
- Confirmation
- A candidate is not saved memory until you approve it
- Attachments
- Original bytes are not retained by the backend
Before processing
Cloud AI starts with account-level permission.
Kopti asks for explicit permission before sending new text, transcripts, photos, receipts, or PDFs for cloud AI processing. The permission is stored per account and enforced by the backend across devices.
You can withdraw that permission in Data & Privacy settings. Existing saved information remains available, while new AI drafts and attachment imports stay disabled until processing is allowed again.
What is sent
Only the capture selected for the requested draft is processed.
Kopti sends the text or transcript you submit and any selected attachment through its private AI gateway to OpenAI. The purpose is to prepare proposed item details, events, reminders, and document metadata.
Voice notes use Apple Speech to create an English transcript, using on-device recognition when available. The temporary audio file is deleted after transcription or cancellation; the transcript is what may be offered for cloud processing.
- A note about maintenance, purchase, replacement, or renewal
- A selected receipt, photo, or PDF
- Enough existing item context to prepare the requested candidate
Before saving
AI output remains a candidate until you confirm it.
The review step separates extraction from memory. You can inspect which item is affected, what will be added to history, which reminder will be created, and which document details will be kept.
Edit or discard inaccurate output. Only the confirmed structured fields become part of your stored Kopti data.
After processing
Structured memory and original files follow different paths.
Confirmed items, events, reminders, document metadata, and capture history are stored so the app can provide its memory and reminder features.
Original attachment bytes are not retained by Kopti's backend. When you choose to keep proof, the original file is stored locally by the iPhone app. Pending, completed, failed, and deleted records follow the retention periods described in the current Privacy Policy.
Your controls
Review consent, export data, or delete the account.
Settings provides the cloud-processing control, structured-data export, optional chat-history export, capture-history clearing, and account deletion flow.
An accepted deletion request signs the user out and queues server deletion, normally completing within 24 hours. App Store subscriptions are controlled separately through Apple and are not cancelled by deleting the Kopti account.
The Privacy Policy is the authoritative source for current providers, data categories, retention periods, and contact information.