Nobi for Windows · In private development

YOUR INFORMATION

Privacy, in plain language.

How the current Nobi development build handles local information, account sign-in and optional online features.

Effective 31 October 2026 · Current development build

1. What Nobi is

Nobi is an independent Windows desktop companion maintained by its developer and available in private development. Its character animation and basic desktop interaction run on your computer. Cloud account and natural voice features are optional and under evaluation. A cloud account is not required for local character interaction.

For support, privacy questions or account deletion requests, contact the Nobi developer at malik.draggon@gmail.com.

2. Information kept on your computer

Nobi stores settings, local character and animation libraries, and other feature data in its own Windows application-data folders. Character imports remain local unless you separately choose a feature that sends specific content online.

Saved cloud session credentials are protected using Windows credential encryption. Local diagnostics record bounded event and error information. They are separate from the website and are not automatically sent by this website.

3. Google sign-in and basic profile data

When you choose Google sign-in, Google and Supabase process authentication for Nobi. Nobi requests basic identity scopes: openid, email and profile. This can provide a provider identifier, email address, email-verification status, display name and profile picture.

Nobi uses this information to identify your Nobi cloud account, show account details and protect access to supported cloud features. Basic identity information may be stored with your account by Supabase and in protected local account state. A profile picture may be fetched from an allowed Google image host for display.

Nobi’s Google sign-in does not request Gmail, Google Drive, calendar or contacts access. Google profile information is not used to grant Windows permissions, advertise to you, or authorize desktop actions. The application does not request Google access for these unrelated purposes.

4. Email accounts

If you choose email registration, Supabase handles your account email, password authentication, confirmation and recovery messages. Nobi submits the information needed for the requested account operation over HTTPS. Passwords and sign-in codes are not intended to be written to application logs.

5. Optional voice, AI and desktop context

Nobi Sounds is a local sound mode. SILMA is an optional local speech engine requiring a separate download. Local voice libraries are separate from cloud authentication.

When you explicitly use an enabled cloud feature, the text or audio needed for that request can pass through Nobi’s Supabase gateway to an approved speech or AI provider. The private testing integrations include OpenAI, ElevenLabs and Fish Audio. A provider’s presence in the code does not mean every provider or voice is available. General paid inference and production billing are currently disabled.

Microphone, screen-help and external AI-tool connections have their own controls. Signing in does not grant microphone, screen, file or app access. If you separately enable a feature that sends selected context to an online provider, that feature’s permissions and disclosures apply.

6. Service providers and records

Supabase provides cloud authentication, account storage and the gateway. Google processes Google authentication. Enabled AI and speech providers process the specific request content they receive under their own terms and privacy policies. The website host processes network information necessary to serve pages.

Nobi’s current usage and cost records contain operational metadata such as request status, model, timing and measured usage. The current gateway’s usage tables are not designed to store conversation text or audio. This does not promise that an upstream provider keeps no records.

Google account information is used for the disclosed account and security purposes. It is not sold or used for personalized advertising.

7. Retention and deletion

Local libraries and settings remain on your computer until you remove them. Signing out clears the current local cloud session; it does not delete a hosted account or your local libraries. Removing Google access also does not itself delete a Nobi account.

Cloud account records are retained to operate the account and support security and usage accounting. In-app account deletion is not yet enabled in the development build. Send privacy or deletion requests to malik.draggon@gmail.com; the developer may need to verify your identity before acting on an account request. Records needed for security, abuse prevention, usage reconciliation or applicable obligations may need to be retained. Upstream providers have their own retention practices.

8. Website cookies and external links

This website source includes no advertising, analytics scripts, tracking pixels, contact form or website account sign-in. The website host processes technical network information needed to deliver these pages. Its hosting policies also apply. Links to other services are governed by those services’ policies.

9. Your choices

  • Use Nobi’s local character interaction without a cloud account.
  • Choose a local voice mode and manage microphone and optional context permissions separately.
  • Use Stop or Quiet time to interrupt supported companion activity.
  • Sign out of Nobi, and review or revoke Nobi’s Google access in your Google account.

10. Contact and changes

Contact the Nobi developer at malik.draggon@gmail.com for support, privacy questions, corrections or deletion requests. Do not email passwords, sign-in codes or API keys.

This policy reflects the current development build. Changes in account, voice or provider behavior will be reflected here and in the relevant in-app disclosures, with an updated effective date.