Export your organization's data
Version 1.0, of October 30, 2026.
Your data belongs to your organization. You can ask us for a copy at any time, free of charge, including to switch to another provider. Below we say what it includes and what it does not.
Who can request it and how
- An owner of the organization requests it by writing to privacy@founderfold.com from their account email, giving the name of the organization.
- If we have reasonable doubts about who is making the request, we may ask for confirmation by another means before preparing the export.
- You can request it while you use FounderFold, during the notice period for cancellation, during the transition period and for at least 30 days afterwards (terms, clause 13).
Timing and delivery
- We prepare it and deliver it to you within a maximum of 10 working days from your request.
- We send it to your account email, in a compressed and encrypted file. We give you the password through a separate channel.
- We do not charge for the export or for switching provider.
What you receive
A folder with:
- one JSON file for each type of data in the list below, with all your organization's rows;
- a
manifiesto.jsonfile that states when it was generated, which organization it is, how many rows there are of each type and, if anything is missing, why; - in the
capturas/folder, the screenshots from conversations that are still retained (they are kept for 30 days); - if a portfolio works with a repository, its files with their history, in a separate git file.
Reports are not included as PDFs in the export: you can download them as PDFs from the panel while you have access.
What data it includes
- Portfolios, ideas, projects, experiments and their records, with their history.
- Documents.
- Saved reports and their versions, tags, favourites and who they have been shared with, and the sends to people outside your organization, with their email.
- Conversations with the AI and their messages. Messages drafted by the AI carry a machine-readable mark with their origin, the model and the date.
- The configuration of the organization, of its brand and of its agents, with their own instructions and their versions.
- The Explorer's configuration, its rounds and its memory of what it has already seen, while they are retained.
- The organization's activity log and the tasks, with their events.
- The AI usage of each call: date, origin, model and tokens. Who made it, only if the per-person breakdown was switched on at that time and while that data is retained.
- Members, their roles, their profiles and the invitations that are still retained.
- Connector and team tokens: their name and their dates, without their hash.
- Acceptances of the terms and of the data processing agreement.
The owner who requests it receives it. If you use the per-person usage data it contains, clause 9.4 of the terms applies.
What it does not include
- Passwords and token hashes (hash), which are never exported.
- The internal cost in dollars of the AI and of the Explorer's rounds.
- Each person's private usage log.
- Who made each AI call, outside the per-person breakdown when switched on.
- Technical and security logs.
- FounderFold Expert's improvement signals, which are not your organization's data.
- FounderFold's own components: templates, catalogues, manual and the Explorer's list of excluded domains.
- Earlier versions of project documents, notices, weekly follow-ups, updates and in-depth analyses.
- The key people of candidate companies, for whom we are the controller.
- Billing data.
Format
The files are JSON, an open, machine-readable format. Each file is named after the type of data it contains and each row keeps its identifiers, so that the relationships between files (for example, a conversation and its messages) can be rebuilt. Each row carries its fields as they are stored, except for what this page says is not included.
File structure
| Files | What they contain |
|---|---|
manifiesto.json | formato, version, generado (date), organizacion (id, slug, nombre), filas (how many there are in each file) and notas (among them, whether the export is incomplete and why) |
organizaciones.json, organizaciones_marca.json | The organization, its colour and its logo |
miembros.json, perfiles.json, invitaciones.json | Members and their roles, their profiles and the invitations that are still retained |
carteras.json, documentos.json | Portfolios and, with their full content, their documents: idea, project and experiment records, portfolio and Explorer configuration and all other documents |
agentes.json, agentes_organizacion.json, agentes_conversacion.json, agentes_conversacion_versiones.json | The agents of each portfolio and of the organization, with their own instructions and their versions |
conversaciones.json, conversacion_mensajes.json, conversacion_capturas.json | Conversations, their messages and the screenshots that are still retained; their files are in capturas/ |
encargos.json, encargo_eventos.json | Tasks and their events |
informes_guardados.json, informes_versiones.json, informes_etiquetas.json, informes_favoritos.json, informes_compartidos.json, informes_envios.json | Saved reports, their versions, tags and favourites, who they have been shared with and their sends |
explorador_rondas.json, explorador_visto.json | The Explorer's rounds and its memory of what it has already seen |
actividad.json, cierres_paso.json, planes_paso.json, peticiones_refresco.json | The activity log, the closures and plans of steps and the refresh requests |
consumo_ia.json | The AI usage of each call |
tokens_conector.json, tokens_equipo.json | Connector and team tokens, without their hash |
aceptaciones_legales.json | Acceptances of the terms and of the data processing agreement |
After the export
If you cancel, when the export period ends we delete all your organization's data, including at our providers and in backups, within a maximum of 90 days, except what the law requires us to keep. If you ask, we certify this to you in writing.