Stilla beta programme terms and data processing agreement
Les textes juridiques sont disponibles en tchèque (version qui fait foi) et en anglais.
1. Stilla beta programme terms
These terms govern the free trial of the Stilla service in its test (beta) version. They apply between Eywo s.r.o., company ID 21053588, registered office Plzeňská 3350/18, Smíchov, 150 00 Prague 5, Czech Republic, registered in the Commercial Register kept by the Municipal Court in Prague, section C, file 396236 (“Eywo”) and the customer that signed up for the programme at stilla.eywo.digital (the “Customer”). The Customer accepts them by confirming the sign-up; the person signing up declares that they are authorised to act on behalf of the Customer.
1.1 Subject
- Eywo provides the Customer with its own Stilla instance (tenant) with a separate database, available at customer.stilla.eywo.digital.
- The scope of modules corresponds to the Business edition. Eywo may add, change or remove features during the beta.
- The programme is intended for at most 10 customers. Eywo may decline a sign-up or put it on a waiting list. Participation gives no entitlement to a future contract or price.
1.2 Duration and termination
- The beta lasts 6 months from the instance being made available, unless the parties agree otherwise.
- No later than 30 days before the end, Eywo offers a paid edition. The Customer decides by the end of the beta.
- If the Customer does not move to a paid edition, the instance switches to read-only mode. The Customer has 30 days to export data; Eywo then deletes the data including backups and confirms the deletion.
- Either party may end participation in writing with 14 days’ notice. Eywo may suspend access immediately in case of a breach of clause 1.4 or if other customers are at risk of harm.
- If the Customer’s administrator does not sign in to the instance within 7 days of its creation, Eywo may cancel the instance; such an instance contains no Customer data.
1.3 Price and support
- The beta is free of charge. Implementation work beyond setting up the instance and the first training is ordered separately.
- Support is provided through the support widget on stilla.eywo.digital or by email at support@eywo.cz on business days 9:00–17:00 CET. Eywo aims to respond within one business day but does not guarantee availability or response times (SLA).
- Eywo announces planned maintenance in the application and to administrators at least 72 hours in advance.
1.4 Acceptable use and permitted data
- The Customer may store IT operations data: configuration items, events, incidents, changes, contracts and contact details of its employees and suppliers.
- The Customer must not store special categories of personal data (Art. 9 GDPR), data relating to criminal offences, classified information, payment cards, or passwords and access keys in readable form.
- The Customer must not use the service for attacks, circumventing security, reverse engineering, or load beyond a reasonable level.
- The Customer is responsible for managing its users and for having a legal basis for the data it stores.
1.5 Customer data
- Data stored by the Customer belongs to the Customer. Eywo uses it only to provide the service.
- Eywo processes personal data as a processor under the Data Processing Agreement (chapter 2), which forms an integral part of these terms.
- Eywo employees have access to Customer data only with the consent of the Customer’s administrator, for at most 8 hours, recorded in the audit trail. The exception is emergency access during an incident, of which Eywo notifies the Customer within 24 hours.
- Eywo may use aggregated anonymous operating metrics (counts, response times, module usage) to improve the service. Data content is not included.
- The Customer may switch AI features off at any time in Settings. Data sent to the default AI model is not used to train models.
1.6 Feedback
Eywo may use the Customer’s ideas and comments free of charge to develop the product. Eywo will not publish the Customer’s name as a reference without written consent.
1.7 Liability
- The beta is provided “as is”. It may contain errors and is not intended as the only place for critical operational data.
- Eywo’s total liability for damage in connection with the beta is limited to CZK 100,000. The limitation does not apply to damage caused intentionally or by gross negligence, or to harm to health.
- Eywo is not liable for lost profit or indirect damage.
1.8 Confidentiality
The parties keep the other party’s confidential information confidential during the programme and for 3 years after it ends. This does not apply to public information or information a party demonstrably knew before.
1.9 Final provisions
- Eywo may change these terms with 30 days’ notice. If the Customer disagrees, it may end participation under clause 1.2.
- These terms are governed by Czech law. Disputes are decided by the general courts competent for Eywo’s registered office.
2. Data processing agreement
The Customer is the controller and Eywo the processor of personal data that the Customer stores in Stilla. This agreement fulfils Art. 28 GDPR and forms part of the beta programme terms.
2.1 Subject and scope of processing
| Item | Content |
|---|---|
| Purpose | operating the Stilla instance, support and backups |
| Duration | for the duration of the beta plus 30 days for export; then deletion including backups within 35 days |
| Data subjects | employees and users of the Customer, contact persons of its suppliers and clients |
| Data categories | name, work email and phone, role and team, activity records in the application (audit), content of tickets and notes |
| Excluded data | special categories (Art. 9 GDPR), criminal offence data (Art. 10 GDPR), payment data |
| Place of processing | EU; exceptions only for the sub-processors below with appropriate safeguards |
2.2 Eywo’s obligations
- Process data only on documented instructions of the Customer. Settings and actions of the Customer in the application are also instructions.
- Ensure confidentiality of all persons with access to the data.
- Implement the technical and organisational measures under clause 2.5.
- Assist the Customer with data subject requests (access, rectification, erasure, portability). The application provides export and erasure of persons for this.
- Notify the Customer of a personal data breach without undue delay, at the latest within 24 hours of discovery, with a description of the impact and measures taken.
- After the agreement ends, return (export) and delete the data under clause 2.1 and confirm the deletion in writing.
- Allow the Customer to audit: primarily by providing documentation and test results; an on-site audit by agreement once a year at the Customer’s cost.
2.3 Sub-processors
The Customer gives general authorisation for the sub-processors below. Eywo announces changes 30 days in advance; the Customer may object on serious grounds and end participation.
| Sub-processor | Service | Location of Customer data | Safeguard |
|---|---|---|---|
| Cloudflare, Inc. | hosting of the application, database and sign-in service, default AI model (Workers AI), backups | database and backups in the EU; global network | Cloudflare data processing addendum, standard contractual clauses, EU–US Data Privacy Framework |
| Resend (Plus Five Five, Inc.) | sending emails (sign-in codes, notifications) | USA | Resend data processing agreement, standard contractual clauses |
If the Customer uses its own email service or its own AI model, that provider is a sub-processor of the Customer, not of Eywo.
2.4 Eywo access to data
- Eywo employees have no permanent access to Customer data.
- Access is granted only on request after approval by the Customer’s administrator in the application, for at most 8 hours, for named Eywo support staff.
- Emergency access during an incident is allowed without prior consent; Eywo notifies the Customer within 24 hours.
- Every access is recorded in the audit trail that the Customer sees in its instance.
2.5 Technical and organisational measures
| Area | Measure |
|---|---|
| Data separation | a separate database for each Customer; an automated test at every deployment that an instance cannot read another Customer’s data |
| Encryption | transport only over TLS 1.2+; data in the database and backups encrypted at storage level |
| Sign-in | sign-in with a Google or Microsoft account, or a one-time email code; sessions in a secure cookie with limited validity; a user who is not signed in has no access to any data |
| Permissions | roles with least privilege; a new user has no access to data until the Customer’s administrator assigns a role |
| Audit | record of changes and access, kept for 5 years |
| Backups | daily backup of each instance in the EU, kept for 35 days; point-in-time recovery for the last 30 days; regular restore tests |
| Keys and secrets | only in the platform secret store, rotated regularly, never stored in code |
| Changes | every application change passes automated tests and a check on a copy of the data before deployment |
| Vulnerabilities | dependency updates and regular external penetration tests |
| Incidents | incident response procedure with notification to the Customer within 24 hours |