Privacy Policy
1. About this policy
This draft describes the current ReignBit iOS app: a workspace for recording musical ideas, organizing notes and chords, planning arrangements, and tracking production progress.
Operator: awaiting owner confirmation.
Privacy contact: awaiting a confirmed working contact.
2. Information used by the app
- Your musical content: audio recordings, titles, text, chords, tags, notes, tempo and musical key. Recordings also have a duration and waveform values for playback and display.
- Track plans: genres, moods, creative intent, arrangement sections, instrument choices, reference titles and artists, linked ideas, checklists, production stages and dates.
- Local profile and preferences: nickname, selected built-in avatar, default tempo, blind sift setting, reminder preferences, bookmarked prompts and onboarding completion.
- Progress: statistics and streaks calculated from your saved ideas and tracks.
These details support the features you use. The current app does not require a ReignBit account.
3. Storage and backups
Ideas and track plans are stored in the app’s local database. Audio recordings are saved as files in the app’s Documents folder. Profile details and preferences are stored locally in app settings. A separate local record stores whether you have agreed to this policy. The current implementation has no account-based sync or app backend integration.
Depending on your device settings, system backups may include app data. Backups are separate from ReignBit’s local storage and are managed through your device and backup provider. Clearing data in ReignBit does not manage or erase existing backups.
4. Microphone and other permissions
ReignBit requests microphone access when you start recording an idea. You can decline or change access in iOS Settings. Text and chord capture do not require microphone access. Agreeing to this policy does not grant microphone permission.
The current app has no camera, photo library, contacts or location feature. Its reminder controls save preferences; notification scheduling and push notification registration are not implemented in the reviewed version.
5. Third-party services and transfers
The reviewed app contains no integrated advertising, analytics, third-party crash reporting, payment or AI service, and no code that uploads your creative content to an app server. Apple’s operating-system services, including backups you enable, operate separately.
Any support correspondence and processing outside the app must be confirmed by the operator before this draft is published.
6. This policy page
This HTML document contains its own styles and script. It does not load external fonts, images or analytics, set cookies, use browser storage, or upload files. In the app, the Agree button can send the policy version and agreement action to the native app.
Website hosting is not configured. Before publishing an online copy, the operator must identify the host and describe any request logs, cookies or additional services used by that host.
7. Retention and deletion
The current app does not apply a scheduled expiry to saved creative content. Archiving an idea keeps it in the library; it is not deletion.
Settings → Clear data is designed to remove ideas, recordings, tracks, arrangement sections and references, and reset the nickname, avatar and bookmarked prompts. It retains your policy agreement, onboarding completion and app preferences, including default tempo, blind sift and reminder settings. This action does not reset iOS microphone permission.
Existing system backups are managed separately. The current deletion implementation does not report storage errors, so this draft does not promise guaranteed erasure in every failure condition.
8. Your choices and questions
You can edit your content, delete it using the app’s controls and manage microphone access in iOS Settings. A working contact for privacy questions and requests must be added before publication.
Audience and regions: the product is designed for musicians and songwriters. Launch regions and any applicable age-specific terms still require operator confirmation.
9. Changes
This policy should be updated when the app’s data practices change. The operator will provide the effective date with the published revision.
Agree acknowledges the policy in the app. In a regular browser, the button takes you to the full text and does not save app consent. This draft is for review and integration testing.