Privacy policy

What MurmurMill stores, who it is sent to, and how to have it deleted.

Who we are

MurmurMill, at murmurmill.com, is a service for scheduling LinkedIn posts and drafting them with AI. It is operated by CaskStack, LLC, doing business as MurmurMill, 101 Cooper Street, Santa Cruz, CA 95060, United States ("we"). We are the controller of the personal information described here, except where we say Stripe or LinkedIn is, and except for the information customers keep about their clients in client workspaces, for which we are the customer's processor (see "Client workspaces" below). You can reach us at privacy@murmurmill.com.

What we store

Your account

  • Your name and email address, with the email address in lower case. We also keep a signup key: the address with everything from the first + removed and, for Gmail, its dots removed, so that one mailbox cannot open several accounts.
  • Your password, stored only as a hash. You choose it when you confirm your email address.
  • Whether you have confirmed your email address and when, and when you agreed to the Terms and the Privacy Policy.
  • Your time zone, which MurmurMill reads from your browser so posts go out at the time you chose.
  • A "remember me" token, if you tick that box when you log in.
  • A new email address you asked to change to, until you confirm it from the link we send there or cancel it.
  • If you turn on an authenticator app: its secret key, stored encrypted; your recovery codes, stored as hashes inside an encrypted column; and the time step of the last code we accepted, so a code cannot be used twice.
  • If you add a passkey (table passkeys): its name, the credential ID and public key your device gave us, the signature counter, when it was added and when it was last used. The private key never leaves your device or password manager.
  • The organization created for you when you confirm your email address, which is named after you, and your role in it. Its web address is made from your name. If the organization is deleted, its web address is kept for 90 days so that nobody else can take it.
  • Each client you add, as a workspace with the client's name and time zone.
  • If you join an organization by invitation, your role in it and, if you are a member, the clients you may open.

Signing up and confirming your email address

When you sign up, MurmurMill stores your name, email address, time zone, the time you agreed to the Terms and the Privacy Policy, and the referral code from your referral cookie, if you have one. It also gives the account a password nobody knows, and emails a link to the address you gave. No organization and no trial exist until you open the link and choose a password. The referral code is kept with the signup until then, because you may open the link on another device.

The link works once and for 24 hours. If it is not used, we delete the signup, with the name, address, time zone and referral code, 7 days after it was made. Signing up again with the same address after an hour replaces an unconfirmed signup, and signing up again within the hour sends the link again. Addresses on a list of disposable email providers are refused, and a signup from a company address is refused when several people from the same company domain have signed up that day.

The signup page always asks Cloudflare, through its Turnstile service, whether the visitor is a person. Cloudflare's script runs in your browser and decides from signals about your browser and connection. MurmurMill sends Cloudflare the token the check produced, with your IP address, to confirm the result, and signup does not go on without a positive answer. The log-in, invitation, confirmation and resend forms do not show the check to most people: MurmurMill first looks at a hidden field, a signed token that shows the page was loaded and how long the form took, and how often the form is used from your network, and sends only a submission that looks automated to Cloudflare's check.

Invitations and your team

When an owner or admin invites someone, they give us that person's email address, the role and, for a member, the clients the invitation allows. We use the address only to send the invitation, which is one email that links to a page where the person accepts it. An invitation expires 7 days after it was last sent. We keep it until it is accepted or withdrawn, and delete it 30 days after it expires. We store only a hash of the invitation link's secret. Everyone in an organization sees the names, email addresses and roles of the others on its team page, and the clients assigned to each member.

Your LinkedIn connection

When you connect LinkedIn, MurmurMill asks LinkedIn for permission to sign you in (openid, profile and email), which MurmurMill uses to identify the LinkedIn member, and to post on your behalf (w_member_social). We never see your LinkedIn password. We store:

  • Your LinkedIn member ID and display name.
  • The access token LinkedIn issues, and the refresh token if LinkedIn issues one. Both are encrypted in the database.
  • When the access token expires, whether the connection needs to be renewed, and when the account was disconnected, if it was.
  • Which member connected the account.
  • The IDs LinkedIn gives to files and thumbnails MurmurMill uploads for a post.

