Privacy Policy

Effective September 26, 2026

This Privacy Policy explains how Neuroaigent Inc. (“NeuroAIgent,” “we,” “us,” or “our”) handles information in connection with AEO Presence, Central Brain, Central Brain Companion, related websites, licensing, and support.

Information we collect

Account and business information: name, email, organization, role, account status, login timestamps, and communications.
Billing information: plan, subscription or Order information, transaction status, and limited payment metadata. Payment-card details are handled by the payment processor shown at checkout and are not stored by NeuroAIgent unless expressly stated there.
AEO Presence information: submitted URLs, crawl settings, scorecards, report history, scheduled-delivery settings, project permissions, and generated reports.
Central Brain licensing information: license key or identifier, device or installation identifier, activation and validation timestamps, software version, entitlement, and validation status.
Support and security information: information you voluntarily provide, product and operating-system version, error messages, diagnostic details, access changes, administrative actions, and security or audit events.
Website information: ordinary server logs and analytics information such as IP address, browser type, referring page, pages visited, and approximate timestamps, subject to the tools configured on the site and to your cookie choices.

Central Brain local data

Central Brain’s default project workflow stores source references, prepared files, project state, vector data, reports, and configuration on storage you choose. Local MiniLM embeddings are computed on your system. NeuroAIgent does not receive that project content merely because you prepare or search it locally.

Central Brain is not completely offline: activation and periodic license verification contact Keygen and can transmit the license identifier or key, an installation or device fingerprint, IP address, platform information, software version, entitlement, and validation status. The website separately uses the providers described below. Optional cloud and AI connections transmit selected information when you configure and use them.

You control your source folders, output folders, projects, retention, deletion, and backups. Other people, administrators, sync tools, backup services, AI tools, or software with access to those locations or configured connections may also be able to access the information independently of NeuroAIgent.

Optional providers, publishing, and AI connections

If you enable a cloud embedding service, custom endpoint, Pinecone, Postgres, Redis, an AI tool, cloud connector, or another integration, Central Brain sends the selected data needed for that feature to the provider you configured. Those providers process information under their own terms and privacy notices. Review the destination, permissions, and configuration before enabling it.

Project-specific MCP connections can expose prepared project information to supported AI tools. You decide which projects and connections to enable. Sharing and pairing features may transmit selected data directly to trusted devices or users you authorize.

Central Brain Companion

Central Brain Companion does not require a NeuroAIgent account. It does not send Companion documents, pairing invitations, filenames, file metadata, device-usage information, local-network traffic, analytics, advertising identifiers, or tracking information to NeuroAIgent. It contains no third-party advertising, analytics, or tracking software, and it does not send selected documents to third-party AI providers. These statements apply specifically to the Companion’s current local-transfer workflow.

Information stored locally

The Companion stores a device-specific cryptographic identity and approved Mac connection details locally; pairing credentials are stored in the iOS Keychain. It may also store settings and limited operational information needed to show pairing and transfer status. This locally stored information is not transmitted to NeuroAIgent.

Documents you choose to transfer

When you select a document through Apple’s Files picker and initiate a transfer, the Companion sends it directly to the selected Mac over an encrypted local-network connection and verifies the Mac’s certificate fingerprint before connecting. This local transfer does not use a NeuroAIgent-operated cloud relay. The receiving Mac owner decides whether to accept the document and how to store, process, use, disclose, retain, back up, or delete it. NeuroAIgent does not control the receiving Mac, its owner, its users, its security, or third-party software operating on it.

Permissions, pairing, and deletion

The Companion requests Local Network access to reach a paired Mac. You choose documents through Apple’s Files picker and may manage Local Network permission in iPhone Settings; denying it prevents local transfers. You may unpair a Mac in the app. Deleting the app removes app-container data, although iOS may retain some Keychain items unless the app deletes them or the device is erased.

How we use information

Provide, secure, maintain, license, and improve the products.
Run audits, generate reports, manage subscriptions, and deliver requested communications.
Validate licenses, prevent fraud or abuse, investigate errors, and enforce access controls.
Respond to support requests and perform services included in an Order.
Comply with law, resolve disputes, and protect customers, NeuroAIgent, and third parties.

