MCP, API and webhooks addendum
Version: 2026-11-15
Last updated: 15 November 2026
This addendum contains privacy information and specific terms for voluntarily connecting external AI tools, API clients and webhook receivers to BilagPilot. It supplements the Privacy Policy, Terms of Service and the data-processing agreement applicable to the Customer's service. Language, governing law and the remaining contract terms follow the main agreement. For the Norwegian service, this is a convenience translation and the Norwegian version prevails; for the international service, the English version applies.
1. When this addendum applies
The Customer does not need these optional functions to use the rest of BilagPilot. Before a new activation or connection, an authorised administrator must accept this version on the firm's behalf. The checkbox is not preselected. BilagPilot records the firm, version, accepting administrator and time.
Acceptance records agreement to these contractual terms and the Customer's instruction. It is not general data-protection consent from the Customer's clients or other individuals, and does not replace a necessary lawful basis, privacy information, data-processing agreement or assessment of professional confidentiality.
Existing connections continue without BilagPilot recording automatic acceptance. Acceptance is required at the next activation or new connection. Once the firm's administrator has explicitly accepted the current version, that acceptance covers further use within this addendum. Additional permissions still require the ordinary access controls.
2. The Customer's instruction and choice of recipients
By enabling access and configuring a connection, the Customer instructs BilagPilot to disclose data to the selected tool or receiver and carry out actions within the permissions granted. This instruction covers subsequent calls, not just setup. The Customer must protect keys and secrets and select the correct firm, user, client access, receiver and permission level.
The Customer is the controller, or a processor acting for its clients. BilagPilot processes Customer Data on the Customer's instructions as processor or subprocessor. The Customer must be entitled to give the instruction and disclose the data, including under client agreements, professional confidentiality and data-protection rules.
The Customer chooses external services and must assess their roles, processing locations, retention, deletion, security, model training and applicable international-transfer safeguards. A checkbox does not by itself determine a recipient's legal role. OpenAI and other providers handle received information under the agreements and terms applicable to their external service.
This is separate from BilagPilot's built-in AI functions, where BilagPilot itself selects and uses subprocessors. Those follow the ordinary Privacy Policy, data-processing agreement and supplier list.
AI assistants you connect (ChatGPT)
An administrator decides whether ChatGPT connections are allowed and which roles may connect. Each user starts their own connection, signs in to BilagPilot, chooses a firm and approves access. Each connection covers one user and one firm. Client access and permitted actions are checked on every call.
Information from BilagPilot becomes part of the user's conversation with the external service. The Customer must choose a subscription and settings suitable for the information and purpose. BilagPilot recommends a business agreement for client data. Personal accounts are not technically excluded; the Customer must therefore assess model training, Memory, sharing, retention and confidentiality before connecting. BilagPilot does not control those settings.
3. Information that may be disclosed
The interface, the user's client access and the connection's permissions determine what can be retrieved. This may include:
Profile and firm
- Information
- Stable profile ID, display name and firm name. The ChatGPT profile tool does not return the user's email address.
Clients
- Information
- IDs, names, business identifiers, country, status and, where supported and permitted, contact details.
Periods and sends
- Information
- IDs, names, dates, deadlines, statuses, titles, notes, missing items and client responses.
Client comments
- Information
- The client's free text when ChatGPT specifically requests the comment field; the ChatGPT tool limits the comment to 280 characters.
Files
- Information
- Names, types, sizes, times, relationships and review status. Some API/MCP-key tools may also provide a time-limited download link where permitted.
Follow-up and activity
- Information
- Reminder status, times, activity summaries and reports, within the user's access. Summaries may include names and email addresses of invited staff.
Accounting integrations
- Information
- Connection status and synced document gaps, amounts, dates, references and counterparty information.
Actions
- Information
- Content submitted by the user or external tool, and results and identifiers for those actions.
The limited ChatGPT connection returns file metadata, not file contents or download links. Other interfaces may have broader permissions; the Customer must check each connection. Passwords and accounting-system integration keys are not returned as tool results.
BilagPilot cannot verify that ChatGPT’s request for optional fields reflects an explicit request from the user.
Free text may contain personal information even in a title, note or filename. Filtering identity and card numbers and links is an additional safeguard, not a guarantee that all sensitive information is removed. The Customer must minimise data and must not use the connection for information that the external service is unsuitable or unauthorised to handle.
4. Write actions and their consequences
Depending on the interface and permissions, an external tool can create and edit drafts, sort uploads or perform other available actions. Some MCP/API permissions can also allow sending to clients or changing client data. Those require BilagPilot's separate permissions and confirmations; accepting this addendum does not enable them.
Drafts must be reviewed before use or sending. Linking an upload is not a draft and takes effect immediately. A message delivered to a client cannot be recalled. The Customer must check the recipient, scope, content and outcome and must not assume a tool's explanation alone proves success.
The ChatGPT connection described above is limited to reading, drafts and sorting; it does not send messages to clients. Available permissions are shown during setup and in BilagPilot. These functions do not post accounting entries or approve accounting judgements.
5. Webhooks
The Customer chooses the HTTPS receiver, events and client access. BilagPilot sends signed notifications containing event type, time and identifiers, and any external references entered by the Customer. Notifications do not contain document contents, contact lists or message text. Identifiers and external references can nevertheless be personal information or allow information to be linked.
The receiver must verify signatures, protect the secret and handle duplicates, delays, out-of-order events and temporary failures. BilagPilot may retry delivery and stop a receiver after repeated failures. Webhooks do not guarantee delivery at a particular time and must not be the Customer's only control for deadlines or critical tasks.
A changed receiver address counts as a new connection for checking this addendum. Turning off a webhook stops further delivery to it, but does not delete information already received.
6. Use at the Customer's own risk and responsibility
Use of independently selected external AI tools, API clients, automations and webhook receivers is at the Customer's own risk as regards selection, configuration and use of those services. The Customer bears the risk of incorrect receiver addresses, compromised Customer-controlled keys, inaccurate or misleading AI results, its own automations and actions performed within the permissions it grants.
The Customer is responsible for professional review, lawful disclosure, correct recipients and necessary agreements with its external providers. BilagPilot cannot guarantee third-party availability, security, retention, deletion or use of information after disclosure. The Customer must follow up failures and verify that intended tasks were actually completed.
BilagPilot remains responsible for its own service, including access control, authentication, secure processing and keeping disclosures and actions within agreed permissions. The own-risk provision does not excuse BilagPilot's own contractual breaches, wilful misconduct, gross negligence or liability that cannot lawfully be limited. The main Terms' liability provisions otherwise apply. This addendum does not limit individuals' rights or either party's mandatory data-protection obligations.
7. Information retained by BilagPilot
Acceptance of this addendum
- Retention and deletion
- Firm, agreement version, administrator ID and time retained as evidence until the firm's data is deleted. Deleting a user does not remove the firm's acceptance; the user reference may be removed.
OAuth connection and profile ID
- Retention and deletion
- Connection record kept as a security/audit record until firm deletion. Profile ID remains while the user and firm exist. Revocation stops access.
OAuth request and code
- Retention and deletion
- Valid for 15 minutes and 60 seconds respectively; cleaned up after one day.
OAuth tokens
- Retention and deletion
- Stored as cryptographic digests. Access tokens last one hour; refresh tokens rotate and expire after 60 days idle and at most 365 days. Token records are cleaned up 30 days after expiry.
API key
- Retention and deletion
- Secret shown once and stored as a cryptographic digest. Access follows expiry, revocation and permissions. Connection metadata follows the firm's other data.
Invocation log
- Retention and deletion
- Tool, outcome, times and argument digest, not raw arguments or results. 90-day cleanup window.
Confirmations and repeated writes
- Retention and deletion
- Short-lived confirmations expire after 10 minutes. Write results remain for 24 hours to prevent duplicate actions. Other approval queues follow their displayed deadlines.
Webhooks
- Retention and deletion
- Receiver address, selected events/clients and encrypted signing secret while configured. Event and delivery history have a 90-day cleanup window.
OAuth browser cookie
- Retention and deletion
- Browser binding expires after 15 minutes.
Technical cleanup runs through scheduled jobs. Drafts, changes and other Customer Data follow the ordinary retention described in the Privacy Policy and data-processing agreement. External recipients have their own retention and deletion rules.
8. Disabling and revoking access
An administrator can turn off the MCP/API server, revoke keys and OAuth connections and disable or delete webhooks in Settings. MCP/API and webhooks have separate controls; check both to stop all external access. A user can disconnect their own ChatGPT connection.
Disconnection stops future use but does not retrieve or delete information already disclosed. The Customer must arrange deletion with its external provider. BilagPilot may restrict or stop access for security, abuse prevention, legal requirements or provider changes.
9. Changes and contact
Material changes in scope, responsibility or data processing follow the main agreement's notice rules and may require renewed explicit acceptance before a new activation or connection. BilagPilot does not record previous use as automatic acceptance of a new version.
Privacy and disclosure enquiries: privacy@bilagpilot.no. Product support: support@bilagpilot.no. Provider: Bjorvand Solutions, organisation no. 836 135 652.
Bjorvand Solutions
Organisation number: 836 135 652
Email: privacy@bilagpilot.no