Account identity
Authentication is handled by Clerk. VoteStocks can store a linked internal user ID, your email address, display name, and profile image when available.
This privacy page describes the current VoteStocks prototype. It explains the types of information the product can store, how that information is used inside the experience, and what still needs a final legal review before production launch.
Authentication is handled by Clerk. VoteStocks can store a linked internal user ID, your email address, display name, and profile image when available.
The app can store votes, favorites, comments, likes, and other account-linked actions so your experience stays consistent across sessions.
VoteStocks may keep technical logs, session state, or cached market views to keep the product stable, faster, and easier to debug.
Votes, comments, favorites, and account data are used to make VoteStocks function as a personalized product experience.
Your actions are linked to your authenticated Clerk identity so your profile, comments, and sentiment history remain connected.
Technical information may be used to diagnose errors, reduce loading problems, and improve the overall speed of the site.
Sign-in, sessions, and account-level authentication are handled by Clerk. Their own privacy and security policies also apply to the authentication layer.
This page is a product-facing draft for the current prototype. It should be reviewed and finalized before production release.
VoteStocks should not treat this page as completed legal advice. It is a practical draft that still needs formal validation later.