Privacy Policy

Effective September 10, 2026

MeetDrop ("MeetDrop", "we", "us") operates the meetdrop.ai website, the MeetDrop application at app.meetdrop.ai, and our internal administration platform at platform.meetdrop.ai (together, the "Service"). This policy explains what information we collect, why, and the choices you have. Questions any time: privacy@meetdrop.ai.

Information we collect

• Account information. Your name, email address, and profile photo, provided when you create an account, accept an invitation, or sign in through a provider such as Google.
• Sign-in data. We are passwordless: we store the identifiers needed for emailed sign-in codes and passkeys, and records of sign-in events (time, device and browser type, IP address) to secure accounts.
• Customer content. Leads, contacts, events, and messages that you or your organization capture and store in MeetDrop. This content belongs to you; we process it only to provide the Service.
• Company information looked up about a lead. When you capture a lead with a work email address, MeetDrop reads that company’s own public website — the address is taken from the part of the email after the “@” — to fill in what the company does, roughly how big it is, where it is based and when it was founded. This is a request to their website, exactly as your own browser would make; we send no personal data to anyone to do it, and we do not use a third-party data broker. A personal address (gmail.com, outlook.com and the like) is never looked up. What comes back is stored on the lead, shown to you with the site it came from, and you can correct or clear it. It is used only to compare the lead against the ideal customer you described in your settings, so your list can be put in a sensible order.
• Usage and device information. Log data such as pages viewed, actions taken, IP address, and browser type, used for security, audit trails, and improving the Service.
• Website visitors. If you submit a form on meetdrop.ai — the newsletter, the contact form, a question form on an event or guide page, the partner application on our partners page, or the “Try it on yourself” demo — we receive the email address you enter, anything you typed or dictated, any photo you attach, and your IP address. We store it as a lead so we can reply, and we email it to ourselves. The demo also sends one message to the address you provide. A partner application also sends your company website, name and phone number (if you give them) to our administration platform, where it is kept as a partner record so we can build your page. When a builder signs up live on our partners page, we read their public website to check the fit and draft their page, and we email a one-time code to the work address they give us; the check, the code and what they choose are kept on their partner record. When a partner confirms their page from the link we emailed them, the details they tick (states, booth sizes, budget range, services) and their acceptance of the partner terms, with the version and the time, are kept on that same record.
• Writing the demo email. To write the follow-up the demo shows you, the note you typed or dictated, the fields read from a business card, and any sign-off name or links you choose to add are sent to Anthropic (the Claude API), which returns the subject and body. Anthropic processes it only to produce that reply and does not train models on it. Your email address, your IP address and any photo are not sent. If this is unconfigured or unavailable the demo falls back to a template written in your browser and tells you on screen that it did.
• Business cards in the demo. If you add a business card, the image is sent to Anthropic (the Claude API) to read the printed details from it. It is used for that single read and is not stored by us, and it is never attached to the email the demo sends — only the fields it produces, which you can see and correct on screen. If that service is unavailable the card is instead read on your device by an open-source text recogniser your browser downloads from the jsDelivr CDN, and the page tells you which of the two read it.
• Voice in the demo. The demo’s optional voice input records your note and sends the audio to OpenAI to transcribe it; it is used for that single transcription, is not stored by us, and is never attached to anything. In the rare browser that cannot record audio, the demo falls back to the browser’s own speech recognition instead — in Chrome that means the audio is processed by Google, not by us, and we only ever receive the resulting text. If neither is available, voice is disabled and typing works the same. Typing avoids all of this entirely.

Sign in with Google

When you choose "Continue with Google", we receive your basic Google profile: your name, email address, and profile picture. We use it only to create and sign you into your MeetDrop account. Signing in does not give MeetDrop any access to your email — that is a separate, optional step described in Sending from your Gmail below. MeetDrop's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Sending from your Gmail

On a paid plan you can optionally connect a Gmail or Google Workspace mailbox so your follow-up emails are sent from your own address instead of ours. Connecting it grants MeetDrop the https://www.googleapis.com/auth/gmail.send permission, which lets us send a message on your behalf — and nothing else. We do not read, import, store, modify, or delete anything in your mailbox, and we cannot see your inbox or your sent mail. We use this permission solely to send the specific follow-up emails you have written and approved inside MeetDrop. You can disconnect the mailbox at any time in Settings → Sending, which immediately revokes our access at Google. MeetDrop's use of information received from Google APIs, including the Gmail API, adheres to the Google API Services User Data Policy, including its Limited Use requirements; we never transfer or use this access for advertising, and no humans read your mail.

Connecting your CRM

On a paid plan you can optionally connect a CRM — Salesforce first, others to follow — so that the leads you capture are copied into it. Nothing is connected until you choose to connect it, and no lead data leaves MeetDrop for a CRM unless you have.

Connecting uses the CRM’s own sign-in screen. We never ask for or receive your CRM password. The CRM returns a token that lets MeetDrop act as you within the permissions you granted; we store that token encrypted, together with the identifier of each record we created, so that a lead updated in MeetDrop updates the same record rather than creating a second one.

