1. Parties and scope
This agreement is between STUFFIG, s.r.o., IČO 53811844, Ivana Houdeka 1876, 034 01 Ružomberok, Slovakia (Fluri), and the customer identified by the Fluri account and registered website. It applies where Fluri processes personal data on that customer's behalf when delivering hosted themes, checking installation and providing enabled installation analytics. It forms part of the hosted service terms accepted in the account. It does not replace historical software licences or apply merely because someone downloads an older standalone npm package.
The customer is controller of information processed for its website visitors and determines whether, where and on what lawful basis to install the theme and enable measurement. Fluri acts as processor for the delivery and measurements described here. Fluri is separately controller for its account administration, security, legal compliance and its own service-level business analysis described in the privacy notice. Actual roles depend on purposes and conduct, not labels alone. Where a customer acts as a processor for a client, it must have authority for this subprocessing and pass along the relevant terms.
2. Subject matter, purpose and duration
Processing covers browser delivery of a configured visual effect, registered-domain checks, connection acknowledgements, error diagnostics, and optional aggregate theme-page-view reporting. It lasts for the active installation and the retention periods below. A simulated checkout creates only a 14-day evaluation; it is not payment, a paid licence, an invoice or a promise of indefinite service. Removing the website or account disables new configuration delivery and deletes its associated measurements from our application tables. An already loaded browser effect may continue until its next configuration check or page close.
3. Visitors and data categories
Data subjects are visitors to the customer's installed website and the customer's authorised account users. Delivery necessarily exposes ordinary network information to the hosting edge, including IP address, request time, origin or referrer, user agent and requested asset. Our application stores a website identifier, configuration version, first and latest connection times, a bounded generic startup error, and short-lived random event IDs used to avoid counting the same submitted event twice.
If analytics is enabled, the browser submits a theme view with a broad referrer category (Direct, Search, Social or Other) and a randomly generated per-event identifier. The edge derives a coarse country and device class. The application stores aggregates by date, registered website, country, device class and referrer category. It does not store raw visitor IPs, full visitor-page URLs, full external referrer URLs, persistent visitor IDs or visitor-cookie identifiers in these tables. Network providers still process request information needed for delivery and security. No form contents, keystrokes, payment data or sensitive visitor information should be sent to Fluri.
4. Customer instructions and responsibilities
The account settings and this agreement are the customer's documented processing instructions. Analytics is preselected for newly created website setups, can be unchecked before saving and can be disabled independently of theme delivery. Existing saved opt-outs remain unchanged. A preselected customer setting is not consent from the customer’s visitors. Before collecting optional analytics, the customer must determine its lawful basis, provide appropriate visitor notices and implement any legally required consent mechanism. If prior consent is required, do not enable measurement until that requirement is satisfied; Fluri does not supply a universal consent manager. Start the embed with `data-analytics="false"` and use `window.Fluri.setAnalytics(true/false)` from your own consent manager where prior consent is required. The control operates in memory for the current page; the customer’s manager must maintain any required preference and consent record. The loader honours Do Not Track and Global Privacy Control for optional view events. Necessary connection checks continue without counting a view.
The customer must be authorised to modify the registered website, protect account access, avoid sensitive data in configuration names, test compatibility and Content Security Policy, and promptly disable inappropriate use. The public embed identifier is not an account password. The customer may pause, change or delete an installation and export its account configuration. Connection acknowledgement confirms a runtime reported a successful start from an allowed origin; it is not proof of DNS ownership or an independent security certification.
5. Processor obligations
Fluri will process visitor data only on documented instructions, including instructions about international transfers, unless applicable law requires otherwise. If a legal requirement applies, Fluri will inform the customer before processing unless the law prohibits that notice. Fluri will notify the customer if it believes an instruction infringes applicable data-protection law and may pause the affected processing while the issue is resolved.
Fluri will restrict access to authorised persons subject to confidentiality obligations, apply appropriate technical and organisational measures, and make relevant information available to demonstrate compliance. Measures include TLS delivery, authenticated customer sessions, password hashing, ownership checks, bounded input fields, rate limits, origin checks, per-website public embed keys, limited collection and scheduled retention. No measure guarantees that browser-delivered JavaScript cannot be inspected or copied.
6. Subprocessors and transfers
The customer generally authorises Cloudflare, Inc. and its relevant service affiliates for Workers delivery, D1 storage and infrastructure security. The published Cloudflare subprocessor and processing documentation identifies its infrastructure chain. Fluri will impose applicable data-protection obligations on a subprocessor and remains responsible for its own obligations concerning that engagement. Google acts in connection with optional sign-in only when configured; it is not used for customer visitor analytics. Stripe is not connected during the current payment sandbox and does not receive installed-site visitor metrics.
Before engaging a materially different visitor-data subprocessor, Fluri will give affected customers advance notice through the account or their account contact, ordinarily at least 15 days, allowing reasonable objections on substantiated data-protection grounds. The parties will seek an alternative or permit termination of the affected processing if the objection cannot be resolved. Restricted transfers require an applicable adequacy mechanism or appropriate safeguards, including relevant standard contractual clauses where required. This agreement alone is not an international transfer safeguard.
7. Assistance, incidents and requests
Taking account of the nature of processing and information available, Fluri will reasonably assist the customer with data-subject requests, security duties, impact assessments and consultations under applicable law. Requests should be sent to fluritheme@gmail.com with the account and website reference, without visitor passwords or sensitive data. Fluri will notify the customer without undue delay after becoming aware of a personal-data breach affecting customer processing, provide information available for assessment, and supplement it as facts become known. Each party remains responsible for its own regulator and data-subject notification duties.
8. Retention, return and deletion
Installation-view aggregates are retained on a rolling 90-day basis; duplicate-event IDs for approximately one day; configuration activity for 30 days; and rate-limit records for no longer than their operational cleanup window. First/latest connection state persists with the website configuration. The customer can download its configuration and records through Account, disable measurement, or delete the website. Deletion removes corresponding application event and aggregate rows through database relationships. Backups and infrastructure logs follow the provider's operational cycle and lawful security obligations rather than becoming active analytics records. Fluri will delete or return processor-held data after the service ends, at the customer's choice, except where applicable law requires retention.
9. Review and audit
On reasonable request Fluri will provide information needed to demonstrate these obligations and allow proportionate audits, including inspections by the customer or an auditor it authorises. Arrangements should protect other customers, confidentiality and service security; reasonable notice and scope may be agreed without preventing legally required review or regulator access. No audit clause limits a supervisory authority's powers or mandatory customer rights.
10. Service-level reporting and measurement limits
The customer is informed that Fluri's restricted owner dashboard shows aggregate delivery performance, total theme views and top registered websites by reported view count to operate and improve the service. Customer domains can identify individuals; access to those records is restricted. We do not publicly publish customer rankings, sell visitor profiles or use installed themes for advertising. Measures report theme-enabled page loads, not unique people or a complete audience count. Blocking, excluded pages, bot filtering, opt-outs, repeated views and deliberate false submissions can affect the totals. Measurement is not independent billing evidence.
11. Contact and version
Data-protection contact: fluritheme@gmail.com. Effective 15 November 2026, version 2026-11-15-hosted-installations. Mandatory law prevails; nothing here waives consumer rights or promises immunity from legal claims.