No LinkedIn scraping, no acting outside limits you set, and a straight answer on where we stand for government procurement.
Some competitor tools use a browser extension to pull data directly from LinkedIn as you browse, a practice that's drawn scrutiny and active detection efforts from LinkedIn itself. Lakewave has no browser extension and doesn't touch your browsing data on other sites.
Agents investigate and score continuously. That part is always automatic. Action, like sending an email, only happens within limits you define through your AI Supervisor, such as a minimum confidence threshold.
Connect Gmail or Outlook and emails send from your own address, not a shared domain. If you'd rather not connect an inbox, Direct Send lets you export and send manually instead.
Every contact passes through a multi-step verification waterfall before it ever reaches you, with a confidence rating so you know how reliable it is, not a static list that's already stale.
Lakewave sends from your own Gmail or Outlook mailbox. Here is exactly what that connection is, for the rep who connects it and the admin who approves it.
Lakewave is a Microsoft verified publisher (Lynbrook Solutions LLC), so the Microsoft 365 consent screen shows the blue verified badge rather than an unverified-app warning. The Google OAuth app is verified for its send scope. Both show the real company name on the consent screen.
The permission requested is send mail (Microsoft Mail.Send, Google gmail.send). Lakewave cannot read your inbox, your contacts or your calendar. Replies still reach you, without Lakewave reading your mailbox.
A Lakewave account is its own email and password. Registration requires a company email address, but Lakewave does not sign you in through your company's identity provider, and connecting a mailbox is optional and only for sending.
Disconnect a mailbox from the Connections page or revoke it in your Microsoft or Google account; Lakewave stops sending immediately. Ask [email protected] to delete a contact or your account data and it is done under the Data Processing Addendum.
Step-by-step admin approval for Microsoft 365 and Google Workspace, with the exact scopes: Connecting Gmail or Outlook.
Lakewave is a small, founder-led company. Here's where things stand honestly. Reach out directly for current status on anything not yet finalized.
No. Lakewave has no Chrome extension and does not extract data from your browser as you visit other sites. Contacts are found and verified through Lakewave's own agents and data sources.
Action only happens through policy-based limits you define, like a minimum confidence threshold before any contact is sent to. Agents investigate and score continuously, but only act within boundaries you set through your AI Supervisor.
Yes. Lynbrook Solutions LLC, the company behind Lakewave, is a Microsoft verified publisher, so the Microsoft 365 consent screen shows the verified badge. The Google OAuth app is verified for its send scope. Admin approval steps for both are on the Connecting Gmail or Outlook page.
Send only: Mail.Send on Microsoft 365 and gmail.send on Google. Lakewave cannot read your inbox, contacts or calendar. Replies still reach you without Lakewave reading your mailbox.
Email [email protected] from your account address. Individual contacts, uploaded lists and whole accounts are deleted on request under the Data Processing Addendum, and a disconnected mailbox is never sent from again.
Lakewave is a small, founder-led company actively working through standard procurement requirements. Reach out directly for current status on W9 and cooperative purchasing vehicle availability.
Reach out directly: we'll give you a straight answer.
Contact us →