Legal
How NerveHQ handles website submissions, platform information and authorized connected-service data.
What this means in practice
When you request a demo, we receive your name, work email, company, optional workflow notes, referral details, and submission time. The application does not add IP addresses or user-agent strings to analytics or lead records. Our web server processes these network details in restricted security logs. Do not submit credentials or confidential production data.
We use submitted details to respond, qualify the requested workflow, protect the form from abuse, maintain operational records, and understand site performance when analytics consent is granted.
Requests are recorded in NerveHQ-managed storage and CompuArt’s approved CRM or notification systems. Raw consented analytics are retained for 90 days and aggregate reporting for up to 365 days. Restricted web-server security logs are rotated daily and retained for up to 30 days. Lead records follow CompuArt’s operational CRM retention process. Contact nervehq@compuartstore.com to ask about your submitted information or request deletion where applicable.
The sections below also describe connected-service processing in NerveHQ at agents.compuartstore.com. The platform can process account details, prompts, conversation history, uploaded files, approved instructions and memory, retrieved business records and generated reports. Organization administrators control workspace assignments and configured tasks. Private deployments may have additional organization-specific notices and agreements.
Connecting Google Sheets uses Google's sign-in and consent flow. NerveHQ receives authorization tokens, not your Google password. The current integration requests https://www.googleapis.com/auth/spreadsheets, which permits viewing and editing spreadsheets accessible to the connected Google account. This Google permission is not limited to one spreadsheet or to reading only. NerveHQ separately checks the user, workspace, assigned agent and permitted operation. Authorized requests can retrieve spreadsheet identifiers, tab names, ranges, headers and cell values, including personal information present in those cells. This integration does not itself request Gmail access or general Google Drive file-listing access.
Connected information is used to perform the tasks you authorize, such as answering questions, validating records, checking duplicates, preparing reports and carrying out permitted actions. For example, an authorized workflow may read lead rows from Google Sheets and create validated Contacts and linked Opportunities in the configured Odoo system. A read-only task does not authorize changes to Sheets merely because the Google permission allows editing. Scheduled tasks may operate under a configured standing authorization without a new message for each occurrence; platform and Connection controls still apply.
Relevant task context and retrieved content may be sent to the AI provider selected for the task, including OpenAI when a Codex model is used. This can include Google Sheets cell values and personal information within them. Authorized tasks may also send necessary information to configured destinations such as a CRM. Hosting and operational providers process information needed to deliver the service. A private server deployment does not by itself mean AI processing stays on that server. Provider retention, data-use terms and processing locations depend on the actual deployment and provider account configuration; contact nervehq@compuartstore.com for the arrangements applicable to your service before supplying sensitive information.
Connection credentials are encrypted in the server-side vault and supplied by the backend for authorized requests. The Connection gateway is designed to keep those credentials outside agent prompts and tool results. Do not paste credentials into prompts or upload them as task files. Retrieved data and derived information can appear in conversation history, run output, reports, workspace files and approved memory. Short-lived result-page caching does not determine how long these other copies remain. Credential encryption is not a claim that every stored business record or backup is encrypted at rest.
The marketing-site retention periods above do not establish a universal retention period for platform data. Platform retention depends on data type, deployment settings, ongoing tasks, recovery needs and applicable obligations. Some run, upload and audit records are subject to automated cleanup; workspace files, approved memory, backups and copies in external systems may follow separate processes. Contact nervehq@compuartstore.com to request information, correction or deletion for an account or workspace. We may verify identity and authority and explain any applicable retention or backup limitations. Do not send passwords with a request.
You can remove NerveHQ access at https://myaccount.google.com/connections. An authorized NerveHQ user or administrator can also disable or revoke a Connection or its assignments through the available controls. Once revocation takes effect, future use of that grant is blocked. Disconnecting does not erase previously retrieved information, delete records already created in another system or cancel completed actions. Request deletion separately where needed. Changes to the purpose of Google-data use requiring renewed consent must be explained before the new use.
Continue exploring
See how your people can use specialized AI agents, company knowledge, and connected systems from one governed command center.