kadenca

legal · terms of service

Kadenca — Terms of Service

Srlaya Studio, Mgr. Swinkelsstraat 53, 5623 AP Eindhoven, Nederland, KVK 42104493, BTW-id NL005496029B89 ("Srlaya", "we") — for the Kadenca shared studio-management platform at kadenca.app.

Version 2.0 — effective 10 September 2026. Supersedes Version 1.1 (effective 26 August 2026). Acceptance of these Terms includes the Data Processing Agreement in Annex A.


1. The Service

1.1 Kadenca is a shared ("multi-tenant") studio-management application: scheduling, bookings, member and membership management, payment records, documents, and related features, served at <your-studio>.kadenca.app with your studio's name, logo, and accent color.

1.2 The Service is provided as-is from a shared platform: all tenants run the same software version. Features may be added, changed, or (with 30 days' notice) removed. There is no bespoke development on this tier — custom domains, a marketing website, native store apps, and custom features are separate, separately quoted products.

1.3 The Service is a tool for running your studio. You remain responsible for your business decisions, your prices, your schedule, and your compliance with laws that apply to your studio.

1.4 Kadenca is offered to businesses only: a studio operating as a registered business (obrt, d.o.o., j.d.o.o. or equivalent, identified by its OIB or VAT ID). You confirm that you subscribe for business purposes. Consumer protection rules, including the right of withdrawal for distance contracts, do not apply.

2. Price, billing, and payment

2.1 Prices. Two tiers, per calendar month, exclusive of VAT, no setup fee:

TierPriceFor studios with
Standard€49 per monthup to 100 active members
Plus€79 per monthmore than 100 active members

The tiers are the same product; the only difference is the size of the studio.

2.2 Which tier applies. "Active members" are the member (client) accounts that exist in your studio and have not been deleted; staff and instructor accounts are not counted. The Service counts them. A new subscription starts on Standard. If your count exceeds 100, we tell you and move you to Plus; if a Plus studio falls to 95 or fewer, we may move you back to Standard. A tier change is never automatic: we notify you first, and the new price applies from your next invoice, with no pro-rated charge for the current period.

2.3 Billing method. One of two methods applies, and it is fixed at the start: Card billing (clause 2.4) if you subscribed at kadenca.app/signup; Invoice billing (clause 2.6) if your first invoice was issued by Srlaya directly — the studios we onboarded before self-serve signup existed. An invoice-billed studio moves to card billing only by accepting an activation offer we open in the Service's Settings (entering a payment card on Stripe's checkout page); from that acceptance clause 2.4 applies and invoice billing ends with the last invoiced period. We do not otherwise switch a studio between methods without agreeing it in writing.

2.4 Card billing. You subscribe at kadenca.app/signup — or, as an invoice-billed studio, by accepting an activation offer in Settings — by entering a payment card on a checkout page hosted by Stripe.

2.5 Failed card payment. If a charge fails, the Service stays available while Stripe retries the payment and emails you to update your card. If the retries are exhausted and your subscription ends unpaid, we contact you; we may then suspend the Service after one written reminder (your subdomain shows an "unavailable" notice and no data is deleted). Suspension is lifted when the subscription is paid or restarted. If it is not restored within 30 days of suspension, the subscription has ended on the suspension date and clause 5.3 applies from that date.

2.6 Invoice billing. The fee is the tier price in clause 2.1, exclusive of VAT. VAT treatment follows EU B2B rules (reverse charge for VIES-registered customers; stated on each invoice). Billing is monthly in advance, by invoice, payable within 14 days. The first month is pro-rated or starts on the 1st — as stated on the first invoice. If an invoice is more than 14 days overdue, we may suspend the Service (your subdomain shows an "unavailable" notice; no data is deleted) after one written reminder. Suspension is lifted on payment.

2.7 Price changes. Fees may change with 30 days' written notice, effective from the next billing period. If you don't accept a change, cancel per clause 3.

3. Term and cancellation

3.1 Monthly, no minimum term. Either party may cancel with effect from the end of the current paid period; access continues until then.

