Three things pass through the build and are kept afterwards: the brief you write, the chat transcript from the session where the AI puts questions back to you, and the finished site files once the build is done.

The brief

Everything you type into the chat to describe the site you want becomes the brief the AI builds from. It's kept because it's the record of what was asked for, which matters if a question comes up later about what the site was supposed to include.

The chat transcript

The back-and-forth in the chat interface, including any questions the AI asks you to clarify the brief, is kept alongside it. It's the same conversation, just the full version.

The site files

The finished pages the AI builds are kept too, both to host the site and because you're entitled to a copy of them at any point.

Three things sit behind a finished site: the brief you wrote, the chat where you wrote it, and the files the build produced. Each is kept for a reason tied to what it is used for.

The brief

The brief is what the AI builds from, so it is kept for as long as the site it produced is live. If a question ever comes up about why the site looks the way it does, the brief is the record that answers it. Once hosting for that site ends, there is no reason to keep it and it is removed.

The chat transcript

The chat is where the brief was written and refined, so it is kept alongside the brief for the same reason and over the same period. It is not reused for anything beyond that one build.

The finished files

The files are handed over as part of what what you get for the price covers, and once they are yours, they are yours. A copy stays on the server while hosting is active, because that is what makes the site reachable. If hosting is cancelled, that copy is removed, but the files already given to you are not affected by anything happening on the server.

Paying for the build means putting a card into someone else's system. The payment happens through a payment processor, a separate company built to handle card details safely, and it holds the card number, the expiry date and the security code for as long as it needs to process the charge and handle anything like a dispute.

What Scrappy Websites never has

Your card number does not reach Scrappy Websites at any point. The payment processor takes it, checks it and confirms back that the charge went through. What Scrappy Websites keeps on its own side is the record of that confirmation: that a payment was made, for how much, and when, so the build can start and the renewal can be tracked.

Why the split works this way

Handling card data directly means taking on the security standards that come with it, and there is no reason to duplicate work a payment processor already does properly. Keeping card details out of Scrappy Websites' own systems is not a gap in what is collected. It is the setup that keeps the fewest hands on your card details in the first place.