Privacy Policy
Mika is an independent AI chat client operated by Yuli Zhao ("we"). This policy covers the Mika websites at managed-mika.com and transfer.managed-mika.com and the Mika iOS app. Mika is not an official DeepSeek app. Contact: yulizhao1013@gmail.com.
Standard chat history is stored on your device. Optional Mika Transfer temporarily uploads your original ZIP to our transfer service. AI features send data to DeepSeek only after you explicitly agree. Selecting an attachment can upload it before sending a message. You can decline AI permission and keep using local history.
1. Information stored on your device
- Chats and attachments: conversation titles, messages, responses, drafts and supported attachment originals are stored in the browser or app’s local database. We do not operate a Mika account system or a server-side chat history database. Your browser and iOS app have separate storage.
- API key: your own DeepSeek API key is stored in the iOS Keychain in the app, or in this website’s browser local storage. It is sent to DeepSeek to validate the key and authenticate requests. History exports exclude the saved API key. Browser storage is accessible to code running on the same origin; use a trusted device and protect your key.
- Preferences: language, appearance, voice, optional manually selected location, feature preferences and your versioned AI consent choice are stored locally. Mika does not request GPS location. Your selected location, current date and language may be included in AI chat context.
2. Information sent to DeepSeek
After permission, Mika sends the information needed for the features you use to DeepSeek at api.deepseek.com:
- Chat: your message, relevant conversation history and attachments or their provider file references, model instructions and feature settings, to generate replies and conversation titles.
- Attachments: selected images and files, filenames and media types, for upload and processing. Upload can begin when you select a file, before a chat message is sent.
- Speech: microphone recordings for transcription when you use voice input, and selected response text for speech generation when you use read aloud. Microphone access also requires device/browser permission.
- Search and link reading: relevant queries, URLs and context for DeepSeek’s server-side tools. These tools may contact search services or the websites involved.
- Authentication and networking: your API key, IP address and ordinary request metadata required to authenticate and deliver the service. Key validation also contacts DeepSeek, even though it does not send chat content.
The iOS app routes API requests through an on-device local service to DeepSeek over HTTPS; that service is not a developer-operated remote server. The website calls its configured DeepSeek API directly. Standard AI requests do not pass through a remote Mika chat backend. Optional archive transfers, described below, temporarily store a copy of the original ZIP.
DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.) is based in China. Data may be processed and stored in China, outside your country. Provider-side handling, retention and any use to improve models depend on applicable DeepSeek terms and your provider arrangements; Mika does not promise zero retention or that provider-side model training is disabled. See the DeepSeek Open Platform Terms and DeepSeek Privacy Policy. DeepSeek’s own privacy policy does not replace this policy for Mika users. Avoid sending secrets, sensitive personal information or other people’s information without appropriate permission.
3. Website hosting, links and support
Cloudflare hosts the public website and these pages. It may process IP addresses, request details and operational/security data to deliver and protect the site under the Cloudflare Privacy Policy. The installed iOS chat interface is bundled with the app; opening the online policy or support page contacts the website host. External links open third-party sites, whose policies apply.
If you contact us by email, we receive your email address and the information you choose to send. We use it to answer your request and resolve issues. Do not include API keys or unnecessary chat or attachment content.
Mika includes no advertising or analytics SDKs, does not track activity across other apps or websites, and does not sell personal data. Local storage is used for app functionality, rather than advertising tracking.
4. Your choice and withdrawal
Before the first API request, we identify DeepSeek, explain the data involved and ask you to choose “Agree and continue” or “Not now.” A microphone or camera permission alone is not permission to share information with AI. Consent applies to this installation/browser profile and the displayed policy version.
Open Settings → Data → Data sharing with DeepSeek → Withdraw to stop further AI requests and cancel requests still in progress. You can still browse, import, export and delete local records. You may review the disclosure and agree again later. Withdrawal cannot recall data already transmitted or erase provider-held data.
5. Retention, export and deletion
- Local records: retained until you delete them, clear website/app data, or the system removes that storage. Use Settings → Data to export a ZIP or delete all chats. Deleting history also clears local drafts and attachment records; it keeps preferences, your consent choice and saved API key.
- Saved API key: use “Remove saved API key” in Data settings. Removing it does not revoke it at DeepSeek. To revoke or rotate a key, use your provider account.
- Provider-held files and requests: deleting a chat or all local history does not automatically delete uploaded files, logs or other copies held by DeepSeek. Uploaded files have no expiry set by Mika and can remain until removed through the provider, subject to its retention rules. Contact DeepSeek about provider-side deletion, including at privacy@deepseek.com.
- Support: we retain correspondence as needed to handle the request and any applicable legal obligations. Email us to request deletion. Copies you export, share or back up are under your control and are not removed by deleting local chat history.
There is no Mika account to delete. We cannot remotely retrieve, export or erase records stored only on your device.
6. Optional history transfers
If you choose Mika Transfer, you explicitly agree before uploading an archive. The original ZIP is sent over HTTPS and temporarily stored in private Cloudflare R2 storage. There is no additional client-side file encryption. The developer and hosting provider can access the stored archive as needed to operate the transfer service.
The service stores the ZIP, file size, upload status and expiry information, a random transfer identifier, multipart upload details, and a hash of the separate upload/deletion credential. It does not ask for your DeepSeek password or API key, extract or analyze the archive on the server, or send it to an AI service. The ZIP itself may include personal account information and chat content from your export. Cloudflare processes network information to deliver and secure transfers; rate limiting uses the request IP address.
Anyone holding the full QR code or random transfer link can download the original ZIP. Keep it private. New downloads are refused seven days after upload completion, independently of physical storage cleanup. Unfinished uploads expire after 24 hours. An hourly job cleans up expired files and upload sessions; eight-day object lifecycle rules and one-day incomplete-multipart cleanup provide fallbacks. Physical deletion can lag behind expiry. Use “Delete the server copy now” on the upload page to remove it sooner. Deletion or expiry cannot recall copies already downloaded or data already transmitted.
The upload tab saves the QR link and deletion credential in session storage so they survive a refresh. Deleting the transfer here also clears that receipt; closing the tab or clearing browser storage may remove it. Deleting local Mika chats does not delete a previously uploaded transfer; use the upload page’s deletion control. The iOS app accesses the transfer service when you choose to scan and download, then asks for separate confirmation before replacing local history. Import does not itself send the archive to DeepSeek; later AI requests involving imported content are subject to the AI permission above.
7. Purposes, security and your rights
We process information to provide the features you request, based on your explicit permission for sharing with the AI provider; to answer support requests; and where necessary to secure and operate the website or meet legal obligations. Where applicable, these activities rely on consent, performance of the requested service, legitimate interests in support/security, or legal requirements. Network traffic to the public service uses HTTPS. No method of storage or transmission is completely secure.
Depending on your location, you may have rights to access, correct, export or delete personal information, withdraw consent, object to or restrict processing, and complain to your local data protection authority. Use the local controls above or contact yulizhao1013@gmail.com. We will address requests relating to information we hold and help identify the appropriate provider for other requests. Explicit permission is not a guarantee that every jurisdiction permits every use or international transfer.
8. Children and updates
Mika is not directed at children. If you believe a child has provided personal information, contact us. We update this page and its effective date when practices change; material changes to AI sharing require a new in-app consent version before further requests.