Your information. Your introductions.

Information we receive

• Account and sign-in: your email address, account identifier, sign-in provider, verification status, and basic provider profile details such as your name and profile image, if supplied. Google and LinkedIn sign-in use basic identity, profile, and email permissions. We do not request your provider password, contacts, messages, calendar, employment history, or full LinkedIn profile. Our authentication provider may store the basic provider metadata; Paalam uses your name to help fill an empty profile field. Your saved profile is not replaced when you sign in again.
• Your Paalam profile: the name, professional role, company, city/country, offers, needs, and optional social or website links you choose to enter. Your private account profile is separate from the information you submit for an event.
• Event information: an organizer may import your name, email, organization, role, offers, and needs from a registration list. We also store event membership, your corrections, participation choices, consent, introduction decisions, and relevant timestamps. Importing a row does not create an account, send an invitation, or authorize matching.
• Operational information: authentication and security logs, requests to the service, technical identifiers such as IP address and browser information, and email delivery records needed to operate the service and investigate failures or abuse.

Please enter professional information only. Do not put passwords, payment details, health information, or other sensitive information in profile or matching fields.

How we use it

We use this information to sign you in, save your profile, verify event admission, send requested login links and organizer-controlled invitations, suggest potential introductions, record your choices, and keep the service secure. Candidate suggestions compare the offers and needs in eligible event profiles using words and related business concepts. An organizer reviews and releases introductions; the suggestions are not a guarantee of compatibility.

We do not sell your personal information, use it for targeted advertising, or use your profile to train a general-purpose AI model. The controlled launch does not send profile text to an external generative AI model.

Who can see what

• You: your private account profile and your event workspace. Other participants cannot browse your private account profile or the full event roster through Paalam.
• Your event organizer: the roster and event information they manage, your event profile and participation status, and introduction review information. Organizer review notes are not displayed to participants.
• A person introduced to you: after the organizer releases an introduction, both people can see the relevant professional context and the introduction message. Your email and optional event LinkedIn URL are shown to the other person only after both of you accept. Avoid putting contact details in free-text fields if you do not want them included in that earlier context.
• Authorized service operators and providers: information necessary to maintain, support, and secure Paalam. We use Supabase for authentication and database storage, Vercel for hosting, and Resend for transactional email. Google or LinkedIn also processes your sign-in when you choose it. These providers may process information in the United States and other countries under their own service and privacy terms.

We may also disclose information when required by applicable law or when reasonably necessary to address fraud, security incidents, or protect rights. An event organizer may hold a separate registration list outside Paalam; contact them about that copy and their own privacy practices.

Your choices and account access

Signing in or opening an invitation does not opt you into matching. You can correct your event profile, decline participation, withdraw your permission for introductions, and accept or decline an individual introduction. Withdrawal excludes you from further introductions and hides affected introductions in Paalam, but it cannot recall emails or information another person has already seen or copied. You can still sign in to manage your account.

Use the same verified email for Google, LinkedIn, and email access to keep one account. Our authentication service can link verified identities with the same email. Different emails are not automatically merged by Paalam. We do not merge accounts based on a name or a LinkedIn URL entered in a profile.

Contact ezhelan@gmail.com to request a copy, correction, or deletion of your information, stop invitation emails, or ask about an account-linking problem. We may verify account ownership before acting. Do not send passwords or personal sign-in links. Account deletion is currently handled through this contact, rather than a self-service button. Rights and exceptions may depend on where you live.

Retention and deletion

We keep account and event records while needed to provide the service, manage introductions, and handle support or security issues. Event records are not automatically erased when an event ends. You can request deletion, and organizers can contact us to arrange removal of event data they control. We remove information that is no longer needed, subject to legitimate security, dispute, and legal retention needs. Copies in backups may remain until the provider’s backup retention period ends; a deletion request does not retract information already shared with others.

Cookies and technical storage

We use cookies and similar browser storage to keep you signed in, protect the login flow, and return you to the event you selected. Personal email links contain a one-time credential: keep them private. The controlled-launch app does not load optional web analytics or advertising trackers. Hosting, authentication, and email providers still maintain operational and security records.

Updates

We will update this notice when our practices change and show the update date here. Material new uses or sharing will be explained before they take effect, with additional permission where required.