The connection is one-way, outbound. We send the lead — their name, job title, company, email address, phone number, the note you captured, and the event it came from — and we create or update that person’s record. We do not import your CRM’s contacts, accounts or opportunities into MeetDrop, and we do not read records we did not create, beyond confirming the connection works and matching your colleagues to their CRM users so each lead is owned by the right person.

Once a lead reaches your CRM it is governed by your own agreement with that CRM provider, not by this policy. You are the one deciding to send it there, and the CRM provider’s terms and privacy notice apply to it from that point on. Deleting a lead in MeetDrop does not delete the copy in your CRM.

You can disconnect at any time in Settings, which stops all further syncing and discards the stored token. Records already created in your CRM stay where they are, under your control.

How we use information

• To provide, operate, and secure the Service, including authentication and account recovery.
• To send transactional email — sign-in codes, invitations, and service notices. We do not send marketing email without your consent.
• To keep audit logs of security-relevant actions, which protect you and your team.
• To provide support and improve the Service.
• To score the leads you capture against the ideal customer you describe, so you can see who to follow up first. Scoring never changes who receives an email from you, and never hides a lead from you.

We do not sell personal information. The leads and contacts you capture in the app are never used for advertising, never shared with an advertising network, and never leave the Service for that purpose. On the marketing website we do run advertising measurement for our own ads — see Cookies.

Service providers

The website relies on Vercel (hosting), Resend (sending the emails described above), Neon (storing leads), Anthropic (reading the demo’s business cards and writing its follow-up email), OpenAI (transcribing the demo’s voice notes), Google Fonts (typefaces) Google Analytics, and — on the marketing website only — Meta Platforms and LinkedIn, which set cookies so we can measure our own ads and show them to people who have already visited our event pages. Each receives only what it needs to do its job.

We use a small number of providers to run the Service, each processing data only on our instructions: Vercel (hosting), Neon (database), Resend (transactional email delivery), Anthropic (drafting follow-up emails from your notes, and reading business cards you add in the demo), OpenAI (transcribing demo voice notes), and Google (optional sign-in, and — if you connect a mailbox — the Gmail API to send your follow-ups from your own address). We also use Deepgram (transcribing voice notes) and Stripe (payments; card details go to Stripe and are never seen or stored by us). If you connect a CRM, that provider receives lead data at your instruction — see Connecting your CRM — and is not our processor but your own.

Analytics

We use Google Analytics 4 on meetdrop.ai to understand which pages and features people use. It sets cookies and shares your IP address with Google, which we ask it to anonymise. We do not use Google Analytics for advertising, and we do not run it on the app; the advertising pixels described under Advertising are separate from it. You can opt out with Google’s browser add-on or by blocking analytics cookies; the site works exactly the same either way.

So that we know how people find us, the site notes where a visit came from — the referring site, the page you landed on, and any campaign tags on the link — and passes that along when you follow a link into the app. If you then create an account, it is stored once on that account and never updated. It is used only to understand which channels bring people to MeetDrop, and it is not shared with anyone.

Advertising

We advertise MeetDrop on Meta (Facebook and Instagram) and on LinkedIn, and we measure whether those ads work. To do that, the marketing website runs the Meta pixel and the LinkedIn Insight Tag.

They tell those networks that a browser visited a page here, which lets us count the visits our ads produced and build audiences from pages visited — for example, everyone who read a particular event playbook. Audiences are built from the page, never from what you type: the contents of a form, a voice note, a business card or a lead are never sent to an advertising network, and neither is your email address.

You can opt out through each network’s own ad settings, or by blocking third-party cookies in your browser. The site works identically either way — nothing is withheld and nothing breaks.

Cookies

We use essential cookies to keep you signed in and to protect the Service.

On the marketing website (meetdrop.ai) we also run the Meta pixel and the LinkedIn Insight Tag. These set third-party cookies, tell those networks that a browser visited a page here, and let us measure whether our own ads worked and reach people who have already visited. They run on the website only — never inside the app, and never on a page where you enter or read lead data. Blocking advertising cookies changes nothing about how the site or the Service works for you.

Retention and deletion

We keep your information while your account is active or as needed to provide the Service, comply with legal obligations, and resolve disputes. You can request deletion of your account and associated personal data by emailing privacy@meetdrop.ai.

Deleting a lead, or deleting your account, also destroys anything MeetDrop looked up about that lead’s company. If a person unsubscribes from your follow-ups, we discard what we looked up about them at the same time as we stop the emails, and keep only what you captured yourself.

Security

Data is encrypted in transit. Access is passwordless by design — sign-in codes, passkeys, and provider sign-in — with role-based access controls and audit logging on our administration platform. No method of transmission or storage is 100% secure, but we work to protect your information appropriately.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information. Contact us at privacy@meetdrop.ai and we will respond.

Children

The Service is for business use and is not directed to children under 16. We do not knowingly collect personal information from children.

Changes to this policy

If we make material changes, we will post the updated policy here and revise the effective date above.

Contact

MeetDrop · hello@meetdrop.ai for anything, or privacy@meetdrop.ai for a privacy request, a deletion or a data-rights question — both reach us.