Privacy Policy
Personal Data Processing Notice
Version 1.0 — [[publication date]]
This notice explains how Evolutha processes personal data through EVO KIOSK: the cloud platform for remotely managing and monitoring Windows kiosks and digital signage stations, the website evokiosk.evolutha.app and the Player software installed on devices. It is provided under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR).
1. Data controller
The controller is Evolutha, full legal name, registered office at address, postcode and city, country, VAT/tax code __, certified email __.
Data protection contact: info@evolutha.com confirm whether a dedicated mailbox such as privacy@evolutha.com should be created. Privacy contact or DPO: name and contact, or state that none has been appointed.
2. Controller and processor: two distinct roles
For account data, browsing data and commercial enquiries, Evolutha acts as controller.
For data produced by the devices managed by the Customer (telemetry, logs, screenshots, uploaded files, router and SIM credentials entered by the Customer), Evolutha acts as processor under Article 28 GDPR: the Customer is the controller, decides purposes and retention, and must inform the people whose data may appear on screens or in images.
A Customer installing the Player in a workplace must comply with the information duties set out in Article 4 of Italian Law 300/1970 and with applicable rules on remote monitoring. Confirm whether an Article 28 data processing agreement exists with customers and whether it should be published as an annex.
3. Data we process and where it comes from
| Category | Data | Source |
|---|---|---|
| Account and access | Name, email, role, password (managed by the platform and not readable by Evolutha), optional second authentication factor; when signing in with Google, the email address and identifier provided by Google | User |
| Organisation | Company name, contact email, country, VAT number, phone, address, plan, billing cycle, number of devices | User |
| Payments | Transaction and subscription identifiers, amounts, payment status and summary supplied by the payment provider. Card details are entered on the provider's page and are not stored by Evolutha | Base44 Payments (Wix Payments) |
| Managed devices | Device identifier and token, model, operating system, Player version, displayed URL, configuration, online/offline status, hardware telemetry (CPU, RAM, disk, network, GPU, uptime, displays), logs, command history, uploaded files, screenshots | Customer devices |
| Connectivity (optional) | SIM operator, phone number, PIN and PUK, router address and credentials, SMS commands, when entered by the Customer for diagnostics | Customer |
| Support | Subject and text of the ticket, email and name, ticket access code, operator replies and any replies drafted with artificial intelligence tools | User |
| Sales enquiries | Name, email, company, phone, message and demo requests | User |
| AI assistant | Exchanged messages, language, originating page, contact details and notes voluntarily provided | User |
| Browsing and conversions | IP address, browser technical data, pages visited, advertising conversion events and related identifiers | Automatic |
4. Device monitoring and people on screen
Screenshots requested from the dashboard capture whatever is visible on the device screen at that moment and may contain third-party personal data: customers, visitors or employees standing in front of the kiosk. Screenshots are taken on request and do not form a continuous recording; no audio or video is captured.
Telemetry and logs describe the technical state of the machine and may indirectly contain IP addresses or visited web addresses.
Router and SIM credentials are processed only to enable the diagnostic features requested by the Customer. Confirm how they are encrypted at rest and which internal roles may access them.
5. Purposes and legal bases
The legal bases below are a proposed qualification of each processing activity: they must be validated by legal counsel before publication.
| Purpose | Proposed legal basis |
|---|---|
| Create and manage the account, provide the Service, register devices and licences, activate the free trial | Performance of a contract — Art. 6(1)(b) to be confirmed |
| Handle payments, renewals, invoicing and accounting or tax duties | Contract and legal obligation — Art. 6(1)(b)(c) |
| Provide support and answer tickets and assistance requests | Contract and pre-contractual steps — Art. 6(1)(b) |
| Answer information, demo and sales enquiries | Pre-contractual steps; consent for promotional communications — Art. 6(1)(a)(b) |
| Prevent abuse and fraudulent use (for example repeated free trials), ensure security and defend legal claims | Legitimate interest — Art. 6(1)(f) |
| Measure website usage and improve the Service | Legitimate interest or consent, according to the choices made in the banner — Art. 6(1)(a)(f) |
| Measure advertising effectiveness and record Google Ads conversions | Consent — Art. 6(1)(a); no tracking before consent |
| Respond to authority requests and comply with legal obligations | Legal obligation — Art. 6(1)(c) |
7. Recipients and providers
Data is processed by providers acting as processors under Article 28 GDPR, or as independent controllers where the law requires it (for example the payment provider). The list reflects the integrations actually present in the application.
| Provider | Role | Data involved | Location / transfer |
|---|---|---|---|
| Base44 — application platform: hosting, database, authentication, email delivery, file storage, AI model access | Processor | All data handled by the application | country and safeguard to be confirmed |
| Wix / Base44 Payments — payments and subscriptions | independent controller or processor: to be confirmed | Transaction identifiers, amounts, purchase email | country |
| Google — Google Ads tag, Google Fonts, Google sign-in | Third party; Ads only with consent | Browsing data, IP address, Google email or identifier for sign-in | country |
| Unsplash — images on the public page | Third party: receives the visitor IP address | Browsing data | country |
| TeamViewer — remote support at the Customer's request | to be confirmed | Technical access to the assisted device | country |
| Self-hosted RustDesk server — only if configured by the Customer | Customer infrastructure | Support session | to be confirmed |
| Provider of the language model used by the AI assistant through the platform | Processor | Text of conversations and requests | to be confirmed |
| Advisers, accountants, competent authorities | Independent controllers | Only the data needed for the individual request | Italy |
8. Transfers outside the European Economic Area
Some of the listed providers may process data outside the European Economic Area. In that case the transfer relies on an adequacy decision, on standard contractual clauses under Article 46 GDPR, or on an applicable derogation.
For each provider, state whether processing takes place outside the EEA and which safeguard is in place: this draft does not attribute locations or safeguards that have not been verified.
9. Retention periods
The periods below must be confirmed by the Controller and aligned with the platform's actual settings: this draft does not invent durations.
| Data | Retention |
|---|---|
| Account, organisation and configuration | For the duration of the contract and __ months after termination |
| Invoices and accounting records | __ years, as required by law |
| Device telemetry | __ days or months |
| Application logs and activity records | __ days |
| Device screenshots | __ days, or until deleted by the Customer |
| Support tickets | __ months after closure |
| Sales enquiries and leads | __ months |
| AI assistant conversations | __ months |
| Advertising conversion records | __ months |
| Backup copies | __ days |
| Cookie preference | Stored in the visitor's browser until deleted or the device changes |
10. Registration, payments, support and the AI assistant
- Registration: email and password, with address verification by one-time code; Google sign-in is also available. To prevent repeated free trials the platform records the email address and the company domain used to activate the 7-day trial.
- Payments: card details are entered on the payment provider's page. Evolutha receives the outcome, amounts and transaction identifiers, not card data. Confirm whether business tax data is processed directly or by the provider.
- Support: a ticket can be opened without an account, using a unique code sent by email. Some replies may be drafted with artificial intelligence tools and are reviewed by operators confirm whether review is systematic.
- AI assistant: conversations are stored and the text may be sent to the language model provider to generate the answer. Users are asked not to enter sensitive data, credentials or confidential information in the chat.
- Remote support: at the Customer's request, TeamViewer or a RustDesk server may be used to access the assisted device.
11. Security
Evolutha applies appropriate technical and organisational measures: encryption in transit (TLS), unique per-device tokens, multi-tenant isolation through row-level access rules, local device credentials protected with DPAPI/LSA, no password stored in plain text and logging of administrative actions.
Confirm whether multi-factor authentication is mandatory for administrators, whether backups are tested periodically, and whether breach-handling procedures (Art. 33-34 GDPR) should be declared.
12. Your rights
Data subjects may exercise the rights of access, rectification, erasure, restriction, portability and objection, and may withdraw consent at any time (Art. 15-22 GDPR). Withdrawal does not affect the lawfulness of processing carried out before it.
Requests should be sent to info@evolutha.com or to the dedicated mailbox. A reply is provided within one month. A complaint may be lodged with the Italian data protection authority (www.garanteprivacy.it) or with the competent supervisory authority.
Where the data concerns a device managed by a Customer, the request should be addressed to that Customer as controller; Evolutha provides the necessary assistance.
13. Changes and contacts
This notice may be updated. The current version is the one published on this page, with the update date shown above. Material changes are communicated by email or by a notice in the restricted area confirm the chosen method.
Questions about this notice: info@evolutha.com.
Appendix A — Google Ads API integration
The Google Ads API integration is available in the restricted area of the platform and can be used only by the Evolutha Owner account. It is not offered to Customers to connect their own advertising accounts: the platform manages a single Google Ads account, the Controller's own, and the imported data is shared across the whole platform.
Data processed: the Google Ads account identifier and name, the list of accounts accessible to the token, aggregated campaign, ad group and keyword metrics (impressions, clicks, cost, conversions and attributed revenue), search terms and, when the Controller enables it, the parameters of the conversion action created for the free trial. No data of visitors, platform users or managed devices is read.
Purposes: reviewing advertising performance in the restricted area (reporting, monitoring and alerts) and generating optimisation suggestions. Legal basis: legitimate interest of the Controller in analysing its own advertising campaigns (Art. 6(1)(f) GDPR).
Providers involved: Google (Google Ads API), subject to its own notice and transfer safeguards, and the provider of the artificial intelligence model used through the Base44 platform, which receives only aggregated campaign metrics in order to generate the suggestions. Tokens are never sent to the browser or to third parties. Name, location and safeguards of the AI provider: to be confirmed.
Retention: access and refresh tokens are encrypted (AES-GCM) and reside on the platform servers; imported metrics remain in the platform database. No automatic deletion is implemented: data and tokens are removed on the Controller's request.
Revocation: from the Google Account (Security → Third-party access) or from the Settings page of the restricted area. After revocation, access stops at the latest when the access token in use expires, within one hour. Use of data received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Transfers are governed by section 8.
Legal documents