How Vibeblt handles builder and project data.

Account information: when you sign in with Google or GitHub, Vibeblt may receive your email address, name, avatar, provider account identifier, and other basic profile details needed to create and secure your account.

Builder profile information: you may add or edit your public name, username, bio, avatar image or avatar URL, Twitter/X URL, GitHub URL, and other public builder details.

Project information: when you submit a project, Vibeblt stores listing details such as project name, tagline, description, live URL, category, tech stack, project tags, help tags, thumbnail, screenshots, review status, review notes, and publication status.

Community activity: Vibeblt stores comments, replies, likes, follows, saved engagement state, project ownership, timestamps, and moderation state so conversations and dashboards work.

Technical information: Vibeblt may receive IP address, browser, device, referral, page activity, cookies, logs, and analytics events from hosting, analytics, authentication, and security tools.

Approved and published projects may be visible to anyone. Public project pages can include your builder profile, project details, screenshots, thumbnail, live URL, tags, comments, like counts, follower counts, and related engagement.

Drafts, projects in review, private dashboard views, account email addresses, and admin review controls are not intended to be public, though no online system can be guaranteed to be perfectly secure.

Vibeblt uses information to run authentication, create profiles, accept project submissions, review listings, publish approved projects, support comments and replies, show likes and follows, manage dashboards, prevent abuse, troubleshoot bugs, improve the product, and respond to support requests.

Vibeblt may also use public project and profile content to feature or promote the directory and the builders using it.

Public content is shared by design when you publish or participate publicly on Vibeblt.

Vibeblt may share information with service providers that help operate the site, including authentication, database, storage, hosting, analytics, email, security, and infrastructure providers. These providers process information on Vibeblt's behalf.

Vibeblt may disclose information if required by law, to protect users or the service, to investigate abuse, or as part of a business transfer such as a merger, acquisition, or sale of assets.

Vibeblt does not sell personal information and does not use submitted project data to run third-party ad targeting.

Vibeblt uses cookies and similar technologies to keep you signed in, protect sessions, remember auth state, measure site usage, and understand which pages or features need improvement.

If you use Google or GitHub to sign in, those providers may process information under their own privacy policies. Your live project URLs may also take visitors to third-party sites controlled by the project owner.

Vibeblt uses reasonable technical and organizational safeguards for account, profile, submission, and engagement data. No method of transmission or storage is completely secure.

Vibeblt keeps information as long as needed to operate the service, maintain public listings, resolve disputes, comply with legal obligations, prevent abuse, and improve the product. If you want your account, profile, or project content removed, contact Vibeblt.

You can edit your builder profile from settings, manage project drafts and submissions from your dashboard, and choose what project information to submit for review.

You can ask to access, correct, export, or delete account information by contacting hello@vibeblt.com. Some information may need to be retained when required for security, legal, audit, or abuse-prevention reasons.

Vibeblt is not intended for children under 13, and Vibeblt does not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact Vibeblt so it can be reviewed and removed where appropriate.

Vibeblt may update this policy as the product changes. The updated date at the top of this page will show when the policy was last revised.