Your work

Isolation lives in the database, not in our good intentions

The first question a house asks is what happens to its designs. The answer that matters is not a policy document — it is where the boundary is enforced, and whether a mistake in application code can cross it.

Here it cannot. This page says why, and where the limits are.

A forgotten filter returns nothing, not somebody else’s rows

Every table that holds a house’s work — designs, their attributes, the photographs read in, the users, the demand signals — has row-level security switched on in Postgres. The application connects as a plain, non-owner database role, which means those policies are enforced against it rather than bypassed.

The practical consequence: a query in application code that forgets to filter by tenant does not leak. It returns nothing. The filters in the code are a convenience; the policy is the boundary.

The tenant is set per transaction and discarded when the transaction ends, so a pooled connection cannot carry one request’s tenant into the next. And the policies fail closed: with security on and no policy matched, the row is invisible.

The vocabulary is shared. Your designs are not.

Crafts, garments, occasions, regions, cloths and cuts are the common spine — readable by every tenant, and not writable by the application role at all. That is what makes the catalogue worth being in.

Your designs, your scans, your people and your demand signals sit behind the tenant boundary and do not cross it.

What crosses, crosses as counts

One thing is deliberately cross-tenant: the market rollup. It runs inside database functions that group by catalogue words — a motif, a colour family, a silhouette, a region, an occasion, a week — and return sums, averages and a count of how many tenants contributed.

No tenant identifier is in the return type, so none reaches the application, and none can reach a screen. A threshold on the minimum number of contributing tenants exists so a thin cluster can be excluded from a rollup rather than pointing at one house.

Who can see across, said plainly

Platform administrators can. It is a named role that the database policies check by name, it is how the catalogue is edited and how support is given, and every other session is confined to one tenant with no way to widen itself.

We would rather write that sentence than let you discover it. A vendor who claims nobody at all can see your work is either describing a system they do not operate, or describing one they cannot fix.

Sign-in is the one place a lookup has to happen before a tenant is known, and it is a single narrow function that returns one user by email and their authentication fields — not a general exemption.

What is kept, and for how long

Business work is not on a deletion clock

The retention sweep only ever looks at rows carrying a purge date. Business designs do not carry one, so there is no path through that code that can reach them. Where a deletion date does exist, it is stamped when the work is made and never recalculated — changing a setting tomorrow cannot reach back and delete something early.

And nothing is deleted that was not warned about first. That is enforced in the query, not in a runbook.

A face is held for as long as you say

If a photograph of a person is used, the holding window is chosen at the point of consent: twenty-four hours, seven days, or thirty. Thirty days is the longest this platform will hold a face, and that ceiling is in the code rather than in a policy.

Where a design came from stays answerable

A design made from a reference records the picture it started from, so the question is still answerable months later. The comparison between the two — what was kept, what was changed — is worked out from the two designs’ own catalogue tags rather than written into a column of its own, because a stored copy is a copy that can quietly disagree with the records it describes while still looking authoritative.

The same discipline runs through the catalogue itself: researched vocabulary is stored with its provenance and marked as awaiting review, and words awaiting review are not offered in pickers. The point of recording where something came from is to avoid acting on it blind.

What this page does not say

It does not say who owns the output. That is a contract, not a schema, and it is decided in writing when access is granted — not implied by a paragraph on a marketing site.

It is not a certification. Nothing here claims an external audit, a standard, or a badge, because none has been done and saying otherwise would be the easiest lie on this page to check.

It describes how the system behaves today. Where your own obligations are stricter than what is written here, say so early — it is a better conversation before access than after.

The limit

Designs are rendered by an inference provider, which means image data leaves this platform to be made. Which provider, on what terms, and what may be sent are answerable questions and part of the conversation — not something to be waved away in a sentence here.

Ask us the awkward version of this.

Send the questions your legal team would ask rather than the ones a marketing page invites. Where the answer is no, or not yet, you will get that answer.