Who owns what Makerstead holds.

The simplest way to read the data model is row-by-row. Each row below is a separate database table; ownership and retention are decided per row, so a product and an owner message are different “things” with different owners.

The desktop rule is short and is the same rule advertising copy from Makerstead:

• Business data (your profile, your published care pages, your service logs, your photos) is yours. Makerstead hosts it; you take it with you when you go.
• Customer data: The participating business controls its customer relationship and may use customer-submitted information to provide requested services, subject to applicable privacy laws. Makerstead processes and stores that information on the business’s behalf.
• Platform bookkeeping— billing state, login events, abuse signals — lives at the platform layer and belongs to Makerstead. None of it is ever resold or fed to a model.

There are two kinds of cancellation, and the rule is the same for both:

• Soft-cancel (subscription lapses at the end of the current billing period, you have not actively asked for deletion). Your published care pages still resolve publicly for a 90-day grace window so any owner who scans a QR still reaches a working page. Service entries are read-only; no new records can be published. The export action stays open.
• Hard-cancel (you actively ask for the rows to be deleted). Makerstead exports a final archive to the same channels listed below, then permanently deletes the rows. The archive stays on a separate shelf for thirty days in case the export was interrupted, then that too is deleted.

The full retention window (with timing for each row type) is on the privacy page. The way subscription refund mechanics interact with the grace window is on the refunds page.

Every row on your bench is exportable. From the dashboard, the export action returns one CSV file with all of the following row kinds on a single wide spreadsheet — cells are empty where a column does not apply to a given row, so a single header row serves every kind:

• Product— the published care-page core: id, name, category, created date, current owner, last service date, pending-transfer flag.
• Customer— one row per product that has a named current owner: product id, owner name, owner email.
• Request— every care request the maker steered back to the bench: id, status, topic, customer name, customer email, created date, plus the denormalized product name.
• Service history— the full service log: id, performed date, kind, notes, plus the denormalized product name.
• Ownership transfer— every transfer a record has ever gone through: id, from and to owner emails, status, decision and expiry timestamps, the maker’s note.

The export endpoint lives at /api/export/products. Subscription state is gated to active plans: a lapsed maker gets a clear reactivation surface in place of the file. The export stays available during the 90-day publish-grace window after cancellation, and on request after that window.

• We do not resell business data.
• We do not resell customer data.
• We do not sublicense it, broker it through an aggregator, or post anonymised snapshots back to a public learning surface.
• We do not train — nor allow a third party to train — a generative model on your records, your owner messages, or any of the platform’s own bookkeeping. The no-train promise is mutual and runs both ways.

The standing consequences of breaking any of these are spelled out in the acceptable-use policy.

For data access, correction, deletion, or a portability question, email makerstead@polsia.app. Include the record URL or your bench name and the action you’re asking for. The desk acknowledges within two business days.