1What can be exported, and from where
All the organisation’s data in a single file: Settings → Subscription → “Export all data”. The organisation’s administrator can do it at any time, including during the read-only days after the subscription ends. Every export is written in the organisation’s access log.
A single athlete’s data, from their card (the athlete’s rights of access and portability), and measurements by source as CSV, from the Data page.
Exporting is free, and stays free when moving to another provider.
2The file format
A JSON file in UTF-8 (format “markerdrift-org-export”, version 1). Dates are ISO 8601 (YYYY-MM-DD; timestamps with their time zone), numbers are numbers, and texts are as written in the software, untranslated.
At the top: the format name and its version (formatVersion), the creation time (generatedAt), the list of what was left out (omitted) and the organisation’s data (organization), including its settings.
Then the tables (tables). Each table has the list of its columns (columns) and its rows (rows): each row is a list of values in the same order as the columns. Tables are linked by identifiers: for example player_id in a measurement is the id of a row in players. The organisation’s code is not repeated in the rows: it is the file’s.
Then the uploaded files (files): photos and logo, each with its path, type, size and base64 content. At the end, the number of rows of each table (counts) and the tables that could not be read (notAvailable).
When the format changes, the formatVersion number changes: whoever receives the file always knows how it is built.
3The tables
The tables in the file, in the order in which they appear.
| Table | What it contains |
|---|
| teams | The organisation’s teams |
|---|
| seasons | Seasons |
|---|
| season_periods | Periods within a season, with name, colour and dates |
|---|
| positions | Positions (with the goalkeeper flag) |
|---|
| players | Athletes: personal data, team, position, leaving date, restriction |
|---|
| profiles | Staff and player accounts: name, role, permissions, preferences |
|---|
| player_aggregations | An athlete’s additional teams, with dates |
|---|
| metrics | Metrics and their definition (unit, scale, direction, summary, thresholds) |
|---|
| custom_metrics | Metrics calculated with a formula |
|---|
| provider_profiles | Providers’ import profiles (column mapping) |
|---|
| import_logs | File uploads: when, by whom, how many rows |
|---|
| competition_types | Competitions and their type |
|---|
| calendar_days | Calendar days: activity, microcycle day, notes, tests |
|---|
| session_types | Session types |
|---|
| gym_focuses | Gym focuses |
|---|
| sessions | Sessions |
|---|
| matches | Matches: opponent, result, competition |
|---|
| day_notes | The staff notebook on calendar days |
|---|
| session_participation | Attendance and minutes played |
|---|
| measurements | All measurements: GPS, perceived exertion, wellness, force plates and the other sources |
|---|
| anthropometrics | Anthropometric measurements |
|---|
| player_reference_values | An athlete’s declared reference values (MAS, heart rates) |
|---|
| injuries | Unavailability periods: injuries, illnesses, other reasons |
|---|
| injury_phases | The return phases of each period |
|---|
| injury_clinical | The clinical detail of each period (diagnosis, tissue, clinical notes) |
|---|
| athlete_checkins | Athletes’ submissions from their phone, with notes and who read them |
|---|
| soreness_zones | Body areas indicated by athletes |
|---|
| flag_reviews | What the staff saw and decided on Flags signals |
|---|
| player_consents | The consent register |
|---|
| athlete_links | Athletes’ phone links (without the code or the PIN) |
|---|
| dashboard_layouts | Dashboard layouts |
|---|
| report_views | Saved report views |
|---|
| print_templates | Print templates |
|---|
| legal_acceptances | Accepted documents, with version and date |
|---|
| audit_log | The access and change log |
|---|
4What is left out, and why
Credentials: the link code with which an athlete fills in the form from their phone, and their PIN. They are access keys, not data: in a file sent around by e-mail they would only help whoever intercepts it.
Account e-mail addresses and passwords: they live in the authentication system, separate from the organisation’s data. Addresses can be requested from support@markerdrift.com; we do not know the passwords ourselves.
Billing data: Paddle keeps it, as the issuer of the invoices.
Nothing else: the service keeps no organisation data outside these tables.
5How to leave
Cancellation is done from Settings → Subscription: the service stays active until the end of the period already paid.
Then the software stays open in read-only mode for 60 days: all staff can still sign in, read and export. At the start of that period the address given at sign-up receives an e-mail with the dates. If the subscription resumes during those days, everything goes back to how it was.
After the 60 days the accounts are deactivated. Up to 90 days after the end of the contract you can ask support@markerdrift.com to receive all the data or to delete it straight away: we reply within 30 days (clause 11 of the Data Processing Agreement).
Then the data is deleted, with an e-mail at least 14 days before and a confirmation afterwards. Backups delete themselves within 7 days.
Moving to another provider costs nothing on our side, and we answer questions about the file format.
6Known technical limits
The file is as large as the data: one season of a squad’s GPS data weighs tens of megabytes, and preparing it can take a few minutes. The file downloads while it is being built.
If the connection drops, the software does not save a half file: just repeat the export.
Photos are inside the file as base64: any tool that decodes that format recovers them.