Effective Date: February 17, 2026
1. Introduction
This Privacy Policy explains how LetsBridge AB ("LetsBridge", "we", "our") collects, uses, shares, and protects personal information when you use our website, app, and services globally. It applies to all users—including Visitors, Members, Networkers, Clients, and Service Parties— regardless of country of residence.
We are committed to global privacy compliance, including (where applicable) GDPR (EU and UK), CCPA/CPRA (California, U.S.), PIPEDA (Canada), PDPA (Singapore), the Privacy Act 1988 (Australia), and other relevant regional frameworks.
2. What Information We Collect
We collect different types of information to operate LetsBridge and provide our services.
Account Data: Names, email addresses, phone numbers, LinkedIn profiles, company and role details, login credentials, and session logs.
Usage Data: Pages visited, time spent, features used, IP addresses, device and browser types, and activity history within the app and website.
Contact Data from Networkers: Names, companies, job titles, and contact details uploaded by Networkers, plus relationship metadata (such as strength of connection and method of contact).
Meeting and Communication Data: UTM links, message delivery tracking, response actions, video engagement metrics, and metadata from introductions and follow‑ups.
Payment and Financial Data: Transaction history, payout records, and tax‑related information needed to process payments and comply with legal obligations.
3. How We Use Your Information
We use your information to operate and improve LetsBridge, including to:
- Provide, maintain, and improve our website, app, and related services
- Match users using Relevance and Relationship Scores to enable trusted introductions
- Facilitate, verify, and track introductions and meetings
- Process payments, rewards, and applicable taxes
- Provide customer support and prevent fraud or abuse
- Analyze aggregated trends and performance to improve our products
We may use anonymized and aggregated data for analytics, product development, and business insights. We will not share identifiable user or contact data with third parties for their own purposes without your consent.
4. Lawful Bases for Processing
Our legal bases for collecting and using personal data include:
- Consent (for example, when you upload contact data or connect third‑party services)
- Contractual necessity (for example, to verify and pay for introductions)
- Legitimate interest (for example, to prevent abuse and improve our algorithms)
- Legal obligation (for example, for tax and regulatory compliance)
5. Sharing and Transfers
We do not sell personal data. We may share information with:
- Technology, analytics, and payment processors acting on our behalf
- Legal or regulatory authorities when required by law
- Partners who help us maintain and improve our services
International Transfers: Your data may be stored or processed in the EU, U.S., Canada, Singapore, Australia, or other regions. Where we transfer data internationally, we rely on mechanisms such as Standard Contractual Clauses, adequacy decisions, or other recognized regional compliance frameworks.
6. Third-Party Authentication
LetsBridge uses OAuth authentication with Google, Microsoft, and LinkedIn to simplify account creation and login. We access only the information necessary to create and authenticate your account.
Google Sign-In
When you sign in with Google, we request the following permissions:
Scopes requested:
openid – identity verificationhttps://www.googleapis.com/auth/userinfo.email – email address accesshttps://www.googleapis.com/auth/userinfo.profile – basic profile access
What we access:
- Your name
- Profile picture
- Primary Google account email address
- Google account ID (for authentication purposes only)
How we use this data:
- Create and authenticate your LetsBridge account
- Display your name and profile picture in the application
- Send important account notifications and introduction updates
- Identify you when you return to the platform
How we store this data:
- Profile information is stored in our secure database with encryption at rest
- Email addresses are used for account identification and communication
- Account IDs are used for authentication purposes only
- We never access or store your Google password.
How we share this data:
- Your name and profile picture are visible to other users in introductions
- Your email is shared only with introduction participants when you schedule meetings
- We do not share your authentication data with third parties for marketing or ads
Your control:
- Update your profile information at any time from Settings → Profile
- Disconnect Google from Settings → Preferences
- Revoke LetsBridge's access from your Google Account permissions
- Deleting your LetsBridge account removes stored authentication data
Microsoft Sign-In
When you sign in with Microsoft, we request the following permissions:
Scopes requested:
openid – identity verificationprofile – basic profile accessemail – email address accessUser.Read – read user profile information
What we access:
- Your name
- Profile picture (high‑resolution for optimal display)
- Primary Microsoft account email address
- Microsoft account ID (for authentication purposes only)
How we use this data:
- Create and authenticate your LetsBridge account
- Display your name and profile picture in the application
- Send important notifications and introduction updates
- Identify you when you return to the platform
How we store this data:
- Profile information is stored securely with encryption at rest
- Email addresses are used for identification and communication
- Account IDs are used only for authentication
- We never access or store your Microsoft password.
How we share this data:
- Your name and profile picture are visible to others in introductions
- Your email is shared only with participants when you schedule meetings
- We do not share your authentication data with third parties for marketing or ads
Your control:
- Update your profile at any time from Settings → Profile
- Disconnect Microsoft from Settings → Preferences
- Revoke access from your Microsoft account permissions
- Deleting your LetsBridge account removes stored authentication data
LinkedIn Sign-In
When you sign in with LinkedIn, we request the following permissions:
Scopes requested:
openid – identity verificationprofile – professional profile accessemail – email address access
What we access:
- Your name
- Profile picture
- Email address
- Professional information (job title, company, headline)
- LinkedIn account ID (for authentication purposes only)
How we use this data:
- Create and authenticate your LetsBridge account
- Display your name and profile picture in the application
- Populate your professional profile with job title and company information
- Send important notifications and introduction updates
- Help other users understand your professional background during introductions
How we store this data:
- Profile information is stored securely with encryption at rest
- Professional information is used to create your LetsBridge profile
- Email addresses are used for identification and communication
- We never access or store your LinkedIn password.
How we share this data:
- Your name, profile picture, job title, and company are visible to other users when you participate in introductions
- Your professional information helps facilitate B2B sales introductions
- Your email is shared only with participants when you schedule meetings
- We do not share your authentication data with third parties for marketing or ads
Your control:
- Update your profile information from Settings → Profile
- Disconnect LinkedIn from Settings → Preferences
- Revoke access from your LinkedIn settings
- Deleting your LetsBridge account removes stored authentication data
Data Retention for Authentication
- OAuth access is maintained until you disconnect or delete your account
- Profile information is retained as part of your active account data
- Upon account deletion, OAuth‑linked data is removed within 30 days
- You can request immediate data deletion by contacting [email protected]
7. Third-Party Calendar Integrations
LetsBridge integrates with Google Calendar and Microsoft Outlook to help you schedule introduction meetings efficiently. Calendar integration is optional and requires your explicit consent.
Google Calendar Integration
When you connect your Google Calendar, we request the following permissions:
Scopes requested:
https://www.googleapis.com/auth/calendar.readonly – read calendar free/busy timeshttps://www.googleapis.com/auth/calendar.events – create and manage calendar events
What we access:
- Free/busy data across your calendar to display available slots during business hours (typically 8 AM – 6 PM in your time zone)
- All events only to detect busy vs. free time and scheduling conflicts
- We do not access event titles, descriptions, locations, or other detailed content unless strictly necessary for the service
How we use this data:
- Display available meeting time slots to you and introduction targets
- Prevent scheduling conflicts by checking all events on your calendar
- Create calendar events for scheduled introduction meetings
- Send invitations to participants and update meeting status
- Detect cancellations or reschedules to keep introduction records accurate (where supported by push notifications)
How we store this data:
- OAuth tokens are encrypted at rest using industry‑standard AES‑256 encryption
- Tokens are stored securely with role‑based access controls
- Free/busy data is queried on‑demand only and not stored permanently
- Meeting event details (time, attendees, meeting ID) are stored to track status
How we share this data:
- We do not share your Google Calendar data with third parties
- Invitations are sent only to participants explicitly involved in scheduled introductions
- Meeting times are visible only to the participants
- Calendar access tokens are never shared with any third party
Your control:
- Disconnect Google Calendar at any time from Settings → Calendar Integration
- Disconnecting revokes access and deletes stored OAuth tokens
- Revoke access directly from your Google Account permissions
- Delete individual events from your Google Calendar at any time
- Deleting your LetsBridge account removes calendar integration data within 30 days
Data retention:
- OAuth tokens are retained until you disconnect or delete your account
- Meeting event data is retained as part of introduction records
- You can request deletion of your calendar data via [email protected]
Limited Use Disclosure:
LetsBridge's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google Calendar data to serve ads, allow humans to read it except in limited cases (security, legal, or with your consent), or transfer it to third parties except as described in this policy.
Microsoft Outlook Calendar Integration
When you connect your Microsoft Outlook calendar, we request the following permissions:
Scopes requested:
User.Read – read basic profile informationCalendars.ReadWrite – read and write calendar dataoffline_access – maintain access when you are not actively using LetsBridge
What we access:
- Basic profile information to verify your identity
- Free/busy times across your calendar to show available slots
- All events only to determine busy vs. free time and detect conflicts; we do not read event content beyond what is necessary
- Permission to create and manage meeting events for scheduled introductions
How we use this data:
- Display available time slots to you and introduction targets
- Prevent conflicts by checking your existing calendar events
- Create and update calendar events for scheduled meetings
- Send invitations and update introduction status when meetings change
How we store this data:
- OAuth tokens are encrypted at rest using AES‑256
- Tokens are stored with strict role‑based access controls
- Free/busy information is queried on‑demand and not stored permanently
- Meeting details (time, attendees, meeting ID) are stored for introduction tracking
How we share this data:
- We do not share your Outlook calendar data with third parties
- Invitations are sent only to meeting participants
- Meeting times are visible only to you and the other participant
- Access tokens are never shared externally
Your control:
- Disconnect Outlook at any time from Settings → Calendar Integration
- Disconnecting revokes access and deletes stored tokens
- Revoke access from your Microsoft account permissions
- Delete individual Outlook events whenever you choose
- Deleting your LetsBridge account removes calendar integration data within 30 days
Data retention:
- OAuth tokens are retained until you disconnect or delete your account
- Meeting event data is retained as part of introduction records
- You can request deletion of your calendar data via [email protected]
8. Your Rights
Depending on your jurisdiction, you may have the right to:
- Access the personal data we hold about you
- Request correction or deletion of your data
- Object to or restrict certain processing activities
- Request data portability in a structured, commonly used format
- Withdraw consent at any time (without affecting prior lawful processing)
Specific rights for OAuth data include:
- Request a copy of OAuth‑linked data (profile information and calendar tokens)
- Request deletion of OAuth tokens and related profile data
- Export your profile information in a machine‑readable format
- Disconnect OAuth accounts at any time from in‑app settings or provider pages
To exercise your rights, email us at [email protected].
9. Data Retention
We retain personal data only for as long as necessary to:
- Provide and maintain our services
- Comply with legal, tax, and regulatory obligations
- Resolve disputes and enforce our agreements
Contact data uploaded by Networkers can be deleted at any time from within the platform. Some analytics data may be retained in anonymized or aggregated form.
OAuth and calendar data retention:
- Authentication data is retained until you disconnect or delete your account
- Calendar OAuth tokens are retained until you disconnect your calendar
- Meeting event data is retained as part of introduction records
- Anonymized usage analytics may be retained after account deletion
10. Cookies and Tracking
We use cookies and similar tracking technologies to:
- Authenticate users and maintain sessions
- Remember preferences and settings
- Measure usage, performance, and engagement
- Improve our user experience and product features
You can manage cookie preferences in your browser settings or (where available) in our in‑app privacy or cookie settings panel.
11. Security Measures
We implement industry‑standard security measures to protect your data, including:
- Encryption in transit and at rest
- Role‑based access controls
- Regular security audits and monitoring
For OAuth and calendar integrations specifically, we:
- Encrypt OAuth tokens using AES‑256 at rest
- Use TLS 1.2+ for all API communications
- Limit access to token data using strict role‑based controls
- Implement automatic token rotation and expiration handling
- Conduct regular security reviews of integration implementations
No system is 100% secure, but we strive to protect your information at the highest practical standard.
12. Children's Privacy
LetsBridge is not intended for children under 16, and we do not knowingly collect personal data from minors. If we learn that we have collected such data, we will take steps to delete it.
13. Changes to This Policy
We may update this Privacy Policy from time to time. Material updates will be communicated via email or in‑app notifications, and the latest version will always be available on our website.
Recent changes: On February 17, 2026, we added comprehensive OAuth authentication and calendar integration disclosures (Sections 6–7).
14. Contact
If you have questions, requests, or complaints regarding this Privacy Policy or our handling of your personal data, please contact us at:
Email: [email protected]
Data Controller: LetsBridge AB, Hälleskåran 45, 129 42, Hägersten, Sweden