Privacy Policy

Information We Collect

DeviceLink collects only the minimum information necessary to provide our services:

• Account information (the email address held by the sign-in method you use: Google, GitHub, Microsoft, or an email and password you set yourself)
• Device identifiers for authorization and tool routing
• Tool call usage records (tool name, timestamp, credits consumed)
• Shared directory metadata (the names of folders you explicitly publish, and their paths where the device reports one - a folder shared from a browser tab reports its name only)
• Security and audit records (see Security and Audit Logs below)
• Product usage data (see Analytics and Usage Data below)

DeviceLink does not store the contents of your files. File data is streamed in real-time between your device and the requesting client, and is never persisted on our servers. Passing a request along means our service decrypts it, so the contents exist in server memory for as long as it takes to forward them to the AI platform you connected. They are never written to disk, cached, or logged. The security page describes this in more detail.

How We Use Your Information

• Authenticate and authorize your devices, by signing you in and by checking each device can prove it holds its own key
• Route requests between the AI platforms you connect and your own device
• Track credit usage for billing purposes
• Maintain service reliability and security

Analytics and Usage Data

We collect product usage data to understand how DeviceLink is used, where setup fails, and what to improve. This data is processed on our behalf by our analytics provider, hosted in the European Union and named on the subprocessors page.

When you are signed in, this activity is linked to your account: your user ID, together with the organization and workspace you are working in. We do not send the email address on your account to our analytics processor. We use that link to support you, to see how teams actually use the product, and to tell a real problem from a one-off. Your IP address is never sent to our analytics processor, and IP-based geolocation is disabled there, in both the web app and the CLI agent. Your IP address is recorded in our own security audit log, described below.

In the web app we record the pages you visit, the actions you take in the interface, your browser and operating system, and errors the application runs into. We never record file names, file contents, directory paths, or tool arguments.

The DeviceLink CLI agent reports usage data from your machine: a random install identifier generated on first run, the agent version, your operating system platform and major version, CPU architecture, and lifecycle events such as sign-in, connection, and the names of tools invoked. It never reports file names, file contents, directory paths, tool arguments, your username, or your machine identifier, and it does not record your IP address. Your device name is sent to DeviceLink, not to our analytics processor, so that you can tell your devices apart in the dashboard; it defaults to your computer's hostname unless you set one. A folder shared from a browser tab is named after the browser instead, because a web page cannot read your computer's hostname.

Sharing a folder from a browser tab reports the same kind of lifecycle events - that a folder was shared or removed, that the browser connected or disconnected, and which tools ran - together with how many folders are shared. It never reports the names of those folders, the names or contents of files inside them, or tool arguments. Error reports from the web app are stripped of filesystem paths before they are sent, and the parts of the interface that list your files are excluded from interaction recording.

That install identifier is anonymous until you pair the device. When you sign in from the CLI, we link it to your account so that a device connecting and a tool running can be seen as the same person's session rather than as two unrelated ones. Opting out of CLI telemetry means the agent sends no install identifier and makes no such link.

CLI telemetry is enabled by default and can be disabled at any time by setting DLINK_TELEMETRY=0 or DO_NOT_TRACK=1 in your environment. That setting applies to the CLI agent only. The web app, including folder sharing from a browser tab, has no equivalent switch today and keeps reporting the product usage described above; if you want your analytics events erased, ask us on the support page.

Security and Audit Logs

Actions taken against an organization - signing in, approving a device, changing a member's access, calling a tool - are written to an audit log. Each entry records what was done and to which resource, the result, the email address of the account that did it, the IP address and browser user agent the request came from, the AI client used where one applies, and the time. This log exists so that an organization can see who did what, and so that we can investigate abuse and security incidents.

Audit entries for an organization are visible to that organization's administrators. They are retained while the account is active, and are kept after an account is deleted where we need them as a record of security-relevant activity.

Processors We Use

We use providers to run the service. They process data on our behalf and only for the purposes described here. Every one of them is listed on the subprocessors page, together with what it is used for, what it processes and where. That page is the authoritative list and records when it changes, so this policy does not need reissuing when a provider is added or removed.

The AI platforms you connect are not subprocessors. They receive your file contents because you asked them to, under their own terms, and you choose which to connect and which folders they can reach.

Third-Party Integrations

DeviceLink integrates with AI platforms including Claude (Anthropic), ChatGPT (OpenAI), and other MCP-compatible clients. When you connect DeviceLink to a third-party AI platform, that platform may access your shared directories through our MCP server, subject to your explicit consent and the directories you choose to share. Beyond the product analytics described above, which are linked to your account, we do not share your data with third parties beyond what is necessary to fulfill tool call requests you initiate.

You may revoke access granted to any AI platform at any time by disconnecting the connector from that platform's settings, or by revoking your OAuth token via the DeviceLink profile page. Revoking access immediately invalidates all active sessions for that platform.

Data Security

All communications are encrypted in transit (TLS). Authentication uses ES256 JWT tokens with short expiration times. Approving a device requires it to cryptographically prove it holds its own key. OAuth flows use PKCE (S256) to prevent authorization code interception.

Data Retention

• Account data - retained while your account is active
• Device authorization records - an authorization request expires if it is not approved within 20 minutes; approved device keys are retained while the device is registered
• Access tokens - short-lived, configurable expiration (typically minutes); automatically refreshed
• Refresh tokens - time-limited with configurable TTL; extended on active use, expire after period of inactivity
• Usage charge records - retained while your account is active, and after account deletion where we are required to keep billing records
• Audit log entries - retained while the account is active, and kept after deletion where needed as a record of security-relevant activity
• Product analytics events - retained by our analytics processor under its standard retention; deleted on request
• File contents - never stored; streamed in real-time only

Your Rights

You have the right to:

• Access your data - view your profile and usage history at /profile
• Correct your data - update account information through your identity provider
• Delete your account - from the Danger Zone on your profile page, or by asking us
• Revoke access - disconnect devices or revoke an AI platform's access at any time

Deleting your account removes your sign-in identities and the email address attached to them, closes your personal organization and its workspaces, ends your memberships of any other organization, revokes every paired device so that a running agent can no longer connect, and revokes the access you granted to AI clients.

Two things are deliberately kept: billing and usage charge records, which we retain as financial records, and audit log entries, which are a record of security-relevant activity and may name the account that performed an action. If you want your product analytics events erased as well, or a copy of the data we hold, ask us on the support page and we will action it within 30 days.

Changes to this page

• October 2026 - Described sharing a folder from a browser tab, and what it reports. Stated that the CLI telemetry switch applies to the agent only and that the web app has no equivalent. Corrected the device authorization expiry to 20 minutes. Replaced the duplicated provider list with a link to the subprocessors page. Stated that file contents pass through our bridge in memory on the way to the AI platform you connected.