← NotOnRecord

Privacy Policy

Last updated: July 31, 2026

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. 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 submitted message to a specific person
• Message content after it has been delivered to the meeting chat

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 briefly in an encrypted store (AES‑256‑GCM) only until delivery succeeds, then permanently erased. This exists solely so a server restart between your payment and delivery cannot lose your paid message. It is never linked to your identity, and it is not a record of who sent what.
• 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.
• 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 no record connects a person to the message they sent. 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, participant lists, or any other data from your Teams environment.

NotOnRecord operates completely outside your organization's Microsoft tenant. Messages submitted through NotOnRecord are not stored in your organization's mailboxes and are not subject to Microsoft's eDiscovery or compliance features.

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

• Microsoft Bot Framework: Used to post messages to Teams meetings. Subject to Microsoft's privacy policy.
• Twilio: Used for SMS relay. Subject to Twilio's privacy policy. Twilio processes your phone number; we do not retain it.
• Stripe: Processes payments. Stripe retains payment records as required by law and by card-network rules. We hold no record linking a payment to a message.
• 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.
• Purchased call recordings are kept for a short window (currently 7 days) so you can review and download them, then deleted. Recordings that are never purchased are deleted within 24 hours of the call.
• We keep a one-way hashed do-not-contact list so we can permanently honor opt-outs. It contains no readable phone numbers or email addresses.

None of these are ever linked to the identity of a message sender.

Children's Privacy

NotOnRecord is not directed at children under 13. We do not knowingly collect information from children.

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.