1. Information we collect

Account. Your name, email address and profile picture from Google. Google is the only way to sign in to VoiceMoat.

Connected social accounts. For each Twitter or LinkedIn account you connect: your handle, your display name, the date you connected it, and an access token that lets us post and read on your behalf.

Your content. The posts, threads, replies and drafts you write, generate or schedule through VoiceMoat, and the ideas and topics you save.

Dictation and read-aloud. If you use the microphone button in audenAI, your browser turns what you say into text, and VoiceMoat receives only that text, handled like anything else you type. If audenAI reads a reply aloud, your browser turns the reply into speech on your device or through its own speech service. We never receive, record or store audio.

Your writing analysis. A voice profile derived from your own posts, covering things like tone, sentence rhythm, vocabulary and phrases you avoid. It exists so that drafts read like you rather than like everyone.

Engagement figures. For your own posts: impressions, reactions, replies, reposts and follower counts. For public posts in the shared library: public reaction, comment and share counts only.

Usage records. Which features you used, how many credits they spent, your plan and billing status, and product analytics about how you use the app. Inside the signed-in dashboard this includes Google Analytics and PostHog session recordings, with anything you type masked, linked to your account. On this website, analytics follow your cookie choice, as set out in our cookie policy.

2. How we collect LinkedIn data, and why it matters

LinkedIn does publish a post analytics API, but it is gated behind the Community Management partner program and VoiceMoat has not been approved for it. LinkedIn engagement therefore reaches VoiceMoat through the VoiceMoat browser extension instead. The extension runs in your own browser, uses the LinkedIn session you are already signed into, reads the figures for your own posts, and sends them back to your VoiceMoat account.

It runs only if you install it, only on your own account, and only while you are signed in to LinkedIn. It does not read your messages, and it does not act on anyone else's account.

When you refresh Inspiration or Replies, or track a creator, the extension also reads a small batch of public LinkedIn posts (from your home feed, that creator, or a hashtag) into a shared library of public posts every VoiceMoat user can browse. It stores each post's author's public name and photo, never who showed it to you.

One consequence is worth knowing: your LinkedIn numbers are only as fresh as the last time the extension ran. A quiet week in your analytics can mean an unsynced account rather than a quiet week.

3. How we use your information

To run the service: signing you in, connecting your accounts, generating and improving drafts in your voice, scoring drafts against your voice profile, publishing and scheduling posts when you ask it to, and showing you how your posts performed.

To meter and bill: counting credits, applying plan limits, and processing your subscription.

To keep the service working: diagnosing errors, preventing abuse, and enforcing our terms.

To contact you: service and billing emails, and product updates you can unsubscribe from.

We do not sell your data. We do not use your content to train public AI models.

4. Connecting VoiceMoat to an AI assistant

On the Pro and Enterprise plans you can connect VoiceMoat to ChatGPT, Claude or another assistant that supports the Model Context Protocol. That assistant can then call VoiceMoat tools on your behalf.

Whatever a tool returns goes to that assistant: your account email and plan, your connected profiles, your voice profile and writing analysis, your posts, and their engagement figures. This happens when you ask the assistant something that needs it, and the data is then handled under that assistant's privacy policy as well as this one.

Your social access tokens are never sent to an assistant. Publishing always takes two steps: the first call returns a preview and a one-time code and writes nothing, and only a second call carrying that code publishes. You can end the connection at any time from Settings > Assistants > Disconnect, or by removing VoiceMoat in the assistant.

5. Data storage and security

Your data is stored on Supabase with row-level security, so one account cannot read another account's rows.

Social access tokens are stored encrypted. They are never returned by our API, never returned by any connector tool, and are used only to publish or read on your behalf.

An access token issued to an AI assistant is checked against the specific VoiceMoat server it was issued for, so a token minted for another service cannot be used against ours.

6. Third parties who process your data

Supabase for the database, file storage and sign-in. Google for sign-in. Third-party AI providers for writing, analyzing and searching text and for generating images. The Twitter and LinkedIn APIs for publishing to and reading your connected accounts. Dodo Payments as our merchant of record. Resend for email. PostHog for product analytics and session recordings, in the app and, if you accept analytics cookies, on this website. Google Analytics, loaded on this website through Google Tag Manager, for site and product usage. Framer for hosting this website and its cookieless page analytics. Vercel for hosting the app and its cookieless page analytics. Ahrefs for cookieless analytics on this website. Sentry for error reports, with personal details removed first. Upstash for rate limiting, which uses your IP address. If you connect an AI assistant, WorkOS receives your account ID and email address to issue that assistant's access. If you give Growth a web address to read, Firecrawl fetches that page.

Each has its own privacy policy. We share the minimum each one needs to do its job, and we do not sell your data to anyone.

If you use dictation or read-aloud, your browser's own speech service may process the audio or the text being read, for example Google in Chrome. That happens between you and your browser, under the browser maker's privacy policy.

7. How long we keep it

We keep your data while your account exists, because the product depends on it. A voice profile trained on your posts is the thing that makes a draft read like you.

When you delete your account we keep it for 30 days so you can restore it, then delete it, keeping only your email address and the ID of any social account that started a trial. Public posts in the shared library are not linked to your account and stay after you leave. We may keep billing records where the law requires.

8. Your choices and your rights

You can disconnect a social account, disconnect an AI assistant (Settings > Assistants), or unsubscribe from product emails at any time from Settings.

You can delete your account from the Settings page. We cancel your subscription at the end of the billing period, cancel any posts still scheduled, end access for any connected AI assistant, and sign you out everywhere. For 30 days the account is kept, and signing in again with the same Google account restores it; canceled posts stay canceled. After 30 days we permanently delete your profile, connected accounts and tokens, voice analysis, generated content and stored engagement figures. We keep your email address, and the ID of any social account that started a trial, so each trial can be used only once.

Depending on where you live, you may have rights to access, correct, export or object to our use of your data. Email founder@voicemoat.com and we will action it.

9. Changes to this policy

If we change what we collect or who processes it, we will update this page and the date at the top. We will email you about material changes.

10. Governing law and where your data goes

VoiceMoat is operated from India, and this policy is governed by the laws of India.

The third parties named above operate their own infrastructure, so your data may be processed outside India. We share only what each one needs to do its job.

11. Contact

For privacy questions, contact founder@voicemoat.com.