3.2 We may terminate for material breach (including clause 4 misuse) with 14 days' written notice if the breach is not cured, or immediately for unlawful use.

4. Your obligations

4.1 Keep your admin credentials secure; you are responsible for actions taken under your studio's accounts.

4.2 Use the Service lawfully. Do not upload unlawful content, attempt to access other tenants' data, probe or overload the platform, or resell the Service.

4.3 You are the owner of, and responsible for, the data you and your members enter — its accuracy and your legal basis for processing it (see Annex A). Obtain any consents your members' data requires.

5. Data ownership, export, and deletion

5.1 Your studio's data is yours. We claim no rights to it beyond what is needed to operate the Service (Annex A).

5.2 On request, and always at termination, we provide an export of your studio's data in a common machine-readable format (database export; uploaded files as files) at no charge.

5.3 After termination we keep your data for 30 days (in case you return or need an export), then delete it from the live platform; encrypted backups expire on their regular rotation. Statutory retention of our own invoices is unaffected.

6. Card payments from your members (Stripe Connect)

6.1 Optional, and your own Stripe account. You may activate card payments for your members ("Naplata karticama" in Settings). This creates a Stripe account in your studio's name, which you complete and verify in Stripe's onboarding, including creating your own Stripe login.

6.2 Stripe's terms. Payment processing services for studios on Kadenca are provided by Stripe and are subject to the Stripe Connected Account Agreement, which includes the Stripe Terms of Service (collectively, the "Stripe Services Agreement"). By activating card payments or continuing to use them on Kadenca, you agree to be bound by the Stripe Services Agreement, as the same may be modified by Stripe from time to time. As a condition of Kadenca enabling payment processing services through Stripe, you agree to provide Kadenca accurate and complete information about you and your business, and you authorise Kadenca to share it and transaction information related to your use of the payment processing services provided by Stripe. Stripe processes your data as described in the Stripe Privacy Policy.

6.3 You are the merchant. Your members pay you, never Kadenca. Card payments settle to your bank account from your Stripe account. You pay Stripe's processing fees, and you bear and handle refunds, chargebacks, disputes and any resulting losses — in your own Stripe dashboard. You are responsible for your own tax, VAT and fiscalisation (fiskalizacija) obligations on those sales, and for issuing your members whatever receipt or invoice Croatian law requires.

6.4 What Kadenca does. On your instruction, the Service creates your Stripe account, shows its status, opens Stripe's checkout page on your account when a member pays, records the resulting payment in your studio's ledger, and — when your staff click refund in the Service — issues that refund on your Stripe account. Kadenca charges no fee on your members' payments and never holds, routes or receives your revenue; our only remuneration is the subscription in clause 2. The Service stores no card data.

6.5 Limits. While your studio is suspended (clauses 2.5, 2.6), the Service does not record incoming card payments; a payment already in progress still reaches your Stripe account and you reconcile it there. Decisions about your Stripe account — verification, holds, payout timing, disputes — are Stripe's, made under the Stripe Services Agreement, and we cannot reverse them.

7. Availability, support, and maintenance

7.1 We operate the Service with reasonable skill and care: EU hosting, daily encrypted backups, monitoring, and security updates. No specific uptime percentage is guaranteed on this tier. Planned maintenance is done outside Croatian business hours where practicable.

7.2 Support: email to support@kadenca.app, in Croatian or English, answered within 2 business days. Support covers the use and availability of the Service, not data entry, member communication, or training beyond the initial onboarding call.

8. Intellectual property

8.1 The platform, its software and design remain the property of Srlaya. You receive a non-exclusive, non-transferable right to use the Service while subscribed.

8.2 Your name, logo, content, and data remain yours; you grant us a licence to display them within the Service and in transactional email sent on your behalf.

8.3 We may state your studio's name and logo as a Kadenca customer reference; tell us in writing if you prefer not, and we won't.

9. Liability

9.1 Our total liability per contract year is capped at the fees you paid in the 12 months preceding the event.

9.2 We are not liable for indirect damages (lost profit, lost members, lost data to the extent restorable from a backup we offered to restore). Nothing limits liability for intent or gross negligence, or where law forbids limits.

