Plainsmith
Websites Trades Tools Owner’s Side Pricing Get started Sign in
What we hold, and what we do with it

Privacy Policy

Last updated November 14, 2026 · Plainsmith LLC is a Colorado limited liability company.

What we collect, and why

  • Your questionnaire. Business details, services, contact info, and the answers you give in our forms. It is the material we build the website from.
  • Saved drafts. Once you enter your email in the questionnaire, your progress saves to our server as you type, so you can finish on another device. This is on by default and explained beside the field. A server draft stays until you submit or 30 days pass without a saved change. After 48 hours without a change, we attempt one reminder for an unfinished draft.

    Choose browser-only saving to keep further draft changes on that device. The switch needs browser storage to remember your choice; if storage is blocked, server saving may continue. Switching doesn’t remove an earlier server draft or cancel its reminder. Submitting the questionnaire or asking for a save-by-email link still sends your answers to us.

  • Photos and logos you upload. Stored so we can put them on your site.
  • Support history. We keep your support messages and our replies under the retention policy below.
  • Domain searches, which go to the public registry. The names you type into our domain checker are sent to public registry servers (RDAP) to check availability. We cache the answer for an hour.
  • Your customer and job records. We store the contacts, conversations, appointments, quotes, invoices and other job records you keep in the Console, along with their documents, photos and signature records. You can view and export them during service, and after it under the retention policy below.
  • What happens on the call itself. The greeting identifies the automated assistant before it asks anything. During the interactive conversation, Twilio turns the caller’s spoken answers into text, which we keep in the customer’s record. We don’t record that whole conversation. We store generated audio clips of the assistant’s speech for later playback. The text goes through a language model on Cloudflare’s network to identify the request. ElevenLabs generates the assistant’s voice. If ElevenLabs fails, a speech model on Cloudflare’s network does. A line that hasn’t been recorded yet is spoken live by Twilio’s built-in voice.
  • If they leave a voicemail instead. They hear a beep and record a message. That recording lands in Plainsmith’s Twilio account. We fetch it to turn it into text on Cloudflare’s network and send you the words. If transcription fails, we provide the recording link.
  • Payments go to Stripe. You enter your card details in Stripe’s hosted checkout. Plainsmith receives the payment status and receipt details. Keep card numbers out of forms, support messages and uploaded files.
  • Visits to the sites we host for you. We record the page viewed, referring site, city and country so the owner can see traffic in their account. Cloudflare supplies the location information. For each site’s daily visitor count, we hash the IP address and browser description with the date and site. That counting identifier changes each day. IP addresses also appear in abuse-control logs; scheduled cleanup removes entries older than seven days. When a signed-in account visits, we classify the visit as an account holder’s or, if the site belongs to that account, as the owner’s own. We keep account and session records separately from these visit records.
  • Stopping the visit count. Open the site with ?nostats=1 on the end of its address to save an opt-out for that site and browser profile. ?nostats=0 turns counting back on. The setting needs browser storage; if storage is blocked, it may not take effect. Clearing site data or changing profiles can lose the setting.

What we don’t do

  • We don’t sell or rent your information to anyone.
  • We don’t run advertising trackers or third-party analytics cookies on this site.
  • The visit-counting code does not save a lasting visitor identifier in your browser. It uses a browser-stored opt-out flag; Plainsmith’s admin page also sets that flag. Account sign-in and questionnaire drafts use separate browser storage.
  • Plainsmith does not use your information or your customers’ information to train AI models.
  • Your finished site may appear in our portfolio. Tell us and it won’t.
  • We use your questionnaire to build and support your site. It passes through the services named below, and the business information you approve appears on your public site.

Whose data it is

Your customers' details are yours, not ours. We hold them to run the thing you are paying us to run, and we act on your instruction. You decide what to collect and can ask us to delete it. We process the records to run and support your service, protect it from abuse, and handle the requests or legal obligations described on this page. Once the retention policy below takes effect, we delete hosted records under its deadlines and exceptions. In the language the privacy laws use, you are the controller and we are your processor. If your insurer or a bigger customer asks for that in a signed document, email us and we will take care of it. We are two people, and no such form is drafted yet.

If somebody with a badge asks

If law enforcement or a court asks us for your data, we tell you before we hand anything over, so you can object — unless the order itself forbids us from telling you, which does happen. We do not volunteer anything, and we ask to see the order.

If the business changes hands

If Plainsmith is ever sold or merged, your data goes with it and this policy goes with it too. We would email you before that happened, and if you would sooner go than come along, your export and your deletion work exactly as they do today.

Keeping it, and what happens if we lose it

Our hosted records use encrypted Cloudflare storage and HTTPS connections. Plainsmith staff production access is limited to Jason Walls and Tadar Puakpaibool. They use it to run and support the service, follow your instructions, answer data requests and handle the legal obligations described here. When investigating a problem, we tell you about it whether you reported it or we spotted it first. If data of yours is ever reached by somebody who should not have it, or lost, we email you within 24 hours of learning something might be wrong — not 24 hours from us finishing the investigation. There is more of this on the security page.

If you called a business that uses our assistant

Email support@plainsmith.co with the number you called from and we will find what we hold from that call. You don’t need an account with anybody. We pass the request to the business you called, because the records are theirs and they may be in the middle of a job with you. We tell you we have done it. If the law requires us to act without them, we do, and we tell them. If we turn a request down you can appeal by replying, and a person answers within 45 days, wherever you are.

Our contact form and texts

When you send the form on our contact page, we keep what you entered and the date you sent it. That’s your name, email address, request and reply choice, and, if you gave them, your mobile number and the texts you agreed to. We use them to answer you. To have them deleted, email support@plainsmith.co from the address you gave us. We also keep the IP address you sent it from, to limit how many messages one connection can send.

