Privacy & agreements
An organization and its member studios often share responsibility for members’ data, for example through a joint privacy notice. Linyup records who is responsible on each side and lets you have every member studio sign the studio agreement between you, each reading it in their own language.
Everything on this page is for organization admins.
Your organization’s details
Section titled “Your organization’s details”Go to Organization settings → General and fill in Legal details:
- Legal name: the registered name of the association or company, with its address, tax number and VAT number where you have them. The address shows as one line; select Edit to change it.
- Email, and optionally an Email for privacy requests.
- Legal representative: the person who signs agreements on your organization’s behalf, with their role (for example President).
Only organization admins can see these details.
Organization settings → Privacy shows who is named, and lists your member studios, each with its own data controller as the studio entered it. A studio that has not filled in its details yet shows Controller not filled in yet.
Write a studio agreement
Section titled “Write a studio agreement”- Go to Organization settings → Documents and choose New document.
- Pick the type Studio agreement and give it a title.
- Set Written in to the language your text is written in. That text is the original and the one that applies.
- Write the text. Where a studio’s own details belong, use a field in double braces. Each studio sees the text with its own details filled in.
| Field | Filled with |
|---|---|
{{controllerName}} |
The studio’s data controller |
{{controllerAddress}} |
Its address |
{{controllerTaxCode}} |
Its tax number |
{{controllerVatId}} |
Its VAT number |
{{controllerEmail}} |
Its email |
{{studioName}} |
The studio’s name in Linyup |
- Choose Publish. Linyup translates the text into English, German, French and Italian, and each reader sees it in the language they use Linyup in, with a note that the original applies. A signature is always recorded against the original. To use your own translation for a language, write it next to the original before you publish. It must keep the same fields.
A studio can sign only once the details your text uses are filled in. If the text names the tax number, a studio without one is asked to add it first.
Agreements never appear on public pages.
Sign for the organization
Section titled “Sign for the organization”Each version needs two signatures: yours and the studio’s. Open the agreement from Organization settings → Privacy and use Sign version … for the organization. The name is filled in from your legal representative. You sign each version once, for all studios.
Follow who has signed
Section titled “Follow who has signed”The agreement’s page shows In force for … of … studios and, for each member studio, its details, the version and date it last signed, and where it stands:
| Status | Meaning |
|---|---|
| Not signed | The studio has not signed the current version. Its owner sees a banner asking them to. |
| Waiting for the organization | The studio signed. Your signature for this version is missing. |
| In force | Both sides signed a version that is still valid. |
| Details changed | The studio changed its details after signing, and is asked to sign again. |
| Excluded | You recorded that this agreement does not apply to this studio. |
Studios an agreement does not apply to
Section titled “Studios an agreement does not apply to”Each studio agreement has its own list of excluded studios. On the agreement’s page, switch on Excluded next to a studio this agreement does not apply to, then choose Save. That studio is no longer asked to sign it and does not count toward In force for … of … studios. Its other agreements are not affected: a studio can be excluded from one agreement and still sign another.
Switch it off again to bring the studio back in. Signatures it gave before are kept, and count again.
Your privacy notice on member studios’ pages
Section titled “Your privacy notice on member studios’ pages”Your organization can also write a privacy notice (or terms, or regulations) and offer it to its member studios as their default. You write it once; every member studio shows it on its public pages, filled in with its own details, and asks for it when someone signs up, next to the studio’s own documents. Each studio can switch it off for its own pages under Settings → Privacy, for example when it publishes its own privacy notice instead. To make sure members accept a document whatever a studio chooses, require it for an affiliation (below).
- Go to Organization settings → Documents and choose New document.
- Pick the type Privacy policy (or Terms, Regulation, Other), set Written in, and write the text.
- Where a studio’s details belong, use a field:
| Field | Filled with |
|---|---|
{{studioName}} |
The studio’s name in Linyup |
{{controllerName}} |
The studio’s data controller |
{{controllerAddress}} |
Its address |
{{controllerEmail}} |
Its email for privacy requests, or its general email |
- Choose Publish, then switch on Show on member studios’ pages.
A notice is public, so it can only use the details a privacy notice must publish anyway. A text that uses the tax number or the VAT number is refused when you publish.
A studio that has not filled in its details yet still shows the notice: its name stands in for the controller, and its contact email for the privacy email. An address it has not entered stays empty, so write the text so that reads well, for example with the address on a line of its own.
When a member accepts the notice at signup, Linyup records which version they accepted and the studio’s details as they were filled in. A studio that switches your notice off stops showing it right away, and shows it again when it switches it back on.
Documents your affiliations require
Section titled “Documents your affiliations require”An affiliation your organization issues, such as a federation licence, can require your documents: your rules, your regulations. Open the type under Organization settings → Affiliation settings and tick them under Required for this affiliation (see What an affiliation requires). The document does not need to be shown on the studios’ pages.
Every member studio’s signup forms that request that affiliation then ask for them, filled in with the studio’s details like your notice, and its members complete what is missing in their member space. This applies at a studio that switched your notice off too: that choice is about what its pages show, not about what your affiliations require.
Studios marked before
Section titled “Studios marked before”Before October 2026 a studio was marked once for everything: outside every agreement, or showing its own notice. A studio marked that way still reads as excluded from every agreement until you change it on one of them; changing one leaves the others as they were. A studio marked as showing its own notice keeps yours off its pages until the studio makes its own choice.
Publish a new version
Section titled “Publish a new version”When you change the text, Publish new version asks how the change applies:
- Silent update: signatures already given stay valid and the agreement stays in force. Studios are invited to sign the new version, but nothing lapses. Right for a typo, or a changed translation.
- Require re-signing: the agreement stops being in force for each studio until the studio and your organization both sign the new version. Right for any change to what the parties agree.
Every earlier version and signature stays on record.