Summary
- No accounts, phone numbers, cookies, advertising identifiers, or analytics scripts.
- Message history, received files, identity keys, and settings are stored locally on your device.
- Room messages and files are end-to-end encrypted with a key carried in the invite link.
- The signaling server coordinates connections and can see limited connection metadata.
- Operational logs are used for abuse prevention, debugging, and download counting, not profiling.
Website requests
The public website does not set cookies and does not load third-party analytics, tracking pixels, remote fonts, or advertising scripts. Pages, images, CSS, JavaScript, and downloads are served from the Fliporium domain.
Like most public servers, Fliporium keeps short-lived access logs for abuse prevention and troubleshooting. These logs can include request time, IP address, user agent, HTTP method, path, status code, and similar request metadata. Access logs are rotated and kept for up to 14 days.
Desktop app data
The desktop app stores its working data locally next to the executable in a
fliporium-data folder unless you configure a different data
directory. That local data can include your identity key, peer list,
settings, message history, search index, and received files.
When the app joins a room, it connects to the Fliporium signaling server. The server receives the room id, your device routing id, the display name your device announces, and the WebRTC signaling data needed for peers to connect. This metadata is necessary to establish connections, but it is not the message or file content.
Messages and files
Live chat and file transfer use WebRTC data channels between devices. Room
content is encrypted with a room key carried in the invite link fragment
after #. Browsers do not send that fragment to the server, so
the server does not receive the room key from invite links.
Some network conditions require a TURN relay, and messages sent while a peer is offline can be held temporarily by the signaling server. In both cases, the server handles encrypted data. It cannot read message text, file contents, reactions, edits, deletes, or pins.
Offline message blobs expire after 14 days. They are also bounded by server limits so the backlog cannot grow without limit.
Download count
The public stats page shows a single aggregate number:
completed downloads of fliporium.exe. The counter is a
monotonic total, not a per-user table. Download request logs may include IP
address and user agent so incomplete transfers, crawlers, and obvious bots
can be filtered from the public count.
Contact form
If you use the contact form, the server stores the message in a private server-side inbox and may relay it by email to the maintainer. A contact submission includes the name, email address, optional subject, message body, timestamp, and IP address used for rate limiting and abuse handling.
Contact submissions are used to reply to you and operate the project. They are not added to a mailing list and are not sold, shared, or used for advertising.
Third parties
The website does not use Google Analytics, Facebook Pixel, Plausible, Cloudflare Insights, remote font providers, or ad networks. If SMTP relay is configured for the contact form, the submitted message may pass through the configured email provider in order to reach the maintainer inbox.
Children
Fliporium is not designed for children and is not marketed to children. People under 13 should not use it.
Changes
Material privacy changes should be reflected on this page and in the public project history. The goal is to keep this page specific enough that a user can understand the real tradeoffs without reading the source code.
Contact
Questions about privacy or security can be sent to chris@fliporium.com or through the contact page.