designesy
Score a site

Trust surface

Privacy

Designesy treats privacy as infrastructure.

This page states how the public designesy.org surface handles information: what is collected, what is not, and how open design intelligence stays fetchable without turning visitors into product. Operator: Designesy LLC. Contact: hello@designesy.org.

PublicPlain language · not a cookie wallUpdated 2026-07-19

Stance

Working sentence

The public site exists so people and agents can inspect design rules, review practice, and portable packages. Trust is part of that product: fewer hidden systems, clearer defaults, and no invented surveillance language.

Principles

01

Public by design, minimal by default

designesy.org is an institutional surface for design intelligence. Its purpose is clarity, review, and portable rules. It does not harvest personal data for ads or resale.

02

Empty is better than filler

We do not invent tracking claims, cookie walls, or consent theater for features this site does not run. What is stated here is what is operated.

03

Open packages are intentional

Machine exports such as open.json and kit JSON are public so people and agents can fetch design rules. That openness is a product choice. The exports carry design rules and no data about you.

04

Contact stays voluntary

Email is the contact path. Writing to us is optional. Messages are used to respond and operate the organization. They are never used to build marketing profiles.

What may be collected

01What you send usEmail you choose to write to hello@designesy.org, and any files or context you attach. Used to reply and run Designesy LLC work.Held by Designesy LLCNo marketing profiles
02Continuity waitlistIf you join /continuity, we collect the work email and optional role, interest, site URL, and note you submit. Used only to operate the Continuity early-access list and related product access. It is not sold and not used for ad profiles.Held by Designesy LLCNot sold · no ad profiles
03What the host may logStandard web-host logs for reliability and abuse defense: request path, approximate time, user-agent, and network address as retained by the hosting provider. Not used for advertising profiles on this surface.Kept by the hosting providerNo ad profiles
04Usage counts for the score API and MCP toolsFor each day: how many calls each MCP tool and the score API received, which kind of client made them (browser, MCP, GitHub Action, CLI, or script), and an approximate number of distinct callers. Callers are counted through a one-way hash of the network address, salted per day, inside a counting sketch that cannot list them. The URL scored, any contract, and the address itself are not stored. Counts expire after 400 days.Held by Designesy LLCNo URLs or addresses · 400 days
05What the browser keeps locallyInterface preferences that stay on your device when present (for example sound or motion preference used by live labs). These are not sold and are not required for reading docs.Stays on your deviceNot sold · not required

What we do not do here

01Sell personal data
02Run third-party advertising trackers on this surface
03Require an account to read public docs, contracts, kits, labs, or Open
04Turn open machine feeds into a dossier about individual visitors
05Ask for more personal detail than the work requires

Open exports

These routes publish design packages on purpose. They describe Designesy systems and review cargo. They are not personal profiles of site visitors.

Third parties

Hosting and mail

The site is served through a web host and content delivery network. Those providers process the technical request data needed to deliver pages. Email is handled through ordinary mail infrastructure when you write to us. We do not add separate advertising SDKs to this public surface.

If this changes

If Designesy adds accounts, analytics products, payment flows, or other personal-data systems, this page will be updated before those systems become the default public path. Silence is not adoption of hidden tracking.

Requests

For privacy questions, correction requests about correspondence you sent, or operational concerns, write to hello@designesy.org. Include enough context to locate the request. We respond as an organization.