Privacy
What we collect, what we don’t, and what we do with it.
Last updated 22 July 2026.
In plain English
Buildscape is operated by Orchestrating Design — “we” below means Orchestrating Design. We store your account email (via Supabase, who handle sign-in) and whatever you choose to publish. We use PostHog to see which pages and features get used, in aggregate — not to sell your data. We count views and tool clicks with our own first-party counters. Some tool links earn us a commission if you sign up through them, and some workflows on the site are paid placements — both are disclosed below. You can ask us to delete your account at any time.
Account data
Sign-in is handled by Supabase Auth (Google sign-in or a one-time email code). We store your verified email address, the handle and display name you choose, and your bio if you add it. We never see or store a password — Supabase (Google, for Google sign-in) verifies identity, and Supabase issues a token we check on each request.
Product analytics
We use PostHogto understand how the product is used — which pages get visited, which features get used, in aggregate. This sets cookies and records navigation events (page views, sign-ups, publishing a workflow) tied to an anonymous or (once you’re signed in) your account ID. PostHog only loads on the main site — never on embedded workflow widgets placed on other sites. If no analytics key is configured, none of this runs: no cookies, no network calls, no tracking.
First-party view & click counts
Separately from PostHog, we keep our own simple counters: how many times a profile or workflow has been viewed, and how many times a tool link has been clicked. Tool-click records include a one-way hashed, daily-rotating version of your IP address (never the IP itself) plus the page you clicked from, so we can measure clicks without being able to trace them back to you.
Describing a workflow with your voice
Dictation is your browser’s own — depending on your browser and device it may send audio to Google or Apple to transcribe. We never record or store audio. The text you generate a workflow from is sent to Google Cloud, where a Gemini model turns it into a workflow. Google processes that text on our behalf under our Cloud terms, and does not use it to train its models.
Affiliate disclosure
Some tool links on the site (in workflow nodes and tool listings) are affiliate links. If you sign up for or purchase a tool through one of these links, we may earn a commission — at no extra cost to you. This never affects which tools appear in a workflow; it only funds keeping the site free.
Sponsored-content disclosure
“Sponsored” is the one word we use for anything money was involved in — on a tool, on a workflow, anywhere. If you see it, somebody paid for something. It never changes or hides the actual content, and it is always shown rather than buried.
It covers two arrangements, and you are entitled to know which you are looking at. A sponsored placement means somebody paid us to surface a workflow or a tool more prominently — that is the only kind that buys position, and it is arranged and set by us. A workflow marked “sponsored by” somebody, or simply “sponsored” without a name, is the author telling you they were paid or given something by a third party: no money reached us, we did not arrange it, and it buys no placement whatsoever. Authors write that one themselves and we do not verify it.
Deleting your account
There isn’t yet a self-serve “delete my account” button in the product. To request deletion, email hello@buildscape.ai from your account’s address and we’ll remove your account row, your workflows, and associated data. Until that ships as a self-serve flow, you can make any workflow or your whole profile private at any time from its visibility toggle.
Contact
Questions about this policy? hello@buildscape.ai.