Data export and switching

Our register of what you can take with you, in which structures and formats. It forms part of our terms of service.

This version: 7 November 2026 · Copy to save or print

The short version

The workspace owner can download everything at any time, in Settings, Data export.
Records come as one JSON file and files as ZIP, in their original formats.
Every record keeps its ID, so comments, replies, versions and decisions can be connected again elsewhere.
We help you switch, and we charge nothing for it.

How to get your data

Records. In Settings, Data export, press Download records. You get one JSON file for the workspace.
Files. On the same page, download a ZIP for each project. Download them one at a time on a good connection, since a project can be large.
Only the owner. The export covers hidden projects too, which even admins can’t open. Reviewers and members can still download what they have access to, where the link allows it.
Something missing? Write to beratung@mynd.com. If you’ve left or lost access, we provide the export ourselves during the retrieval period.

Formats and standards

What: Records
Format: One UTF-8 JSON document
Standard: JSON (RFC 8259), Unicode

What: Times
Format: Text, always in UTC, for example 2026-11-07T09:30:00.000Z
Standard: ISO 8601

What: File archive
Format: ZIP with stored, uncompressed entries, using ZIP64 above 4 GB
Standard: PKWARE ZIP application note

What: Files
Format: Exactly as uploaded: for example MP4, MOV, PDF, DOCX, PNG, JPEG, WebP, MP3, ZIP
Standard: The formats themselves

What: Courses
Format: The ZIP you uploaded, unchanged
Standard: SCORM or HTML, as uploaded

What: Comment positions
Format: x and y from 0 to 1, across the width and down the height of the page or frame
Standard: Our own, described here

What: Drawings
Format: kind plus points or corners from 0 to 1, with color and line width
Standard: Our own, described here

What: Video and audio time
Format: timeMs, in milliseconds from the start
Standard: Our own, described here

What	Format	Standard
Records	One UTF-8 JSON document	JSON (RFC 8259), Unicode
Times	Text, always in UTC, for example 2026-11-07T09:30:00.000Z	ISO 8601
File archive	ZIP with stored, uncompressed entries, using ZIP64 above 4 GB	PKWARE ZIP application note
Files	Exactly as uploaded: for example MP4, MOV, PDF, DOCX, PNG, JPEG, WebP, MP3, ZIP	The formats themselves
Courses	The ZIP you uploaded, unchanged	SCORM or HTML, as uploaded
Comment positions	x and y from 0 to 1, across the width and down the height of the page or frame	Our own, described here
Drawings	kind plus points or corners from 0 to 1, with color and line width	Our own, described here
Video and audio time	timeMs, in milliseconds from the start	Our own, described here

What’s in the records

The file’s top level holds format (wunderblick-workspace-export), formatVersion (now 1), exportedAt, and the sections below. A section is a list of records, and records point at each other by ID.

Section: workspace
What it holds: One object
Fields: id, name, slug, plan, trialEndsAt, createdAt, logo (mimeType and base64 data, or null)

Section: users
What it holds: People named anywhere in the export, including those who have left
Fields: id, name, email

Section: members
What it holds: Who belongs to the workspace
Fields: id, userId, role (OWNER, ADMIN, MANAGER, EDITOR), status, createdAt

Section: invites
What it holds: Invitations
Fields: id, email, role, invitedById, status, expiresAt, acceptedAt, createdAt

Section: tags
What it holds: Project tags
Fields: id, name, color, createdAt

Section: projectTemplates
What it holds: Project templates
Fields: id, name, createdAt, folders, layers, tags

Section: projects
What it holds: Projects
Fields: id, name, description, stealth, storeInGermany, archivedAt, approvedAt, approvedById, createdById, createdAt, updatedAt, tagIds, managerUserIds, memberUserIds

Section: folders
What it holds: Folders within a project
Fields: id, projectId, parentFolderId, name, kind (REVIEW, TRANSFER), position, approvedAt, approvedById, createdAt, updatedAt

Section: transferLinks
What it holds: File-transfer links, without their secret part
Fields: id, folderId, expiresAt, hasPassword, requireEmail, allowUpload, downloadCount, lastDownloadAt, revokedAt, createdById, createdAt

Section: files
What it holds: Files
Fields: id, projectId, folderId, name, position, status (IN_REVIEW, CHANGES_REQUESTED, APPROVED), statusUpdatedAt, approvedAt, approvedById, createdAt, updatedAt

Section: versions
What it holds: Each uploaded version of a file
Fields: id, fileId, versionNumber, uploadedById, uploadedByLabel, sourceType (R2_UPLOAD, EXTERNAL_URL), mimeType, sizeBytes, kind (IMAGE, VIDEO, AUDIO, PDF, DOC, SCORM, SLIDESHOW, WEBSITE, OTHER), width, height, durationMs, frameRate, pageCount, slides, scormEntryPath, ready, createdAt, externalUrl, storedIn, exportPath, slidesAreOriginals

