Privacy Policy

Effective October 5, 2026

This Privacy Policy explains how Lntrns LLC ("Heldearly," "we," "us") handles information when you use Heldearly (heldearly.com). Heldearly texts a person one question every few days, turns their answers into short written stories with the help of AI, and keeps those stories on a private timeline for their family.

We try to collect as little as possible and to be plain about the rest. If anything here is unclear, email us at hello@heldearly.com.

Who we are

Heldearly is operated by Lntrns LLC. We are the controller of the information described below. You can reach us any time at hello@heldearly.com.

Who this policy covers

Three kinds of people use Heldearly, and this policy covers all of them:

  • Account holders: the person who signs up on our website, pays for the subscription, and invites the others. Account holders sign in with a code we text to their phone. Accounts created with an email address can still sign in with a code we email them.
  • Storytellers: the people we text questions to. A storyteller has no web account. They take part only by text message, starting with a first text they send us from their invitation.
  • Viewers: family members an account holder adds by phone number so they can read a storyteller's timeline. Viewers sign in with a code we text them.

An account holder can also be their own storyteller. This policy also covers anyone who visits heldearly.com.

Information we collect

We collect only what we need to run the service:

  • From account holders: your mobile number, email address, name, and birthday (we use it to confirm you're an adult), your language and time zone, and your billing details. Payments are handled by Stripe, and we never see or store your full card number.
  • About the people account holders invite: the details you give us about each storyteller, such as their name, how they're related to you, their birthday, and any other details you choose to add, and the name and phone number of each viewer you add.
  • From storytellers: your phone number, which we receive when you send your first text, and everything you send us after that: messages, voice notes (and their transcripts), photos, and videos. We also keep the times and days you'd like questions to arrive.
  • From viewers: a record of each time you sign in, including the IP address and browser you used.
  • Created from what storytellers share: the stories we write, illustrations of objects that come up in them, and a private map of the people, places, dates, objects, and themes in the answers, which we use to ask better questions and write the stories.
  • Collected automatically: technical information when you use the website, such as your IP address, browser, and device, the pages you visit and the buttons you use, and recordings of website sessions. See "Who we share it with" and "Cookies and similar technologies" below.

How Heldearly works

An account holder signs up and invites a storyteller with a personal invitation link. Nothing is sent to the storyteller until they open the invitation and send us the first text themselves. We never text anyone first. Sending that text is how a storyteller agrees to take part.

After that, we text the storyteller a question every few days. AI helps us understand each reply and choose what to ask next. When there's enough for a story, AI writes a draft, and a person on our team reviews it before it's published to the storyteller's timeline.

The timeline shows published stories, the photos a storyteller sent with them, and illustrations we create. It never shows the text conversation itself.

How we use your information

We use your information to:

  • Provide the service: send questions, understand replies, write and publish stories, and show each timeline to the people allowed to see it.
  • Send the messages and email that come with the service, such as sign-in codes, billing notices, a note when the first story is ready, and a heads-up to the account holder when a storyteller asks about billing or stops replying.
  • Process subscriptions and payments through Stripe. A subscription is monthly or annual.
  • Keep people safe. If a message suggests someone may be in crisis, we reply with information about free support lines and alert our team.
  • Provide support, keep the service secure, fix problems, and understand how it is used so we can improve it.
  • Measure visits to the website, including which ads bring people here.
  • Comply with the law and enforce our Terms.

We do not use storytellers' answers or stories to advertise to anyone, and we do not sell personal information.

Who can see what

  • Storytellers see their own conversation with us in iMessage.
  • Account holders see the timeline of each storyteller they invited, the details they entered, and whether each storyteller has started. They don't see the text conversation.
  • Viewers see the timeline of each storyteller they've been added to, and nothing else.
  • Our team can see conversations, stories, and account details. We look at them to review stories before they're published, keep people safe, answer support requests, and fix problems, and only people who need that access have it.

An account holder can remove a viewer at any time. The viewer loses access the next time they load the page.

How AI is involved

We use AI to choose questions and follow-ups, understand what a reply is asking for (for example, a request to pause), pull out the people, places, dates, and objects in an answer, transcribe voice notes, decide which object in a story to illustrate, draw that illustration, and write each story's first draft.

To do this, the relevant messages, transcripts, and story drafts are sent to the AI providers listed below, which process them to return a result to us. We don't use anyone's content to train AI models of our own, and a person reviews every story before anyone else can read it.

Who we share it with

We share information only with service providers that help us run Heldearly, and only as much as they need to do their job. We do not sell your personal information.

Our current service providers are:

ProviderPurposeData shared
StripePayments and subscriptionsAccount holder's name, phone number, the email they enter for receipts, and payment details. When we have them, also Meta's cookie IDs, the browser's user agent, IP address, and the page address from that visit. Campaign tags (such as utm) are not stored on the payment.
LinqSending and receiving text messages (iMessage and SMS)Storyteller's phone number and everything sent in the conversation, including photos, voice notes, and videos
ResendEmail deliveryAccount holder's email address and name, and the emails we send them
PreludeTexting sign-in codes to account holders and viewersAccount holder's and viewer's phone numbers
VercelWebsite hosting, and routing our requests to AI providers (AI Gateway)Technical and request data, and the content we send to AI providers
Anthropic (via Vercel AI Gateway)Choosing questions, understanding replies, and writing follow-ups and storiesStoryteller's messages and transcripts, story drafts, and details from earlier answers
Google (via Vercel AI Gateway)Pulling people, places, dates, and objects out of answersStoryteller's messages and transcripts
OpenAI (via Vercel AI Gateway)Drawing illustrations of objects from storiesThe object's name and a short line from the story, so we can draw the picture
TypeSafeChoosing which object in a story to illustrate, when this service is configuredThe story's title, draft, and object names. If it isn't configured, we choose from the title ourselves and send nothing.
GroqTranscribing voice notesVoice note audio
CloudflareStoring photos, voice notes, videos, and illustrationsThe photos, voice notes, and videos storytellers send, and the illustrations we create
SupabaseDatabase hostingAccount, conversation, and story data
InngestRunning background steps, such as handling each incoming messageAccount IDs and message content
SentryError monitoringTechnical diagnostics, with phone numbers masked
SlackAlerts to our teamSafety and system alerts, which can include a storyteller's name, a masked phone number, and a short excerpt of a message
PostHogProduct analytics and session recordingsPages visited and buttons used, browser and device data, an account holder's email and name, a viewer's account ID, and recordings of website sessions. Recordings hide anything typed into a form. On pages that show stories, names, or contact details they also hide those details and all images; on sign-up and onboarding, only our own headings, instructions, and error messages are visible.
MetaAdvertising measurement (Meta Pixel and Conversions API). The pixel runs on heldearly.com, but never on invitation, timeline, or dashboard pagesPages visited on heldearly.com, which sign-up steps were reached, browser and device data, IP address, and Meta's cookie IDs. A scrambled browser identifier, so events from the same browser can be matched before an account exists. For account holders, a scrambled account ID, a scrambled email when we have a real address, and a scrambled phone number when we have one. Names and birthdays are not sent. For a new subscription or an added storyteller, the amount charged. Renewals are not sent.
FathomCounting website visitsPages visited and browser data, without cookies or personal identifiers

We may also disclose information if required by law, to protect someone's safety, or in connection with a merger, acquisition, or sale of assets.

Cookies and similar technologies

We use a few cookies and similar browser storage. Some are needed for the site to work, and the rest are for analytics and advertising:

NameWhat it's forType
heldearly_payer_sessionKeeps account holders signed inCookie, required
heldearly_viewer_sessionKeeps viewers signed inCookie, required
heldearly:onboarding-scene:v1Saves your sign-up answers in this browser so you can pick up where you left off. It never holds your sign-in code.Browser storage, cleared when you finish
ph_…_posthogPostHog analytics: recognizes repeat visits from the same browserCookie and browser storage, analytics
_fbp, _fbcMeta advertising measurement. _fbc is only set when you arrive from a Meta ad.Cookie, advertising
he_fbc, he_fbclidRemembers the Meta ad click so later sign-up steps can still be tied to it.Cookie, advertising
he_meta_eidA random browser identifier for Meta advertising measurement. It is not your name, email, or phone number.Cookie, advertising
he_meta_firedStops us from reporting the same sign-up or purchase to Meta twiceBrowser storage, advertising
he_meta_stepsStops us from reporting the same sign-up step to Meta twiceBrowser storage, advertising

Fathom doesn't use cookies. Stripe sets its own cookies on its checkout pages to prevent fraud.

You can block or delete cookies in your browser settings. Blocking the required ones will sign you out.

Advertising and how to opt out

We use Meta's tools to measure which ads bring people to Heldearly, how far through sign-up they get, and whether that leads to a purchase. The Meta pixel never runs on invitation, timeline, or dashboard pages. Meta may combine this with other information it has about you, under its own privacy policy.

You can limit this tracking:

  • Use your browser's tracking protection or a tracker blocker. Most of them block both Meta's pixel and PostHog.
  • Control how Meta uses this information for ads in your Facebook or Instagram settings, at facebook.com/adpreferences.
  • Opt out of interest-based ads from many companies at optout.aboutads.info (US) or youronlinechoices.eu (Europe).

How long we keep it

We keep information while the account it belongs to is active.

An account holder can delete their account from the dashboard. The deletion happens 7 days after the request, and it can be canceled until then. At that point we cancel the subscription and permanently delete the account, its storytellers, their conversations, stories, photos, voice notes, and videos, and any viewer who can't see another timeline.

An account holder can also permanently remove a single storyteller at any time, which deletes that storyteller's data right away. Archiving a storyteller instead keeps their timeline and can be undone.

We keep a short record of each deletion (such as the account holder's email address and name, masked phone numbers, and payment IDs) so we can show it happened, and we keep payment and tax records for as long as the law requires. Copies in backups and logs expire on their normal schedules.

Your choices and rights

You can:

  • As an account holder: update your payment details or cancel from Manage billing on your dashboard, remove viewers and storytellers, and delete your account.
  • As a storyteller: text STOP at any time and we'll stop sending you messages, and text START to begin again. For a shorter break, text something like "pause for two weeks", and text RESUME to come back early. To have what you've shared deleted, tell us in the conversation or by email, and a person on our team will follow up.
  • As a viewer: ask the account holder to remove you, or email us.
  • Anyone: email hello@heldearly.com to see, correct, delete, or get a copy of your information. We may need to confirm it's you before we act.

Depending on where you live, you may have other rights, such as objecting to how we use your information or complaining to a data protection authority. We won't treat you differently for using any of them.

Security

We protect information with encryption in transit, access controls, and one-time sign-in codes instead of passwords. We check every visit to a timeline against the person signed in, and we mask phone numbers in our logs.

Invitation links are personal. Anyone who opens one can send the first text and start the conversation, so share it only with the person it's for.

No method of transmission or storage is ever completely secure, so we cannot guarantee absolute security.

Where we process information

Heldearly is based in the United States, and most of our service providers process information there. If you use Heldearly from somewhere else, your information is transferred to and processed in the United States.

Children

Heldearly is not for children under 13. Account holders and storytellers must be 18 or older, which is why we ask for birthdays. Viewers must be at least 13, and an account holder may add a viewer under 18 only with permission from the viewer's parent or guardian. We do not knowingly collect information from children under 13. If you believe a child under 13 has been added, contact us and we will delete their information.

Changes to this policy

We may update this policy from time to time. When we do, we will revise the date at the top of this page and, for significant changes, let you know directly.

Contact us

Questions about your privacy? Email hello@heldearly.com. Heldearly is operated by Lntrns LLC.