A little winter. A small data footprint.
You can read the website and try the snow without registering. The Fluri engine runs in your browser and does not automatically report installations, pointer activity, or visitor impressions to us. We do not sell personal information or build advertising profiles.
Website owners can separately choose to register a domain, submit daily aggregate counts from their own systems, and request a public community listing. Registration and reporting are optional; they are not requirements of the software license. This notice covers those services, hosting, correspondence, and browser storage.
Who is responsible
The operator of fluri.xyz and the controller for the processing described here is Frantisek Gejdos, Slovakia. For privacy questions or to exercise your rights, contact fluritheme@gmail.com.
This notice covers the Fluri website, playground, participation portal, and private dashboard. Independently operated websites using Fluri are responsible for their own privacy practices and source analytics. Installing the library does not register a website or send its visitors’ activity to Fluri.
Information and purpose
Page delivery and security
Our hosting provider receives information needed to serve and protect the website, such as your IP address, requested URL, request time, browser or device information supplied in HTTP headers, and technical response information. These requests are processed to deliver content, maintain reliability, and prevent abuse. Where the GDPR applies, our basis is our legitimate interest in providing a secure and functioning website.
Messages you send us
If you email us, we receive your email address, the content of your message, and any details you choose to include. We use them to respond and handle the matter you raise, based on our legitimate interest in answering correspondence. Where your request concerns steps towards a contract, the relevant processing may instead be necessary to take those steps at your request. We do not add you to a marketing list.
Browser interactions
Pointer positions, snow physics, live performance measurements, and preview controls are processed in browser memory. The application does not send this interaction history or your playground configuration to a Fluri server. Exporting a configuration creates a file locally; copying a command uses your device’s clipboard when you request it.
Optional website participation
Registration and management
If you register, we store your chosen display name, domain, contact email, site identifier, DNS verification challenge and verification date, settings, acceptance version and time, and records of your reporting and public-listing choices. Management and reporting credentials are stored as hashes. The service uses these records to verify domain control, provide the participation features you request, and protect access. Providing these registration fields is necessary to use the optional service, but not to browse Fluri or use the library.
Where the GDPR applies, processing necessary to provide participation you personally request is based on taking steps at your request and performing the participation agreement. Where you act for an organisation, our legitimate interest is administering its requested participation and communicating with its authorised representative. Our legitimate interest in preventing unauthorised access supports credential and security processing.
Aggregate reporting
A verified owner can enable reporting and send daily totals and the Fluri version from their own backend. We use these totals to understand participating use and maintain the private project dashboard. The reporting API accepts totals rather than visitor-level events. We do not store visitor IP addresses, browser identifiers, fingerprints, individual browsing histories, or page URLs in the participation database. Our hosting provider still processes technical information when a backend contacts our API.
Reports describe owner-reported effect impressions: an enabled Fluri effect was visible for at least one second while the tab was visible, as measured by the owner’s system. Counts are not unique people, independently verified audiences, or a count of every website using Fluri. Owners must assess the lawfulness of their source collection and sharing; enabling this service does not provide visitor consent or establish an exemption from consent requirements.
A public listing is a separate choice
Allowing aggregate reporting does not permit a public listing. A domain appears in the community only after DNS verification, a separate owner permission, and our approval. That permission covers the submitted display name, domain, and website link. It does not grant a separate right to reproduce logos or screenshots. Contact emails, credentials, and private impression totals are not part of the public listing.
Where a listing contains personal data, publication is based on the optional permission you give. You can withdraw it in the participation portal; withdrawal removes the listing from the current public service and does not affect the lawfulness of publication before withdrawal. It does not require you to stop using Fluri. Copies previously made by independent third parties are outside our control.
Preferences on your device
The website can remember your chosen snow on/off setting, and the playground can save a configuration when you choose Save locally. These preferences stay in your browser’s local storage and are not used to identify you. The participant portal keeps entered credentials in page memory rather than browser storage. Leaving or reloading the page clears that in-memory state.
The private project dashboard sets a necessary, secure session cookie only after its administrator signs in. See the cookies and local storage page for names, lifetimes, and controls.
Service providers and international processing
Cloudflare provides hosting, request protection, DNS resolution for owner-requested verification, and the D1 database used for participation records. That database is configured with EU jurisdiction; network and support processing can still involve other locations. Verifying a domain sends its public DNS challenge name to Cloudflare’s DNS resolver. Cloudflare’s network operates internationally; processing can involve countries outside Slovakia and the European Economic Area, including the United States. Its data processing addendum describes processor commitments and applicable transfer mechanisms, including contractual safeguards. Read Cloudflare’s privacy policy for its own processing practices. Contact us to request information about applicable safeguards.
Participation records and reports are available to the project operator and service providers supporting those features, subject to the separate public-listing choice above. We do not publish an owner’s contact email or private reports. Emails sent to our Gmail address are handled by the email services used by the sender and recipient. We do not add participants to a marketing list. Information may be disclosed when required by law or necessary to protect legal rights.
README download badges use aggregate package statistics from npm; they do not measure installations or visitors on websites using Fluri. Following an external link takes you to that provider’s service and privacy policy.
How long information is kept
Live simulation state lasts for the browser session. Saved motion and playground preferences remain on your device until replaced, cleared, or removed by your browser. An administrator session lasts at most eight hours, or until logout or server-side session revocation.
Daily aggregate reports are retained for up to 395 days. A daily cleanup removes older reports and unverified registrations older than 30 days. Verified registration, contact, credential-hash, and permission records remain while the owner keeps the registration active. Turning reporting off revokes its reporting credential and stops new reports; existing totals remain until their retention period ends or the registration is deleted. Owners can delete a registration and its reports through the portal, or contact us for help.
Deleting a registration removes it from the active database and current public community results. Cloudflare D1 recovery history can temporarily contain earlier database states. Its Time Travel documentation describes the applicable recovery window, currently up to seven days on Workers Free or 30 days on Workers Paid. Recovery copies are not the live service; a recovery must respect previously requested deletions.
We retain correspondence only as needed to handle the matter and maintain a necessary record, unless a legal obligation or legal claim requires more. Technical hosting and security records follow the provider’s operational, security, and legal retention criteria, described in Cloudflare’s privacy policy.
Your choices and rights
Where applicable, you may request access, correction, deletion, restriction, or portability of personal data, object to legitimate-interest processing, and withdraw consent for a public listing without affecting earlier lawful processing. These rights have conditions and exceptions. We do not make automated decisions with legal or similarly significant effects about you.
The participation portal lets a credential holder view and export their registration and reports, update contact details and choices, and delete the registration. You can also contact fluritheme@gmail.com; we may ask for information reasonably needed to verify your request. If a credential is lost, contact us rather than submitting somebody else’s domain.
You may complain to the Office for Personal Data Protection of the Slovak Republic, or another competent supervisory authority. The European Commission’s guide explains data protection rights. You can explore the website without participating, pause snow, and clear saved browser preferences.
Changes to this notice
We will update this notice if the website’s data practices change. The revision date on this page identifies the current version. Questions are welcome at fluritheme@gmail.com.