Data formats and export

How to download your data

A studio's owner and admins download the full package under Settings → Studio export. After a studio is deleted, its owner can still download the package during the retention period described in the privacy policy.

A team member downloads a narrower package with their own share of the work (its scope is described below).

The package is several ZIP files, and you download each part separately. We keep a prepared package on our servers for a limited time; you see the date under Settings → Studio export.

Your own account data (sign-in methods, sessions, messages sent to your address) is downloaded separately under Account → Data and privacy.

What the package consists of

Part one: the studio-export.json document with all the data, the CSV sheets in the csv/ directory and a README.txt file explaining the package.

Every further part holds the files of one project, in the media/ directory. A project whose files are very large is split into several parts. No file is left out because of its size.

Every part's name carries its number and the number of parts in all, and the index in the document lists every part of the package.

A file that could not be read from storage when the package was prepared is listed in the document as unavailable.

When a studio's data goes beyond what we can prepare automatically, you are not handed an incomplete copy: preparing it ends with a message, and we prepare the data by hand when you ask us to.

Data categories

The studio-export.json document has one section for each of the categories below.

• studio: The studio: name, the date it was founded, and invitations sent to the team.
• team: The team: who belongs to the studio, with what role, permissions and since when, together with each person's first name, last name and email address.
• clients: The studio's clients: name, contact details, company, tax ID and notes. Only in the studio's full package.
• projects: Projects: name, client, address, status, stages, tasks, rooms, who is assigned, and which tools are turned on, plus the studio's project templates.
• brief: Each project's brief: the client's answers in readable form together with the raw record, inspirations and the equipment list, plus the send history: every version of the brief exactly as it looked at the time. Photos are in the "media" directory.
• publications: Materials for the client (space planning, concept design and technical drawings): rounds, the files in them, when they were shared, the client's feedback, comments, approvals (with the chosen variant) and when the client opened the presentation.
• consultations: Consultations and the calendar: the studio's availability settings, booked meetings, including cancelled ones (with the reason shown to the client) and rescheduled ones, plus the studio's and projects' calendar entries.
• survey: The site survey: survey packages, room records, gaps, documentation sources, existing conditions and the history of changes.
• files: Project files: name, kind, size, versions and dates. The files themselves (each version separately) are in this archive's "media" directory.
• shoppingList: Shopping lists: products, prices, quantities, statuses and links to shops. Product photos are in the "media" directory.

A team member's package

This package contains your share of the work in this studio. It is narrower than the export the owner downloads. Below is exactly how.

• It has only the projects you are assigned to. Studio projects you are not part of are not named here, not even by a single field.
• There is no "clients" section. The studio's clients' contact details (address, phone, company, tax ID, notes) belong to the studio and do not leave it. What stays on the project is just the client's name, exactly as you see it in the app.
• There are no invitations the studio sent: that is its own record, not yours.
• Booked consultations concern only your projects.
• Files in the "media" directory are files of those same projects. There is nothing there from projects you cannot see in the app.

Formats

JSON document

All the data is in one JSON document, with an index (the manifest) at the start: the schema version (5), the list of sections with their sources, the list of exclusions with reasons and the list of the package's parts.

CSV sheets

Encoding

UTF-8 with a byte-order mark

Separator

comma (,)

Decimal mark

point (1234.56)

• The CSV files are a convenience, not a second copy of the data. The complete package is the studio-export.json document. The sheets hold only the parts that really are a table.
• Briefs, concepts and surveys are not in the sheets: they are nested structures, and spread over rows they would be a worse copy of themselves than the one in the document.
• The encoding and separator are chosen so the file opens correctly in Excel with English settings: every letter reads correctly, the columns are separated and numbers use a decimal point.
• Cells starting with =, +, - or @ get a leading apostrophe so the spreadsheet treats them as text. Numbers are not affected: a price of -12.50 stays a number.

Files

A file's path in the package: {project part}/media/{kind}/{number}-{name}

• Project files: every version separately, exactly as uploaded.
• Inspiration and equipment photos from the brief, uploaded by you and by the client.
• Product photos from the shopping lists.

• Inspiration, equipment and product photos are stored converted to WebP (inspirations and equipment: at most 1920 px). We do not keep the originals, so the package holds exactly what we have.
• Project files are in the package byte for byte as they were uploaded.
• Directory and file names inside the archive are reduced to ASCII so they open correctly on any system. The original name of every file is in the “media” section.
• The package is split into parts: part 1 holds the documents and spreadsheets, every further part holds the files of one project. The “part” field of each file says which part it is in.
• No file is left out for its size. A file we could not read is not in the archive; the “media” section names it in its “omitted” list with its name, size and the reason.

What the export deliberately leaves out

Each exclusion has a reason recorded in the code and in the index of every package.

• Passwords and sign-in data. Passwords, session tokens and encryption keys are keys to accounts, not studio data. A copy of them in a file on disk would be a working way into the application.
• Active client links. Links sent to clients (the brief, the project portal, an invitation) work without signing in. The package never contains them, because otherwise it would be a key to your clients' data. Instead of the token we record only whether the link exists.
• Team members' private account data. A team member's own account data: sign-in methods, password, sessions and messages sent to their address. It belongs to that person, not to the studio, and everyone downloads their own in Account → My data.
• Internal application mechanisms. A technical record of the application working (queues, retries, file cleanup). It says nothing about the studio beyond what the other sections already say.
• Technical fields. A technical field: a concurrency marker, an idempotency key, or a repeat of data already in another section.
• Derived data. In-app notifications are built from events that are already in the package, and they carry no per-person "read" state. Nothing is lost by leaving them out.
• Thumbnails and working copies. Thumbnails and shrunk copies of images. They are the application's own working files, not something anyone uploaded. The "media" directory holds every image at the largest size we have.
• Thumbnails and reduced versions. They are the app's working copies, not a file anyone uploaded. Every image is in the package at the largest size we keep.
• Images from conversations with Projado support. They belong to the person who sent them, not to the studio. That person finds them in their account export and in the Help panel.

Good to know

• This package holds the studio's data: projects, briefs, concepts, surveys, shopping lists, clients and the team. Your own account data is downloaded separately under Account → My data.
• It contains no working client link. Where a link exists we record only whether it is active, never the address or the token itself.
• Files and photos the studio uploaded are in the “media” directory, and the “media” section of this document says which file belongs to which entry.
• Data about clients and people who sent in documentation is personal data of third parties. Your studio is its controller. Keep this package responsibly.

The package reflects the data as it stood when preparation started (the snapshotAt field) and may not include changes made while it was being prepared. Each module was read in one transaction, so the data within a section is consistent.