Skiplino AI assistant connector — privacy notice

Version 1.0 · Effective 2026-11-17

This notice explains how Skiplino handles personal data when your company connects Skiplino to an AI assistant (such as Claude, ChatGPT, Codex, Visual Studio Code or Cursor) through the Skiplino connector at https://mcp.skiplino.com. It supplements the Skiplino Privacy Policy, which still applies to everything this notice does not cover — including who the data controller is and how you exercise your rights as a data subject.

1. Who can use the connector

Only Skiplino company administrators whose company has switched the connector on. A signed-in user can only reach data of their own company; the connector has no way to name or reach another company.

2. What data is processed

CategoryExamplesWhere it comes from
Account dataemail address, company, sign-in method, sign-in timeyour Skiplino account
Connection dataIP address, country, browser/app identifier and TLS client fingerprint — of your browser when you sign in, and of the AI assistant when it uses the connectorrecorded at sign-in and on use
Business data returned to the assistantqueue and ticket activity (counts, statuses, waiting and service times, feedback), branches, services, team members (name, code, branch, desk, last sign-in), opening hours and closures, company contact detailsyour company’s Skiplino data
Requests you makethe tool called, its arguments, the outcome, and — for changes — the preview and the approvalyour use of the connector

What is not returned: passwords, tokens, payment and card data, and other credentials. Customer contact details in tickets (such as phone numbers and email addresses) and message delivery logs are masked or omitted.

Skiplino does not receive or store your conversation with the AI assistant. It only sees the requests the assistant makes to the connector.

3. Why

4. Who receives the data

When you use the connector, the results of your requests are sent to the AI assistant you chose to connect — for example Anthropic, OpenAI, Microsoft or Cursor — and are handled there under that provider’s own terms and privacy policy. You and your company decide which assistant to connect; Skiplino does not choose it and does not control what it does with the data afterwards. Review the assistant provider’s policy before you enable the connector.

Skiplino’s own service providers (hosting and monitoring) process the connector’s records on Skiplino’s behalf, as for the rest of the Skiplino platform.

5. How long

DataKept for
Access tokens1 hour
Refresh tokens (sessions)30 days; 7 days for desktop apps (Visual Studio Code, Cursor, Codex, Claude Code)
Authorization codes60 seconds
Pending change approvals5 minutes
Audit records (tool, arguments, outcome, time)90 days
Operational telemetry (request, error and performance logs)90 days
Network access and security logs (IP address, requested address, security decision)30 days
Consent record (owner’s name and email, notice version, time)as long as the company account exists
Connector account record (email, company, last sign-in)no automatic expiry; ask privacy@skiplino.com to delete it

Audit records of a read keep the arguments of the request. Arguments can contain what you typed into the assistant (for example a ticket reference), so they are retained for the 90 days above.

6. Your controls

7. Security

Sign-in uses OAuth 2.1 with PKCE. Tokens are short-lived and refresh tokens rotate; a reused refresh token revokes the whole session. Every request is checked against the user’s company, role and the company’s connector switch.

8. Changes to this notice

We publish changes at this address with a new version number. If your company’s owner accepted an earlier version in Account → AI assistants, they are asked to review and accept the new one there; the connector keeps working in the meantime.

9. Contact

Need help? Contact support@skiplino.com or visit skiplino.com.