Privacy Policy

Account details. Your name, email address and sign-in method (email and password, or Google), handled through Firebase Authentication. We never see your Google password.

What you give us to work with. The website you paste, the campaigns you pick, edits you make, the emails you write and send, and the sender name and address you choose.

Business contact data. To find companies and decision makers, Beaconly looks up publicly available business information — company details and people's names, job titles, work email addresses and professional profiles — from a third-party B2B data provider.

Email activity. For emails sent through Beaconly: delivery status, replies and a short excerpt of each reply, so you can follow up and so meetings can be booked.

Calendar data, if you connect it. Which calendar is connected, its time zone, when you're busy (to find open times) and the meetings Beaconly books. We don't read the contents of your other events.

Technical data. IP addresses and request logs, used to keep the service secure and to limit abuse. Beaconly doesn't use advertising or analytics trackers.

• To run the service: research your site, suggest campaigns, find and rank companies and contacts, write emails, send them, track replies and book meetings.
• To keep your work as projects you can come back to.
• To secure the service, prevent abuse and fix problems.
• To contact you about your account or important changes.

Beaconly uses OpenAI models to summarize websites, suggest campaigns, assess how well companies fit, write and rewrite emails, and understand replies (for example, whether someone wants to meet). The text needed for each task is sent to OpenAI through its API. We don't use your data to train our own models.

We share data only with the providers that run parts of Beaconly, and only what each one needs:

• Firebase (Google) — sign-in and accounts.
• OpenAI — the AI features above.
• Apollo — company and contact data.
• Mermail — the mailbox that sends your emails and receives replies.
• Composio and Google Calendar — connecting your calendar and booking meetings.
• Cloud hosting and database providers — running the app and storing its data.

We don't sell personal data.

If you've received an email sent with Beaconly, it was sent by a Beaconly user who chose to contact you, using business contact details. Every email lets you opt out by replying. To ask what we hold about you, or to have it removed, write to toannhu@nudgen.net.

We keep your account and projects while your account is open. Sent emails and their replies are kept with the project they belong to. When you ask us to delete your account, we delete your data within 30 days, except where we must keep records by law or to resolve disputes.

• Disconnect your Google Calendar from a project at any time, which revokes Beaconly's access to it.
• Turn automatic meeting booking off for any project.
• Delete projects that haven't sent emails from your dashboard.
• Ask for a copy of your data, a correction, or deletion of your account by writing to toannhu@nudgen.net.

Depending on where you live (for example in the EU or UK), you may have further rights, including to object to processing and to complain to your data protection authority.

Beaconly stores your sign-in session (via Firebase) and your in-progress research for the current tab in your browser's storage, so a reload doesn't lose your work. These are needed for the service to work; we don't use cookies for advertising or tracking.

Data is sent over HTTPS. Credentials for connected services are stored encrypted, and access to production data is limited. No system is perfectly secure, so if you think something is wrong, please tell us at toannhu@nudgen.net.

We'll update this page when our practices change and, for material changes, let you know by email. Questions about privacy go to toannhu@nudgen.net. See also our Terms of Service.