Telarsys Chat Web

Descripción

Telarsys Chat Web adds a commercial conversation widget to WordPress and provides browser-based interfaces associated with Telarsys services: QR time tracking, GPS capture, and installation of the Time Clock PWA (Registro Horario).

On WordPress sites configured as solucioninformatica.es or www.solucioninformatica.es, an administrator can separately enable the desktop installer download. A visitor starts it through an exact link to https://www.solucioninformatica.es/descargar-instalador-siam/ or the same path on the domain without www, enters a temporary one-use code, and explicitly selects a local folder in a compatible Chromium browser. No shortcode or separate WordPress page is required. This feature downloads an installer archive and its XML configuration files; it never opens, extracts, or executes them and does not inspect or transmit the selected folder’s contents.

The plugin acts as an interface. The Chat requires a provisioned and active Telarsys installation; authorization and business operations are performed by the Telarsys service. Time-tracking functions also require the Telarsys Web API configured for the site or specified in compatible legacy links.

The plugin does not include trial periods, local expiration, advertising, telemetry, or analytics.

External services

This plugin depends on external Telarsys services operated by Solución Informática a Medida S.L. Communication occurs only when the corresponding features are activated, configured, or used.

Installation and Web Chat

The installation process and Web Chat communicate from WordPress with the central Telarsys service at https://erpsiam.azurewebsites.net.

• During activation, the activation code and the site’s HTTPS URL are sent.
• When checking status, the site URL and technical installation credentials stored only on the server are sent.
• When starting a conversation, the visitor’s name, company, telephone number, email address, originating URL, and message are sent.
• Technical installation and conversation identifiers, the public conversation token, idempotency identifiers, and a pseudonymous anti-abuse signal derived from the visitor’s IP address are also sent. The IP address is not sent in plain text in that header.
• Messages, status queries, and conversation closure transmit the conversation identifier and public token, the submitted text when applicable, and the required sequence or idempotency data.

These communications activate the installation, authorize the site, create and maintain conversations, and prevent duplicates or abuse. The private installation credential is never exposed to the browser.

Desktop installer download

This feature is disabled by default, restricted to WordPress installations whose configured home and site hosts are exactly solucioninformatica.es or www.solucioninformatica.es, and independent of the Web Chat, QR, GPS, and Time Clock features. On other domains its administration, public assets, and download endpoints remain inactive. When enabled on an allowed site, an administrator generates a six-digit temporary code, displayed as 123-456, that expires after 15 minutes and authorizes one operation. A new code invalidates the previous one.

• The visitor must validate the code before confirmation or folder selection. WordPress does not contact Azure, prepare the archive, enumerate configuration data, or download any file before the authorization is consumed for that operation.
• Cancelling the folder selector releases its short reservation when possible. Once the visitor has selected a folder, atomic server-side state prevents parallel reuse and a second download with the same authorization.
• WordPress requests the current installer publication from instaladorsiam, builds the physical InstaladorSiam.zip archive, and then lists and downloads the XML files from datosconexion outside the ZIP into the same selected folder.
• Every item in datosconexion must be a Windows-compatible XML file at the container root. An empty publication, a folder, a non-XML item, a case-insensitive filename collision, an invalid size, or a changed ETag rejects the operation without a global success state.
• The two restricted container SAS values belong to the same account and are encrypted and authenticated in WordPress with distinct contexts and autoload disabled. They are never sent to the browser or displayed again after saving.
• The source may be an ad hoc read/list SAS with an expiry, or a service SAS associated through si with an Azure stored access policy. In the latter case, permissions, start, and expiry may be inherited from Azure and absent from the URL; the administrator must configure that policy for Read and List only, without Write, Add, Create, or Delete.
• The access code is generated cryptographically with random_int() and is not stored in plain text. WordPress stores only an HMAC verifier and temporary reservation/operation state. For each active code, validation is limited atomically to five requests per pseudonymous network origin and one hundred requests globally during its 15-minute lifetime; the raw IP address is not stored and every rejected request receives the same generic response. XML download tokens are short-lived, file-scoped, source-bound, and single-use.
• The visitor’s local folder path, folder handle, existing file list, and local file contents are not sent to WordPress, Telarsys, Microsoft Azure, or any other service.
• The plugin does not open, extract, or execute any downloaded file. Progress reaches 100 percent and success is reported only after the archive and all XML files have been closed successfully.

