Privacy

Meetings is operated by Particulars and Universals, Inc. (“Particulars,” “we,” “us”).

Information Meetings processes

Room information

Meetings processes the room code and the material needed to conduct the room, including instructions, target or grouping text, timer settings, ending behavior, room state, and timestamps.

Room information is visible to devices that have joined that room and to a paired read-only display. Do not enter confidential, sensitive, regulated, or personally identifying information into an instruction.

On supported iPhones, the facilitator can also show the active room code, target, instruction, and timer in a Live Activity on the Lock Screen or Dynamic Island. That presentation is generated on the facilitator’s device from the same temporary room state. Instructions are marked privacy-sensitive for system privacy treatments, but the facilitator remains responsible for their device and notification-preview settings.

Anonymous technical information

Meetings creates random, app-scoped identifiers so a facilitator, participant, or display can connect to the correct room. The service also processes room membership role, join and last-seen times, and whether a participant has armed sound. The facilitator sees aggregate connection and sound counts, not a list of participant identities.

The participant site stores a random device identifier and an anonymous service session in browser storage, including when that site is shown inside the iPhone app. The iPhone app may also keep its anonymous service session and limited room-recovery material in protected local storage. These identifiers operate Meetings; they are not Particulars accounts or participant profiles.

Infrastructure information

Our hosting and database providers may process IP address, browser or device information, request times, and similar security or operational logs when a device connects to Meetings.

Meetings does not include advertising SDKs, cross-app tracking, session replay, or product analytics. We do not sell room information or use it for advertising.

How information is used

We use this information only to:

• create, join, synchronize, and recover a temporary room;
• show the current instruction, target, clock, and room status;
• keep an active facilitator cue visible in a device Live Activity;
• play an ending cue after a participant explicitly arms sound;
• protect facilitator and display controls;
• maintain reliability, prevent abuse, and troubleshoot failures; and
• meet legal obligations.

Who can see room information

A room code allows a participant to join the room-public experience. A separate, high-entropy capability protects facilitator control, and another protects the read-only display. Capabilities are stored as cryptographic hashes on the server.

Anyone given a live room code may be able to see that room’s public instruction and clock. Share room codes only with the intended group. Never send a display setup string or facilitator recovery secret to support.

Storage and retention

The current app creates rooms with a two-hour expiry. Meetings enforces a hard maximum of 24 hours. Expired room content and membership records are scheduled for deletion automatically, and temporary anonymous service users are removed after they are no longer associated with a room.

Infrastructure providers may retain limited security, request, and backup logs for their configured operational retention periods. Those logs are not used to reconstruct meeting content or participant profiles.

The browser, including the participant view embedded in the iPhone app, may retain its random device identifier and anonymous service session until its site data is cleared. The iPhone may retain local session or recovery data until the app removes or replaces it or the session expires. Material held in Keychain can outlive an app deletion and reinstall.

Service providers

Meetings uses:

• Supabase for anonymous authentication, database storage, server functions, and realtime delivery; and
• Vercel to host the participant and display websites.

These providers process information on our behalf to deliver and secure Meetings. Their own privacy and security terms govern their infrastructure.

Security

Meetings uses encrypted network connections, least-privileged facilitator, participant, and display roles, server-side authorization, hashed capabilities, and automatic room expiry. No internet service can guarantee absolute security.

Your choices

Participants can leave a room by closing its page or tapping Leave in the iPhone app. Browser participants can remove locally stored identifiers by clearing site data for meetings.particulars.team. Removing the iPhone app clears its app container, including the embedded participant site’s storage, although Keychain material may persist as described above.

Room data expires automatically, so Meetings generally cannot identify or retrieve a particular participant’s anonymous data.

Questions about privacy can be sent to clay@particulars.team.

Changes

We may update this notice as Meetings changes. The effective date above will be updated when a revised notice is published.

Contact