LinkedIn also returns your email address, whether LinkedIn has verified it, your first and last name and your profile picture address when you connect. MurmurMill does not save them.

Your posts

  • The text of each post, when it is scheduled, its status, how many times publishing was attempted, the reason if it failed, and the post ID LinkedIn returns once it is published.
  • For link posts, the link address and the title, description and thumbnail image taken from the linked page.
  • For image and document posts, the files you upload, with their original file name, type, size, order and the alt text you or the AI wrote. Documents also keep a title.
  • Who created each post.

Uploaded files and link thumbnails are kept privately in Laravel Object Storage. After a post is saved, MurmurMill serves its uploaded files only to signed-in members who may open that client workspace, and to our staff in a support session. While you are still composing, a preview of a file you just uploaded is served from a temporary signed web address that works for anyone who has it, for up to about an hour. Files you upload and then abandon are held in a temporary folder and removed automatically after about a day.

Brand voice

The brand voice you save: the voice description, who you are, your audience, your offer, your content topics, the phrases to avoid, and the website address you drafted it from.

The material you give MurmurMill to draft a brand voice is not saved. That material is the text of the website you point it at, your answers to its questions and up to three sample posts. It is sent to the AI provider for that one request (see below). Only the profile you review and choose to save is stored.

Billing

Each organization has a trial end date. Once an owner chooses a plan, MurmurMill also stores the Stripe customer ID, the card brand and last four digits, and the subscription's plan, status, number of profiles and end date. It records when the trial reminder was sent, when a payment fell past due, and when the organization lapsed. MurmurMill gives Stripe the organization's name and the email address of its first owner. Your full card number, billing address, phone number and tax IDs are entered at Stripe and held by Stripe, not by MurmurMill.

Your clients and the approval link

When you send a client a link to review a batch of posts, MurmurMill stores the client's name and, if you enter one, their email address, who sent the link, when it expires and whether it was withdrawn. The link's secret is stored encrypted, beside a hash used to look it up. Anyone who has the link can open it until it expires, without an account.

For each decision the client makes on the link, MurmurMill stores whether they approved the post or asked for a change, any comment they wrote, a fingerprint of the post text they saw, what happened next (for example scheduled, or not scheduled and why), the IP address and browser user agent of the client's request, and the time. MurmurMill clears the IP address and the user agent from a decision 90 days after it was made. The rest of the decision stays, as described under "How long we keep it".

Weekly plans and post plans

The themes you enter, the mix of post formats, the number of posts per week, the planned angle, format and date of each post, the status of each plan, whether a weekly plan is paused and why, how many times it has failed, and any error message when a plan could not be written.

The AI usage ledger

For every request to the AI provider MurmurMill records which organization, workspace and member it was for, what it was for (for example a draft, a rewrite, hashtags, alt text, a brand voice or a plan), the model and effort level, the number of tokens used, the cost, whether it completed, and the time. The ledger does not contain the text that was sent or returned. MurmurMill deletes each row 13 months after it was made.

Technical records

  • Every visit to MurmurMill, signed in or not, is stored as a session in the database with your IP address, browser user agent, the time of your last activity and, once you sign in, your user ID. The session also holds data such as the form-protection token, the page you were heading to and messages shown to you. That data is encrypted before it is stored; the IP address, user agent, user ID and time of last activity beside it are not. The privacy policy, the terms, the data processing addendum and the sub-processor list are the exception: opening one sets no cookie and stores no session.
  • Rate limits for sign-in attempts, AI actions and plan writing are kept in the application cache. The sign-in limit is keyed by the email address you typed and your IP address, in plain text.
  • The bot checks on forms keep keyed hashes of your network and of the email address you typed in the application cache, not the raw values, to count attempts and to recognise a token used twice. They expire within a day.
  • Signup limits are kept in the application cache too: how many signups and invitation sign-ups came from your IP address in the last hour and day (kept in plain text with the address), and how many confirmation emails were sent for an address from your IP address in the last hour (kept with a hash of the address). They expire within a day.
  • To avoid applying a notification from Stripe twice, MurmurMill keeps the ID and type of each notification it receives and the time it was handled. It holds no customer details. We delete these records after 90 days.
  • Queued background work, failed background jobs, and the application's error logs can hold identifiers and error messages from the requests that failed. Application monitoring by Laravel Nightwatch records technical data about requests, errors, database queries, queued jobs, mail and notification events and log entries, and keeps it for 90 days. Our servers and Cloudflare, which protects the site, keep technical logs such as IP addresses, to keep the site secure.

