✦ Legal
Privacy Policy
Last updated November 13, 2026
This policy explains what The Writing Wives collect when you use Author Tools or work with us on your Meta advertising, why we collect it, how long we keep it, and how to have it removed. It is written to be read, not skimmed past; if anything is unclear, ask us.
1. Who we are and what this covers
The Writing Wives ("we", "us") is a small business run by Malorie and Jill Cooper in Swift Current, Saskatchewan, Canada. We help independent authors market their books. This policy covers two things:
- Author Tools — the tools at authortools.net and its subdomains: Write (write.authortools.net), Copy Studio (ad-copy.authortools.net), the help center (help.authortools.net), Book Mockup Studio (bookmockups.authortools.net), Graph Lens (lens.authortools.net), Ad Image Studio (ad-images.authortools.net), Ad Video Studio (video.authortools.net), the Author Tools blog (blog.authortools.net), Meta Ads for Authors (flightdeck.authortools.net), our ad-management method and the hosted Flight Decks that go with it, the shared sign-in at account.authortools.net, and Support (support.authortools.net), with the Feedback tab that appears on our sites.
- Our Meta advertising service — when we create and manage Facebook and Instagram ads for you as a client.
Our community on Skool, our Substack, and thewritingwives.com are run on other companies' platforms and have their own privacy policies alongside this one.
2. What we collect
Free tools, no account
Book Mockup Studio runs in your browser. The cover images you load into it stay on your device; they are not uploaded to us. The first time you download a mockup we ask for an email address so we can send you occasional news about the tools and the community; that address goes to our email list (EmailOctopus) and you can unsubscribe from any message. If you are signed in to Author Tools we skip that prompt.
Graph Lens fetches the public page you point it at and shows you the structured data on it. We do not keep or log the pages you inspect.
The blog
You can read the blog without an account, and it sets no cookies of its own. If you sign up for news on the blog, your address goes to our email list (EmailOctopus), tagged as coming from the blog, and EmailOctopus emails you to confirm before anything else is sent. Sign-ups pass a Cloudflare Turnstile check, and Cloudflare limits how often one network can try.
Some posts include YouTube videos. We use YouTube's privacy-enhanced mode (youtube-nocookie.com), but the player still loads from YouTube, so YouTube receives your IP address and browser details when you open such a post. Google's privacy policy covers what YouTube does with that.
If you write for the blog, we keep your name and email address so you can sign in to the editor, every draft and earlier version of your posts, and a record of any AI assistant you connect to it. Your name appears as the byline on what you publish.
Author Tools account (member and purchased tool access)
- Sign-in details: your email address and, if you give one, your name. You sign in with a link we email you, or with a password if you set one on your Profile; we store only a scrambled form of the password (a salted scrypt hash), never the password itself.
- Membership: whether you are a member of The Writing Wives on Skool and at which tier. Skool passes this to us when you join or your membership changes, so the member tools know to let you in.
- Community Membership Credits: your monthly allowance and what you have spent it on (server renders, AI images and clips, AI copy stages), so we can show you a balance.
- Purchased Credits: we store and track purchases of credits and the current remaining balance.
- Things you upload: pictures, video clips, book covers and, for Copy Studio, your manuscript as an EPUB. Uploads are stored in your private library until you delete them. A manuscript is read once, chapter by chapter, to build the copy engine's notes, and the EPUB file is deleted as soon as that read finishes; the notes (positioning, excerpts, character descriptions) stay with the book in your account.
- Things you make: reels, still ads, copy, image and clip prompts, generated pictures and clips, and the settings behind them.
- Book sources: the Goodreads page for a book you add (public information: blurb, shelves and reviews) and any reviews or blurb you paste in.
- Connector access: if you connect an AI assistant to Author Tools through our MCP connector, we record the authorisation you granted so you can revoke it.
- Purchases: Membership accounts are paid for via Skool. Non-membership purchases are made through Stripe. We do not have access to, or store, any address or payment information from either service.
Meta Ads for Authors
If you use Meta Ads for Authors, we keep a record of your ads for each Flight Deck: one for your own ads, and one for each client you run ads for. Your AI assistant sends it to us through our connector, and the Attribution bookmark sends what it reads from your Amazon Advertising console. A record holds:
- the history of your campaigns (the ad sets, every change, the decisions from each review and your notes)
- Meta's daily figures for each ad set (spend, clicks, impressions) and age-and-gender totals
- Amazon Attribution's daily figures for each ad group (clicks, page reads, sales)
- the copy of your ads
- your Meta ad account number
We don't store charts, Meta's raw activity log (it names the people who made changes), or anything about individual readers; Amazon and Meta give us totals only. We build your Flight Deck from the record. A deck you share by link can be seen by anyone with the link until it expires or you turn it off, and it never shows your ad account number or who manages your ads.
Meta Ads connector (metaapi-mcp.authortools.net)
When you connect your AI app to Meta through Author Tools, we store, for each connection:
- the Meta access token you paste, encrypted so that it can only be unlocked with your AI app's own sign-in
- which Meta user and kind of token it belongs to, and when the token expires
- your Author Tools account
- when the connection was made and last used
We store your AI app's sign-in codes and tokens only as one-way hashes.
We don't store your ads, reports or anything else Meta sends back. Each request passes through to Meta, and the reply goes straight to your AI app. Your AI app never sees your Meta token, and tokens never appear in our logs.
We keep a short security record of connections being made, refreshed and ended. It never contains a token, and we delete it after 90 days.
Ending a connection and deleting your data. In your Author Tools account, open Connected apps and choose Disconnect next to the connection. Your AI app stops working with Meta at once, and the stored token is deleted. The rest of that connection's record is removed within 7 days. For anything else, or to ask us to delete your data, email support@reply.authortools.net.
The connector runs on our application servers at Akamai/Linode (see section 5). Access to them is protected with multi-factor authentication. It talks only to Meta's Graph API, and we share none of this data with anyone else.
Amazon Attribution connector (amazonapi.authortools.net)
When you connect your Amazon advertising account to your AI app through Author Tools, you sign in with Amazon and allow our connector to read your Amazon Attribution data. The connector only reads. It never creates, changes or pays for Amazon ads.
On your requests, it reads from Amazon:
- your advertising profiles (their id, country, account name and account type)
- your Attribution advertisers and publishers, and your tag templates
- Attribution reports: clicks, product detail page views, purchases, sales, units and Kindle pages read (KENP), by campaign, ad group, ad and day, and which products they were for
Reports pass straight through to your AI app; we don't store them. We store, for each connection:
- the refresh token Amazon issues to Author Tools when you allow access, encrypted, and never written to our logs (Amazon's hour-long access tokens are held in memory only, never stored)
- your advertising profiles (id, country, account name and account type), the ids of your Attribution advertisers, and your Amazon region (North America, Europe or Far East)
- your Author Tools account, the name of the AI app you connected, and when the connection was made, refreshed and ended
We keep a short security record of connections being made, refreshed and ended, and of each request the connector carries out (your account, which tool, when, and whether it worked). It never contains a token, what you asked for, or report data, and we delete it after 90 days.
Ending a connection and deleting your data. In your Author Tools account, open Connected apps and choose Disconnect next to the connection. That deletes the stored Amazon token and the profile and advertiser details at once, and the rest of that connection's record within 7 days. You can also remove Author Tools' access on Amazon's side, in your Amazon account's Login with Amazon settings. For anything else, or to ask us to delete your data, email support@reply.authortools.net.
The connector runs on our application servers at Akamai/Linode (see section 5). Access to them is protected with multi-factor authentication. It talks only to Amazon's advertising API, and we share none of this data with anyone else.
Meta advertising clients
- Contact and business details: your name, email, business name, the books and links we advertise.
- Ad account access: the permissions you grant us in Meta Business Manager so we can build and run campaigns in your ad account. The account, its payment method and its data remain yours and stay with Meta.
- Creative assets: covers, images, video and copy you give us or approve for your ads.
- Performance reports: we keep reporting data for the campaigns we run (spend, reach, clicks, conversions and similar figures) so we can manage your ads and show you how they did. We keep at most about one year of history.
Support and feedback
When you write to us through Support, the Feedback tab on one of our sites, or our support email address, we keep:
- What you write: your message, its subject, whether it's feedback or a request for help, and the conversation that follows.
- Your email address and, if you give it, your name, so we can reply. If you're signed in, we use your account's address and link the conversation to your account.
- Email you send us: the sender, the subject and the text. We keep any email that reaches our support address this way, including auto-replies and spam. We don't keep files attached to emails.
- From the Feedback tab: the page you were on (its address without anything after the path), your screen size, the time and your timezone, your browser type, and any details the page adds to help us (such as which book or design you had open, by its ID, never its contents). A screenshot is included only if you attach one; nothing is captured automatically.
- If you're signed in: a note of your membership and tool access when you wrote, so we can see what you're using when we help.
If you write without signing in, we email you a link to confirm the address is yours. Until you confirm it, the conversation is not linked to anyone's account.
To stop abuse, signed-out messages pass a Cloudflare Turnstile check, and we limit how many messages one address or one network can send. Those limits store your IP address and email address only as one-way codes, which are cleared out once the hourly limits reset.
Technical information (all services)
Our servers keep ordinary logs: IP address, browser type, the pages and API calls requested, and timestamps. When something goes wrong (for example an AI provider refuses a request), we keep an error record that can include the text of the request so we can fix the problem; these records are visible only to us.
We do not collect payment card numbers. Membership payments are handled by Skool; Write subscriptions and credit purchases by Stripe; anything you pay us for advertising work is invoiced and paid through the payment provider named on the invoice.
Ad measurement (Meta Pixel and Conversions API)
We advertise Author Tools on Facebook and Instagram, and we use Meta's tools to see which of our ads lead to sign-ups and purchases.
- In your browser: on the pages where we have turned it on, Meta's Pixel loads from Meta and tells Meta you viewed the page. Meta receives the page's address, your IP address and your browser details, and sets its own cookies (see section 7). The Pixel never runs on admin pages.
- From our server: when you create an account, start a trial, or buy a plan or credits, our server tells Meta directly (Meta's Conversions API). It sends the event, what you bought and its price, your email address and account number scrambled with SHA-256 (so Meta can match them to a Meta account without reading them), the values of Meta's cookies if your browser has them, and your IP address and browser type.
We never send Meta your name, your uploads, your manuscripts, or anything you make with the tools.
3. How we use it
- To run the tools: sign you in, store your library, draw and render your reels, generate the copy, pictures and clips you ask for, and keep your credits straight.
- To answer your questions and feedback, fix what you report, and decide what to build next. We count tickets by site and type, and measure how quickly we reply, to see where we fall short. When a report becomes a task for us, we copy it to our own internal task board with your name and email address taken out.
- To run your advertising: build, manage and report on your campaigns.
- To email you about your account and the tools (sign-in links, alerts about something you asked for), and, if you opted in through the mockup tool, occasional news you can unsubscribe from.
- To keep the service safe: every image and clip prompt is screened automatically before anything is generated, and blocked prompts are kept for our review (see section 4).
- To understand what is used and fix what breaks, using logs and error records.
- To measure our own advertising: which of our Facebook and Instagram ads bring sign-ups and purchases (see Ad measurement). Meta uses these events to measure our ads and decide who sees them, which can include showing our ads to people who have visited our pages.
We do not sell your information, and beyond the ad measurement above we do not use it for advertising of our own. We do not build profiles of you from your manuscripts or your ads.
4. AI features and the services behind them
Several member tools use outside AI services. When you use one of those features, the material needed for that job is sent to the provider and the result comes back to your account:
- Anthropic (Claude models) writes the copy engine's analysis and ad copy. It receives the book's blurb, reviews, the manuscript text during the validation read, and the copy you have already picked.
- fal.ai generates pictures and short clips from the prompts you approve, and animates pictures into clips. It receives the prompt and, for clips, the picture.
- Tavily runs web searches for the copy engine's research steps (for example, what readers of a genre expect). It receives the search query only.
Support conversations are also read by AI assistants that work for us, which run on Anthropic's Claude models. They sort and tag messages, mark spam, add notes for us, and draft replies. They never see your email address, and they cannot send anything: a person on our team reads every reply before it goes to you, and sends it.
These providers process your content only to perform the task you asked for, under their business terms. We do not use your uploads, manuscripts or outputs to train models of our own.
Safety screening. Before a picture or clip is generated, its prompt is checked automatically by an AI classifier that runs on systems we control, against a fixed rule that nothing sexualising minors is ever produced. A blocked prompt costs nothing and is not sent to the image provider; it is kept, with your account, for our review. Where the law requires it we will report content of that kind.
5. Who we share it with
We share information only with the companies that help us run the service, and only what they need:
- Hosting and storage: Cloudflare (websites, uploaded files and generated media in R2 storage, and the Turnstile check on our forms) and Akamai/Linode (application servers, including Support's).
- Email: Resend (sign-in links, account messages, and support email in both directions) and EmailOctopus (the news list, from Book Mockup Studio and the blog).
- Payments: Stripe (Write subscriptions and credit purchases). Stripe holds your card and billing details; we see only what you bought and whether the payment went through.
- Membership: Skool and Zapier, which tell us when a member joins or changes tier.
- AI providers: as described in section 4.
- Meta: when we run ads for you, everything about those ads lives in your Meta ad account under Meta's own terms. For our own ads, Meta receives the ad-measurement events described in section 2, under Meta's terms and data policy. When you use our Meta Ads connector, your requests go to Meta's Graph API with your own token, for your own Meta app.
- Amazon: when you use our Amazon Attribution connector, your requests go to Amazon's advertising API with the access you granted when you signed in with Amazon, under Amazon's own terms.
We do not share ad performance data, manuscripts or anything else about you with third parties beyond this, other than if the law requires it or you ask us to. If we ever sold or handed over the business, your information would go with it under the same rules, and we would tell you.
6. How long we keep it
- Account details, library uploads and things you make: while your account exists, or until you delete them. You can delete uploads from your library at any time.
- Manuscript EPUBs: deleted immediately after the copy engine's read finishes. If a read fails, the file is deleted when you remove the book or ask us to.
- Ad performance reports: at most about one year, then deleted.
- Meta Ads for Authors records: daily figures for 90 days; the campaign history, decisions and ad copy until you delete them; earlier versions for up to 90 days. Records stay after a membership lapses, so you can still download or delete them.
- Server logs and error records: up to 90 days.
- Meta Ads connector: your stored Meta token until you disconnect (it is deleted at once); the rest of a connection's record, within 7 days after it ends; the security record of connections, 90 days (see Meta Ads connector).
- Amazon Attribution connector: your stored Amazon token and profile and advertiser details until you disconnect (they are deleted at once); the rest of a connection's record, within 7 days after it ends; the security record of connections and requests, 90 days (see Amazon Attribution connector).
- Our log of ad-measurement events sent to Meta: 90 days. Your IP address and browser details are removed from it as soon as each event is sent.
- Support conversations, with any screenshots: 2 years after the last activity on the conversation, then deleted. Spam, and conversations from an address that was never confirmed, are deleted 90 days after their last activity.
- Records we must keep, such as invoices: as long as tax and business law requires.
Deleted data can persist in backups for up to 30 days before it is gone for good.
7. Cookies
Author Tools sets a few cookies of its own, all of them needed for the site to work or to remember your choices. On some pages Meta sets its own as well:
- Sign-in:
at_sessionkeeps you signed in across the tools and renews itself every hour;at_session_atnotes when it was last renewed;at_signin, on account.authortools.net only, keeps you signed in for up to seven days of inactivity. Support uses the same sign-in cookie: when you open the Feedback tab on one of our sites while signed in, your browser sends it to support.authortools.net so we know it's you. - Appearance:
at_appearance,at_lightandat_darkremember whether you chose light or dark mode and which theme.
- Your answer about ad measurement:
at_consentremembers whether you said yes or no, for six months (see section 8). - Ad measurement (Meta's): on pages where the Meta Pixel runs, Meta sets
_fbp, which identifies your browser to Meta, and, if you arrived from one of our ads,_fbc, which records that click. Both last up to 90 days. Our server reads them when it reports a sign-up or purchase (see Ad measurement).
Apart from the Meta Pixel there are no third-party analytics on our sites. The free tools and the blog set no cookies of their own.
8. Your rights and choices
Wherever you live, you can ask us to tell you what we hold about you, correct it, or delete it, and you can withdraw consent to any optional use (for example, unsubscribe from the news list). We honour the rights given by Canada's PIPEDA, the EU and UK GDPR, and state laws such as California's CCPA, for everyone, not only where they strictly apply.
To delete your data: email malorie@thewritingwives.com with your name, the service (Author Tools, or our advertising work), and what you want deleted. We confirm and complete the deletion within two business days. The full steps are on our data deletion page.
Ad measurement: if you are in the European Economic Area, the UK or Switzerland, or we can't tell where you are, we ask before the Meta Pixel runs, and nothing about you goes to Meta, from your browser or our server, unless you say yes. Anyone, anywhere, can say no. Your answer is kept for six months in the at_consent cookie, for all our sites; change it any time with Cookie settings at the bottom of our pages. You can also block third-party scripts or cookies in your browser (most content blockers do), or change your ad preferences in your Facebook or Instagram settings. The tools work the same either way.
Requests cover your support conversations too. Because anyone can type any email address into a form, we'll confirm you control the address before we show you, or delete, conversations sent from it.
For Meta Ads for Authors, you can also do it yourself: the Your records card on your ads home has a download for each deck, and "Delete everything" removes all your decks, records, share links and exports at once.
If you are in the EU or UK and are unhappy with how we handled a request, you can complain to your data protection authority; in Canada, to the Office of the Privacy Commissioner. We would rather hear from you first.
9. Security
Everything travels over encrypted connections. Uploads are stored under keys private to your account and served through short-lived links. Access to servers, storage and admin screens is limited to the two of us. No system is perfectly secure; if we ever learn of a breach affecting your information we will tell you and the authorities as the law requires. Support conversations and screenshots are visible only to us and to the AI assistants described in section 4, which never see email addresses.
10. Where your data lives
Our servers and storage are in the United States and Canada, and the providers in section 5 may process data in other countries where they operate. When data leaves Canada, the EU or the UK we rely on the providers' standard contractual protections.
11. Children
Author Tools and our advertising service are for adults running a writing business. We do not knowingly collect information from anyone under 18; if you believe we have, tell us and we will delete it.
12. Changes and contact
We will update this page when what we do changes, and note the date at the top. Substantial changes to how member data is used will also be announced in the community.
Questions and requests: malorie@thewritingwives.com. Post: The Writing Wives, Unit 204, 245 Central Ave North, Swift Current, SK S9H 0L3, Canada.
See also our Terms of Service and Data deletion page.