Privacy

Kadance Privacy Policy

This policy covers the Kadance app and its private-beta access form. Kadance minimises data, does not sell personal information, and uses neither advertising nor cross-app tracking.

1. Controller and contact

The data controller and service operator is Daniel Salgado Rojo, an individual established in Spain who operates Kadance. For privacy questions or to exercise your rights:

• [email protected]
• General support: [email protected]

2. Who the service is for

The first external beta is limited to people aged 18 or over who live in Spain and have been admitted by invitation. Kadance is not directed at children, and content depicting minors may not be contributed during this phase. If we identify a child's data, we may block access and remove the content.

3. Data we process

• Account and identity: account identifier, name, email, sign-in provider and session status. If you sign in with Google, we indirectly receive the basic details you authorise to identify you; the external beta does not access your Google Drive.
• Service organisation: classrooms, courses, classes, invitations, enrolments, roles, permissions, tags and relationships between participants.
• Library and content: titles, original names, duration, size, file type, dates, tags, clips and provenance. Personal videos remain on the device until you choose to contribute or publish one; Kadance then stores the shared copy, thumbnails and required derivatives.
• Safety and moderation: private reports about users or content, reason, optional details, related identifiers, resolution status and strictly necessary operational evidence.
• Operation and security: IP address and basic connection data that providers may record, requested route, result, timings, errors, authorised transfers and storage accounting. Logs must not include videos, titles, local paths or report text.
• Beta application: email, profile, and optionally name and dance styles, together with language and limited campaign-source data.

Kadance does not scan your gallery or the rest of your device. It processes only files you choose and private folders managed by the app. Optional product analytics described in the technical design remains disabled.

4. Purposes and legal bases

• Providing the requested beta, authentication, synchronisation and managing classrooms and content: performance of the service terms and requested pre-contractual steps.
• Managing the interest list and optional beta communications: consent, which you may withdraw.
• Protecting accounts, limiting abuse, maintaining the service and resolving reports: legitimate interests in service safety, integrity and a respectful environment, balanced against your rights.
• Handling deletion, rights requests and applicable duties: compliance with legal obligations.

Where a feature is optional and relies on consent, refusing it will not prevent use of core features. If information is necessary to create the account, join a classroom or transfer content you select, not providing it may prevent that specific operation.

5. Who receives the data

Data is shown only to people authorised by the classroom structure and is made available to providers needed to operate Kadance: Amazon Web Services for federated identity, API, database, storage, processing, logs and email; Cloudflare for the website, abuse protection and email routing; and Google for user-selected sign-in and distribution through Google Play. Each provider processes data for its role and under its terms.

The main infrastructure planned for the beta uses AWS's Ireland region. Some global providers may process data from outside the European Economic Area using the transfer safeguards applicable to them. Kadance does not sell data or share it with advertising networks.

6. Retention

• Account, profile and organisation: while the account or relationship remains active, until authorised departure or deletion.
• Shared content: while it remains published or is needed for an authorised relationship; incomplete uploads normally expire within a technical maximum of one day.
• Technical logs: 14 days in the planned beta configuration.
• Database recovery copies: an encrypted rolling window of up to 35 days; they are not used as the active catalogue, and a restoration must reconcile later deletions.
• Moderation reports: while open and, once resolved, for 90 days to handle reviews or disputes; they are then deleted automatically.
• Beta applications: while needed to manage admission or until consent is withdrawn.

Personal videos stored only on the device are not on Kadance servers. Uninstalling the app, clearing its data or losing the device may remove them; originals retained in your gallery or source folder remain outside Kadance.

7. Your rights and deletion

You may request access, correction, erasure, restriction, objection and portability where applicable, and withdraw consent without affecting earlier processing. You can delete your account in the app or through the public deletion resource. Write to [email protected] for any request; we may ask for information already provided to verify your identity without collecting more than necessary.

If you believe we have not handled your rights properly, you may complain to the Spanish Data Protection Agency (aepd.es).

8. Security, decisions and changes

Kadance uses environment separation, encryption in transit, private storage, classroom permissions, temporary URLs, abuse limits, minimised logs and self-service deletion. No system is completely infallible; report incidents to [email protected]. We do not make automated decisions with legal effects or create advertising profiles.

The interest form retains its specific beta-privacy-v1 consent. Material changes to this policy will receive a new version and, where appropriate, require renewed acceptance.

These documents will be reviewed before the external beta opens. Material changes will receive a new version.