Wired × Head

· software

Backstage – Privacy Policy

Topic
software

Effective date: 30 October 2026

1. Controller and contact

1.1 This Privacy Policy describes how personal data is processed when the software application “Backstage” for macOS, iOS and iPadOS (the “Software”) is used.

1.2 The Software is provided by Christoph Landsky, Scheidemannstr. 14, 51067 Köln, Germany, email: christoph.landsky@googlemail.com (the “Licensor”). See also the legal notice.

2. Summary

2.1 The Software doesn’t require an account and doesn’t use servers operated by the Licensor. It contains no analytics, advertising or tracking functions.

2.2 Data is processed on the user’s devices and in storage locations and services that the user selects and connects (“Third-Party Services”). The Licensor doesn’t receive or process any personal data processed with the Software.

2.3 Personal data only reaches the Licensor if a user contacts the Licensor, for example by email. Such data is processed solely to handle the request, on the basis of Art. 6(1)(f) GDPR, and is deleted once it’s no longer needed for that purpose.

3. Data stored on the user’s device

3.1 The Software stores the data entered by the user on the user’s device. This includes bands and band members, songs and lyrics, releases, productions and tasks, gigs and associated contacts, locations, financial records, documents, and settings.

3.2 Access credentials (a Discord bot token, a Discord webhook URL and a Google authorisation token) are stored in the operating system’s keychain.

3.3 This data may include personal data of third parties, such as band members or gig contacts. The user is responsible for processing such data lawfully.

4. Shared band folder

4.1 The user may select a band folder, for example in iCloud Drive, Google Drive for desktop or Dropbox. The Software then synchronises its data with that folder so that several devices and band members share the same data. In the band folder the Software:

  • writes the file backstage-data.json with the band’s shared data and the file Glossar.md,
  • creates a folder Songs with one subfolder per stage and one folder per song. Each song folder contains the subfolders of Songs/zTemplates (if present), a song sheet and a production task list in Markdown format, and a hidden file .backstage-song that links the folder to the song,
  • moves or renames song folders when their stage or title changes, and adopts such changes made by the user in the file system,
  • creates one folder per gig under Live and one per release under Releases, each with a generated overview (Gig.md or Release.md). Release folders also contain the subfolders Artwork, Fotos and Content. These folders are renamed when the date, title or type changes,
  • stores guides as Markdown files under Anleitungen and moves the file of a deleted guide to the trash.

4.2 Files placed in these folders by the user are read only to display them within the Software. They aren’t transmitted to any other recipient by the Software.

4.3 The transmission and storage of the band folder are carried out by the storage provider selected by the user, under that provider’s terms. Anyone with whom the user shares the folder can access its contents.

5. Google Drive

5.1 On iOS and iPadOS, the user may connect a Google account to synchronise data directly through the Google Drive API. Authorisation takes place via Google OAuth. The Software requests the following permissions:

  • Google Drive (https://www.googleapis.com/auth/drive). This permission is used only to list the user’s folders and shared drives for selecting the band folder, and to access the following files in the selected folder:
    • backstage-data.json (shared band data): read and write,
    • Glossar.md (band glossary): read and write,
    • cadi-data.json (data file of the predecessor application, if present): read only.
  • Email address (openid, email). The email address is used only to show the connected account in the settings.

5.2 The Software doesn’t open, modify or delete any other files in Google Drive. Song sheets, task lists, gig and release overviews and other Markdown files aren’t transmitted via the Google Drive API. They’re created only on devices that use a local band folder (Section 4).

5.3 Data is exchanged directly between the user’s device and Google. The authorisation token is stored in the device’s keychain. When the user signs out of Google Drive in the settings, the Software revokes the token. The user can also revoke access at any time under Google Account → Third-party connections.

5.4 Backstage’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Data received from Google is used solely to provide the synchronisation function described above. It isn’t sold, used for advertising, or transferred to third parties.

6. Calendar

With the user’s permission, the Software reads and writes events in the calendar selected by the user (local, iCloud, or an account configured in the system’s Calendar app). Events remain with the respective calendar provider. The Software stores the event type (for example rehearsal or gig) in the event’s URL field.

7. Discord

If the user enters a Discord bot token and server ID, the Software communicates directly with the Discord API. It reads the server’s channel list, creates and renames forum posts for songs and gigs, reads and sends messages in these posts, and loads profile images from Discord’s servers. If a webhook URL is entered, the Software posts announcements to the respective channel. Discord processes this data under the Discord Privacy Policy.

8.1 When the user adds a reference track from Spotify, YouTube or SoundCloud, the Software requests its title and cover image from the respective provider’s oEmbed interface. The link and the device’s IP address are transmitted to that provider.

8.2 When the user searches for a location, the search terms are transmitted to Apple Maps.

9.1 Processing on the user’s device takes place under the user’s control. Data is transmitted to Third-Party Services only on the user’s instruction, in order to provide the function requested by the user. The respective provider is responsible for its own processing.

9.2 The Licensor doesn’t sell or transfer personal data. Depending on the device settings, Apple may collect diagnostic data. That data doesn’t reach the Licensor unless the user sends it to the Licensor.

10. Retention and deletion

10.1 Data remains on the device until the user deletes it. Under Einstellungen → Daten → Alle lokalen Daten löschen, the user can delete the band data on the device.

10.2 On iOS and iPadOS, deleting the Software removes its data and settings. On macOS, the data is stored in ~/Library/Application Support/Backstage and can be deleted there after the Software has been removed.

10.3 Files in the band folder are deleted like any other file in that folder. Under Einstellungen → Google Drive → Abmelden, the user signs out of Google Drive and revokes the Software’s access.

11. Rights of data subjects

11.1 Under Articles 15 to 21 GDPR, data subjects have the right of access, rectification, erasure, restriction of processing, data portability and objection. Since the Licensor doesn’t process any data handled with the Software, these rights are to be exercised against the providers of the connected Third-Party Services for data processed by them.

11.2 Data subjects have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), for example the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen.

12. Children

The Software isn’t directed at children under the age of 16.

13. Changes to this Privacy Policy

The Licensor will update this Privacy Policy if the processing of data by the Software changes. The current version is published at this address and shows its effective date.

Back to top