Named service providers and what they receive

Stripe processes checkout, subscriptions, taxes, invoices, refunds, disputes, and the customer portal. Stripe receives the purchaser’s name, email, billing address, payment details, plan, amount, transaction identifiers, IP/device or fraud-prevention signals, and subscription activity. NeuroAIgent receives limited payment and subscription metadata rather than complete card numbers. See Stripe’s privacy policy.
Keygen issues and validates machine-bound licenses. Keygen receives the license key or identifier, purchaser email in the license record, Stripe customer/subscription/price references, plan and seat metadata, expiration and suspension state, activation and validation times, IP address, and the device fingerprint and platform information sent by the installed app. It does not need your Central Brain project documents. See Keygen’s privacy policy.
Resend delivers license, download, payment-failure, and renewal emails. Resend receives the recipient email address, sender and reply-to address, subject, message body—including delivered license keys and download links—and delivery metadata. Opens or clicks may also be recorded if enabled in the Resend account. See Resend’s privacy policy.
Google Analytics measures website use and selected checkout or contact-button events, and loads only if you allow analytics cookies (see Cookies). Google may receive page URL, referrer, campaign parameters, approximate location derived from IP address, browser/device information, timestamps, and analytics identifiers. We do not intentionally send names, email addresses, license keys, Stripe IDs, Keygen IDs, document contents, or completed-payment details to Google Analytics. See Google’s privacy policy.
YouTube (Google) hosts videos shown on some pages. Nothing is loaded from YouTube until you press play; playing a video loads Google’s privacy-enhanced player (youtube-nocookie.com), which receives your IP address, browser/device information and the page you are on, and may set cookies or similar storage. See Google’s privacy policy.
GoDaddy hosts the WordPress website and its database, caching, backups, and ordinary server logs. It can process IP address, request headers, pages requested, timestamps, information submitted to the website, and the account, commerce, license-reference, support, and operational records stored in WordPress. The commerce bridge does not intentionally store complete payment-card numbers or full license keys in its ordinary database tables. See GoDaddy’s privacy notice.
Microsoft Azure hosts Central Brain installer files in Azure Blob Storage. When you download an installer, Azure can receive the requested file and URL, IP address, timestamp, browser or download-client information, referrer, request identifiers, and transfer/status details. Installer hosting does not require your Central Brain project documents. See Microsoft’s privacy statement.

We may also disclose information to a destination you deliberately configure, when required by law or legal process, to protect rights and safety, or in connection with a merger, financing, acquisition, reorganization, or sale of assets. We do not sell personal information. We do not intentionally use the website analytics events described above for cross-context behavioral advertising. For clarity, the Companion’s current local-transfer workflow does not send its documents or pairing information to these providers.

Cookies and similar technologies

Cookies are small files a website stores in your browser. This website uses them in three groups. Optional cookies stay off until you choose: nothing in the analytics or marketing groups loads before you allow it, and rejecting is as easy as accepting.

Strictly necessary (always on): na_consent remembers your cookie choices for 180 days, or until we change this section and ask again. It holds your choices, the policy version, the time you chose, whether your browser sent a Global Privacy Control signal, and a random ID. Cloudflare, which protects and delivers this website, sets __cf_bm to tell people from automated bots; it expires after 30 minutes. If Cloudflare shows you a security check, it may also set cf_clearance to remember that you passed. WordPress sets sign-in cookies (wordpress_logged_in_*, wordpress_sec_*, and wordpress_test_cookie) only if you log in to this website; they last until you close your browser, or 14 days if you choose “Remember Me.” Signed-in administrators may also receive wp-settings-* cookies that keep dashboard preferences for up to one year.
Analytics (optional): if you allow analytics, Google Analytics 4 loads and sets _ga, which distinguishes visitors, and _ga_<container-id>, which keeps session state. Google’s default lifetime for both is two years from your most recent visit; some browsers cap it sooner (Chrome caps cookie lifetimes at 400 days). If you do not allow analytics, Google Analytics does not load.
Marketing (optional): if a page includes the TrustedSite certification badge, the badge loads only after you allow marketing cookies. TrustedSite may then set its own cookies, with names beginning _tccl_ or trustedsite_, under its own privacy policy.

