Privacy Policy
Bo\/ada Story Builder
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Bo/ada Story Builder stores your story titles, optional author name, genres, cover choices, scenes, writing, notes, fictional character details, group participant names and turn progress on your device. Preferences are stored locally. The app automatically creates a random installation secret in the iOS Keychain. When connected, it sends stories and their modification timestamps to our backend using that secret. The server stores story content and a hash of the secret, along with deletion markers needed to prevent deleted stories returning during synchronization. Group turn progress and preferences stay on the device, although participant names included in scene titles become part of synchronized stories. The service receives ordinary network requests; Railway infrastructure may process IP addresses, request timing, network and operational metadata. We do not request an account, email address, location, contacts, photos or payment details.
How we use information
Local storage enables offline writing, editing, organization and export. The installation secret limits server access to this installation's private namespace. Server storage provides installation-scoped synchronization and backup while the secret remains available; it does not provide sign-in, cross-device account transfer or recovery after losing the secret. Modification times and deletion markers resolve conflicts and prevent stale copies from restoring deleted content. Network and operational information supports serving requests, reliability and security. The app does not use advertising or analytics SDKs.
Service providers and sharing
The application backend and its persistent storage are hosted by Railway, which processes content and infrastructure metadata to run the service. The application has no third-party analytics, advertising, email delivery or external content-generation integration. The backend does not send story content to another external API. If you choose Copy, Save PDF or the iOS share menu, the selected content goes to your clipboard, chosen file location or chosen recipient/application under your control; those destinations may have their own privacy practices. Authorized service administration can access server-stored content; this is not end-to-end encrypted storage.
Data retention
Local stories remain until you delete them or remove the app's local data. Exported files and clipboard copies are managed separately by you and their destination apps. The Keychain secret can survive removal of the app, but no recovery is promised. Server stories remain until replaced by a newer version or deleted through the app. Per-story deletion markers remain until all installation data is deleted, to prevent stale synchronization. The service has no scheduled content-expiry policy. Railway infrastructure logs or independently managed backups may remain according to provider configuration and operations; we do not assert a fixed retention period for those systems.
Deleting your information
Delete a story from Stories to remove its current local and server copy. Settings offers Delete all stories and server data, which clears local stories and group progress and sends an authorized deletion request for the installation's server records and deletion markers. When offline, server deletion is queued until the app next connects; keep the app installed and reconnect to complete it. The SQLite implementation uses secure deletion and checkpoints its journal, but deletion of active records does not immediately erase independently managed provider backups. Uninstalling alone does not send a server deletion request. Exported files and copies shared elsewhere must be deleted separately at their destinations.
Permissions and your choices
The app does not request location, camera, microphone, contacts, photo library or notification permissions. Shake detection, optional system sounds and haptics support idea dice and can be disabled in Settings. You choose the location and recipients through system file and sharing controls; cancel those controls to withdraw an export. Network synchronization operates when a connection is available. You may use the writing features offline and delete server content through Settings when connected.
Your privacy rights
You can inspect, edit, copy and export your stories in the app, and delete individual stories or all installation data. Depending on applicable law, you may also request access, correction, deletion, restriction, objection or portability by contacting rufuscrowther@icloud.com. This address is a public privacy contact, not an account identifier or an in-app email delivery service. Because there are no accounts and the service does not collect an identity directory, we may need enough information to verify a request without exposing another installation's data. Do not send your installation secret or private story text by email. You may raise a concern with your relevant data protection authority where applicable.
Security
The app uses HTTPS for deployed network communication, cryptographically random installation credentials, iOS Keychain storage and server-side authorization on every private route. The server hashes installation credentials and separates records by that hash and story identifier. Local documents use atomic writes and iOS file protection. The backend validates document sizes and shapes and does not log installation headers or story bodies. Public home and privacy pages require no login or cookies. Content is stored as readable text in the service database, and these measures do not guarantee absolute security. Protect access to your device and exported files.
Children’s privacy
Bo/ada Story Builder is intended for teenagers and adults interested in creative writing and is not directed to children under 13. There are no accounts, advertising or social profiles. Avoid entering sensitive personal information about yourself or others into stories, character notes or participant names. A parent or guardian with privacy concerns may contact rufuscrowther@icloud.com; requests will be handled with appropriate verification and the limits of installation-scoped identification.
Changes to this policy
We may update this policy when the app's processing, features or hosting practices change. The current policy is available from Settings and this public privacy page. Its effective date identifies the version in use. Material changes will be reflected in this policy and, where appropriate, in the app's release information. Contact rufuscrowther@icloud.com for privacy questions.