Policy

Privacy Policy

Effective date: September 5, 2026

This Privacy Policy applies to The Original Songwriting Adventurer.

Summary

The Original Songwriting Adventurer keeps ordinary songwriting content and activity on your device unless you choose to sync, share, export, or contact support. The developer can access content you publish as a shared Writer Challenge and information you send to support. The app has no developer-run account system, advertising network, or third-party analytics system for your writing activity.

Data We Do Not Collect for the Developer

The developer does not intentionally collect or store, on developer-controlled servers:

• your private lyrics, notes, Treasure Maps, Writing Plans, prompts, drafts, or exported creative work, except content you choose to share in challenges or send to support
• account profiles or login credentials for an in-app account system
• advertising identifiers for tracking or ad targeting
• developer-hosted analytics about your writing activity inside the app

Local Device Storage

The app may store your writing data, Writing Plans, reminders, settings, and progress locally on your device so the app can function properly between sessions.

iCloud and Apple-Managed Services

If you choose to use features that rely on Apple-managed services, such as iCloud sync, your data may be stored, synced, or transmitted by Apple under Apple's own privacy practices and terms. The developer does not receive your private sync data merely because you use iCloud sync. Shared Writer Challenges use a separate public database, described below.

To keep iCloud sync reliable, the Title Bank keeps the 2,000 most recent saved titles, concepts, lines, and ideas for sync. Writing Plans may also sync plan titles, planned days, completion status, reminder timing, and active-plan status through Apple-managed iCloud storage. When the Title Bank library approaches its limit, the app shows a warning; if the limit is exceeded, older saved lines may be trimmed from the synced library while the most recent 2,000 are kept.

Shared Writer Challenges

If you create or join a shared Writer Challenge, the app may use Apple CloudKit to store or retrieve the challenge code and the limited challenge details needed for that shared challenge to work. Depending on the challenge type and the choices you enter, those details may include user-authored phrases, selected words, keeper fragments, a nickname, and an expiry date.

Shared challenges use the public CloudKit database. People with the code can retrieve the challenge, and the developer can access its content and CloudKit creator record identifier through administration tools for support and moderation. A nickname or identifiable content can link a challenge to you. Do not include private, confidential, sensitive, or third-party-infringing material in shared challenge content.

In-App Purchases

Subscription billing, free trials, renewals, and purchase restoration are processed by Apple through the App Store. The developer does not receive your full payment card or payment credential details.

Support Contact

If you contact the developer directly, including by email or through the in-app Contact & Feedback form, the developer may receive the information you choose to provide in that message, such as your name, email address, message, song title, and the contents of your request. The app may also include basic support details in the email body, such as app version, build number, subscription or access status, notification status, purchase status, iCloud sync status, last sync warning, and recent challenge status. If you enable optional session diagnostics, the email also includes category counts and timing measurements collected during the current app run, without automatically including lyrics, titles or prompts. Apple launch and hang measurements may describe earlier runs. Support information is linked to the name and email address you send with it and is used to respond to you and handle the support issue. Diagnostics stay on-device unless you choose to send them. None of this information is used for cross-app tracking or advertising.

Retention and Deletion

Because the developer does not maintain a developer-hosted user database for in-app writing data, there is generally no developer-side account record to delete for your local songwriting content.

• delete the app from your device to remove local app data stored on that device
• manage or remove synced content through your Apple device and iCloud settings if you choose to use iCloud
• Challenge codes normally expire after seven days; expiry prevents joining and is not a promise that the stored record has been deleted. To request deletion of a shared challenge or information previously sent to support, contact support and identify the challenge code or support conversation. Copies already received or exported by other people are outside the app's control.

Consent and User Choice

By choosing to use optional Apple-managed services or by contacting support directly, you decide whether to share information through those channels.

Third-Party Services

Apple and any third-party websites, tools, or services you intentionally open from the app operate under their own privacy policies and terms.

Contact

If you have questions about this Privacy Policy, contact support through the protected support form.