Product privacy policy

This policy describes how Credence Software ("Credence," "we," or "us") handles information when you use the Credence product through the Credence MCP connector at mcp.credence-software.com. It covers the connector used with an AI assistant such as Claude or ChatGPT. The marketing-site privacy policy covers credence-software.com only. A written agreement with your organization may add further terms for customer records stored in Credence.

Information we process

  • Account and permission data. When you connect, Credence identifies your user, your customer organization, and the OAuth scopes you granted. The connector uses read and, when you authorize writes, write.
  • Authentication data. The connector stores the OAuth state needed to keep you signed in, including access tokens and refresh tokens. Those values are encrypted at rest in the connector's token store.
  • Customer records you ask for. A tool returns records your Credence permissions already allow you to see. That can include portfolios, properties, units, leases, rent roll, tenants, vendors, contracts, payables, receivables, bank accounts, bank transactions, chart-of-account records, journal bundles, ledger lines, capital events, fixed assets, projects, jobs, and document metadata. A short-lived document view link is returned only when you open a document you can access.
  • Changes you ask the assistant to make. Create and update tools send the fields you request to Credence. Payment card data and payment execution are not part of these writes. The connector cannot delete records, approve a workflow, or post the ledger.
  • Files you attach. If you ask the assistant to upload a file, the file contents needed for that upload pass through the connector to Credence. Uploads are limited to one file of up to 10 MiB on a supported parent record.
  • Technical data. Our hosting and the connector may process IP address, request time, and error details so we can operate and secure the service.

How information is used

  • To authenticate you and apply your existing Credence permissions.
  • To run the tool you, through your assistant, asked the connector to run.
  • To keep the connection available until you disconnect it or the token expires.
  • To measure connector reliability and diagnose failures.
  • To investigate abuse and comply with law.

Who receives information

  • Your AI assistant. Claude (Anthropic) or ChatGPT (OpenAI), or another assistant you connect, receives the tool arguments it sends and the tool results Credence returns. That provider's own privacy policy covers how the assistant stores the conversation.
  • Your Credence organization. Records created or updated through the connector are stored in the same Credence account as records created in the product.
  • PostHog, when connector analytics is enabled. We send a customer-scoped identifier (credence:{customer id}:{user id}), your user id, customer id, and granted scopes. Tool-call analytics can include the tool name, arguments, and result after the analytics SDK redacts credentials, tokens, and large encoded file contents. We do not add a required conversation-intent field to tools.
  • Infrastructure providers that host the Credence application and the MCP connector.
  • Authorities or other parties when disclosure is required by law or necessary to protect Credence, our users, or the public.

We do not sell personal information for money. We do not use the connector to collect health information, government identifiers, or payment card data.

Retention

  • Credence access tokens expire after one hour unless an environment sets a different lifetime.
  • Credence refresh tokens expire after 14 days by default. Refresh tokens rotate, and a replaced token cannot be reused.
  • Encrypted connector OAuth state is kept for up to 30 days of inactivity when Credence does not supply an earlier expiry.
  • Customer records remain in Credence for the life of the customer account, under that organization's agreement.
  • Analytics and diagnostic logs are kept for as long as needed to operate, secure, and troubleshoot the connector, and then deleted or de-identified.

Your choices

You can disconnect the connector in the assistant you used to add it. Disconnecting stops new tool calls. To ask for access, correction, or deletion of personal information associated with the connector, email info@credence-software.com. We may need to verify the request. Depending on where you live, you may have additional rights to access, correct, delete, or restrict processing, or to complain to a supervisory authority. Customer records belonging to your organization are handled under that organization's Credence agreement.

Children

The connector is not directed to children under 16, and we do not knowingly collect personal information from children under 16 through it.

International transfers

Credence is based in the United States. Service providers and the assistant you connect may process information in the United States and other countries. Where required, we use appropriate safeguards for those transfers.

Changes

We will post updates on this page and change the date below. A material change to the connector's data practices may also be reviewed again by an assistant directory that lists the connector.

Contact

Questions about this policy: info@credence-software.com. See also the product terms and support.

Last updated: October 28, 2026.