Privacy Policy

We collect only the information needed to operate Void, understand how it is used, communicate with interested users, and improve the product.

When you use a room

Depending on the features you use, we may process:

• Your display name or alias
• Room names, timers, and settings
• Messages, direct messages, reactions, and other room activity
• Optional contact information you choose to share
• Room codes, invitation information, and session identifiers
• Participant presence and connection status
• Push-notification subscriptions, when enabled

You do not need to create an account or provide an email address to create or join a room.

Void does not currently support file or image uploads.

Information stored in your browser

Void uses browser storage to keep rooms working. Your browser may store:

• Room and participant identifiers
• Session and invitation information
• A temporary or read-only copy of room messages
• Direct-message history
• Contact information shared by participants
• Room encryption keys
• Push-notification preferences
• Analytics identifiers and consent choices

Some locally stored information may remain on your device after a room expires until Void clears it, you leave the room, you clear your browser storage, or your browser removes it.

Waitlist information

When you join the Void waitlist, we collect your email address.

We use it to send:

• A welcome email
• An invitation to the optional Void Telegram group
• A launch announcement

We do not intend to use the waitlist for unrelated promotional email.

You can unsubscribe through an email’s unsubscribe link or by contacting kat@avoid.chat.

Feedback

You may voluntarily provide feedback through:

• Optional PostHog in-app surveys, when shown
• Optional emoji feedback inside Void
• A Google Form linked from the product
• An email sent directly to us

You may occasionally be shown an optional PostHog survey, and you may also voluntarily submit an emoji reaction inside Void. Emoji feedback records only a normalized sentiment category, such as positive, neutral, or negative. Other feedback forms may include ratings, written comments, and any information you choose to include. Please do not submit highly sensitive personal information through a feedback form.

Analytics and technical information

When you use Void, we and our service providers may process limited technical information such as:

• Browser and operating-system information
• Device and screen information
• Pages or product areas visited
• Selected actions taken inside the product
• Analytics identifiers and consent choices
• Approximate timestamps and referral information
• IP-address information processed by hosting or infrastructure providers

Void uses consent-based PostHog analytics to understand usage patterns. This may include visits to pages and routes, interactions with landing-page features, successful email signups, opening the product, creating and joining rooms, intentional departures, being removed from rooms, rooms ending because a timer expired or a host ended them, and optional emoji feedback.

We do not use analytics or feedback tools to collect message contents, room names, room codes, display names, contact information shared within a room, optional written feedback, or other user-generated chat content.

Void uses selected PostHog events rather than general autocapture or session replay.

Void does not currently use named user accounts or PostHog’s identify() function to associate analytics with a registered profile.

We use information to:

• Create and operate temporary rooms
• Deliver messages and room activity
• Manage participant access and host controls
• Provide optional direct messaging and push notifications
• Expire and delete rooms
• Prevent spam, abuse, and security incidents
• Diagnose errors and maintain the service
• Understand which product features are useful
• Review feedback and improve Void
• Send the limited waitlist communications described above
• Comply with applicable law and valid legal requests

We do not sell personal information.

We do not use chat messages for advertising.

Where European data-protection law applies, we rely on one or more of the following legal bases.

Providing the service

We process room, participant, session, and message information because it is necessary to provide the service you request when you create, join, or participate in a room.

Consent

We rely on consent when you:

• Accept optional analytics
• Join the waitlist
• Enable push notifications
• Submit feedback
• Voluntarily share contact information

You may withdraw your consent at any time.

Legitimate interests

We may process limited operational and technical information where reasonably necessary to:

• Protect Void and its users
• Prevent spam and misuse
• Diagnose technical problems
• Maintain and improve the product
• Understand broad product usage

When relying on legitimate interests, we consider whether those interests are outweighed by users’ privacy rights.

Legal obligations

We may process or preserve information when required to comply with applicable law, valid legal process, or obligations relating to security and user safety.

We aim to keep personal information only for as long as reasonably necessary for the purpose for which it was collected.

Our general retention approach is:

Rooms, messages, and participant records

Until room expiration and the short read-only grace period.

Optional room contact information

During the room’s active lifetime, subject to room cleanup.

Direct messages

Relayed through the server and not stored in the main application database; copies may remain in participants’ browsers.

Waitlist email addresses

Until launch communications are complete, you unsubscribe, or you request deletion.

Feedback

For as long as reasonably useful for reviewing and improving the product.

Product analytics

For as long as reasonably necessary to understand and improve Void, subject to PostHog’s applicable retention practices.

Push subscriptions

Until unsubscribed, invalidated, removed, or no longer required.

Infrastructure and security logs

According to operational needs and the practices of the relevant provider.

Browser-stored information

Until cleared by Void, the user, or the browser.

We may retain limited information longer where reasonably necessary to investigate misuse, resolve a dispute, protect the service, or comply with law.

Void uses third-party providers to operate the service.

Railway

Railway hosts Void’s application and PostgreSQL database. Railway may process application traffic, database information, IP addresses, and technical logs as part of providing its hosting infrastructure.

PostHog

PostHog provides product analytics, optional in-app surveys, and support for Void’s optional emoji feedback.

Void uses PostHog’s European Union cloud environment. PostHog may process selected analytics activity, analytics identifiers, technical properties, optional survey responses, and normalized emoji feedback categories.

Loops

Loops stores waitlist email addresses and sends Void’s welcome, Telegram invitation, and launch communications.

Google Forms

Google processes information you voluntarily enter into Void’s extended feedback form according to Google’s applicable privacy practices.

Push-notification providers

When you enable push notifications, your browser or device’s push service processes a subscription endpoint and related technical credentials so notifications can be delivered.

These providers process information for the services they provide to Void. We do not sell personal information to them.

Void uses cookies and similar browser technologies to:

• Maintain room access and sessions
• Remember participant and interface information
• Store limited local room history
• Support direct-message history
• Remember analytics choices
• Provide consent-based product analytics

Optional analytics should operate only after the applicable consent choice has been made.

You can reject optional analytics through Void’s consent controls.

You can also clear cookies and browser storage through your browser. Doing so may remove local room history, sign you out of rooms, or prevent some features from working correctly.

Void and its providers may process information in more than one country.

Where European personal data is transferred outside the European Economic Area, the relevant provider may use approved safeguards such as an adequacy decision or the European Commission’s Standard Contractual Clauses.

Where reasonably available, Void selects European processing regions, including PostHog’s EU cloud environment.

Depending on where you live, you may have the right to:

• Ask whether we hold information about you
• Request access to that information
• Correct inaccurate information
• Request deletion
• Restrict or object to certain processing
• Withdraw consent
• Object to direct marketing
• Request a portable copy of certain information
• Complain to a relevant data-protection authority

These rights are subject to applicable legal limitations.

Because Void does not require accounts, we may sometimes have limited ability to determine which information belongs to a particular person. We may ask for enough information to locate and verify a request, but we will not ask for more than reasonably necessary.

To make a request, email kat@avoid.chat.

Void is not intended for children under 13.

We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information through Void, contact kat@avoid.chat so we can review and, where appropriate, delete it.

We use reasonable technical and organizational measures intended to protect information against unauthorized access, loss, alteration, and misuse.

However, no online service is completely secure, and we cannot guarantee that information will never be accessed, disclosed, altered, or lost.

You are responsible for deciding what information is appropriate to share with other room participants.

We may update this Privacy Policy as Void changes.

When we update it, we will:

• Revise the Last updated date
• Update the What’s changed notice at the top
• Summarize material changes in plain language

For significant changes, we may also provide a notice on the website, inside the product, or by email where appropriate.