Privacy

What the packages do

Nothing leaves your infrastructure because of Wingtics. The components have no telemetry, no phone-home, and no analytics of their own — they render whatever your connector returns. There is no Wingtics server for them to talk to.

A connector talks only to the analytics provider you configure it with. @wingtics/next exists so that provider credentials stay on your server: the browser calls your route, your route calls the provider. The token never reaches the client bundle.

Whatever your analytics provider collects about your visitors is governed by that provider’s policy, not this one. Wingtics does not add to it or send it elsewhere.

What this website collects

wingtics.com runs Vercel Web Analytics, which is cookieless and does not fingerprint visitors. It records aggregate page views, referrers, country, and device class. There is no cross-site tracking, no advertising identifier, and no attempt to identify you.

The demo dashboard reads this site’s own analytics, which is why the numbers there are real. That is also the only personal-data processing behind this site: it measures itself and shows you the result.

Cookies

No tracking cookies. The only client-side storage is a theme preference and the state of the component playground’s controls, both kept in your browser’s local storage and never transmitted.

Third parties

• Vercel — hosting and the cookieless analytics described above.
• npm and GitHub — reached only when you follow a link or install a package, under their own policies.
• Fonts come from the Google Fonts catalogue but are downloaded at build time and served from this domain, so your browser never requests anything from Google.

Questions

Ask in the open on GitHub. This page changes when the answer changes; it is version-controlled with the rest of the site, so its history is public.