Skip to content

Privacy Policy for VibeCode Wiki

Last updated: October 1, 2026

This page contains processing rules, user rights, and analytics principles.

1. General provisions

This policy describes what data may be processed on VibeCode Wiki, for what purposes, and on what legal grounds.

The document applies to all website pages and related technical services.

2. Operator and contacts

For personal data processing questions, use the operator contact below.

vbfbk2010@gmail.com

3. Data categories

  • Technical visit data (anonymized statistics) when analytics consent is provided.
  • Service HTTP request data required for security and site stability.
  • Local browser preferences (for example theme selection and consent state).
  • For VibeCode Jobs: request text, category, budget, deadline, region, source link, moderation status, and Telegram contact only when the user submits a request and explicitly confirms public contact publication.

4. Community articles and reactions

When authoring is available, drafts, revision history and uploaded draft images are private to their author and authorized reviewers for the selected direction. New articles and all edits require approval before they become public.

Publication shows the confirmed public display name and avatar. The numeric Telegram account identifier and authentication credentials are not part of the public author profile.

One selected emoji reaction is stored per signed-in account and article. Public readers see aggregate reaction counts, not account identifiers.

5. Article view counts

A view is recorded only with analytics consent after at least five seconds of visible reading. An article receipt prevents repeated counting in the same tab for 24 hours; a separate tab can record another opening.

This counter does not create a persistent visitor identifier and does not substitute cookies or fingerprinting when analytics is declined. Withdrawing consent cancels pending counting and clears local receipts; already aggregated counts are not reversed.

Expired server receipts and rate-limit records are cleaned hourly. Delivered publication outbox records are retained for 30 days after delivery. This cleanup does not delete drafts, images, article totals or pending publication events.

6. Processing purposes

  • Maintain site availability, security, and performance.
  • Analyze content and navigation quality to improve material structure.
  • Diagnose technical errors and prevent abuse.

7. VibeCode Jobs

Imported Telegram requests are shown as links to the original public post when such link is available. The site does not publish direct personal contacts from imported requests as a separate contact action and redacts contact-like fragments from imported text.

For requests submitted through the website, the verified Telegram username can be shown in the public Jobs feed only after explicit confirmation by the submitter. The request can be removed or the contact can be hidden upon request to the operator.

8. AI guide and Vibi

The Vibi AI guide can send the user question, short site-material snippets, and a minimized recent Telegram chat context to the configured Vibi model provider so the assistant can answer by the current discussion.

Telegram context is limited to relevant recent messages. Where possible, Telegram username values are removed before the model payload: the assistant uses display names or a neutral participant label instead of @handles.

Service logs must not contain Vibi provider keys or raw model prompts. The Telegram context layer for the site widget can be disabled by setting AI_BOT_TELEGRAM_CONTEXT_CHAT_ID=0.

9. Legal grounds

  • User consent for analytics cookies and related technologies.
  • Operator legitimate interest for protection and administration of the resource.
  • Separate consent for public contact publication in VibeCode Jobs when a user submits a request through the website.

10. Transfer to third parties

External services are used for analytics and infrastructure (for example Cloudflare, Yandex Metrika, and Google Analytics) within the scope required for their operation.

No sale of personal data to third parties is performed.

11. Retention periods

  • Technical logs are stored only as long as needed for diagnostics and security.
  • Analytics data is retained in aggregated form according to service settings.
  • Local browser data is retained until user cleanup.

12. User rights

  • Receive information about data processing and applied approaches.
  • Withdraw analytics consent and delete local site data in the browser.
  • Contact the operator about correction and deletion within applicable law.

13. Policy changes

This policy may be updated when data-processing workflows, connected services, or legal requirements change.

The current version is published on this page with an update date.