Privacy Policy

This Privacy Policy applies to the Neuralbase website at https://neuralbase.cloud, the dashboard, and the hosted API services. It covers information we process when you browse public pages, authenticate, create workspaces, use API keys, submit memories or documents, or interact with support channels we make available.

This Privacy Policy does not cover third-party services you access directly, such as Google or GitHub sign-in flows, except to the extent we receive profile information from those providers as part of authentication.

We collect the following categories of information:

• Account and profile information: name, email address, avatar URL, OAuth provider identifier, and organization membership records.
• Authentication and session information: session identifiers, OAuth state values, login timestamps, and related security records used to create, validate, and expire dashboard sessions.
• Workspace and API information: organization records, API key identifiers, key prefixes, revocation status, last-used timestamps, and usage records associated with the workspace or account.
• Customer content: memories, uploaded documents, extracted text, summaries, entities, metadata, retrieval results, and backup metadata associated with the service.
• Billing and quota information: plan selections, subscription status, billing-cycle dates, usage counters, and usage events for API calls, memory operations, and document parsing.
• Technical and diagnostic information: request paths, response timing, queue status, rate-limit events, processing status, and operational error information needed to secure and maintain the service.
• Local device preferences: theme preferences, feature-preview settings, sidebar state, and last-used login provider stored in your browser's local storage.

We collect information directly from you, automatically from your use of the service, and from integrations you choose to use.

• Directly from you when you sign in, create a workspace, generate API keys, upload documents, write memories, or configure settings.
• From Google or GitHub if you choose those sign-in methods and grant the provider permission to share basic profile data with us.
• Automatically from service activity when the platform records usage, queue, rate-limit, quota, and backup events.

We use information to provide, operate, secure, and improve Neuralbase.

• Authenticate users and maintain dashboard sessions.
• Create and manage organizations, memberships, API keys, and user settings.
• Process customer content to parse documents, create summaries or extracted entities, generate embeddings, store vectorized memory, and return retrieval results.
• Enforce quotas, rate limits, backup eligibility, and plan-based feature access.
• Monitor reliability, debug errors, investigate abuse, and protect the service.
• Maintain backup schedules for eligible paid accounts.
• Communicate with you about the service, including operational changes and account issues.

When document AI features are enabled, content may also be processed by local model services running in our infrastructure to generate summaries, classifications, or extracted entities. When document AI features are disabled, the service falls back to non-AI extraction logic where applicable.

We disclose information only as needed to operate the service, comply with law, or protect rights and security.

• Infrastructure and hosting providers: Vercel for the frontend, Supabase Postgres for account and transactional storage, Redis for cache and queue state, and Qdrant for vector storage and snapshot operations.
• Model and parsing providers: Voyage AI for embeddings, and local model tooling we operate for certain document extraction features.
• Authentication providers: Google and GitHub if you choose their login flows.
• Legal and safety disclosures: when required by law, regulation, legal process, or to protect Neuralbase, our users, or the public.
• Business transfers: in connection with a merger, acquisition, financing, or sale of assets, subject to appropriate confidentiality and legal safeguards.

Neuralbase does not sell personal information and does not share personal information for cross-context behavioral advertising.

Neuralbase uses a session cookie named neuralbase_session to keep authenticated dashboard users signed in. The site also stores interface preferences in browser local storage, including theme, feature previews, sidebar state, and last-used login provider.

We do not currently run a third-party advertising or behavioral analytics stack on the site. Because there is no universal standard for browser "Do Not Track" signals, Neuralbase does not currently treat DNT as a separate opt-out mechanism.

We retain information for as long as needed to provide the service, comply with law, and enforce security and operational requirements.

• Account, organization, and API-key records are retained while the account or workspace remains active and for a reasonable period afterward where needed for security, fraud prevention, legal compliance, or dispute resolution.
• Session and OAuth state records are retained only until logout, expiration, or cleanup.
• Memories and parsed document results are retained until deleted by the user, removed through service operations, or deleted as part of account closure.
• Paid-plan backup records are retained according to the active retention period. Scheduled snapshots currently use a 30-day retention window on eligible plans.
• Local storage preferences remain on your device until you clear them or your browser removes them.

Depending on where you live, you may have rights to access, correct, delete, or receive information about the personal information we process. You may also have the right to appeal a denial of a request or to limit certain kinds of processing.

You can already manage some information directly through the product, including deleting memories or documents, revoking API keys, and updating profile-related information through your authentication provider. For privacy requests that require help from us, use the support path at https://github.com/ovieodeimor-max/Neuralbase/issues/new or any support channel listed in your order form or workspace.

California residents can also request information about categories of personal information collected, sources, purposes, and categories of disclosures, subject to applicable law and any relevant exemptions.

We use administrative, technical, and organizational measures designed to protect information from unauthorized access, loss, misuse, or alteration. No internet or storage system is perfectly secure, and we cannot guarantee absolute security.

Neuralbase is operated using infrastructure that may process information in the United States or other countries where our service providers operate. By using the service, you understand that information may be transferred to and processed in those locations.

Neuralbase is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

We may update this Privacy Policy from time to time to reflect changes to the service, applicable law, or our processing practices. We will post the updated version on this page and revise the "Last updated" date when we do.

For questions about this Privacy Policy, open a request through GitHub support. For general product information, see the public repository at https://github.com/ovieodeimor-max/Neuralbase.

Read the Terms of Service for the rules that govern use of the platform.