Addresses we stop emailing

Amazon tells us when an email to an address bounced for good, or when the person marked it as spam. When it does, MurmurMill keeps a SHA-256 hash of that address, whether it was a bounce or a complaint, and the time, and does not send email to that address again. The hash is not anonymous: anyone who has the address can compute it. We keep no other record of delivery results, and the address itself is not stored in this record. We keep the hash for as long as MurmurMill sends email, including after the account that owned the address is deleted, so that we do not email that address again. We remove a hash only if the owner of the address asks and has fixed the mailbox.

Client workspaces

Two kinds of information are involved, and we treat them differently.

  • Your account. Your member account, your organization, billing, sign-in and security records, the AI usage ledger, the addresses we stop emailing and the staff audit log. We are the controller of this information.
  • Client workspace data. The posts, files, brand voice, plans, connected LinkedIn accounts and approval links in each client workspace, with the client details and decisions they hold. The customer decides what goes in and why, so the customer is the controller, and we process it only to run MurmurMill for them, on their instructions. Our data processing addendum and our sub-processor list apply. We do not use client workspace data for our own purposes, and we do not sell it.

If you are a ghostwriter's client, or someone whose details are in a client workspace, please contact the ghostwriter or studio that works with you first about your information and your rights. If you contact us instead, we will pass your request on to them.

When we help you

Inside MurmurMill, our staff do not browse your clients' content. They work in a separate staff area that asks for a second sign-in code. It shows account details, such as names, email addresses, client names, statuses and dates, but not your posts, files, brand voice or approval comments, and no AI output.

To help with a problem, we may need to see MurmurMill as one of your members sees it. We do that only in a support session:

  • We log it when it starts and when it ends, with a reason and a support ticket. We do not log page by page what was viewed.
  • It lasts at most 60 minutes.
  • It is read-only. We cannot change, schedule, publish or delete anything, and AI is off.
  • When it starts, we email your organization's owners and admins. It is also listed for your owners and admins on your Team page, with the staff member's name and the reason, and they can end it there.

We keep a log of staff actions and support sessions for 400 days. It holds the staff member's name and email address, what they did, which organization and account it concerned, the reason, the ticket, the staff member's IP address and browser, and the time, and none of your content. The few things staff can do outside a support session are to resend a confirmation email, remove an address from the list of addresses we stop emailing after you have fixed the mailbox, and extend a trial by up to 14 days. Each is logged.

Separately, a small number of named operators can use our hosting and database tools to run the service. We use that access to operate and secure MurmurMill, not to read your content, except to carry out your instructions or a request for help that needs it.

How we use it

  • To run your account and publish your posts to LinkedIn at the time you chose.
  • To retry posts that fail for temporary reasons, and to email you when one cannot be published.
  • To send your clients the posts you ask them to review, schedule the ones they approve, and tell you what they decided.
  • To run your trial and subscription, and to tell you when the trial is ending, when it or a subscription has ended, and when the AI allowance is nearly or fully used.
  • To write drafts, rewrites, hashtags, alt text, brand voice profiles and weekly plans with AI when you ask for them or turn a weekly plan on.
  • To check posts and AI requests against a list of restricted words, so that content LinkedIn and our terms do not allow is not scheduled, published or written.
  • To help you when you have a problem, and to record what our staff do when they help.
  • To keep the service secure and to measure what the AI features cost.

