Privacy

Who runs this

Hold the Send is operated by Nathan Platter, personally. There is no separate company. Email nathan@holdthesend.com.

Cookies

The marketing pages run one analytics script. It counts page views, clicks and which page you came from, and sends that to the analytics provider at in.heycatch.ai. It stores a random visitor id in your browser so a return visit counts as the same visitor. It does not read message text, form fields or anything you type. There is no advertising cookie and no ad network. There is no cookie banner, because nothing here is used for advertising or sold.

We also count when a demo draft is held, a visitor uses the demo Send button, or someone clicks the booking link. Demo sends are simulations, and booking clicks are not confirmed appointments. In the signed-in desk, we count held drafts, successful copies and messages the rep marks sent. An internal account id links those events across visits; we do not send your email, invite code, customer details or draft text to analytics. Signing out clears that analytics identity. Local development and preview sites do not send analytics.

Two first-party cookies are used for the product itself:

• lb_ref. If you arrive from a partner link, the browser stores this cookie for 90 days. Checkout reads it so that partner can be credited on the order. It is not sent to an ad network.
• Desk session. After you sign in at desk.holdthesend.com with an invite code, the server sets a cookie that is HttpOnly, Secure, and SameSite=Lax. It lasts 7 days. Invite codes are stored as salted hashes. The code itself is not stored.

The desk

Before a draft goes to the AI, the desk masks these items. Phone numbers, emails, Social Security numbers, labeled dates of birth, labeled account, loan and policy numbers, and street addresses. Names are not masked.

After that mask, the draft request goes to the AI service that writes the reply. The site does not send the message. A person copies it and sends it from their own phone or CRM.

Pasted reply threads, and an activity log of drafted, flagged, copied, and marked-sent, stay in that browser. Message text stays out of the activity log. The desk can download that log. Draft requests are processed to create the reply; they are not saved as server-side conversation history.

The store floor is different: records you enter there are saved on our server for your store. These include buyer names, vehicle details, notes, appointments, handoffs, consent and opt-out records, and rep activity. People with access to that store can use its floor records. Do not enter payment-card details, government identifiers, or information your store has not authorized you to share.

Reps can file a desk request, a bug or an idea. That text is masked before it is stored. The server keeps those requests with the store's usage counts.

Payments

Card and bank payments are handled by Stripe. This site does not store card numbers. Account follow-up records keep subscription IDs, store or Solo classification, feedback dates and any quote or naming permission you explicitly provide. They do not include your pasted customer conversations. When trial reminders are activated, the customer email service receives your billing email from Stripe and the reminder text; card details stay with Stripe. A net-30 request collects a billing email, a store or company name, and a contact name. A person reviews the request, then Stripe emails the invoice.

Security log

The server keeps a security log of events such as sign-in results. It does not store message text, invite codes, cookies, or raw IP addresses. Those rows are kept for 365 days.

When a store stops

When a store stops using the desk, that store's data on our server (its desk invite records, usage counts, and desk requests, store-floor records and floor profiles) is deleted within 30 days of the stop. A store that has not stopped is left alone.

Want a copy first? Email nathan@holdthesend.com and we send that store's data as a JSON file before it is deleted.

The security log above stays for 365 days. It holds no message text, invite codes, or raw IP addresses. Threads and the activity log in a browser stay on that device until the browser clears them.

Demos

Demo pages use fictional stores and fictional shoppers.