Firecracker Privacy Policy
1. Operator and scope
This policy explains how the individual doing business as LifeSignExperiments (the “operator”) handles information in the Firecracker songwriting app, on its official website, and when you contact support.
2. Information we handle and why
- Account information. We use your account ID, sign-in email address, and identifiers from your chosen sign-in method to register, authenticate, and protect your account. We send a verification code when you sign in by email. If you sign in with Apple or Google, we receive the information needed to authenticate you from the provider you choose. Features you use without registering may use an anonymous identifier as needed.
- Projects and app settings. Your device stores projects such as chord progressions, recovery drafts, and settings such as appearance, language, and creation reminders. Recovery drafts and reminders are handled on your device. When you use project sync, we handle the names, progressions and playing settings, creation and modification times, owner identifiers, and update and deletion records of saved projects on our servers so you can store and retrieve them under your account. You can choose where to share a project image using your device’s share sheet.
- App Store purchases. We use product and transaction information, purchase or subscription status, and purchaser identifiers to verify purchases, grant and restore access, prevent abuse, and measure purchase activity. We use an anonymous purchasing ID when you are signed out. After sign-in, purchase information may be linked to your account ID. Apple processes your payment details.
- Retailer licenses. During web registration, we use the code you received at purchase and your account ID to link the license to your account. In the app, we use the license record linked to the account you sign in with to verify Pro access. The license register holds a verification value for the code, retailer and issuance information, the link to your account, and registration, revocation, and recovery records. We use these records to verify access, prevent misuse, and respond to requests.
- Support. For email inquiries, we use your email address, message, and attachments to reply and investigate issues. The in-app feedback form handles what you enter, optional categories, reply addresses and images, and any app version, build number, OS version, device type, and language details you choose to submit. Associated account and submission IDs help protect and verify submissions.
- Crash diagnostics. We use crash information, error categories, information needed for diagnosis, app and OS versions, and device model to investigate issues. Diagnostics are on by default. Turning them off in Settings stops new submissions. See “Retention and deletion” for data already sent. Usage-event analytics are off in the first public release.
- Public content and website. When you download the chord progression and playing examples catalog or updates, or visit our official website, delivery providers may handle your IP address, requested resources, and ordinary request information as needed for delivery, troubleshooting, and security.
3. Service providers
We use Supabase for authentication, project sync, feedback intake, license management, and public content delivery. The production database’s primary region is Tokyo. Resend delivers verification codes and stores email and delivery records in the United States. Apple and Google process sign-ins when you choose their services. Apple and RevenueCat process App Store purchases and verify access. We use Sentry’s US region for diagnostics and Dynadot’s email service for support messages. Website hosting and delivery providers process the information needed to serve the site.
Service providers handle information as needed to provide and protect the service. We follow applicable law when information is handled outside Japan. Contact us at the address below for details about providers, processing locations, and safeguards.
4. Retention and deletion
We retain account information and cloud projects as long as needed to provide the account and sync features. You can start account deletion from the account screen in Settings. Deletion covers the account’s cloud projects, authentication records, and associated feedback, as well as that account’s projects, recovery data, and authentication information on the device used to request deletion. Use the settings on other devices or in your operating system to manage local copies and device backups.
The message, reply address, app and device details, and attachments submitted through the in-app feedback form are generally scheduled for deletion 180 days after acceptance. We keep support email as long as needed to handle and follow up on the request. Diagnostic data already received follows the retention and deletion settings in Sentry.
Apple and RevenueCat purchase records are kept after account deletion as needed to verify or restore purchases. When you delete an account, we unlink retailer licenses and keep records needed for recovery, revocation, and fraud prevention. Backup copies may remain until they expire so we can recover from failures. Records that the law requires us to keep are retained under those requirements.
5. Safeguards and privacy requests
We use safeguards appropriate to the information we handle, including access restrictions and protection for data in transit. To request notice of the purposes for which we use your retained personal data, or to request access, correction, deletion, or suspension of use, email hello@firecracker.music. You can also use this address for privacy questions or complaints. We will explain the process and any identity checks and respond in accordance with applicable law.
Use the same contact address to request the operator’s legal name and address or more information about our safeguards. We will provide this information promptly upon request.
If our data practices change in a significant way, we will announce the changes and their effective date in the app or on the official website. Where the law requires consent, we will obtain it before applying the changes.
The planned effective date is December 1, 2026.