1. Who operates Neuron
Neuron is operated by Feline Labs LLC. Privacy and security questions can be sent to [email protected].
2. Data Neuron collects
Neuron may collect and process the following data when customers use the service:
- Account information, including email address, authentication events, plan, and support messages.
- Billing information needed to process subscriptions, Spark top-ups, invoices, refunds, and disputes.
- Assistant content, including prompts, responses, conversations, generated artifacts, files, and metadata.
- Memory records, corrections, preferences, source references, and deletion/export events.
- Integration data from connected services such as email, calendar, file storage, and documents.
- Scheduled job definitions, run logs, approval records, Spark usage, provider usage facts, and audit logs.
- Technical data such as IP address, device/browser metadata, error logs, rate-limit events, and security logs.
3. How data is used
Feline Labs uses data to provide and protect Neuron, including to:
- Run assistant workflows, memory, files, integrations, scheduled jobs, approvals, and generated artifacts.
- Meter usage, manage Spark balances, process billing, reconcile checkout events, and prevent abuse.
- Secure accounts, detect misuse, enforce limits, and comply with legal obligations.
- Communicate about account access, billing, security, support, service changes, and policy changes.
At launch, Neuron does not send promotional or marketing emails unless a person separately opts in to receive them. Neuron may still send transactional messages needed to provide the service, including account, security, billing, purchase, support, and important service or policy notices.
4. AI providers and subprocessors
Neuron sends relevant prompts, context, files, tool results, and usage metadata to AI model providers and infrastructure providers when needed to complete a user request. Feline Labs does not sell customer content.
Customers should not connect highly regulated data unless Feline Labs has explicitly agreed in writing that the account is approved for that use case.
5. Google Workspace data and Limited Use
Neuron's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.
Google Workspace data is accessed only for the capability a customer selects and uses only to provide that user-visible capability, to secure and operate the service, or as otherwise required by law. Neuron does not use Google Workspace data to serve advertising, sell it, or train generalized AI or machine learning models. Before Google consent and before a relevant action, Neuron explains the capability and whether the requested data will be sent to an AI processor or another external destination.
For Workspace-derived inference, Neuron uses a fixed OpenRouter route with data collection denied, zero-data-retention requested, and no price-based routing or provider fallback. Neuron keeps raw and derived Workspace data out of generalized memory, reusable prompt logs, provider feedback, shared evaluations, and ordinary analytics. The reviewer-facing downstream processor inventory remains a release gate until its effective allowlist is formally accepted.
6. Integrations and credentials
Customers choose which integrations to connect and can disconnect them in the product. Neuron uses integration tokens and permissions only to provide requested assistant workflows, scheduled jobs, sync, retrieval, and approved actions. Disconnecting an integration stops future access. Workspace artifacts and cached derived copies are subject to the Workspace lifecycle policy; content-free tombstones may remain only to prevent duplicate actions and prove deletion.
7. Security controls
Neuron is designed with security controls appropriate for an early paid product:
- Encryption in transit for web app and API traffic.
- Access controls for accounts, workspaces, integrations, billing, and administrative surfaces.
- Audit records for assistant runs, Spark usage, provider events, integration changes, and deletion actions.
- Approval gates for sensitive external actions where the product requires confirmation.
- Rate limits, abuse monitoring, checkout reconciliation, and provider-event idempotency.
- Account export, deletion readiness, and integration credential cleanup paths.
9. Data retention
Retention depends on the plan, account state, legal obligations, security needs, and product controls. Customers can request export or deletion. Some billing, ledger, security, and abuse-prevention records may be retained when necessary for accounting, dispute resolution, fraud prevention, legal compliance, and audit integrity.
10. Customer choices
Customers can request access, export, correction, deletion, or integration disconnection by emailing [email protected]. Product surfaces may also provide self-serve controls for memory visibility, deletion, account export, and integration removal. Step-by-step instructions for reviewing, disconnecting, revoking, exporting, and deleting Google Workspace-related data are available on the Google Workspace data controls page.
11. Children
Neuron is not intended for children and should not be used by anyone under 13. Customers must not knowingly submit children's personal data without appropriate authority and legal basis.
12. Changes
Feline Labs may update this policy as Neuron changes. Material changes will be reflected by updating the date on this page and, where appropriate, notifying customers through the product or account email.