M
M
e
e
n
n
u
u
M
M
e
e
n
n
u
u
M
M
e
e
n
n
u
u
M
M
e
e
n
n
u
u

09

Data

Data commitments

Version 2026-10-16

Checked against the code

The data agreement every engagement signs before real data connects, the two approvals needed to go live, and Siege's commitments on use, retention, breach notice and export.

01

01

No real data before the agreement

Every client contract carries a data agreement, and it is signed before any real client data connects to the system. Until then the system runs on sample data only. Going live on real data needs two yeses: one from a person the client names, and one from Siege. Either party can withhold its yes, and each yes is given in writing and kept with the contract.

No real data before the agreement: sample data only, the data agreement signed before any real client data connects, a yes from a person the client names and a yes from Siege, then going live on real data.

02

02

What the agreement sets

Clause

What it sets

Scope

Which kinds of data the system may hold, and their fields

Location

The hosting provider and region of the database, file storage and backups

Access

Who at Siege may reach client data, for what purpose, and how each access is granted and removed

Security

The controls on the Security and control page

AI

Each AI feature turned on, and only the fields each one needs, listed for the client’s review

Use

Client data serves the client only

Retention and deletion

How long data, backups and logs are kept, and how data is deleted on the client’s written request

Breach notice

How quickly Siege tells the client of a breach, and what the notice contains

Export

How the client takes a full copy of its data and its model

The agreement is a schedule to the contract. Changing it, for example to turn on a new AI feature or move data to a new region, needs both parties.

03

03

Siege's commitments

Term

Commitment

Use

Client data is used only to serve the client. Siege never sells or shares it, never uses it for another client, and never uses it to train a model. The client’s own AI provider account is set so the provider does not keep or train on what is sent.

Breach notice

Within 72 hours of Siege becoming aware of a breach that affects the client’s data, backed by an incident runbook and uptime alerting (see Security and control).

Retention

The client’s data lives in the client’s own system and stays the client’s. Source data the client hands Siege for a move or a clean-up is purged when the work it was for is accepted, or sooner if the client asks, and any copy Siege holds is deleted within 30 days after the engagement or license ends.

Export

An administrator can take a full copy of the client’s data from the system at any time, in open formats, without asking Siege.

Book a call
Your move

The new world will not wait.

Tell us what you mean to build, and we will tell you plainly what it would ask of you.

By sending, you agree to our Terms and Privacy Policy.

By sending, you agree to our Terms and Privacy Policy.

By sending, you agree to our Terms and Privacy Policy.