If you checked a box agreeing to texts, we send the kinds of text that box names. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. The texting terms say more.

We don’t sell or share your mobile number, or your agreement to get texts, with third parties or affiliates for marketing or promotions.

Where it lives

Questionnaires, support records and tool records use Cloudflare databases and file storage. Payments and billing records use Stripe. Pushover delivers alerts to Plainsmith’s phones: questionnaire alerts include contact details and submitted business information; inquiry alerts can include a phone number and message excerpt. Email notifications and messages use Resend.

Calls use Twilio, on your business’s own number in Plainsmith’s Twilio account. Twilio recognizes spoken answers during the interactive conversation; Cloudflare models process that text to identify the request. Voicemail recordings are held in that account, and we use a model on Cloudflare’s network to transcribe them. ElevenLabs generates the assistant’s speech, with a Cloudflare speech model as the fallback; Twilio’s built-in voice speaks any line not yet recorded.

In the normal tool flow, Cloudflare holds a reply draft for you to review and send from your phone. Your device and mobile carrier handle that text. Where automatic sending has been configured, Twilio also handles the message.

Providers may process information outside the United States. Public site content is cached across Cloudflare’s network, and a domain search goes to the registry operator wherever it runs.

For anything about your data, email support@plainsmith.co and Jason answers it.

How long we keep it

We keep your website material, support history, website inquiries, and customer and job records while your paid service is active. Website material includes the questionnaire, photos and logos you give us. Hosting ends with paid service unless you buy out the site; the buyout terms describe the hosting period and help with moving it. The records terms explain downloads and retention.

This retention policy takes effect November 5, 2026, for accounts opened from that date. If your account was opened before then, we’ll email you at least 30 days before the policy applies to you. Until then, the earlier promise applies: when paid service ends, your Console stays open, free and read-only, with your customer and job records there to view and download, and we do not delete them.

Under this policy, you will have free, read-only access after paid service ends, with a complete archive to download from your Console. The deletion deadline will be at least 12 months after paid service ends or we email your notice, whichever is later, including for plans that have already ended. We will show that deadline in your account, email it and send reminders 30 and 7 days before it. If a required notice fails or the complete export is not ready, we will hold deletion or extend the deadline so you have the promised time to download your records. A paid restart completed before the deadline will cancel scheduled deletion. After the deadline, we will delete hosted records from our live databases, file storage and inquiry archives.

Email and phone copies

Automatic hosted-record deletion does not remove copies in Plainsmith staff email or Pushover alerts on our phones. Copies under our control are covered by the data requests and seven-day response promise under Your rights, with the same exceptions. Copies already delivered to your mailbox or devices are under your control.

Records of what you paid Plainsmith, such as our invoices, payment receipts and domain charges, are kept separately for accounting, tax, disputes and other legal obligations. These differ from the invoices and payment records you keep for your own customers in the Console. A legal hold can require records to be kept longer; we restrict their use to that obligation and review the hold before deletion resumes.

After a website buyout

Our form service still receives new inquiries and emails them to you. It doesn’t add them to a new lead history or inquiry archive in Plainsmith. Inquiry emails and staff notifications still contain what the customer sent.

Save new photos and other files from their private links within seven days of upload. A link can expire sooner when it covers files uploaded at different times. The upload date sets each file’s seven-day deadline; emailing the inquiry again doesn’t restart it. We delete those stored uploads after their deadlines and retry failed deletions.

While the form forwards, we keep its routing details, such as the website address, destination email and sender setup. You can ask us to stop forwarding and delete those details. The seven-day rule for new uploads is separate from the retention policy for your earlier account and Console records.

When the new policy deletes account records

Deleting other records does not end an unfinished hosting, domain-transfer or DNS handover promise. We keep the contact and domain details needed to finish it, with its dates and staff evidence. When we finish that work, we remove those contact and domain details and staff notes, leaving identifiers and dates to show which duty was fulfilled.

Keeping old links closed after deletion

Account deletion leaves minimal sign-in records, including the account email, account and Console identifiers, and verification records for access changes. These prevent revoked sessions or links from working again and keep a new account with the same email out of the old Console. They contain no business profile or customer and job history.

Deletion also needs a confirmation that the old access was revoked. That confirmation is removed when deletion finishes.

Older database rollback and backup copies can remain for up to 30 days after live deletion. We use them for recovery; they cannot be opened through your account. Voicemail audio is held in Plainsmith’s Twilio account, and this policy does not delete it.

Site visit records are deleted after 120 days, or 30 days for visits identified as bots. If you never become a customer, questionnaires are deleted within 12 months. Saved questionnaire drafts follow the limit described under Saved drafts above.

Your rights

Email support@plainsmith.co from the address on your account and we’ll send you a copy of what we hold about you, or correct it, delete it, or export it, your choice, within 7 days. You can ask for deletion at any time, without waiting for a retention deadline. The exceptions above for billing, legal holds, backups, unfinished service promises and minimal sign-in records still apply. If the request comes from anywhere else we will write to the account address first, because a data request nobody checks is a way to hand your customer list to a stranger. If you’re in a jurisdiction with formal privacy rights under the GDPR, the UK GDPR, the CCPA or Colorado’s own act, those requests are honored the same way.

Changes

We date changes here and email affected account owners before material changes take effect. Material changes take effect no sooner than 30 days after notice and posting.

For your businessWorkflow toolsPricingComparedCalculatorOwner’s Side
support@plainsmith.co
Plainsmith · website previews in 48 hours · workflow tools included
AboutNotesSecurityPrivacyTermsPhoto credits