On this page
How to read this page
This is the short, practical version of our privacy policy. Each row is one kind of data. Where a service outside Moonreply receives it, the third party services page says exactly what it gets and when. Cookies and browser storage are listed one by one in our cookie policy.
About you, when you use Moonreply
Account holders, workspace members and people invited to join a workspace.
| What | Why | How long we keep it | Who else receives it |
|---|---|---|---|
| Account and sign inYour name, email address, username, profile image and sign in method, such as a password or your Google account. Clerk also records your sign in sessions and devices, and whether and when you finished or skipped the welcome tour, so it shows only once. We also record whether you chose reduced motion, so the app moves the way you asked on every device. | To create your account, sign you in and check that every request really comes from you. | While your account exists. Clerk holds these details; we keep your account ID next to the records you create. | Clerk. Google, if you choose to sign in with Google. |
| Workspace detailsWorkspace name, timezone, the postal address printed in your emails, and who belongs to the workspace in which role. | To keep each workspace separate, decide who may do what, and include the sender address the law requires in commercial email. | While the workspace exists. Workspaces are deleted on request to us. | Your postal address appears in every campaign email the workspace sends. |
| Team invitations and team changesThe email address of each person invited to a workspace, the role offered, who invited them, when the invitation was sent, accepted or withdrawn, and a fingerprint of the invitation link. The link itself is never stored. A history of team changes records who invited, joined, left, changed a role, transferred ownership or was removed, and when. | To let the invited person join with the role offered, only from the email address the invitation was sent to, and to show the owner and admins how the team changed. | While the workspace exists, or until you ask us to delete them. An invitation stops working after seven days, once it is used, or when it is withdrawn. | The active mailbox connected by the workspace owner sends the invitation email. If it cannot send, the person who invites shares the secure link themselves. |
| Connected mailboxesSender name and address, server settings, the mailbox password or app password, or the Google or Microsoft access token, daily send counts and the last connection error. Passwords and tokens are encrypted. | To send your campaigns and replies from your own mailbox, and to read new mail in it to find replies and bounces. | Until you remove the mailbox. A mailbox that has sent campaign email can be paused but not removed in the app, so its encrypted password or token stays stored until you ask us to erase it. | Your mailbox provider, such as Google, Microsoft or the email host you use. |
| MoonAgent conversations and memoryYour messages, MoonAgent's answers, the contacts and statistics it looked up, drafts, lead lists, reports, approvals, and facts saved to memory by you or by MoonAgent. | To answer your requests, keep a history you can return to, and remember context you chose to save. | Conversations stay while the workspace exists. You can archive them in the app and ask us to delete them. Memories stay until you delete them. | DeepSeek, the AI model provider, receives each request with the context it needs. |
| Job outreach profileResume text taken from the PDF you upload, the role you want, your preferences, chosen contacts, drafts and the date you agreed to AI processing. We keep the text, not the file. It is encrypted and only you can open it. | To tailor job search emails to your experience. | Until you choose Remove profile. Campaigns you already created from it stay in the workspace. | DeepSeek, when AI drafting for Job outreach is on and you have agreed. Withdraw consent on the Job outreach page stops it. |
| Integrations, keys and webhooksYour HubSpot access token (encrypted), API and MCP key names with a fingerprint of each key, webhook addresses with their encrypted signing secrets, and delivery results. | To import contacts from your CRM, let tools you authorize use your workspace, and notify your own systems of events. | The HubSpot token is deleted when you disconnect. Revoked keys stay as records without the key itself. Webhook delivery records are deleted after 30 days. | HubSpot, and any app or system that holds a key you created or a webhook address you added. |
| Usage, limits and delivery testsCounts of searches, email checks and AI requests used, spending limits, delivery test sends and the authentication results they returned. | To apply plan and daily limits, control costs, and show whether your mailbox authenticates correctly. | Delivery tests while the workspace exists. Usage counts, with no content and no user, are kept after the workspace is deleted, so an allowance cannot be reset by deleting and starting again. | Nobody, except the mailbox providers that carry a delivery test. |
| Plans and paymentsFor each workspace: the plan, billing period, subscription status, renewal and cancellation dates, verified contact pack purchases and balance, and the Stripe customer, subscription and checkout IDs that link them. Card details are entered on Stripe's payment page; we never see or store your full card number. | To apply the plan you paid for, add the verified contacts you bought, apply the limits of your plan and answer billing questions. | While the workspace exists. Stripe keeps its own payment records for as long as the law requires. | Stripe, which processes payments. Checkout runs in Stripe test mode today, so no real payment is taken. |
| Retired LinkedIn recordsFor workspaces that used our former LinkedIn feature: the LinkedIn account name and email, an encrypted access token, drafted task messages, and the names and LinkedIn profile addresses of the people in those tasks. | None today. The feature is retired and no longer contacts LinkedIn. | Still stored. Ask us and we delete them. | Nobody. |
About people who receive emails sent with Moonreply
Contacts that a workspace adds or finds. The workspace decides who to contact; we process this data on its behalf.
| What | Why | How long we keep it | Who else receives it |
|---|---|---|---|
| Contacts and listsEmail address, name, company, job title, website, timezone, any extra columns the workspace imports, and the lists each contact belongs to. | To build campaign audiences and personalise messages for the workspace that added them. | Until a workspace member deletes the contact. A contact in an active or paused campaign cannot be deleted until that campaign is finished. | Added by the workspace from files, HubSpot, the API, MoonAgent or Find contacts. Visible to apps holding a workspace key, and to DeepSeek when MoonAgent looks them up. |
| Campaign emails and sending historyCampaign steps and wording, who received which step and when, the recipient address, subject and first 160 characters of each email, message IDs and the mail server's response. | To send each step exactly once, keep replies in the same thread and report results. | While the workspace exists. Recipients cannot be removed from a campaign after launch, and sent message records keep the address even if the contact is deleted. | The workspace's mailbox provider carries each email to its recipient. |
| Opens and clicksA record that an email was opened or a link was clicked, with the link address. We do not store the reader's IP address, device or location. | To report on campaigns and to branch a sequence when someone opens or clicks. | While the workspace exists. | Cloudflare or our server's proxy sees the reader's IP address and browser details while passing the request on. |
| Unsubscribes and suppressionThe email address, the reason (unsubscribed, bounced, complaint or added by hand) and the date. | So nobody who asked to stop, or whose address bounced, is emailed again by that workspace. | For as long as the workspace exists, because deleting it would let that address be emailed again. | Nobody outside the workspace. It is part of the workspace export. |
| Replies and other inbox mailFor replies, bounces and automatic replies such as out of office notices that answer an email sent with Moonreply: subject, first 160 characters, message IDs and how we classified the message. Other inbox mail is not stored. Replies written in Moonreply are kept as subject, snippet and a fingerprint of the text. | To stop a sequence when someone replies, suppress bounced addresses and show replies in the inbox. | While the workspace exists. | The mailbox provider it came from. DeepSeek receives reply snippets when MoonAgent reads your inbox for you. |
| Lead research and email checksBusiness contacts found for a workspace: name, work email, job title, company, website, LinkedIn profile address, where the details were found and whether the address was verified. Also the searches run and the result of each email check. | To search contacts already found before paying for a new search, avoid duplicates, and offer only addresses that passed a mailbox or domain check. | Until the workspace or the person concerned asks us to delete them. These records are not in the workspace export yet. | Found through Apify and public websites, and for our own workspace also our lead library. Addresses being checked go to a verification tool on Apify. DeepSeek sees the results MoonAgent shows you. |
| Find contacts previewsContact suggestions, published email addresses, source pages and short excerpts from public company websites, stored encrypted and visible only to the person who ran the search. | So you can check the sources before importing any contact. | Seven days, then deleted automatically. Contacts you import become workspace contacts. | Company websites are visited from our server. If you choose Read more deeply, the page addresses go to a page reading tool on Apify. |
| Lead libraryA library of business contact records (name, work email, job title, company, website, professional profile address and location) that we compiled from third party business contact datasets, including exports of professional profile data and business contact databases. We keep it in Google Colab and Google Drive, and only our own workspace searches it, for our own outreach. Research contacts and verification results from our own workspace can be copied into it. | To find contacts for our own outreach before paying for a new search. | Kept by us until the person concerned asks us to remove them. | Searched through a secure tunnel run by Cloudflare or ngrok, only by our own workspace. Never searched for or shared with other workspaces. |
About everyone who visits our site or app
Website visitors, signed in users and people who open a tracked email.
| What | Why | How long we keep it | Who else receives it |
|---|---|---|---|
| Server and network logsIP address, browser details, the page or address requested and the time, plus technical errors. | To keep the service secure, stop abuse and fix problems. | For the periods set in our hosting and Cloudflare settings. Rate limit records in memory last a few minutes. | Cloudflare and our hosting provider. |
| Website analyticsPages viewed, the page you came from, browser type and page load times. No cookies are set. | To understand which pages people use and how fast they load. | As set by Cloudflare Web Analytics. | Cloudflare, only if we turn analytics on. It runs only after you allow analytics. |
| Cookies and browser storageSign in cookies, short lived security cookies, a record of your cookie choices and, if you allow them, a few display preferences. | To keep you signed in, protect mailbox connections and remember choices such as a collapsed sidebar. | Each item is listed with its duration in our Cookie policy. | Clerk sets the sign in cookies. Cloudflare may set a security cookie. |
Your choices
- Download your workspace data at any time from Settings, Export your data.
- Remove your Job outreach profile, delete MoonAgent memories, disconnect HubSpot and revoke API keys yourself in the app.
- For anything else, including a copy of records the export does not cover yet or deleting your data, email aamirmursleen@gmail.com.
- If you received an email sent with Moonreply, use its unsubscribe link to stop that sender, and read what we hold about recipients.