Telemetry

Exactly what CPlugin products send to the CPlugin update service — product, version, trading server names, installation key, licence state, start times — what they never send, why, and where it is kept.

CPlugin server plugins talk to one place: the CPlugin update service at update.cplugin.com. That connection delivers your licence and your trial, tells you about new versions and lets us see which versions run where. This page lists everything the connection carries. Nothing is sent that is not listed here — and if a product ever sends a new field, this page is changed first.

We collect no user data. The only purpose of the connection is licensing: to recognise which plugin instance runs on which server. For that we need two things and nothing else — a unique identifier of the plugin instance (a key the plugin generates for itself) and the names that identify the server (company name and server name). Nothing else from your server settings or licences is read or sent. No client, account, trade or database data is sent; the requests have no fields for them.

What you will see in your server journal

On every start a plugin writes one line to the trading server journal, so that nobody has to find this page by accident:

CPlugin: checking license and updates at update.cplugin.com. No client, account, trade or database data is sent. What is sent and why: https://cplugin.com/telemetry

When the plugin connects

At start. A plugin with a valid paid licence connects 30 to 120 seconds after it starts; a new installation, a trial or a plugin without a valid licence connects at once, because its right to run depends on the answer.
Once a day. Every installation has its own fixed time of day, chosen from its installation key, so that requests are spread over the day.
After a failure or a wake-up. After a failed attempt the plugin retries with growing pauses (15 minutes up to 6 hours); after the operating system wakes from sleep, a trial installation connects again at once.

The connection is HTTPS to update.cplugin.com, port 443. The update service never connects to your server — it only answers the plugin's own requests. There is no setting that turns the connection off: a paid licence keeps working until the end date of its file if the service cannot be reached, but a trial does not start without it.

What is sent

Each request is one signed message from the plugin to the service. Its content:

What	Details	Why
Product	which CPlugin product it is (for example `slippage-control-mt4`), its version number and the number of the exact program build	so we can tell you about new versions and find which version has a problem
Every start of the plugin	a random start identifier, start time, product version, build identifier, trading server build	counting starts, finding failures after an update. Starts are queued and sent until the service confirms them, so a start made while offline arrives later
Plugin instance key ("installation key")	the public half of a key pair that the plugin creates for itself on its first start. It is not a password, not an account number and not a licence of MetaTrader or of any other software; it is not taken from your trading server at all. The private half stays on your server, encrypted, next to the plugin	identifies this one installation of the plugin, signs every request
Old instance identifier	a code from the plugin's own settings file (the `discoveryManager` setting), only if you have one set. It is not a password	to recognise a copy of the plugin that was installed before this service existed
Trading platform	MT4, MT5 or none (for standalone applications that have no trading server)	compatibility
Company and server names	the company name and the server name as shown in your server settings (for example "Acme Brokers Ltd" and "Acme-Live-1") — only these two names, the same names in three technical forms (raw, normalised for matching, plain text); the server code page (MT4); a mark when a name could not be read in full	binding a licence to the server, counting the trial per server
Server build	trading server build and version; for MT5 also the server identifier and type	compatibility, support
Licence state	whether this plugin is licensed or running as a trial, the number of that licence or trial and its last valid day, and a one-time code that shows the plugin really has that file. The licence file itself is not sent, and we do not keep that code	renewing a licence, lifting a revocation, warning about an expiry
Technical fields	a random number, the time on the server clock when the request is sent, the protocol version and a signature made with the installation key	protection against forgery and replay

Besides the message, the service sees what any server sees:

the IP address of the connection and the time of receipt (stored with every request);
the User-Agent header, CPlugin-Hub/1 <product code>/<version>;
when the plugin downloads an update: the download is recorded with the IP address, the User-Agent and the installation key (header X-Hub-Installation).

What is never sent

Accounts and their logins, groups, balances, credit, equity or margin. Trades, orders and positions. Quotes and price history. Data about your clients: names, addresses, documents, e-mail addresses, phone numbers. The trading server database and its files. Credentials of managers and administrators, passwords. Plugin settings (the one identifier described above is the only value taken from the configuration). Server journals. Files from your disk other than the plugin's own files. The protocol has no fields for any of this.

What the service sends back

Only a signed answer to that one request: the service time, information about a new version, a licence or trial file, a code for linking the server to your organization in Toolbox, and codes of messages for the server journal. The answer carries no commands and no program code that runs by itself. A new version is saved next to the plugin as <plugin>.dll.new, checked against a signed checksum, and is never loaded until you replace the file yourself.

Why we collect it

Licence. To deliver and renew your licence automatically and to bind it to your server.
Trial. A trial needs no registration. The trial period is counted on our side for each product and server (by owner and server name), so reinstalling does not restart it. See the trial terms on the SlippageControl page.
Updates. To tell you about new versions and deliver them as a verified file.
Support and safety. To see which versions run where, to detect a broken update, and to notice a copied installation key.

Where it is stored and for how long

The data is stored in the database of the CPlugin update service, which CPlugin operates, and in the logs of that service. It is kept without a time limit. The purpose is to protect the intellectual property of CPlugin: for example, to notice that a licence which is no longer paid for has started working again years later, or that a licence "transferred" to another company is in fact running on the same server and the same internet address as before. For the same reason the IP addresses of requests are kept too. An IP address is only an identifier of a server; we do not collect data about your clients or traders.

Until you link a server to your organization, the data is an anonymous observation of an installation: we know a server name from the licence of the platform, not who runs it. A server is linked to an organization when someone enters the code from the server journal in CPlugin Toolbox, or when CPlugin staff do it at your request or after checking. Linking is also written to the journal. A trial does not link a server to anyone; extending a trial in Toolbox requires signing in, so that extension is tied to your Toolbox account. Entering a code records the organization, the user and the IP address of the attempt.

Questions

Write to info@cplugin.com. The rest of what we collect on this website is described in the Privacy Policy.

Last updated: October 13, 2026.