Vibecom
Privacy policy
How Vibecom handles voice, connection details, diagnostics, and support information.
At a glance
Vibecom connects your microphone to an intercom server operated by you or your team. It does not require an account and does not include advertising or analytics trackers. Your server operator can receive connection information and, if you enable them, diagnostic reports.
Who this policy covers
This policy describes the Vibecom Apple client and the server built into its macOS app. It also explains what happens when you contact Vibecom support or visit this website. Your organization controls any server it runs. Ask its operator how it handles information on that server.
Your voice and connection
Vibecom uses the microphone for live intercom audio when you transmit. It sends that audio through the server you connect to, for delivery to participants listening on the relevant channels. The standard intercom path does not save voice recordings.
Your server processes network addresses, your chosen display name, session identifiers, channel membership, and connection status to run the intercom. Other participants can see the participant information the app displays. Choose a display name you are comfortable sharing with your team.
The app is designed for trusted networks. The current Apple clients protect the control connection with TLS and encrypt voice packets with a room key shared by the server and joined participants. This does not make conversations private from the server operator or other authorized participants. Participants can also record what they hear using other tools.
Information on your device
The app keeps local preferences and diagnostic event logs to support connection, audio settings, and troubleshooting. Logs can include timestamps, app and operating-system details, audio-device information, network and session information, and participant or room names.
The app caps the size of its local log files and deletes the oldest ones as it writes new logs. Files you export, backups, and copies retained by another person are separate from that automatic cleanup.
Optional diagnostic reports
Send diagnostic snapshots to server is off by default. Turning it on in Settings enables local diagnostic capture, automatic captures when qualifying problems occur, and uploads to the server you are connected to. It does not require you to approve each report separately.
Reports describe app, device, audio-route, timing, network, and session behavior. The snapshot format excludes microphone samples, encoded voice payloads, room passwords, and upload credentials. Ordinary exported logs are a separate format. Review them before sharing because they can contain names and network details.
Snapshot uploads use a separate HTTP connection in this build. They do not have the same transport protection as the live voice connection. Enable them only on a trusted network with an operator you trust.
The server operator controls stored reports and their retention. Turning the setting off stops future capture and uploads. It does not delete reports a server has already received. Ask that operator to delete stored copies.
Information you send to support
If you send email, TestFlight feedback, screenshots, or logs to the developer, the developer receives the contact details and content you include. The developer uses that information to answer your request and investigate problems. Support email passes through Cloudflare Email Routing and is delivered to a Gmail inbox. Do not include passwords or unrelated personal information.
The developer keeps support correspondence and attachments as long as needed to handle the request and follow-up, or to meet legal obligations. You can request deletion through the privacy contact below. A server operator, Apple, and your email provider each control their own copies.
Apple and other services
Apple distributes TestFlight builds and may provide the developer with testing, crash, and feedback information under its own terms and privacy practices. Review Apple's privacy information and the information shown in TestFlight.
The app does not include advertising or analytics SDKs. Vibecom does not sell personal information or use it for cross-app advertising. A VPN, backup service, email provider, or organization you choose to use has its own data practices.
This website
These pages do not set cookies, run analytics, embed third-party fonts, or collect information through a web form. Opening an external link takes you to that service. Cloudflare hosts this website and can process IP addresses and request details to deliver pages and protect its service. See Cloudflare's privacy policy for its data practices.
Your choices and deletion
- Disconnect from a server to leave its intercom session.
- Turn off Send diagnostic snapshots to server in the app's Settings to stop future diagnostic capture and uploads.
- Change microphone and local-network permissions in your device's Settings. Disabling these permissions can prevent voice transmission or connection.
- Delete exported files and any copies you shared when you no longer need them. On iPhone or iPad, deleting the app removes its local app data; offloading the app retains that data. Backups and separately saved exports can remain.
- Ask your server operator to delete server-side logs or reports. Ask the developer to delete support information they hold about you.
There is no Vibecom account to close. Privacy rights can vary by location. Use the contact below for access, correction, or deletion requests concerning information held by the developer.
Changes to this policy
When Vibecom's data practices change, the developer will update this page with a new effective date. Review it when you install a new version or enable an optional feature.
Privacy contact
Email support@vibecom.dev with privacy questions or requests to access, correct, or delete information held by the developer.
For setup and diagnostic controls, see Vibecom support.