Privacy policy

Who processes your data

Revigo, Ter Braak is the controller for the data described below. Questions and requests go to revigo@tbraak.nl.

In short

• Your songs, setlists and annotations stay on your device and are not sent to us.
• Without a team you need no account, and we store nothing about you that identifies you.
• With a team we store what that team needs to work: a display name, your role, and the setlists you share with it.
• We measure how the app is used, but never what you search for, sing or write down.

What stays on your device

Your songbooks, own songs, setlists, annotations, transpositions and preferences are stored locally. They do not reach our servers and we cannot see them.

If you make a backup, you decide where that file goes. If you share a setlist over Bluetooth it travels straight to the device beside you, with no server in between.

Account and signing in

For the app alone you need no account. Internally it uses an anonymous identity that is not tied to you as a person.

To start or recover a team we ask for an email address and send a six-digit code to it. We keep your email address to link you to your team. The code itself is stored only in hashed form and expires shortly after it is sent.

Teams

If you use Revigo Team we store, per team: the team name, the invite code, and for each member a display name, an account identifier, the role (manager or member) and when they joined.

Setlists you share with the team are stored on our servers so the other members can see them. They contain references to songs, the lyrics and chords of your own songs, and any notes you add to the setlist.

Your personal annotations are not shared with the team. They stay on your own device.

Usage statistics

We use Firebase Analytics to see which parts of the app get used, such as that a setlist was created, or how many songs it holds.

These events carry no content. For online search we send only the length of your query and not the query itself, so we can tell whether the feature works without knowing what you searched for.

Error reporting

When the app crashes or hits an error we send a report to Sentry with technical information: the kind of error, where in the code it happened, and details about your device and the app version. We use it to fix the fault.

Purchases

A team subscription is bought through the App Store, through Google Play, or on this site. If you buy in the app, payment runs through Apple or Google and we never see your payment details. We use RevenueCat to know whether the subscription is running, which shares your account identifier along with its status and end date.

If you buy on this site, Stripe processes the payment. Stripe processes your name, email address, address, any VAT number and your payment details. We keep only the Stripe customer and subscription identifiers, the email address that paid, and the status and end date of the subscription. Your full payment details never reach us.

If you sign in on this site to pay for your own team, we use the same emailed sign-in code as the app does.

This website

On revigoapp.eu we use Google Analytics to see which pages are read and whether visitors find the app. It is on by default and sets cookies as soon as you open the site. You can switch it off from the notice on your first visit, or later through Cookie settings at the foot of every page. Switching it off stops measurement immediately and deletes the cookies that were set.

Separately, Sentry runs on the site to report errors, for instance if the sign-in form breaks. It sets no cookies and never sends anything you type into a form. That runs on legitimate interest: a broken payment page we never hear about helps nobody.

Opwekking integration

To import the Opwekking volumes you bought, you sign in to Opwekking. Your Opwekking email address and password are stored on your own device, so the app can sign in again when the session expires.

They are not sent to us and not shared with anyone other than Opwekking itself, to fetch your volumes. Disconnect the integration and they are removed from your device.

Online search

Online search is off by default and asks for your consent first. If you turn it on, we send your query straight to Ultimate Guitar and E-Chords to fetch results. Their own privacy policies apply to those services.

Protection against abuse

To keep our servers from being loaded by automated abuse we use Firebase App Check, where your device confirms with Apple or Google that the app is genuine. No information about you as a person is shared in the process.

Who we rely on

We use the following parties to run the service:

• Google (Firebase): accounts, database, statistics and abuse protection. Our database is in the EU (region europe-west4).
• Sentry: error reporting.
• RevenueCat: subscription status.
• Stripe: payments and invoices for subscriptions taken out on this site.
• Brevo: sending the sign-in code by email.
• Google Analytics: visitor statistics on revigoapp.eu, on by default and switchable off.
• Apple and Google: payments and app distribution.

Transfers outside the EU

Some of these parties are established in the United States or process data there. Where that happens, the transfer relies on the European Commission’s standard contractual clauses or on the EU-US Data Privacy Framework.

How long we keep things

• Sign-in codes: a few minutes, then they expire.
• Team data and team setlists: as long as the team exists. Delete a setlist and it is gone immediately.
• Statistics and error reports: according to the standard retention periods of Firebase and Sentry.
• Data on your device: until you delete it or remove the app.

Your rights

You have the right to see your data, have it corrected or deleted, object to the processing, and receive your data in a portable form. Write to revigo@tbraak.nl.

If you disagree with how we handle your data you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

Children

Revigo is not aimed at children under 16. We do not knowingly collect data from children.

Changes

If this policy changes we update the date at the top. For significant changes we say so in the app.