The check is automated processing of the text of your posts, their link and document titles, their alt text, what you ask the AI to write and what the AI writes. It runs on MurmurMill's own servers, and the text is not sent anywhere for it. Nothing is stored for it beyond the reason shown on a post it refused. When it refuses something, the application log records the kind of content and the listed words it found, never your text. No one decides anything about you from it: it only stops a post or a request, and you can change the text and try again.

MurmurMill contains no advertising and no analytics tracking. We do not sell your data.

If the law where you live asks us for a legal basis, this is the one we rely on for each use.

What we do Why Basis
Run your account, connect LinkedIn, store your posts and publish them on scheduleTo provide the service you asked forContract
Write drafts, rewrites, hashtags, alt text, brand voices and plans with AITo provide the features you asked forContract
Email you when a post cannot be published, about weekly plans, the AI allowance, your trial, subscription and scheduled deletionTo provide the serviceContract
Email your client the posts you sent for review, and record what they decidedTo provide the approval feature you asked forOn your instructions, as your processor
Confirm your email address, refuse disposable addresses, check with Cloudflare Turnstile that a signup is a person, and limit signups from one connection or company domainTo keep trials and email sending for real people, and protect the service from abuseLegitimate interests (security)
Limit repeated sign-in attempts and AI actions, and keep the service secureTo protect the service and its members from abuseLegitimate interests (security)
Stop sending email to an address that bounced or complainedTo protect our email sending reputation and not to email someone who complainedLegitimate interests
Check posts and AI requests against a list of restricted wordsTo keep to LinkedIn's rules and our terms, and to protect members' accountsLegitimate interests
Keep a log of staff actions and support sessionsTo keep your data safe and show who did what when we help youLegitimate interests (security)
Record AI usage and costTo run and price the serviceLegitimate interests
Keep records of orders and paymentsTo meet tax and accounting rulesLegal obligation

Who receives your data

LinkedIn

When a post is due, MurmurMill sends LinkedIn the post text, any images with their alt text, any document with its title (or its file name if it has no title), any link address, title, description and thumbnail, and publishes it with public visibility from the account you connected. MurmurMill also exchanges tokens with LinkedIn to connect and renew your connection. What LinkedIn does with data is governed by LinkedIn's own privacy policy. You can withdraw MurmurMill's access at any time in your LinkedIn settings. Posts already published stay on LinkedIn until you remove them there.

Anthropic, our AI provider

MurmurMill uses Anthropic's Claude through Anthropic's API. When you use an AI feature, MurmurMill sends Anthropic:

  • Drafts: your topic, the tone and length you chose, any link address, title and description, any document title, the shape of post you asked for, and the angles of other posts in the same batch or the full text of an existing draft it should differ from.
  • Rewrites and hashtags: the text of your post and, for a translation, the language you chose.
  • Alt text: the image itself and the text of your post.
  • Brand voice drafts: the website address you enter and up to 20,000 characters of text taken from it, your answers to the voice questions, and up to three sample posts.
  • Weekly plans and post plans: your themes, the dates and formats of the planned posts, the first line of up to 40 of your posts scheduled for the connected LinkedIn account from the last 30 days onward, including drafts and posts still to come (each cut to 140 characters), and up to 60 angles from your recent plans.
  • Drafts, rewrites, hashtags, alt text and plans: your saved brand voice, when you have one.
  • Every request: MurmurMill's own writing instructions. Images are sent as image data.

MurmurMill does not add your name, email address or account identifiers to these requests, but the text you provide may contain them. Anthropic may answer a request with another of its models if the first is unavailable. Anthropic's handling of that data is governed by its terms and privacy policy. Anthropic does not use this data to train its models. It deletes it within 30 days, unless it must keep it longer to enforce its usage policy or because the law requires it.

Websites you point us at

When you enter a link for a post or a website for a brand voice, the MurmurMill server fetches that page, identifying itself as MurmurMillLinkPreview/1.0, and for a link also the preview image the page names, which can be on another site. It follows up to four redirects. The site's operators see requests from our server. MurmurMill refuses private and reserved internet addresses.

