The short version
We collect what we need to run a marketplace that holds money: who you are, what you commissioned, and where to send it. We do not sell personal information.
Analytics is optional and you control it on Your Privacy Choices. We honour Global Privacy Control automatically.
You can ask for a copy of your data or ask us to delete it at Your data. We cannot delete records of money that moved between you and somebody else, and the table below says exactly which those are.
This summary is here to help you find things. It is not the agreement, and where it differs from the text below, the text below is what applies.
1 Who is responsible
KOMPLETE ASSEMBLY LLC decides how and why your information is used on Komplete Assembly. Our registered address is 1096 Inwood Ter, Fort Lee, NJ 07024. Write to help@kompleteassembly.com about anything on this page.
We do not currently operate in Europe. Builders in the EEA, the UK and Switzerland cannot yet be paid here, and we do not run analytics on visitors from those 33 places at all: not with consent, not with a banner. If that changes we will appoint the representatives those regimes require and update this page before opening.
2 What we hold, and why
This table is generated from the same record the software itself uses to decide what to export and what to delete. It is not a description written beside the system; it is the system.
| What | Why we may | How long |
|---|---|---|
| Your account | ||
| Name, email, password hash, the country they say they are in, their language and theme preferences, the time zone their browser reports (so dates read in their local time), which staff powers they have, and their customer id at Stripe. | To provide what you asked for | Tombstone kept while any order, payout or dispute referencing it is retained. |
| The @name a person is addressed by, including retired ones. | To keep the marketplace safe and working | Indefinite. The handle survives; what it points at no longer identifies anybody. |
| IP address, user agent, and the signed-in session. | To provide what you asked for | Until the session expires. |
| An email address and a short-lived token. | To provide what you asked for | Minutes. Expired rows are swept. |
| A saved postal address: recipient, street, city, postcode, phone. | To provide what you asked for | Until deleted by the person. |
| What somebody agreed to be tracked with, and when. | Because you agreed, and you can change that | Until the choice changes or the account goes. |
| Which notices a person wants. | To provide what you asked for | While your account is open. |
| Threads and people somebody has muted. | To provide what you asked for | While your account is open. |
| A record that somebody was stopped from selling, buying or posting, and why. | To keep the marketplace safe and working | Kept. It points at the anonymised user row, so it describes conduct rather than a person. |
| A staff power somebody was granted, who granted it, and when it was taken away. | To keep the marketplace safe and working | Kept. It points at the anonymised user row, so it describes a grant rather than a person. |
| Notices sent to a person, and who caused each one. | To provide what you asked for | While your account is open. |
| A request to see, correct or delete data: the address it came from and what was done. | Because the law requires us to keep it | Two years, which covers the window for a complaint about how it was handled. |
| A message sent through the contact form: a name, an address, what it was about and what was written. | To keep the marketplace safe and working | Two years, or until the person asks for it to go. |
| A country somebody is waiting for us to open. | Because you agreed, and you can change that | While your account is open. |
| What you commissioned | ||
| A funded commission: amounts, both parties, and the shipping address. | Because the law requires us to keep it | Seven years after completion, for tax and chargeback windows. |
| The stages of an order and what each was worth. | Because the law requires us to keep it | With the order. |
| A rating out of five and what one party to a finished order said about the other. | To provide what you asked for | The rating stays with the order record. The words go. |
| A builder submitting work for approval, with a note. | To provide what you asked for | With the order. |
| Photographs attached to a submission. | To provide what you asked for | With the order. |
| Photographs of a kit as it arrived. | To provide what you asked for | With the order. |
| Photographs a buyer took of their own kit, packed, before sending it to the builder. | To provide what you asked for | With the order. |
| The carrier and tracking number of a replacement a builder sent after a reported problem. | To provide what you asked for | With the order. |
| A brief: what somebody wants built, and their notes. | To provide what you asked for | While your account is open. |
| Reference photographs attached to a brief. | To provide what you asked for | While your account is open. |
| A builder's offer: amounts, terms, and revisions. | To provide what you asked for | With the order it produced, or two years if never accepted. |
| The stages a quote proposed. | To provide what you asked for | While your account is open. |
| Photographs a builder attached to their answer on each task of a brief. | To provide what you asked for | While your account is open. |
| A builder holding stock for a quote. | To provide what you asked for | While your account is open. |
| Money | ||
| A double-entry transaction grouping. | Because the law requires us to keep it | Seven years. |
| Individual debits and credits, by account and order. | Because the law requires us to keep it | Seven years. |
| Money paid to a builder, and who approved it. | Because the law requires us to keep it | Seven years. |
| Money held against future chargebacks, taken from a release (or, before 2026-10-11, a payout). | Because the law requires us to keep it | Seven years. |
| A card dispute raised against an order or a tip. | Because the law requires us to keep it | Seven years. |
| A tip between two people, with an optional note. | Because the law requires us to keep it | Seven years. |
| The link to a Stripe connected account and what it can do. | Because the law requires us to keep it | Seven years. |
| Stripe webhook payloads, kept so an event is handled once. | Because the law requires us to keep it | Ninety days. |
| Disputes | ||
| A dispute between a buyer and a builder, and how it ended. | Because the law requires us to keep it | Seven years. |
| Every step taken in a dispute, and by whom. | Because the law requires us to keep it | With the dispute. |
| Photographs attached to a statement in a dispute. | Because the law requires us to keep it | With the dispute. |
| What you publish | ||
| A builder's public page: display name, headline, bio, country. | To provide what you asked for | While your account is open. |
| A Kommunity profile: bio, location, picture. | To provide what you asked for | While your account is open. |
| What a builder offers, in their own words. | To provide what you asked for | While your account is open. |
| Photographs on a listing. | To provide what you asked for | While your account is open. |
| Work a builder chose to show, and where it came from. | To provide what you asked for | While your account is open. |
| A Kommunity post: title, body, and who wrote it. | To provide what you asked for | While your account is open. |
| Machine and human translations of what somebody wrote. | To provide what you asked for | While your account is open. |
| Photographs on a post. | To provide what you asked for | While your account is open. |
| A comment, and who wrote it. | To provide what you asked for | While your account is open. |
| Who follows whom. | To provide what you asked for | While your account is open. |
| The name, description, price and perks of a tier a Kreator defined. | To provide what you asked for | While your account is open. |
| A stored still for each video anybody has embedded, so no reader ever asks the provider for one. | To keep the marketplace safe and working | While your account is open. |
| Every announcement a Kreator sent to their followers, and how many people it reached. | To keep the marketplace safe and working | While your account is open. |
| Which posts somebody has opened, so their feed can grey what they have read. | To provide what you asked for | While your account is open. |
| The small pictures a Kreator made for their members to type in comments. | To keep the marketplace safe and working | While your account is open. |
| A themed sheet of stickers somebody published to the library. | To keep the marketplace safe and working | While your account is open. |
| One picture on a sheet. | To keep the marketplace safe and working | While your account is open. |
| Which comments somebody liked. | To provide what you asked for | While your account is open. |
| Which posts somebody liked. | To provide what you asked for | While your account is open. |
| A daily record of a Kreator reach, engagement and standing. | To provide what you asked for | While your account is open. |
| The level a Kreator holds, whether they are verified, and any operator override. | To provide what you asked for | While your account is open. |
| Which posts somebody saved for later. Private to them. | To provide what you asked for | While your account is open. |
| Uploaded photographs, their original filenames, and who uploaded them. | To provide what you asked for | While your account is open. |
| Bidding | ||
| A maximum somebody was willing to pay, and where they would have had it sent. | To provide what you asked for | Kept while the auction it belongs to is retained. |
| The starting price, reserve, increment and window of one auction. | To provide what you asked for | Kept as long as the listing it belongs to. |
| A price somebody proposed, and where they would have had it sent. | To provide what you asked for | Kept while the listing or order it belongs to is retained. |
| What you joined | ||
| Which tiers a person has joined, when access ends, and the subscription behind it. | To provide what you asked for | While your account is open. |
| Which sticker sets somebody turned on for themselves. | To provide what you asked for | While your account is open. |
| Safety | ||
| Who somebody decided they want nothing to do with. | To keep the marketplace safe and working | While your account is open. |
| A builder's appointment of somebody to help moderate their own space, and when it ended. | To keep the marketplace safe and working | While your account is open. |
| That a builder shut somebody out of their space, and why. | To keep the marketplace safe and working | Kept. It points at the anonymised user row, so it describes conduct rather than a person. |
| Something somebody flagged for a human to look at, and what was decided. | To keep the marketplace safe and working | While your account is open. |
| A version of the Kommunity rules, or a proposal on its way to becoming one, and who proposed and decided it. | To keep the marketplace safe and working | Kept. It points at the anonymised user rows, so it describes an act rather than a person. |
| Messages | ||
| That two people have a conversation, and when each last read it. | To provide what you asked for | Kept while the other participant is. It goes when they go. |
| What somebody wrote to one other person. | To provide what you asked for | Kept with the thread it belongs to. |
| Shipping | ||
| A builder's named set of shipping prices. | To provide what you asked for | While your account is open. |
| Site machinery | ||
| Queues, caches and operational records. These can briefly reference you by account number while work is being done, and are not kept. | To keep the marketplace safe and working | Days at most, then discarded. |
3 What we never see
Card numbers. Payment details go straight to Stripe from your browser. They do not pass through us and we could not produce them if you asked.
Builder identity documents. Stripe verifies builders and holds whatever it collects to do that, under its own obligations. We hold a pointer to the account and what it is allowed to do. This has a consequence worth stating plainly: closing your account here does not delete your record at Stripe, and we have no power to make it.
4 Who else touches it
Stripe processes payments and pays builders. 17TRACK is given a tracking number so we can tell when a parcel arrives. Cloudflare serves the site and tells us which country a request came from. Cloudflare R2 stores uploaded photographs. Resend sends the email we send you, and Zoho receives the email you send us.
The application and its database run on servers we rent from a cloud infrastructure provider in the United States. They store the data on our behalf and do nothing else with it.
On the sign-up, sign-in, password reset and data request forms, Cloudflare Turnstile checks that you are a person rather than a script. It sees your IP address and how you interacted with that one form. It sets no cookie, and it is not used to recognise you anywhere else, here or on any other site. We run it because those four forms are the ones that can be abused to create fake accounts or to send mail to somebody who never asked for it, so it stays on whatever your privacy choices are: it is a security measure, not measurement.
No analytics or advertising vendor is switched on right now. When one is, it appears on this list and it runs only for people who have allowed it.
We do not sell personal information and never have. We do not share it for cross-context behavioural advertising unless you have turned that on yourself.
5 Tracking, and how to turn it off
Some things are not optional because the site cannot work without them: staying signed in, taking a payment, and knowing when a page has crashed.
Everything else is on unless you turn it off, and that includes recording what happens on a page. We say so plainly rather than in a footnote, because you cannot decide about something you were not told.
What the recording does and does not capture. It records movement on a page: what was clicked, what was scrolled past, where somebody gave up. It does not record what you type. Field contents are suppressed in the recorder itself rather than filtered afterwards, and it never runs on payment, escrow or dispute screens at all.
Turn any of it off on Your Privacy Choices. It works without an account and takes effect on your next page load.
We honour Global Privacy Control. If your browser sends that signal we treat it as a complete opt-out automatically, and you do not need to tell us again.
Nothing optional runs on the payment, escrow or dispute screens, whatever you have allowed. Session recording and advertising measurement are excluded from those pages by rule rather than by intention.
6 Your rights
Wherever you are, you can ask us for a copy of what we hold, ask us to correct it, ask us to delete it, and tell us not to sell or share it. Ask at Your data. You do not need an account and it costs nothing.
We answer within 45 days. You will get a case reference straight away, then a link to confirm the address is yours, because anybody can type an email into a form and some of these cannot be undone.
We will not treat you differently for exercising any of this.
Californians: the “Your Privacy Choices” link in our footer is the opt-out link the law requires, and it works without signing in. You may also use an authorised agent.
7 What deleting your account does not do
We would rather say this here than in the confirmation email after you have asked. Some records survive a deletion request, because they are records of money that moved between you and somebody else, and that other person did not ask to be erased.
| What stays | Why | How long |
|---|---|---|
| Name, email, password hash, the country they say they are in, their language and theme preferences, the time zone their browser reports (so dates read in their local time), which staff powers they have, and their customer id at Stripe. | Orders, payouts and disputes reference this row and belong to two people. | Tombstone kept while any order, payout or dispute referencing it is retained. |
| The @name a person is addressed by, including retired ones. | A retired handle must never be claimable by somebody else, or old links impersonate. It points at the anonymised user row, so it names nobody. | Indefinite. The handle survives; what it points at no longer identifies anybody. |
| A record that somebody was stopped from selling, buying or posting, and why. | Erasing this would make the erasure right a way to clear a record and start again clean, at the expense of the people the suspension protects. | Kept. It points at the anonymised user row, so it describes conduct rather than a person. |
| A staff power somebody was granted, who granted it, and when it was taken away. | Erasing this would make the erasure right a way to hide who once held a staff power and what they did with it. | Kept. It points at the anonymised user row, so it describes a grant rather than a person. |
| A request to see, correct or delete data: the address it came from and what was done. | The record that we honoured a request is the only proof we did. Deleting it as part of the deletion would erase the evidence of the erasure. | Two years, which covers the window for a complaint about how it was handled. |
| A funded commission: amounts, both parties, and the shipping address. | A record of money that moved between two people, one of whom did not ask to be erased. | Seven years after completion, for tax and chargeback windows. |
| The stages of an order and what each was worth. | Part of the order record, and the ledger references these rows. | With the order. |
| A rating out of five and what one party to a finished order said about the other. | A rating is a record about the OTHER party, and erasing it on request would be a way to clear bad reviews. | The rating stays with the order record. The words go. |
| A double-entry transaction grouping. | The books. Removing an entry unbalances a ledger that is required to balance. | Seven years. |
| Individual debits and credits, by account and order. | The books, and Ledger::post refuses an unbalanced set by design. | Seven years. |
| Money paid to a builder, and who approved it. | A financial transfer we are required to be able to account for. | Seven years. |
| Money held against future chargebacks, taken from a release (or, before 2026-10-11, a payout). | Part of the payout and release record, and may still be owed back. | Seven years. |
| A card dispute raised against an order or a tip. | Evidence in a dispute with a card network, which has its own timetable. | Seven years. |
| A tip between two people, with an optional note. | A payment, and the person who received it did not ask to be erased. | Seven years. |
| The link to a Stripe connected account and what it can do. | Stripe holds the identity verification under its own obligations; this is our pointer to it. | Seven years. |
| Stripe webhook payloads, kept so an event is handled once. | Idempotency. Removing one lets a replayed webhook move money twice. | Ninety days. |
| A dispute between a buyer and a builder, and how it ended. | A decision affecting two people and the money between them. | Seven years. |
| Every step taken in a dispute, and by whom. | The audit trail of a decision. An audit trail with gaps is not one. | With the dispute. |
| Photographs attached to a statement in a dispute. | Evidence an arbitrator decided money on. The record of a decision cannot lose its exhibits. | With the dispute. |
| A builder submitting work for approval, with a note. | Evidence of what was delivered, which the buyer may still need. | With the order. |
| Photographs attached to a submission. | Evidence of delivered work, and the buyer paid for it. | With the order. |
| Photographs of a kit as it arrived. | Evidence of condition, which is what settles an argument about damage. | With the order. |
| Photographs a buyer took of their own kit, packed, before sending it to the builder. | Evidence of condition, which is what settles an argument about damage. | With the order. |
| The carrier and tracking number of a replacement a builder sent after a reported problem. | Part of the order record: when it arrived is when the inspection window of the buyer started. | With the order. |
| A Kommunity post: title, body, and who wrote it. | Replies from other people hang off it, and deleting it removes their context too. | While the record it belongs to is kept. |
| A maximum somebody was willing to pay, and where they would have had it sent. | A winning price is computed from the runner-up bid, so removing one makes the sale unexplainable. | Kept while the auction it belongs to is retained. |
| The starting price, reserve, increment and window of one auction. | An auction is a record of a sale between two people, and belongs to neither alone. | Kept as long as the listing it belongs to. |
| A price somebody proposed, and where they would have had it sent. | An accepted offer sets an order price, and the rest of the thread is how it was reached. | Kept while the listing or order it belongs to is retained. |
| A comment, and who wrote it. | Comments are threaded, so deleting one orphans the replies under it. | While the record it belongs to is kept. |
| That a builder shut somebody out of their space, and why. | Erasing this would make the erasure right a way to clear a ban and start again clean, at the expense of the space it protects. | Kept. It points at the anonymised user row, so it describes conduct rather than a person. |
| That two people have a conversation, and when each last read it. | A conversation belongs to both people in it, and the other one is still here. The leaver is anonymised on their own users row, so what survives names nobody. | Kept while the other participant is. It goes when they go. |
| What somebody wrote to one other person. | A transcript missing one side misrepresents what happened, and the person hurt by that is whoever received the messages. The sender is anonymised, not the words. | Kept with the thread it belongs to. |
| A version of the Kommunity rules, or a proposal on its way to becoming one, and who proposed and decided it. | A suspension may cite the exact version in force when the conduct happened, and a rejected proposal keeps its reason so the same suggestion is not considered a second time from nothing. Erasing either would let the record enforcement depends on change after the fact. | Kept. It points at the anonymised user rows, so it describes an act rather than a person. |
| A brief: what somebody wants built, and their notes. | A builder quoted against it, and the quote references it. | While the record it belongs to is kept. |
| A builder's offer: amounts, terms, and revisions. | An accepted quote is the contract the order was formed on. | With the order it produced, or two years if never accepted. |
| The stages a quote proposed. | Part of the offer that became a contract. | While the record it belongs to is kept. |
| Photographs a builder attached to their answer on each task of a brief. | Part of the offer that became a contract. | While the record it belongs to is kept. |
| Uploaded photographs, their original filenames, and who uploaded them. | Evidence files and portfolio items point at these rows and belong to two people. | While the record it belongs to is kept. |
| Countries an owner closed to shipping, why, and which owner blocked or unblocked each. | The record that a country was closed must survive the account that closed it. | While the record it belongs to is kept. |
| Vendor IDs and which operator last changed them. | The record that a change happened must survive the account that made it. | While the record it belongs to is kept. |
Everything else goes, and where a record involves somebody else we remove the parts that identify you rather than deleting their record too. Your account itself becomes a marker that no longer names anybody.
A deletion waits if you have work in progress. We do not refuse it; we finish the commission first, tell you what we are waiting for, and complete it the moment that settles.
8 Where it is kept
Our servers and our processors are in the United States. If you are somewhere else, using the site means your information is handled there.
9 Keeping it safe
Traffic is encrypted. Passwords are hashed and we cannot read them. Payment details never reach us. Access to production data is limited to people who need it, and the powers that matter, ruling on a dispute, releasing money, and changing what runs in your browser, are held separately so that no one person has all three.
No system is perfect. If something happens that puts your information at risk, we will tell you and the relevant regulator as quickly as the law requires.
10 Children
This is not a service for children, and we do not knowingly hold information about anybody under 16. If you believe we have, write to help@kompleteassembly.com and we will remove it.
11 Changes
Changes are posted here with a new date. If we start using your information for something materially different, we will ask again rather than assume an old answer still stands: every choice you make is recorded against the version of this policy it was made under.