10. Changes to these Terms

10.1 We may update these Terms with 30 days' notice by email to the studio owner. Continued use after the effective date is acceptance; otherwise cancel per clause 3 — the old terms apply until the end of the paid period.

11. Governing law and disputes

11.1 Dutch law governs. Disputes go to the competent court in the Netherlands, after a genuine attempt to resolve the matter by discussion first.


Annex A — Data Processing Agreement (Article 28 GDPR)

This Annex is part of the Terms and is accepted with them. Where the studio's members' personal data is processed, the studio is the Controller and Srlaya is the Processor.

A1. Subject, nature, purpose, duration. Processing consists of hosting, storing, displaying, backing up, and transmitting (email notifications) the data the Controller and its members enter into the Service, solely to provide the Service described in clause 1, for the duration of the subscription plus the deletion window in clause 5.3.

A1.1 Data subjects: the studio's members and prospective members, its staff/instructors, and guardians of minor members. Data categories: identification and contact data (name, email, phone), membership and payment records (packages, credits, bookings, attendance, payment references and Stripe payment identifiers — no card numbers, the Service stores no card data), signed documents (waivers, consents), uploaded images (avatars, logo), and member notes. The Controller instructs the Processor to store any health-related notes its staff enter (Art. 9 GDPR) only as free-text fields the Controller manages; the Controller is responsible for the legal basis.

A1.2 Card payments (clause 6). When a member pays by card, the Processor transmits the member's name, email and the amount to Stripe on the Controller's own Stripe account, on the Controller's standing instruction. Stripe then processes the payment under the Controller's own agreement with Stripe (the Stripe Services Agreement, clause 6.2), not as the Processor's sub-processor. The Processor receives back and stores only the payment result and Stripe's identifiers.

A2. Sub-processors. Authorized as of v2.0:

Sub-processorRoleLocation
RenderApplication hosting and tenant databasesFrankfurt, EU
CloudflareDNS/CDN; encrypted backups in R2 (EU jurisdiction); Turnstile bot protection on the signup formEU
Resend (Plus Five Five, Inc., San Francisco, USA)Transactional email. Sent from the EU region (eu-west-1, Ireland); Resend stores email metadata and delivery logs in the USA under the EU Standard Contractual ClausesEU sending; metadata in the USA
Amazon Web Services SESTransactional email, as fallback to Resendeu-central-1, Frankfurt, EU
SentryError monitoring, no personal data attachedEU data residency
Stripe (Stripe Payments Europe, Limited, Dublin, Ireland)Subscription billing of the Controller's own account (clause 2.4) — Stripe acts here as an independent controller, see clause 2.4; member card payments run on the Controller's own Stripe account (A1.2)EU

A2.2: changes with 30 days' notice; objection = right to cancel per clause 3.

A3. Processor's duties. Process only on the Controller's documented instructions (the Service's operation is the standing instruction); confidentiality for all persons authorized to process; the technical and organisational measures in A5; assist the Controller with data-subject requests (export/rectification/erasure are largely self-service in-app) and with Art. 32–36 duties; notify the Controller without undue delay, at the latest within 48 hours, of a personal-data breach affecting its tenant; delete or return all personal data per clause 5.3; make available the information needed to demonstrate Art. 28 compliance and allow audits — satisfied in the first instance by written answers and this document, on-site audits at the Controller's cost with 30 days' notice, max once per year.

A4. Location. Hosting, databases, backups and email sending are within the EU/EEA. The one exception is email metadata and delivery logs held by Resend in the USA (A2), transferred under the EU Standard Contractual Clauses (Art. 46 GDPR). No other transfer outside the EEA without an Art. 46 GDPR safeguard and prior notice.

A5. Security measures (summary). Per-tenant isolated databases and file storage; TLS everywhere; passwords stored with modern key-derivation (scrypt); tenant-scoped access tokens; role-based authorization enforced server-side; daily encrypted (AES-256-GCM) off-site backups; audit logging of state-changing actions; least-privilege operator access (a single named operator); monitored error reporting scrubbed of secrets.