Privacy Policy
Last updated: November 20, 2026
The short version: NotOnRecord is built around minimal data collection and sender privacy. We do not retain information that could connect a delivered message to its sender. All outbound messages are sent from NotOnRecord — not from the original sender's number or identity.
About This Policy
This Privacy Policy describes how NotOnRecord ("we," "us," or "our") handles information in connection with the NotOnRecord service, including our Microsoft Teams app, SMS relay, voice delivery, email delivery, and web submission interface. This is the single authoritative privacy policy for the NotOnRecord SMS messaging program operated from +1 (231) 729-2666.
Mobile Messaging Privacy
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.
Text messaging originator opt-in data and consent will not be shared with any third parties.
Phone numbers are used solely to deliver the messages you request and are never sold, rented, traded, or used for marketing. All messaging is sent directly by NotOnRecord on its own behalf as a consumer service — we do not send marketing, affiliate, or lead-generation messages for anyone. Message frequency varies by interaction (typically 1–6 messages per session). Message and data rates may apply. Reply STOP to opt out at any time, or HELP for help ([email protected]).
What We Do Not Collect
NotOnRecord is designed around the principle of minimal data collection. For anonymous messages and calls, we do not collect or store:
- Your name, email address, or any account information
- Your phone number (SMS relay strips sender identity before processing)
- Your IP address (anonymous submission paths suppress IP logging at the server level)
- Any information that could link a delivered message to a specific person (until a message paid by card is delivered, we keep its Stripe payment reference; see Stripe below)
- Message content after it has been delivered to the meeting chat
Occasion calls (a call from Santa and similar gift calls) are the exception: they are attributed by design and take the buyer's email. They are described in their own section below.
What We Process Temporarily
To operate the service, we temporarily process the following. Nothing that identifies the sender is ever written to disk or logged:
- Meeting session data: An active meeting session ID and associated Teams conversation ID, held in memory for the duration of the meeting and discarded when the session ends.
- Message content: Anonymous message text is held in memory while it is relayed or delivered, then discarded.
- Paid deliveries in flight: When you pay to send a message, the recipient address and message are held in an encrypted store (AES‑256‑GCM) only until delivery succeeds, then permanently erased: usually a few minutes, or until the time you chose for one booked for later (up to 7 days). This exists so a server restart between your payment and delivery cannot lose your paid message. Until then, for an order paid by card, the store also holds its Stripe payment reference, so the payment can be refunded if the message cannot be delivered or you cancel a booking. It holds no name, email address or IP address of yours.
- Reply threads: An email sent through notonrecord.com/send carries a private reply link, so the recipient can answer and you can read the answer with your reply code. For that, we keep the first 140 characters of your message, a masked form of the recipient's address (such as jo***@example.com) and any replies, encrypted (AES‑256‑GCM), for 7 days, then delete them. A thread holds nothing about you beyond what you wrote.
- Email read receipts: An email sent from notonrecord.com/email contains a tiny invisible image. When the recipient's email app loads it, we note that the email was opened, when, and how many times, so the sender's confirmation page can show it. This is held in memory only, for at most 6 hours, and we record nothing else about the recipient. Some email apps (Apple Mail, for example) load images automatically, so an email can show as opened when it has not been read; apps that block images never show it as opened.
- Twilio inbound data: When a message arrives via SMS, Twilio provides the sender's phone number to our server. We immediately hash the phone number (keyed HMAC) and discard the original before processing the message. The raw number is never written to disk or logged.
- Call recordings & transcripts: Every AI phone call is recorded, and every recipient is told at the start of the call that it is on a recorded line. We record every call so that you can decide whether the audio is worth buying after you have read the transcript, rather than having to guess beforehand.
What that means for retention: if you buy the recording (either up front as an add-on, or afterwards from your report), the audio is kept with your transcript for a short retention window, currently 7 days, then deleted. If you never buy it, the audio is deleted within 24 hours — automatically, whether or not you ever open your report. We do not keep call audio that nobody has purchased. The written transcript and summary are kept for the usual 7 days either way. (Occasion calls — Santa, birthday, congratulations — have their own, longer schedule; see the Occasion Calls section below.)
- Do-not-contact list: To honor opt-outs, we keep a one-way hashed record of any phone number or email that has asked not to be contacted, so we can block future messages to them. This holds no readable contact details and exists only to protect recipients.
Sender anonymity: We do not log the sender's IP address on any submission path, and once a message has been delivered, no record we keep connects a person to it. Message text is screened for abuse by a third-party content-moderation provider (content only — never your identity, IP, or phone number).
Microsoft Teams Integration
When you add NotOnRecord to a Microsoft Teams meeting, the bot receives event notifications from Microsoft's Bot Framework service. These events include a conversation ID and service URL used to post messages to the meeting chat. We do not store meeting content, except a message someone reports with the Report button (kept 30 days, see Data Retention below), and we keep no participant lists or any other data from your Teams environment.
NotOnRecord's own service runs outside your organization's Microsoft tenant, and the page or number people use to write a message is not part of Teams. The messages themselves do reach Teams: the organizer reads each one in their private chat with the NotOnRecord bot, and a message they share is posted to the meeting chat. Microsoft keeps those chats like any other Teams chat, so the message text falls under your organization's retention and eDiscovery tools. Nothing we add to a message identifies the sender.
A work laptop, a phone your employer manages, or office Wi-Fi can show your employer that you visited notonrecord.com, and when. For the strongest protection, write from your own phone on mobile data.
SMS Messaging Program
Program description: NotOnRecord is a two-way interactive private messaging relay platform. There are two distinct user roles with separate consent flows:
- Senders opt in by texting +1 (231) 729-2666 or submitting the web form at notonrecord.com/send. This first inbound contact constitutes express written consent. No outbound messages are sent to any number that has not first contacted us.
- Recipients receive a single consent request when someone sends them a message via NotOnRecord: "Someone has sent you a private message. Reply OK to receive it, or STOP to decline." The actual message is only delivered after the recipient explicitly replies OK. Recipients who reply STOP are never contacted again.
NotOnRecord is always clearly identified as the sending brand on every message. All messages are transactional and user-initiated — session menus, consent requests, delivery confirmations, payment links, and opt-in/opt-out confirmations. No marketing or promotional messages are ever sent.
Message frequency: Varies based on user interaction, typically 3–6 messages per session.
Message and data rates: Message and data rates may apply depending on your mobile carrier and plan.
Opt-out: Reply STOP at any time to unsubscribe. You will receive one confirmation and no further messages will be sent from that number.
Help: Reply HELP for assistance, or contact us at [email protected] or +1 (804) 274-9984.
Supported carriers: AT&T, Verizon, T-Mobile, Sprint, and all major US carriers. Carrier support may vary.
Phone number data: Your phone number is never stored, logged, or retained in plain text. It is used only to route session messages and is discarded after your session ends. No mobile information (including phone numbers) will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. Mobile information is not sold, rented, or traded. For more information see our SMS Terms.
Anonymous Submission Channels
SMS: Messages sent via SMS pass through Twilio's infrastructure before reaching our server. Twilio's privacy policy governs their handling of your phone number. Our server strips the sender's phone number immediately upon receipt and discards it. We do not log or store phone numbers.
Web link: Anonymous web submissions use a one-time session token. We do not use tracking cookies, fingerprinting, or any mechanism to identify web submitters. IP addresses are suppressed in our server logs for all anonymous submission paths.
Timing Obfuscation
NotOnRecord applies random timing jitter (50–500ms) to all message relay operations. This prevents timestamp correlation attacks that could theoretically link an SMS delivery time to a Teams message appearance time.
Cookies
We do not use tracking cookies. Our website may use strictly necessary cookies for session functionality only.
Third-Party Services
These providers process information on our behalf to run the service, each under its own privacy policy and terms:
- Cloudflare: Carries all traffic to and from notonrecord.com. Cloudflare terminates the encrypted (TLS) connection, so it handles every request in readable form — your IP address, the pages you visit, and what you submit in forms, such as a message and the recipient's number or email address — before passing it on to our server. Cloudflare keeps its own logs, which we do not control.
- OpenAI: Screens the text of every message for abuse before it is delivered. For AI calls, it runs the live conversation: the recipient's voice is streamed to OpenAI during the call, and OpenAI produces the AI's side of the conversation, the transcript and the summary. It also generates the standard voices for voice calls, rewrites a draft when you use the “Rephrase” option, and answers questions typed to our support assistant. Subject to OpenAI's API data policies.
- ElevenLabs: Receives message text to turn it into speech for voice calls sent through notonrecord.com/send and for the voicemail an AI call leaves. If it stands in for a plain AI call that our main calling system cannot place, it also receives that call's message, the recipient's name and any background you typed, the number called and the live call audio, and it keeps its own record of that conversation (audio and transcript) under its retention settings. Subject to ElevenLabs' privacy policy.
- Twilio: Places every phone call and carries its audio, so it receives the number being called. Calls that are recorded are recorded by Twilio; once we have stored our copy of a recording, we delete Twilio's. Twilio also receives texts sent to a Teams meeting's number, with the sender's phone number, which we do not retain. Subject to Twilio's privacy policy.
- Microsoft Bot Framework: Used to post messages to Teams meetings. Subject to Microsoft's privacy policy.
- Stripe: Processes payments. Stripe retains payment records as required by law and by card-network rules. Until a message or call paid by card has been delivered, our encrypted record of the order includes its Stripe payment reference, so the payment can be refunded if it cannot be delivered or you cancel a booking: usually for a few minutes, or until the time you chose for one booked for later (up to 7 days, or 60 for an occasion call). While that record exists, it and Stripe's records together link the payment to the message. It is deleted once the order is delivered, cancelled or refunded; encrypted backups made while it waited keep it until they are destroyed, at most 180 days later.
- Email delivery provider: Handles outbound message delivery and keeps its own mail logs, as any mail service does.
To be explicit about the limits of what we can promise: because these providers keep their own records, a party with lawful authority could seek information from them directly. What we can say is that we hold nothing that connects a payer to a delivered message — credits are purchased in advance and spent later, so no payment event occurs at the moment a message is sent.
Data Retention
We do not retain personal data from message sending. Session data is held in server memory only for the duration of an active meeting session. There are no databases of message content, no log files containing personal information from submission paths, and no backups of user data.
The few narrow exceptions, stated plainly:
- If you voluntarily join a waiting list or sign up for updates, we store the email address you gave us until you ask us to remove it. It is never linked to any message, and you can have it deleted by asking.
- Reply threads for emails sent through notonrecord.com/send (the first 140 characters of the message, a masked recipient address and any replies) are kept encrypted for 7 days, then deleted.
- Purchased AI-call recordings are kept for a short window (currently 7 days) so you can review and download them, then deleted. AI-call recordings that are never purchased are deleted within 24 hours of the call.
- A voice-message call (notonrecord.com/voice) is recorded only if you add the recording when you order it. That recording is available for 15 minutes through a single-use download link, then deleted. If you ask for the link by email, your email address is held in memory only until that email is sent.
- Occasion-call recordings you keep (Santa, birthday, congratulations) are kept for 90 days from the call together with the transcript and summary, and the encrypted booking behind them is held until the call, up to 60 days. See the Occasion Calls section.
- We keep a one-way hashed do-not-contact list so we can honor opt-outs; it contains no readable phone numbers or email addresses. Opt-outs do not expire; we lift one only when the person who uses that number or address asks us to.
- Abuse reports made with the Report button in a Teams meeting, including the reported message text, are kept for 30 days and then deleted. Everything sent through our support form, including a report about a message someone received, is kept for 90 days, with an email address only if you choose to give one for a reply. Copies of reports and requests are normally emailed to our support inbox.
Apart from occasion calls, which are attributed by design (see below), none of these are linked to a message sender's identity, except a support request in which you give us your email address.
Occasion Calls (Santa, Birthday, Congratulations)
Occasion calls — a call from Santa, a birthday call, a congratulations call — are the one part of NotOnRecord that is not anonymous. They are a gift from a named sender: the character says who arranged the call, and the buyer gives an email address (required) so we can email them about the call (a confirmation for a booked time, and afterwards the summary, the report link and any recording kept). Here is exactly what we hold for them, and for how long:
- The booking — the phone number to call, the child's first name and the few details typed about them, who arranged it, the buyer's email and the Stripe payment reference (so a cancelled or failed call can be refunded) — is stored AES‑256‑GCM encrypted until the call is placed, which may be up to 60 days ahead, and is then deleted. The buyer's email is deleted after the last email about that call has been sent.
- If you keep the recording (+$2.99 at booking, or the same price afterwards from your report), the audio, transcript and summary are kept for 90 days from the call so you can download them from your report link; if you keep it at booking, the recording is also attached to the email we send after the call when it is under 5 MB. After 90 days they are permanently deleted.
- If you do not keep the recording, the audio is deleted within 24 hours; the transcript and summary are kept for 7 days, then deleted.
- Emails go only to the buyer's address and only about that call: the booking confirmation, a reminder about 15 minutes before (for a call booked more than 20 minutes ahead), a note if the call is running late, a notice if the call is cancelled or refunded, and how the call went.
Processors for occasion calls: Cloudflare (it carries our website's traffic, including the booking form and your report page, in readable form), Twilio (phone network and recording; Twilio's copy of the recording is deleted once we store ours), OpenAI (live speech, transcription and the summary), Stripe (payment; Stripe receives no child details) and our email provider (delivery of the emails above).
You can cancel a booking free of charge at any time before the call is placed. To have a booking, a recording or a child's details deleted sooner than the schedule above, email [email protected].
Children's Privacy
NotOnRecord's website and services are not directed at children. Occasion calls such as a call from Santa are arranged and consented to by an adult: at checkout the buyer confirms “I am this child's parent or guardian (or have their permission) and I control this phone number.” That adult supplies the only information we hold about a child — a first name and the few details typed into the booking — and the character never asks a child for information during the call. Those details are deleted on the schedule in the Occasion Calls section above; to have them removed sooner, email [email protected].
Changes to This Policy
We may update this policy from time to time. Changes will be posted at this URL with an updated date. Continued use of the service after changes constitutes acceptance of the updated policy.
Contact
Questions about this policy? Contact us at [email protected] or visit notonrecord.com.