Privacy Policy

This policy covers the rikAI app and our websites, rikaillm.com and rikaillm.jp. rikAI LLC is responsible for the processing described here. We do not sell personal data or use it for advertising or cross-app tracking.

• Translations and chats. Chats and settings are saved in the app’s private storage and may be included in your device backups. Clear recent chats in Settings; saved chats must be deleted separately. Text from a chat can be shared as context when you use optional cloud Ask, including earlier messages written while cloud Ask was off.
• Photos and handwriting. Text recognition runs on your device. Cloud Ask sends text, not the source image, handwriting strokes or video. Text recognized from an image or selected from a reader may be included in a question’s context.
• Pronunciation and voices. Pronunciation recordings are analyzed on-device and discarded after use. Speech is synthesized on-device. Cloud Ask does not upload audio. Apple may download speech resources, and optional VOICEVOX voice packs require downloads.
• Preferences. Preferences are saved locally. The assistant’s custom instructions, including a name or nickname you enter, are included in cloud Ask requests when that option is on.
• Local allowances and Anki. Photo, Anki and pronunciation allowance counters are held in the Keychain and can survive reinstalling. Anki records are local. Compatible text cards can be sent to AnkiMobile; audio cards are exported as an Anki package for import. Exporting shares the selected cards and any included audio with the app you choose, whose settings and policies govern subsequent storage or sync.

Off by default on every iPhone. In Settings → Model → Ask with ChatGPT, read the disclosure and choose Allow to permit the context described below to be sent for subsequent Ask requests. You can decline, including on phones that cannot run local Ask, and still use translation and dictionary tools. You do not need an OpenAI account or API key; rikAI operates the API connection. Turning it off stops future cloud Ask requests, but does not recall requests already sent or delete provider records.

• What is sent. Your question, the selected sentence and its translation where available, relevant dictionary and grammar facts, recent conversation context (including prior questions and answers), and assistant preferences. That context may contain text you typed, pasted, scanned or selected from a third-party reader. It is not limited to the latest question. Do not include secrets or personal information you do not want processed online, and only share information you have permission to share.
• Who receives it. The app sends the request over HTTPS to models.rikaillm.com, operated for rikAI on Cloudflare. Our service forwards the question context to OpenAI and streams the answer back. Cloudflare processes the request and response in transit. OpenAI receives the text needed to answer, not the app’s separate device-ID or Pro-status fields. A name or other identifying information in your text or preferences is still part of that text.
• Usage and security. Our service also receives a random persistent device ID, your Pro-status flag and your network IP address to apply allowances and protect against abuse. Ask counts are stored against the device ID and IP address (an IPv6 network prefix for IPv6). Counts reset by UTC day and the previous day’s meter entries are removed when the next request is processed on a later UTC day; this is not a promise of deletion exactly at midnight.
• Content retention. rikAI’s Ask endpoint does not save a chat transcript in its application database. OpenAI’s API data controls state that API content is not used for training by default, unless the API customer opts in, and that abuse-monitoring logs may contain prompts and responses and normally be retained for up to 30 days, with legal exceptions. We do not promise zero retention. Cloudflare also processes operational and security metadata under its privacy policy; its platform logs are separate from our daily counters.
• Limits and fallback. Currently up to 10 cloud answers per device per UTC day are available free, or 200 with Pro. Network and service-wide caps can limit availability earlier. Local Ask requires an iPhone with at least 4 GB of memory and an installed reasoning model. On those phones, turning cloud Ask off or reaching the device’s daily cloud quota uses local Ask. Connection and service failures show an error; they do not automatically retry locally. On lower-memory phones, Ask requires cloud permission and internet, and is unavailable when permission is off or the cloud allowance is exhausted. Translation and dictionary tools remain on-device. A failure or fallback does not undo a request already transmitted.

