Help centre · Export your data

Export your data

Every section of the export file, the format_version policy, exactly what is deliberately left out and why, and the bookings-only CSV.

Your data is yours, and it comes out whole. This page documents the export file so you can check that for yourself — what every section contains, the small number of things deliberately left out and exactly why, and the version policy that keeps the file honest as the product grows. The binding promise is covenant clause §3; this is the plain-English version of how it is kept.

Getting the file

Go to Settings → Data & privacy and press Export. You get one JSON file. No plan gates it, and it stays available after you cancel — export is not a paid feature, it is your right.
Prefer a spreadsheet? Add ?format=csv to the export URL (or use the CSV link on the same screen) to download just your bookings as a CSV that opens in Excel or Google Sheets. The JSON remains the complete, authoritative record; the CSV is a convenience view of one section.
It downloads directly to your device. We do not email it or stage it anywhere — the file exists only where you save it.

What's in the file

The top-level meta block records the service, the format version, when it was generated, your email, whether the booking history was truncated (only above ten thousand bookings), and a notes list that repeats the exclusions below inside the file itself. The rest is your data, section by section:

profile: Your booking handle(s), display name, avatar URL, your public bio and profile links, and your onboarding progress.
event_types: Every event type in full — duration, location, buffers, minimum notice, booking window, custom questions, colour, round-robin assignment — plus its host pool.
schedules: Your availability schedules with their timezone, the weekly hour rules, and any date-specific overrides.
bookings: Every meeting booked through your links: the invitee's name, email, timezone, notes, and answers to your questions, the times, the status, and the meeting link. Each carries its attendee rows for collective bookings. This is the section the CSV mirrors.
team: Invites you sent, event types you host on for other owners, and the teams you are a member of.
calendar_connections: Metadata for each connected calendar — the Google account, calendar id, granted scopes, and whether a credential is stored. The credential itself is never included (see below).
billing: Your plan, status, seat count, period end, trial end, and Stripe identifiers. Invoices are not here — see below.
marketing_attribution: The first-touch attribution we recorded when your account was created: UTM parameters, any Google Ads click id, referrer, and landing path.
addons: Which add-ons (Call Recorder, CRM) you enabled, and the shape of their connection config — with any secret value redacted (see below).
assistant_thread: Your full transcript with the AI setup assistant, including any proposal you had not yet applied.
churn_responses: Any answers you gave the cancellation survey, in your own words. Returned to you here while your account is live.

What is deliberately left out, and why

Only three classes of data are withheld, each for the same reason: returning it in a file that then lives in a downloads folder, an email, or a support ticket would be a worse leak than anything the export protects.

Credentials. Your Google refresh token and any add-on connection secrets (database strings, API keys) are never exported. The calendar-connection metadata is there; the key that acts on your behalf is not. Add-on config keys are shown with their secret values replaced by a redaction marker, so you can see what was configured without the file carrying a live credential.
Booking management tokens.These are bearer links — whoever holds one can cancel or reschedule that invitee's meeting. Putting them in a downloadable file would hand that power to anything that later reads the file.
Invoices and receipts. Tax and accounting law requires us to keep these, and Stripe already renders them as PDFs. Download them from the billing portal.

Meetings you booked with someone else

The bookings section is the meetings you hosted. A meeting you booked on another Neos Meet host's page belongs to that host's account, not yours — it is their booking record, and it comes out in their export, not this one.

The version policy

meta.format_version is a plain integer. We bump it whenever the shape changes in a way a program reading the file would need to know about — most importantly, whenever we start including a kind of data that a previous version left out. Version 2 added the bio and profile links, the assistant transcript, the cancellation-survey answers, the Google Ads click id, redacted add-on config, and team memberships. A reader that keys off the version can always tell a complete file from an older partial one, and any future addition of user data must move the number — a rule a test in our own codebase enforces, so the export cannot quietly fall behind the database again.

If something looks missing

This page is meant to match the file exactly. If you open your export and something you put into Neos Meet is not in it, that is a bug in our completeness, not a design choice — tell us and we will fix it. That is the whole point of writing the policy down where you can check it.

Still stuck?

Email support@neos.network with your booking link and, if there is one, the exact time an invitee tried to book. A real person reads it — there is no bot in front of us.