Your recordings and journal
Recordings, original audio and saved journal content are stored on your device. The original audio is kept separately from the copy prepared for transcription. Transcripts, rewritten entries and other completed content can also be saved locally.
Apple Watch recordings are saved on the watch and transferred to your paired iPhone when a connection is available. Transcription is performed from the iPhone using the selected service. System interruptions, storage and battery can affect recording and transfer.
Audio and text sent for AI processing
All-inclusive cloud transcription and the free cloud allowance send audio to Flecty’s transcription service for speech recognition. By default the app prepares an upload with silence removed; choosing full-audio transcription sends that full copy. Recording locally does not itself require a transcription upload.
Writing styles and text cleanup process transcript text and the selected writing instructions. Timelines process transcript segments and relevant time context; when location is enabled, approximate area names may be included. Optional coaching processes text for the current recording and your coach instructions. These features use the selected cloud or BYOK route. Apple Health values are excluded from model requests.
With BYOK, audio and text are sent directly from your iPhone to the OpenAI or OpenRouter service you select. Your API key is stored locally in the device Keychain. Flecty does not send that key to its application servers or sync it through iCloud. Your provider’s processing, retention and terms apply separately.
Temporary results, usage records and service logs
Flecty’s application service does not save uploaded audio files in its database or object storage. The audio still passes through the processing service; this is not a promise that every infrastructure or AI provider immediately deletes all data.
Text transcription results and generated text results are temporarily cached for retries. Results normally expire after one hour and are then removed by scheduled cleanup. Deleting a journal entry on your device does not immediately remove an in-flight request, cached result or service log.
Service diagnostics include request identifiers, app version, processing duration, audio duration, language and error codes. The current cloud service configuration enables transcription-output logging for paid requests, capped at 16,000 characters per output. The free route disables transcription-text logging. Logs follow the hosting service’s retention settings; the one-hour retry-cache period is not the log-retention period.
Purchase-related identifiers and usage records are retained to verify access, enforce allowances and operate the service. Free requests are limited by the connection IP address and UTC day; the quota service derives a daily keyed identifier rather than storing the raw IP in its quota records or custom logs. This does not make all processing anonymous. Uninstalling the app does not automatically erase service, purchase or provider records.
Optional private iCloud sync
With an eligible paid plan and sync enabled, saved recordings and completed journal content sync through your private iCloud database. Journal metadata can include recorded locations when you enabled location. Sync runs while the app is in the foreground; unfinished processing stays on its original device. Your Apple account and iCloud settings also apply.
Turning sync off or letting a plan expire keeps existing content. Deleting an entry through the app and syncing propagates the deletion to connected devices; local deletion is separate from temporary AI-service records. Apple Health values and BYOK keys are not included in journal sync.
Location, only when you choose
Recording location is off by default. If you turn it on, Flecty requests When In Use permission and collects available locations only during active recording, including when that recording continues in the background. It stops location collection when recording is paused or ends.
Location samples can be saved with the recording and transferred from Apple Watch to iPhone. They help attach places to the timeline. Approximate area names can be sent for AI timeline context. You can turn the feature off or revoke permission in system settings; denying location does not prevent audio recording.
Read-only Apple Health context
Apple Health access is off by default. If you enable it, Flecty requests read access to existing heart-rate, heart-rate-variability (SDNN) and respiratory-rate samples that match valid recording intervals. It does not write health data, start workouts or force continuous sensor sampling. No readable samples means no values are shown.
Health values are used only in memory for the recording view and related event context. They are cleared when the view is left or access is turned off. They are not saved into journal files, exported with entries, synced through journal iCloud sync, placed in application logs or sent in transcription or AI requests. These values support personal reflection and are not medical advice.
Purchases and anonymous app identity
Apple handles App Store payments; Flecty does not receive your payment-card details. RevenueCat manages purchase status using an anonymous app-user identifier and purchase information. The cloud service verifies purchase-related proof to authorize paid processing and apply usage limits. An anonymous app identifier is not a guarantee that purchase and network processing cannot be linked.
A Flecty login is not required. Your Apple account, provider accounts and any information you choose to send to support remain subject to their respective handling. Support messages are used to respond to your request.
Crash reports, reminders and journal lock
Release builds use Sentry for sanitized native crash reports and fixed recording-failure diagnostics. Reports retain limited app/system version, device-model, stack-trace, execution-stage and error-code information. The app removes user identity, journal text, audio, request data, screenshots and session replay from these reports. These diagnostics are not used for advertising or cross-app tracking.
Optional daily reminders use local notifications without journal text or recordings. Journal Lock uses Face ID, Touch ID or the device passcode through system authentication. Flecty does not receive your biometric data or passcode. The lock is off by default and protects app access on that device; it does not add separate content encryption or end-to-end encryption.
Your choices and requests
You can change microphone, location, Apple Health, notification and iCloud permissions in the app or system settings. You can manage local journal entries using the available app controls. Disabling optional permissions does not revoke information already saved with earlier recordings.
To request deletion or an export of your data, email team@yez.llc. We handle these requests by email. You can also use this address for access, correction or other requests about information Flecty holds. We will assess requests under applicable United States law and any mandatory protections that apply to you, and explain any verification or retention requirements. Data held independently by Apple, your BYOK provider or other providers may require a request to that provider. No fixed deletion deadline or provider-retention period is promised here.
Policy updates and contact
We may update this policy as the product and its processing change. The effective date and current policy will be published here. Contact Yez, LLC for privacy questions or data requests at the email below.
Questions or data requests? Contact team@yez.llc.
Also read Terms of Use.