4MOMENTARY INITIALIZING
Click to skip
4MLobby

[ Privacy ]

Privacy Policy

Last updated 21 September 2026

A room holds what it needs to work, for exactly as long as it exists. No account, no cookie, no analytics, no profile, and nothing left behind when the clock runs out. What follows is the detail behind those claims.

What this covers

4momentary is a service for disposable chat rooms. This page describes what the service does with your information when you open the lobby, create or join a room, and use the optional AI companion.

It does not cover the AI provider you bring your own key for. What you send them is handled under their policy, not this one.

What we do not collect

No account, no email address, no phone number, no password of your own. No cookies are set anywhere in the service; you can confirm that in your browser's storage panel. No analytics, no tracking pixels, no advertising identifiers, and no server-side record of which rooms you have visited.

There is no profile of you to build and nothing to sell. The absence is the feature: a room that cannot remember you is a room that cannot betray you.

What your browser keeps

Your display name, accent colour and theme choice; the password of a private room you have entered; and the room token that proves which role you hold. Your AI companion's settings, including its API key, live in your tab's session storage.

This is your device's storage, not ours. It is what makes the next visit remember your name, and clearing site data removes all of it. The only parts that travel to the relay are the ones a room needs: your display name and colour alongside the messages you send, and the token that proves your role.

What the relay holds while a room is live

The room itself: its name, topic, clock, host, whether it is locked or private, and the position it occupies on the space map. For a private room, the password you set, held so the door can be checked. The messages, including images. And the roster: each participant's display name, colour, a server-issued id, and when they were last seen.

Each of those is there for one reason: to deliver messages, to show who is present, and to let the host enforce the room's rules. Nothing is collected for any other purpose.

Presence is kept current by a heartbeat sent roughly every twenty-five seconds. Close the tab and you stop appearing in the roster.

How long it lasts

Until T, the expiry chosen when the room was created. Rooms held in the relay's memory are dropped once they expire; where the relay is backed by Redis, the stored room carries a time-to-live equal to its remaining life, so it removes itself. The service makes no archive and no backup of room contents, and keeps no copy after expiry.

Treat the clock as a ceiling rather than a promise: a room can also end early, by the host's decision or because the server restarted.

The Moth and your AI key

The AI companion is off unless you deploy it, and it runs on a DeepSeek API key you supply. Your key is stored in your own browser and passes through our server only to make the request it authorises; we do not store it, and it is never written to a room.

The conversation you hold with the companion, and any image you show it, is relayed to DeepSeek to produce the answer, and is then handled under DeepSeek's terms. The companion can read the room's messages in order to answer, so a room is not the place for a secret you would not paste into a third-party model.

Ask the companion itself about this policy and it will read this page and quote it back.

Web search and page reads

When the companion's web tools are enabled, a search it runs is sent from our server to DuckDuckGo, and a page it reads is fetched by our server on the companion's behalf. Identical searches are cached in memory for up to ten minutes so the same question is not asked twice.

Those requests carry the query or the address, and nothing about you: no name, no room id, no identifier that could tie the search back to a participant.

Peer-to-peer connections

To move messages quickly, browsers in a room try to connect to each other directly. That connection is negotiated through a public signalling service and public STUN servers, and when it succeeds the other participants' browsers can see your IP address, the same as in any call.

If a direct connection cannot be made, the service falls back to carrying messages through the server instead.

Hosting and server logs

The service writes no access log of its own: there is no table anywhere of who opened which room. The platform it runs on keeps ordinary request logs (address, time, path) for security and operations, on that platform's own retention schedule.

Those logs are not joined to what was said in a room.

Children

4momentary is not directed at children, and rooms are not moderated. If you are below the age at which you can consent to a service like this where you live, please do not use it.

Changes and contact

If this policy changes, the date at the top changes with it. Questions, or a request about information you believe we hold: oz@franzdomingo.dev