The purpose of the communication is solely to copy the current desktop installer publication and its authorized configuration files into the folder explicitly chosen by the visitor. The storage service is Microsoft Azure Blob Storage: https://azure.microsoft.com/ . Microsoft privacy information: https://privacy.microsoft.com/privacystatement .

QR time tracking and Time Clock

These features are disabled by default on new installations and communicate only after the administrator explicitly enables them. They use the Telarsys Web API configured by the administrator. For compatibility, legacy links may include an api parameter, but that public override is accepted only for HTTPS destinations on public azurewebsites.net subdomains.

• The browser sends the q identifier to obtain the time-tracking context.
• When recording an entry or exit, the browser sends q, the record type, the selected service, the employee key when requested, the correction confirmation, and latitude and longitude if the visitor grants location permission.
• The installation page and Time Clock icon may also request the context associated with q from WordPress to obtain the name and logo. If the service returns a logo URL, WordPress requests that image from the specified host.
• Context requests initiated by WordPress only allow HTTPS on public azurewebsites.net subdomains. Remote images are requested only from public destinations using WordPress safe URL validation.

The purpose is to identify the authorized context, record the time-tracking event, and customize Time Clock access.

Legacy GPS capture

The GPS page is disabled by default on new installations and communicates only after the administrator explicitly enables it. It uses the Telarsys Web API configured by the administrator or, for compatible legacy links, an HTTPS public azurewebsites.net destination supplied through the api parameter.

• It sends the link’s t token.
• If the visitor grants location permission, it sends latitude and longitude.
• If the visitor continues without GPS, it sends the token and an indication that no location is available.

The purpose is to associate the location decision with the corresponding time-tracking flow.

Service provider information: https://www.solucioninformatica.es/

Service privacy policy: https://www.solucioninformatica.es/politica-privacidad/

No specific Telarsys terms-of-service page has been identified in this project. This readme does not invent or attribute a policy that has not been provided.

Privacy

WordPress stores the options configured by the administrator, which may include the display name, compatibility telephone numbers, Web API URLs, and interface preferences. It also stores the public installation identifier and its encrypted and authenticated secret, both with autoload disabled. The plugin does not create custom tables, transients, or conversation records.

If the separate desktop installer download is configured, WordPress also stores its enablement flag and two encrypted, authenticated container SAS values with autoload disabled. A generated access code is represented only by an HMAC verifier, temporary one-use state, and bounded attempt counters keyed by a pseudonymous network-origin HMAC; neither the plain code nor the raw IP address is stored. The plain code is shown once to the administrator. The SAS values are not exposed to visitors. The local directory choice and authorization tokens remain only in browser memory for the current operation and are not persisted by the plugin.

Conversation content, contact details, and coordinates pass through WordPress or the browser to perform the corresponding request, but this plugin does not persist them in WordPress options, posts, metadata, files, or tables.

The widget uses browser sessionStorage to retain the creation phase or active conversation. It may store idempotency identifiers, the public conversation identifier and token, sequence, status, minimal waiting-notice data, and the text of a pending message when applicable. It does not store the name, company, telephone number, or email address from the initial form there.

The plugin does not add cookies, localStorage, telemetry, analytics, tracking pixels, or iframes. Executable JavaScript and CSS are distributed locally with the plugin.

The retention and processing policy of the remote service cannot be determined from the plugin code. Consult the provider policy linked in the External services section.