Scope of this notice

This notice describes the current KODE Ń VIBE website, its browser-side interactions and its Supabase-backed member features. The guides and trust pages do not provide a contact form. Other pages load application code and external resources, as described below.

Important: do not publish identity numbers, private financial records, credentials or other sensitive information in community projects.

Information stored in your browser

Some features use localStorage so a choice survives a refresh, or sessionStorage for a temporary redirect. In the current code, this can include:

  • Display preference: the keys theme and kv-notes-theme can retain a light or dark choice.
  • Advice questionnaire: kv-advice-answers can retain selected answers.
  • Project drafts: the temporary wasee-project-draft browser value can preserve the form answers across a sign-in or email-confirmation tab. It expires after two hours. Images are not retained in a draft.
  • Return path: kv-auth-return-v2 can temporarily remember where the browser should return after sign-in. It expires after two hours; related session values can hold the email awaiting confirmation.
  • Demonstration reactions: wasee-project-likes and wasee-project-votes can remember reactions to example project cards on that browser. Older versions may also have left wasee-community-projects data behind.

Display preferences and unfinished form drafts normally remain in that browser profile. The Supabase client also retains a session token so an authenticated member can remain signed in; treat a device with an active session as having access to your account.

Accounts and community submissions

Supabase provides authentication, a Postgres database and project image storage. For email-based accounts it processes the email, password credential, confirmation state, session data, account metadata and authentication events. Plaintext passwords are not written to KODE Ń VIBE's public project tables.

Google sign-in is available. If you choose it, Google and Supabase process the OAuth request, and Google may share profile details you authorise, such as your email, name, avatar and provider account identifier. Email sign-in remains available independently of Google.

When you publish a project, Supabase stores your account identifier, public creator name, optional broad location, project name, summary, links, up to five technology labels, optional image, reactions and timestamps. Project cards and images are intentionally public. The account identifier links the record to its owner. Database Row Level Security limits who can create, change or delete member-owned records; it is a safeguard, not a promise that any internet service is risk-free.

Share only public project information and images you have permission to publish. Never upload secrets, private documents or exact addresses.

Account and transactional email

Depending on the action and project settings, Supabase can send account confirmation, invitation, passwordless sign-in link or code, password recovery, email-change, reauthentication and security-notification messages. Security notices can concern a changed password, email or phone, a linked or unlinked identity, or enrolment or removal of a multi-factor authentication method. Some message types are prepared for future features and are not evidence that the related feature is currently available.

KODE Ń VIBE uses Resend as the configured transactional delivery provider for Supabase account messages. Resend processes the recipient address, sender, subject, message content and technical delivery events needed to send and troubleshoot those messages. Delivery is not guaranteed; check spam folders and use the resend control only when needed.

Account messages can contain time-limited links or one-time codes. Never forward them or share a code. KODE Ń VIBE will not ask you to reply with a password, code or secret key.

Hosting and network requests

Requesting any website file can expose ordinary technical information—such as an IP address, user agent, requested URL, time and referrer—to the hosting infrastructure. The repository does not identify the production hosting operator or its retention settings, so this notice cannot make a specific server-log promise.

The homepage's inherited application bundle may request external services, analytics endpoints, embedded media, images or checkout-related APIs. Those requests can reveal technical request data to the provider. Authentication and project pages also load the Supabase browser library from a content-delivery network and make requests to the Supabase project. The static guides and trust pages do not load those application scripts, but following a link back to an interactive page or external service may do so.

When a signed-in member starts checkout, KODE Ń VIBE sends the account email, account identifier, selected product, amount and a unique payment reference to Paystack. Paystack collects and processes the payment details on its hosted checkout. Supabase stores the resulting reference, transaction identifier, amount, currency, status, provider response and access dates. KODE Ń VIBE does not receive or store the full card or mobile-money credentials.

Supabase and other providers can process data outside Kenya, including in the region selected for the hosted project and in their supporting infrastructure. Provider logs and backups follow their own security and retention practices. KODE Ń VIBE has not set a complete production retention schedule; account and project records can remain until deletion is requested or the service no longer needs them, with additional time possible for backups, abuse prevention or legal obligations.

External links, contact email and public GitHub activity

Links can open documentation, public bodies, project websites, email software, GitHub or other providers. Those services have their own privacy practices. Check the destination before entering information.

KODE Ń VIBE publishes the email address kodenvibe@gmail.com and a public GitHub contact route. Messages sent to that contact address are handled by Gmail and therefore by Google; this is separate from automated account-email delivery. Issues, discussions, pull requests and profile details on GitHub may be public. Do not post a private rights request or sensitive personal information in a public repository thread.

How to remove your data

You control the data stored in your browser. Use your browser's site-data settings to clear storage for kodenvibe.tech. Clearing local storage removes the theme, questionnaire, local reactions and account session on that browser. Clearing session storage or closing the session removes temporary draft, pending-email and redirect data, depending on the browser. Signing out is the preferred way to end a Supabase session. Clearing browser data does not delete the hosted account, published projects, images or member likes.

Browser menus differ, so consult your browser's current help documentation. Export any non-sensitive text you want to keep before clearing. Email kodenvibe@gmail.com to request access, correction or deletion of an account or published project. Include only the account email or project link needed to locate it. The current interface does not provide self-service account deletion, and identity checks may be needed before a request is completed.

For current Kenyan data-protection information, consult the Office of the Data Protection Commissioner. This notice is a description of the prototype, not legal advice.

Privacy questions and corrections

Email kodenvibe@gmail.com for a privacy question or correction to this notice. Send only the information needed to explain the request; never include passwords, secret keys or unnecessary identity records.

This notice should be updated whenever an authentication provider, transactional email route, hosting arrangement, analytics service or payment feature is enabled or materially changed.