Chronicle Engines Privacy Policy

Effective date: July 14, 2026

Chronicle Engines is an interactive fiction app by Jorge Aguirre. The app does not require account creation and does not sell personal information.

Information Stored On Your Device

Chronicle Engines stores story progress, saved cases, journal entries, pending choices awaiting retry, settings, theme choices, privacy consent, and optional provider credentials on your device. Story saves and journal entries use app-managed recovery backups. If a story-data file becomes unreadable, the app may keep the unreadable payload in an on-device quarantine folder so it is not silently overwritten. Provider credentials you enter are stored in the iOS Keychain.

The app can also synchronize saved cases and journal entries through your private iCloud database when that feature is enabled and iCloud is available.

Deleting Story Data

The Delete All Story Data control removes local save slots, journal entries, pending turns, story statistics and achievements, app-managed story-data recovery backups and quarantined payloads, and story-related network caches. It also requests deletion of Chronicle Engines story records from the app's private iCloud sync zone. If iCloud is temporarily unavailable, that cloud deletion request remains pending and is completed before the app pulls story records again.

Deleting story data does not delete provider credentials unless you explicitly choose the separate option to include credentials. When selected, Chronicle Engines also removes bring-your-own-provider keys and the saved hosted-relay transaction credential. Apple subscription records remain managed by Apple.

Optional Online Story And Voice Features

Chronicle Engines can generate stories locally on supported devices. If you choose online story generation, the in-app consent screen identifies the route that is active at that time:

• Chronicle Cloud: story context, protagonist details you type, selected actions, generation settings, and related request details are sent to the Chronicle Cloud relay, which currently routes story generation to DeepSeek.
• Bring Your Own Keys: the same story-generation content is sent directly from your device to the provider you selected: DeepSeek, OpenAI, Anthropic, or Google.
• On-device story generation: story-generation content stays on the device.

If you use voice narration, generated story text and voice settings are sent to ElevenLabs, either through Chronicle Cloud or directly with your ElevenLabs key depending on the active credential route. Narration text is sent only when narration is used.

For Chronicle Cloud subscriptions, the app may send a device-generated client identifier and an App Store StoreKit transaction identifier to the Chronicle Cloud relay so it can verify subscription entitlement, apply usage limits, and route the request to the configured story or voice provider. Apple handles payment processing; Chronicle Engines does not receive your credit card or Apple Account password.

Online story and voice providers may process submitted text to return generated story or narration output. Chronicle Engines uses these services only to provide the feature you requested.

Analytics, Advertising, And Tracking

Chronicle Engines does not use third-party advertising SDKs and does not track you across apps or websites. The app may create ordinary operational records needed to keep the online relay working, debug errors, prevent abuse, and verify subscription access.

Support Contact

If you email support, the information you provide is used to respond to your request.

Children

Chronicle Engines is not directed to children under 13.

Changes

This policy may be updated when Chronicle Engines adds or changes features. Material changes will be reflected in the policy date.

Contact

For privacy questions or deletion requests, contact Jorge Aguirre at jaguirre2192@gmail.com.