Cloudflare Turnstile

On the signup page, and on the log-in, invitation, confirmation and resend forms when a submission looks automated, your browser loads Cloudflare's Turnstile script from challenges.cloudflare.com, and MurmurMill sends Cloudflare the result of the check with your IP address, as described under "Signing up and confirming your email address". What Cloudflare does with that data is governed by Cloudflare's own privacy policy.

Service providers

The providers that process client workspace data, with what each does and where, are also listed on our sub-processor page.

  • Hosting, database and backups: Laravel Cloud, run by Laravel Holdings Inc., in the United States (US East, Ohio).
  • Uploaded files and link thumbnails: Laravel Object Storage, run by Laravel Holdings Inc. and built on Cloudflare R2, which stores them privately. The provider chooses the location automatically, so it is not limited to one region.
  • Network protection and delivery, and the Turnstile check on the signup form: Cloudflare, Inc., which sits in front of MurmurMill on its global network. It handles technical request data such as IP addresses, and the content of requests while they pass through, and for Turnstile the check's token and signals about your browser.
  • Application monitoring: Laravel Nightwatch, also run by Laravel Holdings Inc., in the United States (US East, Ohio).
  • Email delivery: Amazon Web Services. Amazon Simple Email Service sends our email, and Amazon Simple Notification Service tells us about delivery results and bounces. The content and recipient addresses of an email pass through Amazon Web Services while it is delivered.
  • Payments: Stripe, which receives the organization's name and its first owner's email address from MurmurMill, and the name, billing address, phone number, tax IDs and card details you enter at Stripe's checkout and billing portal. Stripe keeps its customer and invoice records as the record of the sale.

