CompanyBook connection privacy
Data used to connect your account, deliver company results and protect access.
What CompanyBook receives
The Data Company Ltd. provides MCP access through your existing CompanyBook account, using OAuth. Tools receive company identifiers and permitted search or lookup options. File contents, URLs, filenames, full spreadsheet rows, unrelated columns and conversation transcripts remain in the host and do not enter CompanyBook tools.
ChatGPT/Codex and their file environments process your questions, files and received results under their own terms and privacy controls. Disconnecting CompanyBook cannot erase data already received by that host. The existing website privacy policy applies to your CompanyBook account.
Records needed for access and security
CompanyBook keeps the OAuth grant and token lifecycle records needed to link the account, expire or revoke access and detect unsafe refresh-token reuse. Company requests use the existing customer API, including its permission checks and applicable quota/accounting records. Reconnection does not erase spent usage.
CompanyBook stores OAuth requests, authorization codes, grant families and token signatures. These records expire after their lifecycle and replay windows. Access checks enforce expiry and revocation independently of physical cleanup. Existing customer API tracking and quota records remain governed by the website privacy policy. The free usage tool does not retain a copy of the quota snapshot.
The host manages list iteration, partial responses and output files. CompanyBook does not store a workflow’s files or offer saved-result recovery. Disabling the connection does not delete existing records needed to enforce access or usage.
Disconnect an OAuth grant in Connections to deny new operations through it. Already admitted requests may have spent their normal API allowance even if a later authorization change withholds the result.
Recipients and controls
Permitted company results go to the connected host and its conversation/file environment. CompanyBook uses its existing service infrastructure and monitoring. MCP and OAuth use the existing HTTP request, latency and error metrics. Integration request and panic logs omit credentials and raw request payloads.
Use Connections to manage OAuth access. Contact CompanyBook through its existing privacy channel for account-data rights. Report the error category and time without credentials, private rows or full conversations.