Data formats and export

This overview describes the data structures and formats you can export your data from WipeWatchers in, which standards apply, and which categories of data are exempt from the export. It fulfils the commitment made in the annex on switching providers of our terms and conditions.

Requesting an export

Signed-in users generate the export themselves under Profile & Settings → Account. You receive a ZIP archive with two files: manifest.json holding all data and README.md explaining the fields. The media files themselves stay on our servers; the manifest carries signed download addresses valid for seven days. You can generate a fresh export at any time, free of charge and without giving reasons. On request we also provide the export by email.

Formats

• Video: MP4 container (ISO/IEC 14496-14) with H.264 video (ISO/IEC 14496-10) and AAC audio
• Audio sidecars: separate MP4 audio files per source, as uploaded by the recorder
• Thumbnails: JPEG (ISO/IEC 10918)
• Metadata: JSON (RFC 8259) in UTF-8 (RFC 3629), timestamps per ISO 8601
• Game identifiers: numeric ids following Blizzard's game data (encounter, map)

Standards and interoperability specifications

For services of this kind — recording and analysing game sessions — no open interoperability specifications and no European standards currently exist that an export could follow. We therefore consistently use the widely adopted, openly documented formats listed above. As soon as relevant specifications exist, we will update this page.

Data structures in the manifest

The manifest carries schema_version, generated_at and media_urls_expire_at, and below them the following blocks:

account

Account id, name, email address, BattleTag, locale, registration date.

guild_memberships

Guild id, name, your role, joining date.

recordings

• Identity: id, client_recording_id (the recorder's local id), kind (recording or clip), content_type
• Description: title, status, visibility (private, guild, public), guild_id
• Time and picture: started_at, started_at_server, duration_s, width, height
• encounter: encounter_id, map_id, difficulty, key_level, result, lowest_hp_pct
• grouping: pull_id, pull_number, raid_session_id, raid_session_title, roster_hash — this is how several points of view of the same attempt belong together
• Group: roster_guids, advanced_combatlog_enabled, warcraftlogs_url
• combat_data: the data derived from your combat log — deaths, interrupts, bosses, boss_hp, roster, spans, keystone, pull_number, recorder, source_recording_id
• files: per file kind (video, audio, thumbnail), content_type, size_bytes, url, plus name for audio sidecars

Scope of the export

You export the recordings you uploaded yourself, together with their metadata and media files. Other people's recordings are not included, not even when they sit in a shared guild vault — they contain those people's personal data.

Categories of data exempt from the export

Exempt is data specific to the internal functioning of the service, or covered by third-party rights or our trade secrets:

• encounter reference data and other game data originating from Blizzard Entertainment
• our analysis, attribution and grouping logic including the underlying thresholds
• internal operational and security data: server log files, diagnostic uploads, records of administrative actions
• billing and payment data held by the payment service provider — invoices are provided on request

We do not store raw combat logs on our servers. They stay on your machine and can be used directly from there.

Known limitations

• We are not currently aware of an equivalent service that offers an import of this data. The intended path is therefore a move to your own ICT infrastructure — pulling the files back onto your machine. The desktop app works locally anyway.
• The download addresses are signed and expire after seven days. That is a safeguard, not a restriction of the export: you can mint new ones at any time.

Switching charges

We charge nothing for the export or for switching providers.