[Not yet live: the Laravel Cloud application and MurmurMill's own Amazon SES and SNS accounts exist, but production is not live and Stripe is in test mode. Confirm that hosting, file storage, email, backups, monitoring, Cloudflare and Stripe are set up as described before publishing]

Advisers, authorities and a new owner

We share information with advisers, such as accountants and lawyers, and with tax or law-enforcement authorities where the law requires it. If MurmurMill is sold or merged, your information passes to the new owner, who stays bound by this policy, and we tell you before it does.

Email we send

MurmurMill sends these emails, and no marketing email.

  • A post did not go out. Sent to the member who created the post, or to the owners and admins of the organization if no creator is recorded or the creator no longer has access to the client. It has the first 140 characters of the post, the reason it failed, which can include text returned by LinkedIn, and a link to MurmurMill.
  • Weekly plans. Sent to the member a weekly plan belongs to, or to the owners and admins of the organization if that member no longer has access to the client: one email when next week's drafts are ready, naming the clients they are for; one when a week could not be planned after three tries, with the last error; and one when a weekly plan is paused because two weeks of drafts were not reviewed.
  • Posts for a client to review. When a member sends a client the approval link, MurmurMill emails the client at the address the member entered. It comes from the member's name "via MurmurMill", replies go to the member's email address, and it has the client's first name, the number of posts and their dates, the link and when it expires.
  • A client's review. When a client approves posts or asks for changes, the member who sent the link is emailed what the client decided on each post and any comments, or the owners and admins of the organization if that member no longer has access to the client.
  • Changes to how you sign in. Sent to your address when you turn an authenticator app on or off, add or remove a passkey, or change your password, and to your old address when you change your email address, with a line saying how to reach us if it was not you. Changing your email address also sends a confirmation link to the new address.
  • Confirming your email address. Sent when you sign up, to the address you gave, from "MurmurMill" with the subject "Confirm your email to start your MurmurMill trial". It has a link that works once and for 24 hours, and you can ask for it again on the page that follows signup, up to 3 times an hour. If you did not sign up, ignore it: nothing is created until the link is used.
  • Your team. An invitation, sent to the address an owner or admin enters, with the inviter's name, the organization, the role and the date the invitation expires. An email to a person whose role was changed, and one to a person who was removed from an organization. An email to the owners when a member leaves.
  • A support session. Sent to the owners and admins when one of our staff starts a support session on your organization, with the staff member's name, the reason, how long it lasts and a link to the Team page, where it can be ended.
  • The AI allowance. Sent to the owners and admins when the organization has used most of the month's AI actions, and again when it has used all of them.
  • The trial and subscription. Sent to the owners and admins three days before a trial ends, with the number of scheduled posts that will move to drafts, and when a trial or subscription ends and scheduling is paused.

If an address is one we have stopped emailing, the email is not sent. If an email cannot be sent, the failure is recorded in our error logs and nothing else is sent. Stripe sends its own emails about receipts, failed payments, cards that need extra verification and expiring cards.

The owners are also emailed 30 days after a lapse, with the date the organization will be deleted and that paying cancels the deletion, and a second time 7 days before that date. Each of these is sent once.

Cookies and sessions

MurmurMill sets only the cookies it needs to work.

  • Session cookie (murmurmill-session): keeps you signed in. It holds a random ID and the record it points to is stored in our database. A session ends after 120 minutes without activity. The cookie is hidden from page scripts, is sent only over encrypted connections, and is withheld from forms and background requests started by other sites.
  • Request protection cookie (XSRF-TOKEN): protects forms and actions against forged requests.
  • Referral cookie (murmurmill-referral): set only if you open a MurmurMill referral link (/r/ and a code). It holds the referral code of the organization that shared the link, and nothing about you. It lasts 30 days, or until you sign up, and is used only to record at sign-up which organization referred you (the code is then kept with your signup until you confirm your email address), so that both organizations can receive the referral credit described in the terms. The cookie is hidden from page scripts and is withheld from forms and background requests started by other sites.
  • Cloudflare security cookie: set by Cloudflare to protect the site from automated traffic.
  • Remember-me cookie: set only if you tick "remember me" when you log in. It keeps you signed in for about 400 days.

MurmurMill sets no analytics or advertising cookies, and at the time of writing it loads no third-party fonts or trackers. It loads one third-party script: Cloudflare's Turnstile, on the signup page and, when a submission looks automated, on the log-in, invitation, confirmation and resend forms. Another exception: when you paste a link into the post composer, your browser loads that page's preview image directly from the page's own site, which can see your IP address.

Where your data lives

Your details are stored in a database hosted by Laravel Cloud in the United States (US East, Ohio). Email is sent through Amazon Simple Email Service in the US East (Ohio) region, and delivery and bounce events come back to us through Amazon's notification service. Uploaded files and link thumbnails are kept in Laravel Object Storage, whose location is chosen automatically by the provider and is not limited to one region. Data we send to LinkedIn and Anthropic is processed on their systems, in the United States and in other countries where they or their providers operate.

If you are in the UK or the European Economic Area

We are based in the United States, and the information we hold is stored and processed there. If you are in the UK or the European Economic Area, that means your information is sent outside your country. UK and EU law allows this when there is a safeguard in place. For our hosting and email providers we rely on safeguards the law accepts, such as the standard contractual clauses that they include in their data processing agreements with us, and we choose providers that offer them. Anthropic is covered by the standard contractual clauses in its data processing terms. LinkedIn receives your posts as a separate controller, under your own agreement with LinkedIn, and is responsible for the safeguards that apply to them. If you would like to know more about the safeguards that apply to your information, or to see a copy of them, contact us at privacy@murmurmill.com.

If you are a California resident

This section describes our practices under the California Consumer Privacy Act (CCPA). It covers the personal information we collect about visitors, members and buyers. It does not cover client workspace data: for that we are the customer's service provider, and the customer is responsible for requests about it (see "Client workspaces" above and our data processing addendum).

What we collect, and why. In the last 12 months we collected the following categories of personal information, from you, from LinkedIn when you connect an account, from Stripe when you pay, and from your use of MurmurMill, for the purposes in "How we use it" above:

Category Examples
IdentifiersName, email address, IP address, LinkedIn member ID and display name, account identifiers
Commercial informationPlan, subscription and payment records (Stripe holds the card details, not us)
Internet or network activitySessions, browser user agent, sign-in rate limits, request logs
Professional informationPosts, brand voice, plans and the files you upload
Sensitive personal informationYour account log-in (email address and a hashed password, and if you set them up, an authenticator secret and the public keys of your passkeys) and your LinkedIn tokens. We use them only to sign you in and to publish for you

Who we disclose it to. We disclose personal information for business purposes to LinkedIn and Anthropic as described above, to the service providers listed in "Service providers", to Stripe for payment, and to advisers and authorities where the law requires it.

We do not sell or share your personal information. We have not sold or shared (for cross-context behavioral advertising) any personal information in the last 12 months, and we do not knowingly sell or share the personal information of anyone under 16. We do not use or disclose sensitive personal information for any purpose that California law lets you limit. We use no advertising or analytics cookies and do not track you across other sites, so a "Do Not Track" or Global Privacy Control signal has nothing to change.

Your rights. You have the right to know what personal information we collect, use and disclose, to receive a copy of it, to have it deleted or corrected, and not to be treated differently for using these rights. To use them, email privacy@murmurmill.com. We will ask you to confirm the request from the email address on the account, so that we do not give your information to someone else, and we will answer within 45 days (we will tell you if we need more time, up to 45 more). You may use an authorized agent: they will need your written permission, and we may check it with you. "How long we keep it" below lists how long we keep each kind of information. California's "Shine the Light" law lets you ask which categories of personal information we disclosed to third parties for their direct marketing: we do not make such disclosures.

How long we keep it

MurmurMill deletes your posts, files, brand voice and plans only when you delete them, when you ask us to delete your organization, or when an organization stays unpaid, as described below. The AI usage ledger is deleted 13 months after each row was made, and loses the identifiers that point to you if the organization is deleted sooner. Expired sessions and expired entries in the application cache are cleared out of the database periodically, and abandoned temporary uploads are removed after about a day.

  • Account, client workspaces, posts, uploaded files, plans, approval links with the clients' decisions, and brand voice: kept while the organization is active and until it is deleted, as described below.
  • Signups whose email address was never confirmed: deleted 7 days after the signup.
  • The web address of a deleted organization: held for 90 days, then released.
  • Invitations: until they are accepted or withdrawn, and deleted 30 days after they expire.
  • AI usage ledger: each row is deleted 13 months after it was made. When an organization is deleted its rows stay until then, with the organization, workspace and user identifiers removed.
  • The IP address and browser user agent of a client's approval decision: cleared 90 days after the decision. The decision itself stays with the approval link.
  • Stripe notification records (the ID and type of each notification MurmurMill has handled): deleted after 90 days.
  • Rate-limit counters and other entries in the application cache: they expire within a day, and expired entries are deleted from the database every day.
  • Hashes of addresses that bounced or complained: for as long as MurmurMill sends email, including after the account is deleted, unless we remove one at the address owner's request.
  • Stripe customer and invoice records: kept by Stripe as the record of the sale.
  • The staff audit log (staff actions and support sessions): 400 days, including after the organization is deleted.
  • The support sessions listed on your Team page: while the organization exists, and deleted with it.
  • Application monitoring data (Laravel Nightwatch): 90 days.
  • Failed-job records: 7 days, then they are deleted automatically.
  • The application's own logs, held by Laravel Cloud: [1, 7 or 30 days, set by the Laravel Cloud plan MurmurMill is on]
  • Database backups: kept for 7 days, so deleted data leaves them within 7 days after an organization is deleted.

When an organization lapses

An organization that has not paid will be deleted on a fixed schedule. This covers a trial that ends without a plan and a subscription that is cancelled, including one Stripe cancels after a card fails every retry. Stripe retries a failed card for up to 2 weeks, and MurmurMill works in full during that time.

  • Day 0: the organization becomes read-only. It can read everything but cannot schedule posts, use AI or connect profiles, and posts that were scheduled move back to drafts.
  • Day 30: a deletion date 30 days later is set, and every owner is emailed the date and that paying cancels it. A second email goes 7 days before that date.
  • Day 60: the organization is deleted, with its workspaces, connected LinkedIn accounts and tokens, posts, uploaded files, plans, approval links and the clients' decisions, brand voice and sessions, and the accounts of members who belong to no other organization, with their passkeys and authenticator secrets. A member who also belongs to another organization keeps their account.

Paying at any point before day 60 cancels the deletion, and the date is cleared. The deletion runs once a day, so it happens on or shortly after the date in the emails. Payments are never refunded.

Deleting your data

In MurmurMill you can:

  • Delete a post that is a draft, scheduled or failed. This also deletes its uploaded files and link thumbnail from storage. A post that is already published cannot be deleted in MurmurMill. Deleting a failed post here does not remove it from LinkedIn if it did reach LinkedIn, and anything already uploaded to LinkedIn stays there.
  • Replace your brand voice by saving a new one.
  • Change your name, time zone, email address and password on your account page, turn off the authenticator app, and remove a passkey. Removing a passkey deletes its stored public key, and turning off the authenticator app deletes the secret key and the recovery codes.
  • Disconnect a client's LinkedIn account in that client's settings. This deletes its stored tokens, moves its scheduled posts back to drafts and pauses its weekly plan. The member ID, display name and posts stay, so the account can be connected again. You can also remove MurmurMill's access in your LinkedIn settings.
  • Reconnect the same LinkedIn account, which replaces its stored tokens.
  • Withdraw an approval link before it expires, so the client can no longer open it.

MurmurMill does not yet let you delete your account from inside the app. To have your account and everything stored under it deleted, email privacy@murmurmill.com. We will do this, and confirm in writing what we deleted and what we kept, within one month. We delete the whole organization with one action, the same one the schedule above uses. It removes the organization, its workspaces, connected LinkedIn accounts and tokens, posts, uploaded files, plans, approval links and the clients' decisions, brand voice and sessions, and the accounts of members who belong to no other organization. A member who also belongs to another organization keeps their account. The AI usage ledger rows for it stay for up to 13 months after they were made, with the organization, workspace and user identifiers removed. The hash of an address that bounced or complained stays too, and so do the staff audit log entries, for up to 400 days. Stripe keeps its customer and invoice records as the record of the sale, and database backups age out within 7 days afterwards.

Your rights

Depending on where you live, you may have the right to see the information we hold about you, correct it, delete it, restrict or object to how we use it, receive it in a portable form, and withdraw consent you have given. You can also complain to your data protection authority. To use any of these rights, email privacy@murmurmill.com. We will answer within one month.

Security

  • Connections to MurmurMill are encrypted, and the session cookie is sent only over them.
  • Passwords are hashed, not stored.
  • You can add a second sign-in step with an authenticator app or sign in with passkeys. Authenticator secrets are encrypted in the database, recovery codes are stored hashed, and each code or recovery code works once. Changing your password signs out your other browsers.
  • LinkedIn tokens, session data and approval-link secrets are encrypted in the database.
  • Approval-link secrets are masked in our application monitoring.
  • Saved uploaded files are served only to signed-in members with access to that client workspace, and to staff in a support session.
  • Sign-in attempts, signups, confirmation emails and AI actions are rate limited.
  • The database is backed up and backups are kept for 7 days.
  • Our staff area needs a second sign-in factor, and inside the app, staff see your content only in a logged, read-only support session.
  • Access to the servers and the database is limited to the people who run MurmurMill.

No system is perfectly secure.

Children

MurmurMill is for professionals and is not directed at children. You must be at least 18 to use it, and we do not knowingly collect information from anyone younger.

Changes to this policy

We will post changes on this page and update the date at the top. Before a material change takes effect, we email the owners of every organization at least 30 days ahead.

Contact

CaskStack, LLC, doing business as MurmurMill, 101 Cooper Street, Santa Cruz, CA 95060, United States, privacy@murmurmill.com