Section: reviewLayers
What it holds: Review layers, without their secret part
Fields: id, projectId, name, position, allowDownload, allowUpload, hasPassword, showVersionHistory, allowCopyComments, allowCrossLayerView, requireEmailVerification, expiresAt, revokedAt, createdById, createdAt, updatedAt

Section: layerReviewers
What it holds: Reviewers in a layer
Fields: id, layerId, guestId, email, name, createdAt, lastSeenAt

Section: reviewCells
What it holds: One version in one layer: the review of it
Fields: id, layerId, fileVersionId, state, createdById, createdAt, updatedAt

Section: reviewDecisions
What it holds: Each person’s status on a review
Fields: id, cellId, layerReviewerId, userId, decision, createdAt, updatedAt

Section: reviewLinks
What it holds: Older per-file review links, without their secret part
Fields: id, fileId, name, createdById, expiresAt, hasPassword, allowDownload, versionId, showVersionHistory, revokedAt, createdAt

Section: linkReviewers
What it holds: Reviewers on those links
Fields: id, reviewLinkId, guestId, email, name, emailVerifiedAt, createdAt, lastSeenAt

Section: revisionLinks
What it holds: Links for designers, without their secret part
Fields: id, fileId, createdById, expiresAt, hasPassword, allowDownload, allowUpload, showVersionHistory, revokedAt, createdAt, reviewLinkIds

Section: designers
What it holds: People on those links
Fields: id, revisionLinkId, guestId, email, name, createdAt, lastSeenAt

Section: guests
What it holds: External people known to the workspace
Fields: id, email, name, emailVerifiedAt, createdAt, lastSeenAt

Section: agreements
What it holds: Who accepted which versions of the terms and data processing agreement
Fields: id, userId, email, userName, company, termsVersion, dpaVersion, source, acceptedAt, confirmedAt

Section: comments
What it holds: Comments and replies, including hidden ones (deletedAt set)
Fields: id, fileVersionId, reviewCellId, reviewLinkId, parentId, userId, reviewerId, layerReviewerId, body, status (OPEN, RESOLVED), internalOnly, pageIndex, timeMs, x, y, slideKey, priority, pinnedAt, createdAt, updatedAt, editedAt, deletedAt, annotations, likes, mentions, attachments

Section: aiBriefs
What it holds: AI briefs, as their text, without the link’s secret part
Fields: id, fileVersionId, reviewCellId, createdById, payload, expiresAt, revokedAt, openCount, lastOpenedAt, createdAt

Section: activity
What it holds: The activity log
Fields: id, actorUserId, subjectType, subjectId, verb, metadata, createdAt

Section	What it holds	Fields
`workspace`	One object	id, name, slug, plan, trialEndsAt, createdAt, logo (mimeType and base64 data, or null)
`users`	People named anywhere in the export, including those who have left	id, name, email
`members`	Who belongs to the workspace	id, userId, role (OWNER, ADMIN, MANAGER, EDITOR), status, createdAt
`invites`	Invitations	id, email, role, invitedById, status, expiresAt, acceptedAt, createdAt
`tags`	Project tags	id, name, color, createdAt
`projectTemplates`	Project templates	id, name, createdAt, folders, layers, tags
`projects`	Projects	id, name, description, stealth, storeInGermany, archivedAt, approvedAt, approvedById, createdById, createdAt, updatedAt, tagIds, managerUserIds, memberUserIds
`folders`	Folders within a project	id, projectId, parentFolderId, name, kind (REVIEW, TRANSFER), position, approvedAt, approvedById, createdAt, updatedAt
`transferLinks`	File-transfer links, without their secret part	id, folderId, expiresAt, hasPassword, requireEmail, allowUpload, downloadCount, lastDownloadAt, revokedAt, createdById, createdAt
`files`	Files	id, projectId, folderId, name, position, status (IN_REVIEW, CHANGES_REQUESTED, APPROVED), statusUpdatedAt, approvedAt, approvedById, createdAt, updatedAt
`versions`	Each uploaded version of a file	id, fileId, versionNumber, uploadedById, uploadedByLabel, sourceType (R2_UPLOAD, EXTERNAL_URL), mimeType, sizeBytes, kind (IMAGE, VIDEO, AUDIO, PDF, DOC, SCORM, SLIDESHOW, WEBSITE, OTHER), width, height, durationMs, frameRate, pageCount, slides, scormEntryPath, ready, createdAt, externalUrl, storedIn, exportPath, slidesAreOriginals
`reviewLayers`	Review layers, without their secret part	id, projectId, name, position, allowDownload, allowUpload, hasPassword, showVersionHistory, allowCopyComments, allowCrossLayerView, requireEmailVerification, expiresAt, revokedAt, createdById, createdAt, updatedAt
`layerReviewers`	Reviewers in a layer	id, layerId, guestId, email, name, createdAt, lastSeenAt
`reviewCells`	One version in one layer: the review of it	id, layerId, fileVersionId, state, createdById, createdAt, updatedAt
`reviewDecisions`	Each person’s status on a review	id, cellId, layerReviewerId, userId, decision, createdAt, updatedAt
`reviewLinks`	Older per-file review links, without their secret part	id, fileId, name, createdById, expiresAt, hasPassword, allowDownload, versionId, showVersionHistory, revokedAt, createdAt
`linkReviewers`	Reviewers on those links	id, reviewLinkId, guestId, email, name, emailVerifiedAt, createdAt, lastSeenAt
`revisionLinks`	Links for designers, without their secret part	id, fileId, createdById, expiresAt, hasPassword, allowDownload, allowUpload, showVersionHistory, revokedAt, createdAt, reviewLinkIds
`designers`	People on those links	id, revisionLinkId, guestId, email, name, createdAt, lastSeenAt
`guests`	External people known to the workspace	id, email, name, emailVerifiedAt, createdAt, lastSeenAt
`agreements`	Who accepted which versions of the terms and data processing agreement	id, userId, email, userName, company, termsVersion, dpaVersion, source, acceptedAt, confirmedAt
`comments`	Comments and replies, including hidden ones (deletedAt set)	id, fileVersionId, reviewCellId, reviewLinkId, parentId, userId, reviewerId, layerReviewerId, body, status (OPEN, RESOLVED), internalOnly, pageIndex, timeMs, x, y, slideKey, priority, pinnedAt, createdAt, updatedAt, editedAt, deletedAt, annotations, likes, mentions, attachments
`aiBriefs`	AI briefs, as their text, without the link’s secret part	id, fileVersionId, reviewCellId, createdById, payload, expiresAt, revokedAt, openCount, lastOpenedAt, createdAt
`activity`	The activity log	id, actorUserId, subjectType, subjectId, verb, metadata, createdAt

