Privacy Policy

Last updated: May 2026

Overview

Narrarium BMS ("the app") is a client-side web application. It runs entirely in your browser and does not operate any backend server that collects or stores your personal data. This policy describes what data is handled, where it lives, and who controls it.

Data we handle

Google account information

When you sign in with Google, the app receives your name, email address, and profile picture via Google OAuth 2.0. This information is stored only in your browser's localStorage and is never sent to any server controlled by Narrarium.

Application settings

Your app settings — including GitHub personal access tokens and Azure OpenAI credentials — are saved in your personal Google Drive appDataFolder. This is a private, app-specific folder in your own Google Drive account that no other app or user can access. Narrarium has no access to any other file in your Google Drive.

GitHub data

The app communicates directly with the GitHub API using the personal access tokens you provide. Repository content is fetched on demand and held in memory; it is not persisted on any Narrarium-controlled server.

Azure OpenAI

If you configure Azure OpenAI, the app sends prompts directly from your browser to your Azure OpenAI endpoint. No prompt or completion data passes through Narrarium servers.

Cookies and local storage

The app uses localStorage to remember your theme preference and cached authentication state. No advertising cookies or third-party tracking cookies are used.

Third-party services

Data retention and deletion

Because all data lives in your browser or your own Google Drive account, you are in full control:

  • Sign out of the app to clear the in-memory session.
  • Clear localStorage in your browser to remove any cached data.
  • Delete the settings file from your Google Drive (look for narrarium-bms-settings.json in the app-data folder) to remove stored credentials.

Contact

If you have questions about this policy, open an issue on the GitHub repository.