---
title: Prepare your data
description: How to prepare and upload your historical selfie base for a Human Token Backtest — image requirements, the CSV format and the SFTP upload.
canonical: https://developer.unico.io/human-token/backtest/prepare-your-data
locale: en
generated_by: markdown-export
---

The Backtest shows how many unique people exist in your historical selfie base and where the duplicates are. To run it, we need two things: **the images** and **a CSV file** describing each one of them. Both are uploaded to our SFTP server.

### 1. SFTP access

Unico will provide you with a username and password for the server `sftp2.acesso.io`, port `22`.

### 2. Prepare the images

- **One selfie per file.**
- **Accepted formats:** JPEG or PNG. Other formats, such as HEIC or WebP, are rejected.
- **Maximum resolution:** 1080x1920 pixels.
- **Up to 1,000,000 images per backtest.**
- File names are up to you, but do not put personal data in them (for example, a national ID number as the file name).

### 3. Build the CSV

A CSV file with a header row and **one row per image**:

| Column | Required | Description |
| --- | --- | --- |
| `client_record_id` | Yes | Your own identifier for the image, unique across the whole file (up to 512 characters). You use it to match the results back to your base |
| `file` | Yes | The image path, relative to the CSV's folder. Example: `images/0001.jpg` |
| `captured_at` | Yes | The exact date and time the selfie was enrolled, with its UTC offset. Example: `2024-03-11T14:05:00-03:00`. A date alone, or a time without an offset, is rejected |
| Other columns | No | Up to 50 columns of your own to break the results down, such as `channel`, `region` or `product`. Each column holds text, a number, a date or true/false |

Example:

```csv
client_record_id,file,captured_at,channel
A-000001,images/A-000001.jpg,2024-03-11T14:05:00-03:00,app
A-000002,images/A-000002.jpg,2024-03-11T14:07:12-03:00,app
A-000003,images/A-000003.png,2024-03-12T09:30:00-03:00,store
```

> **Warning: No personal data in the CSV**
>
> Do not include national ID or tax numbers, names, email addresses or phone numbers in the CSV, including in `client_record_id`.

> **Tip: Why the date matters**
>
> We process the images in the order they were enrolled, as if your base were being built over time. A wrong date changes that order and affects the results.

### 4. Upload to the SFTP server

When you log in, you are already in your own folder. Upload the CSV and the images in this structure:

```text
manifest.csv
images/
├── A-000001.jpg
├── A-000002.jpg
└── ...
```

When the upload is done, let your Unico contact know. We take it from there.

### 5. What happens next

1. **We validate your data:** we check the CSV and look for missing, duplicate or corrupt images. If anything needs fixing, we send you the list of affected rows.
2. **We run the backtest in an isolated environment.** Your base is never searchable in production.
3. **We deliver a PDF report:** how many unique people there are, the duplicates found, and which images were discarded and why (no face, more than one face, invalid file).

### FAQ

**How long does it take?**
It depends on the size of your base. Your Unico contact will give you an estimate once your data has been received.

**What happens to my images afterwards?**
They are deleted within 30 days. This window allows large bases to be reprocessed if needed.

**What if I don't have the exact enrollment time?**
The enrollment date and time are required and must be accurate. Do not fill in a generic time, such as midnight: it changes the processing order and affects the results. If your base does not have this data, talk to your Unico contact before uploading.