Inside a comment:

annotations: kind (PEN, ARROW, RECT, HIGHLIGHT), geometry, createdAt
likes and mentions: who (userId, reviewerId or layerReviewerId), createdAt
attachments: id, url, fileName, mimeType, sizeBytes, isSlideSnapshot (a screenshot saved with the comment), createdAt, exportPath

Connecting it all again

A reply’s parentId is the comment it answers. A comment’s fileVersionId is the version it was made on, and reviewCellId or reviewLinkId says in which review.
A comment’s author is one of userId (a team member, in users), layerReviewerId or reviewerId.
A version’s exportPath, and an attachment’s, is the file’s path inside the project’s ZIP. A path ending in a slash is a folder of slideshow images, in slide order. slidesAreOriginals says whether they are the images as uploaded or the converted ones, for older slideshows.
Files added by link and reviewed websites have no exportPath, since we never stored them. Their externalUrl is what you gave us.
IDs stay the same from one export to the next, so a later export can be matched against an earlier one.

What’s left out

This list is complete, and section 9 of the terms says the same.

Left out: Security data: password hashes, sessions, one-time codes, and the secret part of links and their passwords
Why: Passing them on would endanger your accounts and links, and no other system could use them. Whether a link has a password is included.

Left out: Internal running data: server logs, rate-limit counters, background job states, our references to payment and video providers
Why: They say nothing about your work and are specific to how Wunderblick runs.

Left out: Copies we make from your files: thumbnails, playback copies of video and audio, audio waveforms, unpacked courses, converted slides where the originals were kept, AI brief screenshots
Why: The originals hold everything they contain. If your new system needs them, ask us and we provide what we can.

Left out	Why
Security data: password hashes, sessions, one-time codes, and the secret part of links and their passwords	Passing them on would endanger your accounts and links, and no other system could use them. Whether a link has a password is included.
Internal running data: server logs, rate-limit counters, background job states, our references to payment and video providers	They say nothing about your work and are specific to how Wunderblick runs.
Copies we make from your files: thumbnails, playback copies of video and audio, audio waveforms, unpacked courses, converted slides where the originals were kept, AI brief screenshots	The originals hold everything they contain. If your new system needs them, ask us and we provide what we can.

Limits you should know about

Older files. A file whose record says it was stored but which isn’t there any more is listed in MISSING.txt in the ZIP.
Other systems. No other review tool reads this format directly, so moving comments into one takes a small conversion. We help with that within reason.
Personal data. The records hold names and email addresses, so they are yours to protect once downloaded.

Switching to another provider

Tell us in text form at beratung@mynd.com. You don’t need to give any notice. Say whether you’re moving to another provider, to your own systems, or just want your data erased.
The transition takes up to 30 days. The service keeps running and we help within reason. If 30 days are technically not possible, we tell you within 14 working days and name a period of up to 7 months.
You have at least 30 days after that to retrieve your data.
We then fully erase your data, and backups age out within 30 days. We confirm it on request.

There are no switching fees. The legal details are in section 9 of the terms. Where your data is and who could access it is on our security page. Questions about personal data can also go to our data protection officer, dsb@datenschutzexperte.de.