# Exporting all your data

> Download a complete copy of everything Session holds for your venue in one file, any time, without asking us - and what happens to your data and money if Session stopped.

Who can do this: admins only.

One **Download export** button produces a file with every booking, customer and signed waiver, your whole schedule, your prices and your settings. It's at the bottom of [Settings → Data](/go/admin/settings/data), under [importing data](/docs/import).

<Screenshot
  alt="The Export data section on Settings, Data, showing a Download export button"
  caption="Export data sits under Import data on Settings → Data"
  mat="cream"
/>

## Download your data

<Steps>
<Step>
Open [Settings → Data](/go/admin/settings/data), scroll to **Export data** and select **Download export**. There's nothing to set - the file always contains everything.
</Step>
<Step>
Wait while the file is built (up to a minute for a busy venue). It saves as a `.zip` named with your venue and today's date; double-click it to open the folder.
</Step>
</Steps>

Only Admins can export, because the file contains every customer's contact details and signed waivers - see [admin and staff roles](/docs/team). Each download is recorded in your account's activity history.

## What's in the file

- **`csv/`** - spreadsheets with one row per booking, customer, session, signed waiver and so on, for an accountant, insurer or new booking system.
- **`waivers/`** - the wording of every waiver your customers agreed to, as text files.
- **`json/`** - one file per database table, every field exactly as stored, for a developer or another system's importer.
- **`README.md`** - a contents page listing every file and its row count.

## Signed waivers

`csv/waiver-signatures.csv` shows who signed, when, and what they agreed to, covering waivers signed per booking and per guest, and links each row to the text in `waivers/`. Three limits:

- **The signature drawing isn't in the file.** The row says `Signature captured: Yes`; ask us and we'll get you the image.
- **Only the current wording of each waiver is stored.** If you've edited a waiver since someone signed, that row's text link is blank.
- **Waivers signed once per booking weren't recorded against a session.** Where the booking shows it, the row says `Matched by pinned waiver` - a strong inference rather than a record.

## What's left out

- **Security tokens and API secrets** - booking manage-links, waiver-signing links, webhook signing secrets and API keys.
- **Identifiers that only mean something inside Session.**
- **Survey answers collected by another venue** for a customer you share.
- **Your images.** Logos, header images and session pictures aren't included; the `json/` files record their web addresses.

## If Session stopped

- **Your money settles in your own Stripe account.** Session never holds it, and your payment history, payouts, saved cards and live membership subscriptions stay in Stripe. See [connecting Stripe](/docs/connect-stripe).
- **Your data is this export**, which you can take today without asking anyone.
- **The platform runs without anyone at our end**, on managed infrastructure (Vercel, [Supabase](/docs/data-protection), Stripe and Clerk). A second person holds full access to the code and every platform account. The database has daily backups plus an independent weekly copy with a different provider.

Our [Data Processing Agreement](/dpa) puts this in writing:

- **Section 10.4** - if Session ever stops providing the platform, you get at least **90 days' notice** and a complete export available throughout.
- **Sections 10.1 to 10.3** - you can export at any time during your term and for **30 days** after it ends. After that your data is deleted, apart from booking and payment records kept for tax (up to 7 years).
- **Section 13** - business continuity: the second person's access, the off-platform backup, and that we never hold your funds.

## Common questions

1. **What is the hardest thing to replace if we move?** Your booking page address at `bookasession.org/your-venue`, which posters, QR codes and search results point at.

2. **Can I export just one location or one date range?** No, this is always everything, for all time. Use the [CSV exports on Reports](/docs/csv-exports) for a date range or location; its bookings and attendance files are the same shape.

3. **Could another booking system read this?** The `json/` folder is a complete, structured copy designed for that, but it depends on the system.