Privacy policy.

Movetrics Cloud is provided by Marius Schober, a self-employed sole proprietor trading as Movetrics Intelligence. In this policy, “I”, “me” and “Movetrics Cloud” refer to Marius Schober.

I am the controller for personal data used to operate this website, assess access requests, manage Cloud accounts, communicate with you and protect the service. This policy covers beta.movetrics.com and the associated Cloud application. Provider and VAT information are in the Impressum.

If a university, employer, laboratory, coach or other organisation decides why and how participant recordings are processed, that organisation is normally the controller of those recordings. Movetrics Cloud processes them on its documented instructions as a processor. Its participant notice and applicable data-processing agreement also apply. This policy does not replace an agreement under Article 28 GDPR.

Information comes from you, the people who invite or administer your workspace, files and notes uploaded by authorised users, and technical information generated when the service is used.

• Website and connection data: IP address and connection information, requested resource, time, response status, browser information and technical errors processed by the hosting infrastructure. Application logs also contain operational references and timings.
• Access requests: email address and information entered in the form, including name, role, organisation, equipment and intended use. Optional fields are identified in the form.
• Account and access data: email address, display name, identity reference, approval status, workspace membership and role, sign-in attempts, session records and the version and time of recorded terms acceptance or optional choices.
• Recording and workspace data: original files and filenames; participant or examination references; dates; equipment and source metadata; signals and any marker or movement data contained in a supported file; measurement context, notes, comments and corrections.
• Derived data: normalised recordings, calculated results, charts, comparisons, reports, AI explanations, processing history and audit records. These can remain personal data when linked to a person or recording.
• Support data: your message, reply address, problem description, case references and inspection permission. Avoid unnecessary participant details in messages and filenames.

You can read the public pages without an account. The required request details are necessary to assess access; an approved email address is necessary to sign in. A file and sufficient measurement context are necessary for the analysis you request. Optional product-development permission is not required.

For participant data processed on an organisation’s instructions, the organisation determines and documents the lawful basis. My service agreement with an uploader does not itself supply a lawful basis for processing another person’s recordings.

This policy informs you about processing. Reading it or accepting the beta terms is not blanket consent to all processing or future uses. Necessary service processing does not depend on an optional reuse choice.

Movement and force recordings can reveal information about health, physical condition or disability. Depending on their content and use, they may be special-category data under Article 9 GDPR. Replacing a name with a code does not remove that protection where a person remains identifiable.

Upload only recordings you are authorised to process. Minimise direct identifiers and keep participant-code keys separately. For organisational recordings, establish the required data-processing agreement, inform participants and document an Article 6 basis and, where applicable, an Article 9 exception before uploading. Explicit participant consent may be relevant; an uploader’s general checkbox does not replace it. Provider conditions may impose additional requirements for sensitive data.

The beta is designed for adult account holders and non-medical education, research and performance work. Do not upload children’s recordings or identifiable clinical records without a separately agreed and lawful arrangement. Movetrics Cloud does not use recordings for biometric identification.

If someone uploaded data about you, contact the person or organisation responsible for the recording. You may also contact me; I will help route your request without disclosing another user’s information.

Authorised workspace members can see data according to their permissions. I may access data where necessary to operate the service, resolve an authorised support case, protect security or meet a legal duty. This does not permit unrelated reuse.

EU storage and application regions do not rule out international transfers, particularly for email, support and subprocessors. The linked provider agreements describe transfer arrangements, including European Commission standard contractual clauses where applicable. An adequacy decision can apply only where its conditions are met. Request details or copies of the safeguards applicable to your data from support@movetrics.com.

I do not sell recordings, publish them as a public dataset or use them for advertising. Necessary disclosures may be made to legal advisers or competent authorities for legal obligations or claims. Reports you download and share are outside the Cloud workspace’s access controls.

AI apps or providers that you connect receive data at your instruction, not as my processors. Anthropic, which provides AI explanations, is listed above as my sub-processor. See AI features and connections.

The hosted beta does not automatically delete every recording after 30 days. Originals are needed for reanalysis and complete exports and remain with their examination until deletion.

Eligible metadata is removed by the next successful daily cleanup. That schedule does not itself erase separate provider logs, mailboxes or backup copies.

