This policy explains, plainly, what SETSGIG stores, where it stores it, for how long and what never leaves your device. It was written by looking at how the app actually works, not from a generic template.
The summary, in four lines.
SETSGIG does not sell, rent or share your data with anyone. There is no advertising. There is no tracking: the app contains no behavioural analytics tool whatsoever: no Google Analytics, no pixel, no third-party cookie. What goes to the cloud is only what your team typed in, and only if you create an account.
SETSGIG is operated independently and is in its early stage. The identifying details of the data controller will be published here as soon as the operation is formalised. This changes nothing written in this policy: the commitment not to sell, rent or share your data applies from now.
For anything concerning your data, including the requests described in section 8, write to Talk to us.
SETSGIG was built to work on the device first. If you do not create an account, everything you enter, repertoire, set lists, team, stays only in your browser's local storage. Nothing is sent to any server, and we have no way to see, recover or delete that data.
That has an important consequence: if you clear your browser data or uninstall the app without having an account, that data is lost and cannot be recovered.
| What | Why |
|---|---|
| Your email address | It is your identity in the service. You sign in with it and your password, and it is where the recovery link goes if you forget that password. |
| Team name | To identify the group and keep one team's data apart from another's. |
| Repertoire: song name, artist, key, tempo, time signature, length, structure, links, lyrics and chords typed in by you, tablature, notes and attachments | It is the content of the service. Without it the app has nothing to show. |
| Team: name, role and the key each person sings each song in | It is what lets the chart be transposed into the assigned singer's key. |
| Set lists: name, date, songs, running order, key of the day, who sings and who is scheduled | It is the list for each service, show or rehearsal. |
| Alert record: what changed in each set list and when | To show the team what has changed since the last alert. |
| Plan status: free or PRO and until when | To unlock what was paid for. |
We do not ask for and do not store a national ID, address, phone number, date of birth or card details. Payment, where it exists, is processed by an external platform with its own policy, from it we receive only the confirmation that the subscription is active.
Some things are deliberately personal and are never sent to the cloud or included in the link you share:
They stay in your browser's local storage. Neither we nor your team's leadership can see them.
SETSGIG has a tuner. When, and only when: you tap "Turn the microphone on", the browser asks your permission and the sound is analysed inside the device itself, in real time, to work out the frequency of the note.
The same applies to the "mic ducks the music" feature on the Sound screen: when you turn it on, the app measures only how much sound is coming in, to know whether you are talking. No word is recognised and no fragment is kept.
Nothing is recorded. Nothing is transmitted. Nothing is stored. Closing the tuner or turning the microphone off ends it immediately.
When leadership shares a set list, the data of that set list travels inside the address itself, compressed. The musician opens it and sees everything without installing anything and without creating an account, which is why they need not appear anywhere in our database.
What that means in practice: whoever has the link sees that set list. The link asks for no password, by design. Treat it the way you would treat the printed list that sits on top of the desk, send it to your team's group, do not post it anywhere public.
These three companies are infrastructure suppliers and process the data only to provide the service to us. There is no other third party: no ad network, no metrics tool, no data broker.
Each team sees only its own data, and that is enforced in the database, not on screen. Even if someone alters the app's code in their own browser, the database refuses access to another team's data.
At any time you may ask for:
Write to Talk to us. We reply within 15 days.
To exercise portability yourself, without asking anyone: the History screen has a Download backup button, which produces an open .json file with everything on the device, repertoire, team, set lists, your notes and your pen marks. The Restore backup button, on the same screen, puts that file back on any device. The file does not carry your session or your plan status.
To delete everything yourself: the same screen has a Clear everything button, which erases the content from the device. To delete the cloud copy and the account as well, write to the address above.
For as long as your account exists. If you ask for erasure, we delete within 30 days, except for what the law requires us to keep, for example tax records of payments, where there are any.
Free accounts with no access for 24 months may be deleted, with email notice beforehand.
SETSGIG uses no cookies. It uses the browser's local storage, which serves to keep your repertoire and keep you signed in, and which does not follow you around other sites.
We also keep a copy of the app on the device so it works without internet. That copy is of the program only, not of your data.
The service is intended for people over 18, normally a team's leadership. Teenagers may take part as musicians through the shared link, in which case we collect no data about them at all, since the link creates no account.
All traffic is encrypted. Your password is stored one-way hashed by our database provider, so it cannot be turned back: not even by us. Access to the data is controlled in the database itself, team by team.
No system is perfect. If an incident happens that could put you at risk, we notify you and the competent data protection authority, as the law requires.
If we change something significant, we give notice by email and inside the app before it takes effect. The date at the top always indicates the version in force.