Privacy Policy

By downloading and using Campfire, these terms will automatically apply to you; therefore, you should make sure that you read them carefully.

This application is provided to you by Péter Pandula at no cost and is intended for use as is.

Last updated: 27 October 2026. This version covers Campfire 4.0 and later; cover art and deleting the whole library from the settings arrived in Campfire 4.5, syncing the chosen chord shapes and the per-song transposition, capo, and tempo in Campfire 4.7, and the tuner, which uses the microphone, and syncing tag colors and the metronome accents of each song in Campfire 4.7.1, and the online song details lookup, pasting songs, and sharing them to the app in Campfire 4.9, and song and setlist links in Campfire 5.0, and the app's log in Campfire 5.0.1.

General overview

This page is used to inform you regarding my policies with the collection, use, and disclosure of personal information if anyone decided to use my service.

Campfire is an app for viewing and editing song lyrics and chords that works offline. Your songs and setlists are ordinary ChordPro text files kept in the app's own storage on your device, and on the web in your browser's private storage for the site. There is no Campfire account and there is no server of mine involved anywhere: I never receive your songs, your settings, or anything else about how you use the app. The only times Campfire connects to the internet are for cloud sync and the links it shares, for opening a shared link, for cover art, and for the song details lookup, all described below. The tuner uses your microphone, but what it hears never leaves your device, also described below. Campfire also keeps a log of what it did on your device, which reaches me only if you send it to me yourself, as described in The app's log.

Campfire contains no advertising, no analytics, and no tracking of any kind.

Information collection and use

Campfire does not have any data collection solution integrated; as a result, I am not collecting any personally identifiable information on purpose. However, keep in mind that some data collection mechanisms are beyond my control. For instance, just by downloading the application from the Google Play Store, you are automatically sharing some limited usage data and crash logs with me, the developer, as well as Google. You agreed to this when accepting the Play Services license agreement, over which I have no control whatsoever.

Cloud sync

Campfire can keep your library the same on several of your own devices by storing it in a cloud folder that belongs to you. This is switched off until you turn it on. Until you connect an account in the app's settings, sync makes no network requests at all, and if you never connect one, nothing in this section applies to you.

Sync currently supports Dropbox. When you connect it:

• Your files go to your own Dropbox, not to me. The songs and setlists are transferred directly between your device and Dropbox. I operate no server, and no copy of your library ever reaches me.
• Campfire can only see its own folder. The app requests Dropbox's "app folder" permission, which limits its access to a single folder called Apps/Campfire Sync that is created for it. The rest of your Dropbox is invisible to the app.
• Only your library, and how you play it, is synced. That means your song files and your setlist files, and, in a preferences.json file next to them in the same folder, the transposition, capo, tempo, and metronome accents you set for the songs, the chord shapes you chose for each instrument and tuning, and the colors of your tags. Your other app settings, such as your chosen theme, language, and text size, are never uploaded by sync and stay on the device where you set them (your device's own backup can still carry them to a new device, see Device backup below).
• What Campfire reads about your account. After you connect, the app asks Dropbox for the display name and email address of the account, purely so that the settings screen can show you which account your library is going to, and it keeps the account's Dropbox ID, so that it still recognizes the account after you change its name or email address. These are kept on your device and are never sent anywhere else.
• How signing in works. Authorization uses the standard OAuth 2.0 flow with PKCE, on Dropbox's own consent page opened in your browser. Your Dropbox password is never typed into Campfire and never passes through it. The resulting access and refresh tokens are stored in the app's private storage on your device only (on Android encrypted with a key held by the system, on iOS and iPadOS in the system Keychain), and are never sent anywhere except to Dropbox.
• Disconnecting. Choosing "Disconnect" in the settings asks Dropbox to revoke the token and deletes it from your device. Your files are left untouched, both on the device and in your Dropbox, and so are your shared links, which keep working: stop sharing them first if you want them gone. You can also remove Campfire's access at any time from the connected applications page of your Dropbox account.

Anything stored in your Dropbox is subject to Dropbox's own privacy policy and terms, which are between you and Dropbox. Should Campfire gain support for another cloud service in the future, the same principles will apply to it and this page will be updated to name it.

Song and setlist links

A song or a setlist can be shared as a link that anyone can open. Making a link needs cloud sync with Dropbox, described above; opening one needs no account.

• Sharing puts a public copy in your own Dropbox. When you create a link, Campfire saves the song, or the setlist with its songs, as a zip file in a shared folder inside Apps/Campfire Sync, and asks Dropbox for a public link to it. Anyone who has the link can download that file. While sync is connected, Campfire keeps the file up to date as you change the song or setlist, until you stop sharing it. For this, the app also asks Dropbox for permission to make and list shared links, which covers its own folder only. The list of what you share, with each item's title, file name, link, and the day it was shared, is kept in a shared-links.json file in the same folder, so that every device connected to it shows the same list.
• Stopping. Stop sharing, on the Share screen or in Settings → Sharing, deletes the file from your Dropbox, and so does deleting the song or setlist in Campfire. The link then stops working for everyone. Copies people already imported are theirs, and Campfire cannot reach them.
• Opening a link downloads that file from Dropbox. The app downloads it directly from Dropbox, shows you what it holds, and writes nothing until you import it. Dropbox sees an ordinary download from your device's internet address, and nothing is sent to me.
• The link's page sends nothing. A link leads to a page on this website, which reads the link in your browser. The part of the link that names the file comes after a #, which browsers never send to a server, so neither this website nor a messenger's link preview sees it. The page fetches nothing itself; its buttons open Campfire, its store, the web app, or the file's download.
• Installing from a link. On Android, when Campfire is installed from Google Play through the page's button, Google Play hands the link to the app on its first launch. On iOS and iPadOS, the page's Get Campfire button copies the link; on its first launch, Campfire checks whether the clipboard holds a web address, without reading it, and reads it only if you tap Open it. Anything that is not a Campfire link is ignored.

Microphone and the tuner

Campfire has a tuner that listens to your instrument through the microphone. Nothing it hears is recorded, kept, or sent anywhere.

• Only when you ask. The app never asks for the microphone at launch. It asks when you tap to open the tuner (the Tuner tab, or a song’s tuner button or menu entry), or when you tap Use the microphone on a tuner that was shown without a tap, such as one the app reopens where you left it. Android, iOS, iPadOS, macOS, and your browser ask for your permission first, and you can withdraw it at any time in their settings. On a computer, where the app cannot tell whether it has been allowed, it remembers that you tapped the button once, and from then on opens the microphone whenever the tuner is shown.
• Only while the tuner is on screen. The microphone is open only while the Tuner tab or the tuner over a song is shown and the app is in front. It is closed as soon as you leave the tuner, switch to another app, or lock the screen, so your device's recording indicator is lit exactly while the tuner listens.
• Analyzed on your device, then discarded. The sound is processed on your device as it arrives, only to find the pitch of the note being played, and is then thrown away. No audio, and nothing derived from it, is saved, synced, included in a backup, or sent to me or to anyone else.
• Turning it off. The "Tuner" switch in the app's settings removes the tuner, and with it every way the app could ask for the microphone.

Cover art

A song can name an album cover to show next to it, as the web address of an image written into the song's own file. The address is something you or whoever wrote the song chose, and Campfire has no say in which website it points to.

• Showing a cover. The first time a song with a cover is shown, the app downloads the image from that address and keeps a copy on your device, so it is not downloaded again. The website serving the image sees an ordinary request for it from your device's internet address, as it would from a browser. Copies no song names any more are deleted by the app, and they are never synced or included in your device's backup. You can delete all of them at any time by tapping Cover art cache under Library in the app's settings.
• Searching for a cover. Only when you open the cover search for a song, the artist, album, and title in its search fields are sent to MusicBrainz and to Apple's iTunes Search API, and the thumbnails of the records they find are downloaded from the Cover Art Archive and from Apple. Nothing else about you or your library is sent, and there is no account with either. Those requests are subject to those services' own privacy policies.
• Typing an address. If you enter the address of an image yourself, it is downloaded from that address to show you a preview.
• Turning it off. The "Cover art" switch in the app's settings turns all of this off: no cover is downloaded or shown and the search is not offered.

Song details lookup

While you edit a song’s details, Campfire can look up its artist, album, year, and songwriters online.

• Only when you ask. Nothing is sent until you open Find song details online for a song. Then the title, artist, and album in its search fields are sent to MusicBrainz and to Apple's iTunes Search API, and MusicBrainz is also asked for the songwriters of a recording it found. Nothing else about you or your library is sent, and there is no account with either. Those requests are subject to those services' own privacy policies.
• Nothing is kept, and nothing is written until you save. What the lookup finds only fills in the form. The song’s file changes only when you tap Save, and the results are not stored.
• Turning it off. The "Online song details" switch in the app's settings removes the lookup.

Pasting and sharing songs

• The clipboard is read only when you paste. Campfire reads it when you tap Paste from clipboard or press Ctrl+V (⌘V on a Mac), or Open it on the first launch after installing from a link on iOS and iPadOS (see Song and setlist links), never on its own. On iOS and iPadOS, and in some browsers, the system asks you first.
• Shared and dropped songs stay on your device. Text and files you share to Campfire from another app on Android, iOS, or iPadOS, or drop onto it, are read and converted on your device. A web address among them is never opened. On iOS and iPadOS, a share waits in a folder the app and its share extension have in common until Campfire has taken it, and is then deleted.
• Nothing is saved until you save it. A pasted or shared song opens in the editor and becomes a file in your library only when you tap Save. Until then, the editor keeps the unsaved text on your device only, so that it is not lost if the app is closed.

The app's log

Campfire keeps a log of what it did lately, so that when something goes wrong, you can send it to me and I can find out why. It is not analytics: it stays on your device, nothing sends it anywhere on its own, and it reaches me only if you choose to send it.

• What it holds. When the app started, its version, and which kind of device it runs on; which screens and dialogs you opened, by kind only (for example "song details", never the song itself); what you did, in a few words, such as saving a song, adding songs to a setlist, changing a setting (its name, not what you set it to), opening a search (never what you typed), starting the metronome or the tuner, importing, exporting, sharing, and how each sync went, in counts; and the messages the app writes about what it did and about errors, which can name the files of your songs and setlists. Every line carries the time it was written. It never holds the text of your songs, your settings, your Dropbox account, or what the tuner hears.
• Where it is kept. On your device only, in the app's own storage, never synced. It is limited to about half a megabyte, and older lines are dropped as new ones are written.
• Sending it is up to you. In the settings, the About tab's log row first shows what the log holds, then, if you continue, attaches it to a new mail to me on Android, and on iOS and iPadOS where the Mail app has an account. You can read the mail, and the log, before you send it, or not send it at all. Elsewhere, Campfire offers to share or save the file, and you send it yourself. On a computer, your user name in the folder paths the log mentions is replaced before it leaves the app.
• After a crash. On Android, iOS, iPadOS, and a computer, if the app stopped because of an error, it asks the next time you open it whether you would like to send me the log, once. Choosing Not now sends nothing.
• If you send it to me, I use it only to find and fix the problem you ran into.

Device backup

Android phones and tablets, iPhones, and iPads can back up the data of the apps on them and move it to a new device. If you have this switched on, your Campfire library and your app settings are part of it: on Android in your Google backup or a direct transfer to a new phone, on iOS and iPadOS in your iCloud backup or a transfer from your old device. That copy is made by the operating system according to your device's backup settings, and a backup is stored in your own Google or Apple account under Google's or Apple's privacy policy. Campfire makes no request for it, and I never receive or see it. You can switch it off in your device's settings. The cover images, the app's log, any unsaved text in the editor, and shares waiting to be taken from the iOS share extension are left out of it.

If you use cloud sync, the Dropbox connection and the record of the last sync are left out of the backup on every device, so a restored or new phone or tablet starts disconnected and you sign in to Dropbox again.

On a computer, the library and the app's log are kept in Campfire's folder among your user account's application data, and any backup you make of the computer, such as Time Machine or File History, may include them. On the web, the library and the log live in your browser's storage for the site. They are not part of any backup, and clearing the site's data removes them.

Deleting your data

I hold no copy of anything you keep in Campfire, so there is nothing for me to delete and no request to send: every copy is in a place you control, and you can remove it yourself at any time.

• Your whole library, from the app: open the settings, go to the Library tab, under On this device tap the row that shows how many songs and setlists you have, type DELETE, and confirm. Every song and setlist is deleted from the device. If Dropbox sync is connected, this also deletes them from your Apps/Campfire Sync folder and from every other device synced with it; the dialog says so before you confirm. To delete them from this device only, choose "Disconnect" first. The copies of the cover images are deleted from the same screen, with Cover art cache. Deleting the library also stops sharing every song and setlist, so all your links stop working.
• Your shared links, from the app: in the settings, the Sharing tab's Stop sharing everything deletes every shared copy from your Dropbox, and every link stops working. Your library stays as it is.
• Everything on your device: uninstall the app, which removes the library, the settings, the cover images, the app's log, and the Dropbox connection from the device. On the web, clearing the site's data in your browser does the same.
• In your Dropbox, if you used sync: deleting your library while connected, as above, removes your songs and setlists from the Apps/Campfire Sync folder, leaving only the preferences.json file with the chord shapes and tag colors you chose and, if you ever shared something, the shared-links.json list, then empty. To remove everything, choose "Disconnect" in the app's settings, then delete the Apps/Campfire Sync folder in Dropbox. You can also remove Campfire's access from the connected applications page of your Dropbox account.
• In your device's backup: delete the backup, or switch off backup for the app, in your device's settings or your Google or iCloud account.

If anything is unclear, contact me and I will help.

This website

This website sets no cookies, and it contains no advertising, no analytics, and no tracking either.

• Your language. When you pick a language from the menu at the top of a page, your browser remembers it, so the site opens in that language the next time. The choice is kept in your browser's storage for the site, is never sent anywhere, and is forgotten when you clear the site's data. Until you pick one, the site follows your browser's language.
• Hosting. The website is hosted by GitHub Pages. Like any web server, it sees your device's internet address when your browser loads a page, and GitHub logs it for security purposes, under the GitHub General Privacy Statement. I receive none of it.

Children’s privacy

These services do not address anyone under the age of 13. I do not knowingly collect personally identifiable information from children under 13. If you are a parent or guardian and you are aware that your child has provided me with personal information, please contact me so that I will be able to do necessary actions.

Changes to this Privacy Policy

I may update my Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. I will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted.

Contact me

If you have any questions or suggestions about my Privacy Policy, do not hesitate to contact me.