Privacy policy

The short version

Campfire Chords keeps your songs on your phone. There is no account. Your library, set lists and play history stay on the device and in your own iCloud or Google Drive, which we cannot read.

Five things use the internet. One happens only when you ask: turning a web page into a chord sheet, which sends the text of that page to be cleaned up and does not store it. The others are syncing your library with your own iCloud or Google Drive; crash and usage reports, which describe the app and never your songs; the Pro purchase; and an anonymous identity with an integrity check, which exist so the free imports can be counted. All five are described in full below.

Who this is from

Campfire Chords is published by Baan Software PTE. LTD.. Questions about this policy, or about anything in the app, go to campfirechords@baansoftware.com.

What the app stores on your device

All of it stays in the app's own storage on your phone:

• Your songs: title, artist, language, the chords and words as a chord sheet, the version as it was imported, the address of the page it came from, and your settings for it, such as transpose and scroll speed.
• Your set lists and the order of the songs in them.
• Your play history: which song was played, and when.
• Small settings: theme, text size, whether the screen stays on, and a count of the free imports you have left.

It goes nowhere else except your own cloud storage: iCloud on iPhone and iPad, and Google Drive on Android once you turn sync on in Settings. There it is kept in a folder only this app can use, so your songs are on every device you sign in to. We have no copy of it and cannot read it. Sample songs stay on the device they were added to.

The tuner

In its Auto mode the tuner listens through the microphone, only while it is open and only after you allow it. What it hears is measured on your phone to find the note, and is never recorded, stored or sent anywhere. Tuning by ear plays notes and does not use the microphone.

Importing a page

Web pages you open in the app's browser load on your phone, the way they would in any browser; the sites you visit see an ordinary visit from your phone, under their own privacy policies.

When you tap This is it, the app reads the text of that page, or only the part you selected, and sends it to our server (a Google Cloud Function) together with the page's address and title, the song title and artist you searched for, the language of the title, and the app's version. Our server passes the text and those hints to Google's Gemini API, checks the result against the page, and returns the chord sheet to your phone. Google's handling of the request is governed by Google's privacy policy and the Gemini API terms; ours is this page.

We do not store the page text or the result. Our server's logs record, for each import, a one-way hash of your anonymous identity, the site's host name, the app version, which model was used and how many tokens it took, how long it took and whether it worked. They never contain the page text, the lyrics, the chords or the full address.

An anonymous identity, and the import allowance

There is no account. The first time the app starts, it signs in to Firebase Authentication anonymously, which gives the phone a random identifier that is not tied to your name, email or phone number. It exists so that imports can be counted: our server keeps a record against that identifier of how many imports it has made, in total, today and this month, in Google Cloud Firestore. That record holds numbers and dates, not songs.

Each import also carries a token from Firebase App Check, which uses Apple's App Attest or Google Play Integrity to confirm the request comes from the real app. That is what keeps the service from being used by anyone as a free proxy.

The Pro purchase

Pro is bought through Apple or Google. The app uses RevenueCat to check whether a purchase exists, under the same anonymous identifier, and our server reads that answer to decide whether an import counts against the free allowance. We never see a card number, a name or an email address.

What we collect about how the app is used

Release builds of the app send crash reports and usage statistics to Google Firebase (Firebase Crashlytics and Google Analytics for Firebase), so that we can see which parts of the app are used and what is broken. There is no advertising SDK and no advertising identifier.

The app reports which screen is open by its pattern: the play screen arrives as /play/:songId, never as the song. Alongside that, Firebase records the ordinary things an analytics service records: an app-generated install identifier, the start of a session, your device model, operating system version, country and language. A crash report carries the state of the app at the moment it failed — which line of our code it was running — and not the contents of your songbook.

The following are never sent to Firebase:

• Any song title, artist, lyric or chord.
• Anything you type into search, or into the browser's address bar.
• The address of any page you visit or import.
• Your set lists or your play history.

Google's handling of all of it is governed by Google's privacy policy and the Firebase privacy and security terms. Firebase's default retention applies; we set nothing longer.

There is no switch for this in the app. What is reported describes the app, not you or your songs. If you would rather send nothing at all, both Apple and Google let you limit what apps may report from your phone's own settings, and deleting the app ends it completely.

The app stores

Downloading the app, and buying Pro, are transactions between you and Apple or Google. The stores give developers aggregate statistics — how many people installed an app in a country in a week — which cannot identify anyone. If you have turned on sharing crash and usage data with developers in your phone's own settings, the store may pass on crash reports of its own, separately from ours.

Children

The app has no chat, no social features and nothing public. It does contain a web browser, and the pages it opens are the open web.

Your rights over your data

Your songs are data on a device you own, and deleting the app removes them. What we hold is the import count against your anonymous identifier, the logs described above, and what Firebase and RevenueCat hold as described. To ask about any of it, or to have the import record removed, write to campfirechords@baansoftware.com.

This site

This website loads the Google Ads tag (gtag.js) on every page, so that we can see which of our ads bring people here and to the app stores. Google may set cookies and receive your IP address, browser details and the pages you visit, as described in how Google uses information from sites that use its services. The only other script is a small one on the page that opens a shared song, which works in your browser and sends nothing anywhere.

Changes

If this policy changes, the date at the top of the page changes with it, and a change that affects what leaves your phone will be described in the app's release notes rather than left to be discovered here.