• Free reader time. While a free-tier reader is active in the foreground, the app reports elapsed seconds and the same random device ID to our Cloudflare service, generally every 30 seconds and when closing. The service stores a daily total to enforce the shared reader allowance. Each stored record expires 48 hours after its latest update. These reports do not contain video titles, URLs, posts or subtitles. Pro skips reader-time reporting, but still sends usage information if cloud Ask is enabled.
• Device identifier. The random ID is stored in the device Keychain and may survive deleting and reinstalling the app. It is not an advertising identifier. We use it for allowances and abuse prevention, not advertising.
• Models and allowance date checks. The app contacts our Cloudflare-hosted model service for model catalogues, downloads and free-tier date checks. The host receives network and operational metadata such as IP address, request path, time and response status. These requests do not carry your translation or chat text.
• Voice downloads. Optional VOICEVOX and Open JTalk resources are downloaded from GitHub and SourceForge, which receive download requests including IP addresses under their own policies.
• Purchases. Apple handles App Store payments and subscription management. We do not receive payment-card details. The app receives subscription information from Apple and sends an active-Pro flag with cloud Ask requests to select the allowance.

Readers such as YouTube, X and, where available, Netflix open third-party services. Those services receive web requests, IP addresses, cookies and any account activity under their own terms and privacy policies. rikAI is not affiliated with or endorsed by them. Signing in and available content depend on the service.

Reader sessions may persist in the app’s web-view storage. Sign out through the service to end a session. Word lookup, furigana and image text recognition run locally. If you ask about selected text with cloud Ask enabled, that text and the question context go to rikAI’s Cloudflare service and OpenAI as described above. We do not upload your web-view cookies or passwords through the Ask endpoint. Free-tier reader-time reports contain usage duration, not browsing content.

rikAI includes no third-party advertising or analytics SDK. If you opt in to sharing developer diagnostics through Apple, Apple may provide crash reports. We use those reports to diagnose and fix problems. Our online services also generate operational and security records; these are distinct from analytics inside the app.

• Waitlist. If you join the waitlist, we store your email address and signup time for the launch announcement. Email us to request removal.
• Support. If you email us, we receive your address and anything you include. We retain correspondence as needed to handle the request and related obligations; do not send sensitive chat content unless it is needed for support.
• Website services. Cloudflare hosts our websites and provides cookie-free Web Analytics. Google Fonts receives network requests to load fonts. These providers process IP addresses and other request metadata under their own policies.

On phones that support local Ask, leave the cloud option off to use the installed reasoning model. You can withdraw cloud permission in Settings at any time. Clear local chats or delete the app to remove app files; device backups and Keychain items are separate, and local deletion does not delete provider records already created. We cannot restore your local chats.

We process optional cloud content with your permission to provide answers, and usage and security records to operate the service and prevent abuse. Where applicable law requires a legal basis, we rely on consent for optional AI sharing, performance of our agreement for requested services, legitimate interests for security and support, and legal obligations where applicable. You may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent, or complain to your local data-protection authority. Contact us to exercise them. We may need information to identify your request or records, and cannot promise to locate records from an email address alone because the app has no rikAI login.

Cloudflare and OpenAI may process data in the United States and other countries where they operate, whose laws may differ from yours. Applicable provider contractual safeguards govern those transfers. Provider retention and legal obligations may limit immediate deletion; turning off cloud Ask prevents future requests, not processing that has already occurred.

rikAI is not intended for children under 13. Users must also meet applicable minimum-age requirements and have a parent or guardian’s permission where required by our terms or local law. Do not enable cloud Ask for a child who is not eligible. If you believe a child has provided personal data contrary to these requirements, contact us so we can investigate and address it.

This version clarifies explicit cloud permission on every supported phone, device requirements, and when local Ask is available. We post updates here with an effective date and announce material changes in the app or on our website. A policy update does not turn on optional cloud Ask.

rikAI LLC, 127 Cimarron Drive, Coraopolis, PA 15108, United States. Email ryan@rikaillm.com for privacy requests. See the terms of service for the agreement governing use of rikAI.