Privacy Policy

Last updated: November 14, 2026

MyMissionLetters ("we", "us", or "our") is committed to protecting the privacy of everyone who uses our service. This Privacy Policy explains what information we collect, how we use it, and your rights with respect to that information.

Account holders provide the following when signing up:

  • Your name and email address (used for login and account communication)
  • Your missionary's name and @missionary.org email address(es)
  • Your preference for emails about new features and offers

List members provide only their email address when joining an email list. List members do not create accounts and are not associated with an account holder's login credentials.

Contact and support form submissions include your name, email address, and the message you provide.

Book orders. When you order a printed book, you give us the name, address and phone number to ship it to.

Gifts. When you buy a gift, you give us the names to print on its gift certificate: who the gift is for and who it is from. If you ask us to email the gift to its recipient, you also give us their email address. We use it only to send them that email with the gift certificate, and we remove it from the gift's record once the gift is redeemed or can no longer be redeemed, or you delete your account. If they ask us not to email them again, we keep a coded form of their address, only to honor that request. We keep a record of each gift: those names, the products on it and the price paid for each, when it was bought, the version of the gift terms the buyer accepted, its gift code, and whether and when it was redeemed or refunded. When a gift is redeemed, we link its record to the missionary list it was redeemed onto. Anyone who has the gift code or certificate can see what is on it. The family who redeems a gift sees who it is from. We may tell the buyer whether a gift has been redeemed, but never anything about the family's list, missionary or letters.

Mission archive is retained to help account holders track which emails were sent and when.

