LetsFloat Privacy Policy
Effective date: 2026-06-13
LetsFloat v0.1 is a personal voyage recording app. This policy describes the data handled by the iOS app and the copilot response flow.
1. What LetsFloat Stores
LetsFloat v0.1 uses Sign in with Apple for the first-run entry. It does not provide phone number login, email/password registration, social login, or a public community account system.
The app stores content that you create or configure on your device, including Apple sign-in state, Apple user identifier, optional Apple email, optional Apple display name, ship name, copilot name, voyage text, voice recordings, speech transcripts, voyage conversation messages, titles, anchors, voyage status, favorites, follow-up notes, and cabin control settings.
The app also stores a local entitlement cache, including lifetime unlock state, AI signal balance, cumulative free-record count, and a pseudonymous billing account key.
2. Copilot Response Requests
After you save voyage text or a speech transcript, LetsFloat sends the current voyage text to the configured AI proxy to organize a short title and anchors. The first copilot reply and all later replies are generated by the conversation request, not by the archive request.
If you continue a conversation around a voyage, LetsFloat sends the current voyage text, recent conversation messages within that voyage, and up to three locally selected related voyage snippets. Those snippets may include titles, anchors, short summaries, and brief recent conversation summaries.
The app should only send ship name, current voyage text, input mode, creation time, recent same-voyage messages, and the small related snippets described above. It should not send audio files, device identifiers, contacts, location, photos, or Apple ID credential data.
If there is no text to send, the app does not request a copilot response.
3. Local Data And Export
Voyages, anchors, and voice recordings are stored in the app sandbox. LetsFloat v0.1 supports Markdown and JSON export. Voice recording files are not bundled into the export files in v0.1.
4. Third-Party Services
Copilot responses use a backend proxy to call a cloud model. The iOS app should not include provider API keys.
LetsFloat v0.1 uses DeepSeek for cloud copilot response generation. For this release, the request data retention practice is treated as retained or unknown, and the App Store privacy answers use the corresponding User Content disclosure.
The current voyage text, ship name, input mode, creation time, recent same-voyage conversation, and the small locally selected related snippets may be sent through the backend proxy to DeepSeek. Audio files, Apple ID credential data, device identifiers, contacts, location, or photos should not be sent to the AI proxy.
5. Purchases And AI Signals
LetsFloat v0.1 offers a free tier, a lifetime cabin purchase, and one-time AI fuel packs. Purchases are processed through Apple In-App Purchase.
To sync purchases and AI signal usage, the backend stores purchase metadata only: pseudonymous billing account key, StoreKit transaction identifiers, product ids, AI credit lots, reservations, and consume/release timestamps. The billing ledger does not store voyage text, audio, anchors, or conversation content.
6. Contact
For privacy questions or support, contact 707479145@qq.com.