Trust
A tool that touches your manuscript, your contacts, and your book’s reviews has to earn trust with specifics, not slogans. This page is the specifics.
Human approval gate
Nothing sends without you. Every pitch, post, email, and nudge is a draft until you say go.
Review ethics
We help real advance readers leave honest reviews. We never write fake reviews, never buy reviews, never incentivize 5 stars. We stay inside Amazon's policies — and we'll show you exactly how.
Your data
Read-only Google. We never write to your contacts or calendar, never share, never sell. Stored with row-level security (Supabase/Postgres).
Your voice
We learn your voice to draft; you keep your voice to publish.
The human-approval gate
Every pitch, post, email, and reader nudge AuthorsGTM drafts is exactly that — a draft. It sits in your daily docket with three options: approve, edit, or skip. There is no automated send path in the product. If you never open the app again, nothing goes out on your behalf.
Send it as drafted, in one tap.
Change anything — tone, facts, length — before it goes.
Decide it's not worth sending. Nothing is lost by skipping.
Amazon & retailer compliance
Review generation is the most compliance-sensitive part of this product, so here is exactly what AuthorsGTM does and does not do.
Amazon and other retailers publish community and review guidelines that prohibit incentivized, fake, or coordinated reviews. AuthorsGTM's review engine is built around that boundary: real advance readers, no incentive tied to sentiment, and a human approval gate on every ask. We are not Amazon and can't guarantee any individual review's outcome — we can guarantee the campaign never asks you to cross that line.
Your data
If you connect Google, access to Contacts and Calendar is read-only. AuthorsGTM never writes to, modifies, or posts through your Google account.
OAuth tokens for connected providers are encrypted with AES-256-GCM before they're stored. Token values never reach your browser or client-side code.
Your workspace data lives in Postgres (Supabase), with every table scoped to your workspace by row-level security — the application code has no service-role bypass around that isolation.
Your manuscript, contacts, and campaign data are never sold and never shared outside the systems needed to run your workspace.
Every AI-drafted post and email is checked against a deterministic banlist and a voice profile built from your own writing before it ever reaches your docket. Anything that reads generic gets rewritten once and, if it still fails, hidden until you edit it yourself. You approve the words that go out under your name — always.
Look at a sample launch plan, or start your own free Launch Readiness Report — no card, no commitment.