Privacy Policy

This Privacy Policy explains how LinkUp collects, uses, stores, and shares information when you use the LinkUp website, account system, browser meetings, desktop experiences, and related services.

1. Information LinkUp may collect

Account and sign-in information

When you create or sign in to an account, LinkUp may receive information provided by the authentication method you select. Depending on the provider, this can include:

• Your name or display name.
• Your email address.
• Your profile picture.
• A provider-specific account identifier used to keep you signed in securely.
• Authentication/session information managed by Firebase Authentication.

Google user data

If you choose Continue with Google, LinkUp uses Google sign-in through Firebase Authentication. LinkUp uses the basic Google profile information made available for authentication — such as name, email address, profile picture, and account identifier — only to authenticate you, display your signed-in identity, and associate account-only LinkUp actions with your account.

LinkUp does not request access to Gmail messages, Google Drive files, Google Contacts, Google Calendar events, or other Google service content.

Meeting and waiting-room information

When LinkUp meeting features are used, the service may process information such as:

• Meeting codes and meeting creation time.
• The display name entered by a guest.
• Join-request identifiers and whether a request is pending, approved, or denied.
• Short-lived host or approval tokens used to control meeting access.
• Participant identifiers needed to connect people to the same meeting.

Camera, microphone, and screen sharing

If you enable camera, microphone, or screen sharing, your browser or operating system asks for permission. LinkUp uses the resulting media only to provide the live meeting feature you selected. Real-time meeting media is transmitted using LiveKit infrastructure. LinkUp's current service does not intentionally store those media streams as meeting recordings.

Meeting chat

Meeting chat messages are transmitted to other connected participants through the live meeting data channel. LinkUp's current chat implementation is intended for the active meeting and is not designed as permanent chat history.

Technical and local data

LinkUp and the service providers that operate it may process technical information necessary to deliver and secure the service, such as IP address, browser/device type, network requests, error information, and security logs. LinkUp may also use browser storage or cookies for authentication sessions and local preferences.

2. How LinkUp uses information

LinkUp uses information only for purposes related to operating and improving the service, including:

• Authenticating accounts and keeping users signed in.
• Displaying the user's account identity.
• Creating and joining meetings.
• Operating host approval and waiting-room controls.
• Providing real-time video, audio, screen sharing, and meeting chat.
• Preventing abuse, troubleshooting problems, and protecting service security.
• Maintaining user-selected local preferences.

3. Google API Services User Data / Limited Use

LinkUp's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

• Google user data is used only to provide or improve user-facing LinkUp authentication and account functionality described in this policy.
• LinkUp does not sell Google user data.
• LinkUp does not use Google user data for personalized advertising or advertising profiles.
• LinkUp does not allow humans to read Google user data except when necessary for security, legal compliance, or user-requested support and only when permitted by applicable policy.

4. Service providers and sharing

LinkUp relies on service providers to operate specific parts of the service. Information may be processed by those providers only as necessary to provide those functions.

LinkUp does not sell personal information to advertisers or data brokers.

5. Storage and retention

• Account information: Firebase Authentication may retain authentication/account records while the account remains active, subject to Firebase/Google service operation and applicable deletion requests.
• Meeting and waiting-room records: LinkUp's current waiting-room backend is designed to automatically expire meeting and join-request records after a limited period, generally within several hours. The current implementation uses an approximately six-hour lifetime for meeting/waiting-room records.
• Approval tokens: Short-lived approval credentials are designed to expire quickly; the current implementation uses an approximately five-minute lifetime.
• Meeting media: LinkUp does not intentionally retain live camera, microphone, or screen-share content as recordings in the current service.
• Meeting chat: The current in-meeting chat feature is not designed as permanent stored message history.
• Provider/security logs: Infrastructure providers may retain operational or security logs according to their own policies and legal obligations.

6. Security

LinkUp uses reasonable technical measures intended to reduce unauthorized access, including authenticated account sessions, temporary meeting credentials, host-controlled admission, HTTPS connections, and provider security controls. No online service can guarantee absolute security.

7. Your choices and controls

• You can choose whether to sign in with Google or another available authentication method.
• You can deny camera, microphone, and screen-sharing permissions in your browser or operating system.
• You can mute your microphone, turn off your camera, stop screen sharing, or leave a meeting.
• You can sign out to end the active LinkUp account session on a device.
• You may request deletion of account-related LinkUp data as described on the Data Deletion page.

8. Data deletion requests

For instructions on requesting deletion of LinkUp account-related data, visit https://meetwithlinkup.com/data-deletion. Authentication providers may also offer their own account-access and consent controls.

9. Third-party services

LinkUp's service providers have their own privacy practices. Using an external authentication provider or infrastructure service may also be subject to that provider's privacy policy and terms.

10. Changes to this policy

LinkUp may update this Privacy Policy as features, providers, or data practices change. The current version and its update date will be published at this URL.

11. Questions

Questions about LinkUp's privacy practices or deletion requests can be sent using the developer/support contact shown in LinkUp's OAuth consent information or through LinkUp's public Product Hunt listing.