An encrypted backup of the database and stored files is made every night and each copy is kept for 30 days, so deleted data leaves the backups about 30 days after its deletion. Backups are used only to recover the service; deletions made since a backup must be applied again after any restore.

If a legal obligation or concrete dispute requires longer retention, processing is limited to that purpose and the applicable duty or limitation period. It is not an indefinite general permission to retain recordings.

The public pages do not include advertising trackers or third-party analytics. Fonts and page assets are served with the site. The hosted email-code sign-in flow uses these first-party cookies:

These cookies are necessary for the sign-in and secure service you request; device storage is based on § 25(2)(2) TDDDG. Related personal-data processing uses the service and security bases above. Blocking the cookies can prevent sign-in or workspace changes.

The app also automatically stores chart preferences in browser local storage: selected channels, display mode and zoom, associated with a recording and view identifier. They do not contain the original signal arrays and are not used for advertising. They remain until you clear the site’s local data and may be stored again when a chart is used. Clearing local storage does not delete server-side recordings.

Device storage is subject to § 25 TDDDG independently of the GDPR. Optional storage that requires consent needs a separate choice; accepting the beta terms or this notice does not provide that consent.

The Account page has a separate “Pseudonymous signal reuse” setting, off by default. Its purpose is to allow authorised signal data to be considered for improving import compatibility, data quality and product reliability. The current implementation can mark canonical signal datasets within the workspace as eligible and retain a link to the recorded permission. The data is not irreversibly anonymous.

This permission is voluntary and not a condition of access. It does not authorise publication, sale or AI-model training and cannot supply consent for another participant merely because you control an account. Only enable it where you can authorise the stated use for every affected recording and the necessary participant permissions and legal basis have been established separately.

Withdraw your account’s permission on the Account page or by contacting support. The app records withdrawal and excludes datasets linked to that permission from future eligible reuse. The original remains available for your requested service until separately deleted. Withdrawal does not retrospectively invalidate earlier lawful processing.

Permission to investigate a support problem is separate. It does not authorise permanent benchmark or training-dataset reuse.

AI reads and explanations. In the beta every account has access unless an administrator switched it off for that person. Each person agrees once, on a screen that says what is sent, before their first read. A read then runs only when that person taps or asks for one. The workspace owner can also choose to have a read written automatically when a recording arrives; it is written under the owner’s agreement and shown to the workspace team. The owner can switch on “No AI in this workspace”, after which no read, explanation or AI request is made for anyone in that workspace. Reads already saved are hidden, not deleted; they appear again if AI is switched back on, and are deleted with the result they explain. An administrator sets a monthly allowance for Think deeper, which runs on Claude Sonnet. When it runs out, the Think deeper button stops until the next month, and included explanations, which run on Claude Haiku, continue. If the service-wide cap is reached, all built-in AI pauses until the next month. Nothing else changes, and no charge applies.

The feature sends to Anthropic (Claude models), which I chose: the athlete’s code, the results to be explained, such as jump height, the times of the movement phases, the force curve reduced to 25 values per second, the words a user typed to name a movement and, only where the workspace owner switched notes on, up to three recent notes on the athlete, with the name replaced by the code. It never sends the original file, or the athlete’s name, email address or date of birth from their record. Typed text is checked automatically and the names of the workspace’s athletes and members, email addresses and dates written as numbers are replaced, but the check cannot catch everything: anything else written in a note or a movement word is sent as written, so do not write health details or other people’s names there that the read does not need. A code is a pseudonym, and a force curve can describe a person’s movement, so a read remains personal data and can be health data. A read describes how a person moved, which is profiling; it is never used to make a decision about the person (see Security and human decisions). Anthropic is my sub-processor for this feature. Where a workspace holds recordings for an organisation, the organisation is told of this sub-processor here and in its data-processing agreement, and its owner can object by switching AI off for the workspace. Its data-processing addendum incorporates the EU standard contractual clauses for transfers outside the EEA where data-protection law requires them, and the data may reach the United States. Explanations are saved in the workspace with the result they explain, and are deleted with it. Anthropic deletes its copy of a request within 30 days, unless its safety systems flag it (see Providers); deleting an explanation here does not reach that copy. I may switch to another provider only after it is listed on this page. Your opt-in covers this feature only. It does not replace any information or consent that participants need (see Participant and health data). An explanation is not a medical assessment (see Intended use and medical boundary in the Terms).