When you import Facebook or Instagram posts, your download is read in your browser, and nothing from it leaves your computer except:

  • To us: the posts you choose, as your Mission Archive will keep them (their date and time, and what kind of post each is, such as a story or a reel; their words and links, with the people and the place tagged in them and an album's name; their photos; and a picture for each video, a frame from it when one can be taken; and for a post that shares a YouTube video, that video's address, so that we can fetch its picture from YouTube and keep it with the post), with each picture's file name, type, size and dimensions, and for a story the text typed on it; and a short code for every post the import offers you, so it can skip the ones already in. For most posts that code is a fingerprint of the names of its photo and video files, its links or its place, and for most Facebook posts it also holds the post's time; and, while the import runs, how far it has got (how many posts, photos and videos it will bring in and how many are in, about how long is left, and whether its page is in the background), so your other pages can say whether it is running, paused or stopped.
  • To our error tracker (Sentry), to help us fix problems: counts and reason codes (such as how many of your videos gave a picture, or how your browser opened the download and its photos, with the browser's own error text); how long the import took, how long we estimated it would take, and how long the page was in the background; the names of files, folders and fields in your download, never the words or values in them; and, when something goes wrong, the error and what the import was working on (which of your lists, the short codes of those posts, and the file names, types, sizes and dimensions of their pictures).

Our error tracker never gets what your posts say, your photos or your messages, and your messages and everything else in the download stay on your computer.

We use the information we collect to:

  • Operate and deliver the Service — routing emails from authorized email addresses to list members
  • Send transactional emails, such as welcome messages, join confirmations, and confirmations when a list member leaves a list
  • Respond to support and contact requests
  • Send emails about new features and offers — new features, improvements and promotions — to account holders, missionaries and the people whose email addresses account holders have authorized. Every such email has a one-click unsubscribe link, and account holders can turn them off or back on from their Settings page. When you unsubscribe we keep a record of that address so we do not send it these emails again unless you turn them back on.
  • Monitor for abuse and maintain the security of the Service

We do not sell, rent, or trade your personal information to third parties.

The core function of MyMissionLetters is to forward emails. When someone sends an email from an authorized email address to your broadcast address, that email — including its content, formatting, and attachments — is delivered to your list members. We do not read, analyze, or store the content of broadcast emails beyond what is necessary for delivery and logging.

When someone replies to a broadcast, the reply comes to us and we pass it along to the person who sent the broadcast, and when that person writes back, we pass their answer along the same way. Other mail to our shared broadcast address — a new message, or a reply we can't tie to one broadcast — is passed along to a missionary when we can tell which one it is for: if the writer is on exactly one list, it goes to that list's missionary. To send each message to the right person, we keep a record of who wrote to whom, how we decided, and the messages' email identifiers, for 90 days. We do not read, analyze, or store the content of these messages beyond what is necessary for delivery and logging. If we can't tell who a message is meant for, a copy goes to our support team so a person can help.

Anyone can add existing emails to a list's mission archive through the list's Save-to-Archive address (prefix save-; the list's older archive addresses still work the same way) — either by forwarding an email to it, or by including it as a recipient (typically in Bcc) when composing a new email. Either flow may include content originally sent by or to third parties who haven't directly consented to having their messages stored in our service — for example, a message a missionary received from a friend or mission leader, or an email composed for a small audience that also includes the Save-to-Archive address as a recipient. By using either flow, the person sending takes responsibility for the appropriateness of the archive entry. Owners can delete archive entries at any time from the mission archive page; deletion removes the row, the stored HTML, the source .eml, and any attachments from our storage.

We rely on the following third-party providers to operate the Service:

  • Supabase — authentication and database storage
  • SendGrid (Twilio) — outbound email delivery
  • Cloudflare — receives the emails sent to your list's addresses; stores your letters, their attachments, the photos and files you upload, and your books; and runs parts of our service
  • Stripe — payment processing
  • Lulu — prints and ships printed books; receives each book's pages and cover, and the name, address and phone number it ships to
  • Vercel — web hosting and aggregate analytics
  • Sentry — error monitoring; receives diagnostic context (which can include your account email) when an error occurs during your session, or when an import (Facebook and Instagram posts, Google Photos, or Gmail letters) sends a report of counts, reason codes and timings (the Facebook and Instagram one is described above), so we can triage and fix issues; and each time one of our pages loads, a short notice with a random session code, the version of our site and your browser's details, so we can tell how often pages load without errors. Like any service your browser connects to, Sentry also receives your IP address

These providers receive your information so they can provide their services to us. Some of them also use it for their own purposes, such as preventing fraud and abuse or improving their services, as their own terms and privacy policies allow.

If you choose to sign in with Google, Google handles your sign-in and shares your email address and basic profile details, such as your name, with us. Google also serves the fonts on a few of our pages, and we fetch the pictures for YouTube videos your letters and posts link to from YouTube, sending it only the video's address. Google does these things under its own Privacy Policy.

We retain your account information, list members, and mission archive for as long as your account is active. If you delete your account, the following are permanently removed from our database immediately (except a gift you bought, below):

  • Your account name and email address
  • Your missionary's name and email address(es)
  • All list members on every list you owned
  • All mission archive and message content
  • Your missionary's login (if your missionary set one up)

The letters, photos, files and books we store for you with Cloudflare are deleted at the same time.

Gifts you bought are not removed when you delete your account. We keep each gift's record, with your name and email address, for as long as the gift can still be redeemed, refunded or its value returned, and after that for as long as our tax and accounting records require.

List member email addresses are also removed from a list when the list member leaves the list — via the leave link included in every broadcast — or when the account holder removes them manually.

Data retained by third-party providers. Some data lives outside our database with the providers we use to deliver the Service. Except for what Cloudflare stores for us (below), we cannot delete this data on your behalf, but we minimize what flows to each provider:

  • Stripe retains payment transaction records — including the billing information you provide during checkout, payment amounts, and timestamps — for the period required by financial-records regulations (typically seven years). When you buy something, we give Stripe your account name and email address for your customer record, and an internal identifier with each charge. Stripe uses them to process your payment and to help prevent fraud. We send Stripe nothing about your letters, photos or books beyond those identifiers and the amounts.
  • SendGrid retains email delivery event logs (sent, delivered, bounced) for 30 days. After 30 days these logs are automatically purged. We do not maintain a separate contact list with SendGrid.
  • Supabase may retain authentication records briefly after an account is deleted; these are purged within Supabase's internal retention window.
  • Cloudflare stores the letters, attachments, photos, files and books we keep for you until you delete them or your account, and then they are deleted. Temporary copies made while a book is being prepared are deleted automatically within 30 days of being made. Cloudflare also processes inbound emails in transit and keeps delivery logs, including each message's sender, recipient and subject line, for a limited period (typically up to 31 days).
  • Sentry retains error events — including the affected user's account ID and email, relevant request context, and it can include their IP address — for the period defined in our Sentry plan (typically 30 to 90 days), after which events are automatically purged.

If you have questions about data held by these providers or wish to exercise rights under applicable data protection laws (such as GDPR or CCPA), please contact us and we'll help coordinate the appropriate request.

List members can leave any email list at any time by clicking the leave link included in every broadcast email. Upon leaving, the list member's email address is immediately removed from that list and they will receive no further emails from it.

We set no cookies of our own. When you sign in, your browser keeps you signed in using its local storage, not a cookie. We do not use advertising cookies or advertising trackers.

Stripe, our payment processor, runs on the pages where you sign up or pay, and on your dashboard, your account page, our customer FAQ and two Pro List pages. To help prevent fraud, Stripe sets cookies on those pages (named __stripe_mid, __stripe_sid and m), which last from 30 minutes to more than a year. It may also load hCaptcha, a bot-detection service that sets cookies of its own. Stripe and hCaptcha look at your device and at how you use the page, such as mouse movements and time spent on it. Because they work across many websites, they may collect information about your online activity over time and across other websites that use them. This happens even if you buy nothing on that visit, and is governed by Stripe's Privacy Policy and hCaptcha's Privacy Policy.

A few of our pages load fonts from Google Fonts. Google Fonts sets no cookies, but your browser sends Google your IP address, the page's address and your browser's details to fetch them.

Our site works the same way whether or not your browser sends a "Do Not Track" signal.

We use Vercel Web Analytics to understand aggregate traffic and conversion patterns on our site. It does not use cookies. When you view a page, your browser sends Vercel that page's web address, including any part after a "?" but never the part after a "#". On a few pages that part holds personal information, such as the private code in an order, cancellation, leave or unsubscribe link, and your previous email address on the page that confirms an email change. Your browser also sends the address of the site that linked you to us, if any, and when you take certain actions, such as finishing sign-up, the action's name with a few details, such as whether a promo code was used. As with every visit to our site, Vercel receives your IP address and browser details, and uses them to record your approximate location, device, operating system and browser.

Marketing attribution. When you arrive from one of our own ads or referral links, we record the campaign or referral information from the web address (for example, which ad or link you came from) in your browser's local storage — not cookies. If you later create an account or place an order, we attach that information to your record so we can measure which of our marketing efforts are working. This data stays within our own systems; we do not use an advertising pixel and we do not share it with Facebook, Google, or any ad network. It contains no information about your letters or personal messages.

Email open tracking. Emails we send — broadcasts and transactional messages alike — may include a small invisible image that lets us tell whether the message was opened. We use this only in aggregate, to monitor deliverability and maintain our sender reputation so our emails reach the inbox. You can prevent it by configuring your email program not to load remote images.

We take reasonable measures to protect your information, including encrypted storage of passwords and secure HTTPS connections. However, no transmission over the internet is completely secure, and we cannot guarantee the absolute security of your data.

The Service is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it promptly.

We may update this Privacy Policy from time to time. When we do, we will update the date at the top of this page. Continued use of the Service after changes are posted constitutes your acceptance of the updated policy.

If you have questions or concerns about this Privacy Policy or how your data is handled, please reach us through the Contact page.