Privacy Policy

iFloat does not collect your content.

Your voice, images, video, typed text, translations and history are processed by iOS on your own device. We do not ask you to create an account, we do not operate a server that receives this content, and we do not use advertising, behavioral analytics, crash-reporting or third-party tracking SDKs.

Note: Apple, as the provider of iOS, the App Store, StoreKit, Speech, Translation, Photos and screen capture, may process platform data under its own privacy policy. That is not our collection of that data.

In short: we do not collect personal information, and we do not collect your content.

Specifically, we do not collect, read, upload or sell:

• your name, email address, phone number, mailing address or other contact details;
• an account, password, social account or login credential;
• contacts, calendar, health, fitness, location or precise location;
• advertising identifiers (IDFA), device fingerprints, unique device identifiers or cross-app tracking data;
• your voice, recordings, photos, videos, screen content, typed text, translations or subtitles;
• your usage behavior, tap streams, session length, search history or product analytics;
• crash logs or performance data collected through our own SDK.

What "collect" means here

Under Apple's App Store definition, "collect" means transmitting data off the device in a way that allows the developer or a third party to access it for longer than is necessary to service the request in real time. Data processed only on your device and discarded after processing is not "collected." All core processing in iFloat falls into the latter category.

On-device data we do process

To provide the features, iFloat processes the following data on your device. It does not leave the device unless you actively export or share it:

• Microphone audio — for live transcription and translation; raw audio is not saved by default.
• Camera frames and photos — for text recognition and translation; photos are not saved by default, only recognized text.
• Video/audio files you choose — for audio extraction, transcription, translation and subtitle rendering.
• System audio and screen content — only after you start Floating or Screen Recording and complete the system picker.
• Typed text and translations — for display, speech and local history.
• Settings and preferences — language, appearance, voice and auto-save preferences.

The table below lists the data involved, where it is processed, whether it is retained on device, and whether it is uploaded. Every "Upload" entry is "No." Feature names follow the app UI.

On a phone, the table becomes a stack of cards for easier reading.

Points that are easy to misunderstand

• Raw microphone audio is not written to disk. Live and Floating save only transcribed text. If you enable the microphone while screen recording, that audio becomes part of the video you choose to save.
• Photos are not written to disk. Photo/library translation saves recognized text only; the app does not copy your photo into history.
• Video copies are written to disk. Video Subtitles keeps the imported video copy, exported subtitles video and SRT in the app's private directory so you can edit again. Deleting the record deletes those copies.
• Sharing is initiated by you. When you use the system share sheet, the file goes to the third-party app or service you choose; that third party's privacy policy applies.
• Language resources are downloaded by the system. The first time you use some translation/speech languages, iOS may contact Apple to download resources. We do not receive your text, audio or images.

iFloat requests permissions only when the corresponding feature needs them. You can change them at any time in iOS Settings → Privacy & Security. Denying one permission does not affect other features.

iFloat stores data in the private container iOS assigns to the app. We do not sync to the cloud, and we do not back up data to our servers.

Security settings

• History index and assets use iOS file protection (completeUntilFirstUserAuthentication).
• The history directory is excluded from iCloud backup and is not synced across devices.
• We do not automatically delete history after a fixed number of days. Video copies can take up space; delete them when you no longer need them.

We do not sell, rent or share your personal information for advertising.

Apple system capabilities we use

Third parties we do not use

• No advertising SDKs (such as AdMob or Meta Audience Network);
• No analytics SDKs (such as Firebase Analytics, Google Analytics, Mixpanel or Amplitude);
• No crash-reporting SDKs (such as Crashlytics or Sentry);
• No attribution or cross-app tracking SDKs;
• No account system, cloud sync or cloud inference service.

Legal requirements

Because we do not hold your content, there is generally no voice, image or text to provide to law enforcement. If compelled by law, we may provide support emails you voluntarily sent us; we will try to notify you where legally permitted.

Business transfers

If all or part of iFloat is involved in a merger, acquisition or sale of assets, this policy and related support communications may transfer with the business. We will update this page. Because we do not hold content data, no content data would transfer.

This policy page

This page is hosted on GitHub Pages (or another static hosting service we choose). The hosting provider may log access data (such as IP address, User-Agent and time) for security, abuse prevention and troubleshooting. We do not link those logs to in-app usage, and this page does not use cookies, ads or analytics scripts.

Because processing happens mainly on your device, you control it directly. These are the most common actions:

Legal rights

If you are in the EEA, UK, Switzerland, California, mainland China or another jurisdiction that grants data protection rights, you may have the right to access, correct, delete, restrict, object, port, withdraw consent and lodge a complaint. Because we do not collect your content, many requests will result in "we do not hold your data." We will still help you delete data on your device and will respond within a reasonable period.

• Withdraw consent: turn off the permission in iOS Settings, or turn off auto-save in the app.
• Do Not Sell/Share: we do not sell personal information or share it for cross-context behavioral advertising.
• Complaints: you may contact your local data protection authority; you can also contact us first, and we will try to resolve it.

iFloat is not designed for children and does not ask for age, name or an account. We do not knowingly collect personal information from children.

Because all content is processed on device, we cannot identify a user's age or remotely view or delete content on a particular device. If a guardian believes a child has saved content they do not want to keep, they can delete history in the app or delete the app; they can also contact us for instructions.

If your jurisdiction has stricter rules for children's personal information (for example, China's rules for children under 14 or the U.S. COPPA), please use the app with a guardian and contact us if needed.

We do not transfer your voice, images, video, text or history to other countries or regions because we do not operate a server that receives this content.

Apple's system services (such as the App Store, StoreKit, Speech, Translation, Photos and screen capture) may process platform data in various countries under their own policies. Apple is responsible for that processing, and Apple's privacy policy applies.

iFloat reduces risk by keeping data on the device:

• core speech recognition, translation, text recognition and subtitle rendering happen on device;
• content is not sent to our servers, so there is no content transmission or server-storage risk on our side;
• history index and assets use iOS file protection and are excluded from iCloud backup;
• no advertising, analytics or third-party tracking SDKs are used.

No device is perfectly secure. We recommend setting an iPhone passcode and keeping iOS up to date. If you share a device, consider whether local history may be visible before saving sensitive content.

We may update this policy as features, system capabilities or legal requirements change. The updated version will be posted on this page with a new "Last updated" date and version number.

If a change materially affects your rights (for example, starting cloud processing or adding advertising or analytics SDKs), we will provide a prominent in-app notice and, where required, ask for your consent again. Continued use of the updated app means you have read the updated policy.

If you have questions about this policy, permissions or data handling, or wish to exercise your rights, contact:

We usually respond within 30 days. To protect your privacy, please do not send unnecessary voice, photos or video by email.

The Simplified Chinese version is authoritative. This English version is a translation; if there is a conflict, the Simplified Chinese version controls.