AI connections. You may connect an AI app or provider of your choice to a workspace. When you do, you choose which workspace it can read and whether athlete names and file names are included; otherwise athletes appear as codes and file names are withheld. The AI receives only what it asks for, when it asks for it, at your instruction. I do not choose or pay that provider, and it is not one of my processors. Its own terms and privacy notice apply to what it does with that data. Read access is the default. Changes an AI may make are off unless you allow them, are open only to roles that can change recordings, and are logged. You can undo a change unless the thing has changed again since, it has already been undone, or the recording has been in the trash for 30 days. A connection can move a recording to the trash, as your own “Move to trash” does, but it cannot erase one. Recordings in the trash are erased after 30 days. You can turn a connection off at any time in your Account.

Apart from AI apps you connect yourself, and Anthropic for AI reads and explanations, no AI provider receives Cloud data in the live beta. Anthropic’s commercial terms say it may not train models on customer content from its services. I do not use recordings to train a model through either AI feature. Connecting an AI does not authorise AI-model training on your recordings.

AI outputs can be wrong and require review. They cannot establish missing calibration, units, axes, timing or protocol meaning, or silently change measured values and official calculations. AI must remain optional to the core deterministic workflow. Any further AI feature will be added the same way: before it is switched on, I will identify its provider, data sent, purpose, legal basis, processing locations, retention and transfer safeguards, and provide the controls and permissions it needs. Training or improving an AI model using personal recordings requires a distinct, specific authorisation and an appropriate lawful basis; ordinary uploads, these terms and the present product-development setting do not authorise it. No future provider’s “no training”, retention or EU-residency setting is promised before the provider and configuration have been selected and verified.

The hosted service uses encrypted connections, private storage, authenticated workspace access, role-based permissions, server checks, database row-level restrictions, bounded processing and audit records. Operational access is limited to the task being performed. These safeguards reduce risk; they do not make an internet service risk-free.

The service does not currently make solely automated decisions determining employment, treatment, insurance or other matters with legal or similarly significant effects. Calculations and observations support human interpretation. A chart, score or AI explanation must not be used as an automated basis for a consequential decision about a person.

An athlete in a workspace can be given a read-only copy of every recording of themselves in it, called My data. The copy covers recordings and results and does not include staff notes. The organisation that runs the workspace gives it, and I process the copy on that organisation’s documented instructions, as a processor (see Who is responsible). A full access request goes to that organisation, as controller. For an athlete aged 18 or over, the invitation goes to the athlete. For an athlete under 18, it goes to a parent or guardian aged 18 or over. Recordings of minors need the separately agreed and lawful arrangement described under Participant and health data. This copy is separate from the account export described under Your rights.

Subject to the applicable GDPR conditions, you may request access, correction, erasure, restriction of processing and portability of your personal data. You may withdraw consent at any time without affecting the lawfulness of earlier processing.

Write to support@movetrics.com or the postal address above. Requests are normally free. I may ask for information reasonably needed to establish identity or locate data. I will respond without undue delay and normally within one month; a legally permitted extension for complexity or multiple requests will be explained within that first month.

The Account page offers an export and account deletion. The export includes personal account records; complete recording lineage is included only for workspaces you own alone. Shared-workspace artifacts are excluded to protect others. Contact support for rights requests beyond that download.

Sole-owner account deletion removes its workspace and examination lineage and revokes access. Shared-workspace ownership must be resolved before automated deletion can complete; this does not remove your statutory rights or prevent you from contacting me. Some shared attribution is replaced with a deleted-account reference; external identity cleanup can finish separately.

You may complain to a data-protection supervisory authority, particularly where you live, work or consider an infringement to have occurred. For my business in North Rhine-Westphalia, the relevant authority is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW). You need not contact me before complaining.

I will update this notice when the service or processing changes and give advance information where required. Updating a notice does not create consent for a new purpose. Material new uses, including AI-provider processing or training, require their own assessment, information and necessary permission before they start.

Changed on 28 October 2026: this policy now describes the AI read as it works in the beta (the force curve it sends, that every account can use it after agreeing, and the owner’s switch to turn all AI off), lists Sentry and the Cloudflare backups, and states how long Anthropic keeps requests.