Changing or withdrawing your choice

Use the Cookie settings link at the bottom of our pages to review, change, or withdraw your choice at any time. Withdrawing analytics stops Google Analytics on the current page, deletes its _ga cookies from this website, and keeps it from loading on later pages. You can also delete cookies in your browser settings; we will then ask again.

Global Privacy Control

If your browser sends a Global Privacy Control (GPC) signal, we honor it as an opt-out: marketing cookies stay off and cannot be switched on while the signal is present, and Google’s advertising consent signals stay denied. Analytics remains a separate choice.

Why we use them

Strictly necessary cookies are needed to deliver this website securely and to remember your privacy choice, so they are always on. Where EU, UK, or Swiss law applies, we rely on our legitimate interest in running a secure, working website, and these cookies do not need your consent. We use analytics and marketing cookies only with your consent, which you can withdraw at any time; withdrawing does not affect what happened before you withdrew.

When you save a choice, we keep a record so that we can show consent was given: the random ID from na_consent, the policy version, your choices, whether a GPC signal was present, and the time. The record does not include your IP address or browser details, and we keep it for up to two years.

Retention periods

Orders, invoices, payments, refunds, tax, disputes, and related commerce audit records: seven years after the transaction or subscription ends, unless a longer period is required for an active dispute, legal hold, tax obligation, or fraud investigation.
Central Brain license, entitlement, activation, device-reset, and machine records: while the license or subscription is active and for 24 months afterward. We then delete or de-identify them unless they are tied to a retained commerce record, abuse investigation, dispute, legal hold, or legal requirement. Keygen states that its request logs, backups, caches, and temporary storage may persist for up to 30 days after underlying data is erased.
Support communications and troubleshooting attachments: three years after the request is closed. Credentials and unnecessary sensitive attachments should not be sent and may be deleted sooner.
AEO Presence account, configuration, and report records hosted for a customer: while the account or service is active and for 24 months after closure, unless the customer requests earlier deletion that we can lawfully honor.
Google Analytics user-level and event-level data: 14 months. Google explains that the GA4 retention setting does not necessarily remove information from standard aggregated reports, which may remain available longer.
Website, security, and download request logs: ordinarily 30 days; GoDaddy states that shared-hosting access logs rotate every seven days. A log excerpt preserved for a specific security incident, abuse investigation, or legal request may be kept for up to one year or with the related case.
Transactional email: the WordPress retry outbox keeps an encrypted copy of an unsent message for no more than approximately 23 hours before requiring manual review, and replaces successfully sent content with a delivery receipt. Resend receives the message content and delivery metadata; we target 12 months for accessible delivery history in our Resend account, subject to provider security logs, backups, legal holds, and Resend’s own terms.

Backup copies and service-provider systems may take up to 90 additional days to age out after scheduled deletion unless a provider’s published period is shorter or law requires longer retention. Customer Data stored only on your systems remains subject to your retention choices, not ours. We review these periods at least annually and may shorten them when the information is no longer needed.

Security

We use administrative, technical, and organizational safeguards appropriate to the information and product, including access controls, encrypted transport where applicable, protected secret storage, and security logging. No storage, software, network, or transmission method is completely secure. You are responsible for securing your devices, accounts, networks, credentials, storage locations, and backups.

Your choices and rights

You may manage product settings, optional connections, sharing permissions, local data, and account communications, and change your website cookie choices at any time. Depending on where you live, you may request access to, correction of, deletion of, or export of personal information held by NeuroAIgent. We may verify your identity and retain information where permitted or required for security, fraud prevention, billing, or legal compliance.

Children

The products are intended for adults and authorized business users and are not directed to children under 13. We do not knowingly collect personal information from children under 13 through the products.

International use

Information provided to NeuroAIgent or its service providers may be processed in the United States and other locations where those providers operate. Those locations may have different privacy laws. We use legally recognized protections where required.

Changes to this policy

We may update this Policy to reflect product, practice, or legal changes. We will post the current version with a revised effective date and provide additional notice or obtain consent when required.

Contact us

Privacy requests: privacy@neuroaigent.com
Product and support questions: support@neuroaigent.com