Privacy policy for Vengeance UI.
A plain-language summary of how this public site treats visitor data. The project is a component library, not an account-based product.
No
accounts
Stripe
payments
Public
repo
Vengeance UI
Company page
No user accounts
Vengeance UI does not ask visitors to create an account to browse docs or components.
Stripe-hosted payments
Sponsorship checkout runs on Stripe. Vengeance UI does not receive or store your card details.
External platforms
Stripe, GitHub, Vercel, and social links may process data under their own policies.
Policy summary
This page exists so the footer policy link gives users a real answer instead of a 404.
No user accounts
Vengeance UI does not ask visitors to create an account to browse docs or components.
Stripe-hosted payments
Sponsorship checkout runs on Stripe. Vengeance UI does not receive or store your card details.
External platforms
Stripe, GitHub, Vercel, and social links may process data under their own policies.
Data practices
The site can still be served by hosting and analytics infrastructure, so this policy explains the practical boundaries.
Site logs
Hosting providers may keep standard request logs for security and reliability.
Sponsorships
Stripe handles billing and sends the display name, website, and optional logo URL you submit. Approved details are shown publicly while the sponsorship is active.
External services
Stripe Checkout, GitHub, Vercel, and X each process data under their own policies.
Contact
Information you choose to include in GitHub issues or messages is visible wherever you post it.
Visitor choices
Browse anonymously
You can read the public pages without signing in.
Use GitHub intentionally
Only post contact details or private context if you are comfortable sharing it there.
Ask questions
Use the contact page if anything about this policy needs clarification.