Privacy policy
A plain description of what this site does, what a website preview does, and where an enquiry goes — written in plain language rather than formal legal wording.
Read this first
It matters more than anything else on the page.
What that means in practice
Apart from the 30-day limit on voicemail audio described below, nothing on this page tells you how long anything is kept, what law governs it or what rights you can enforce, because OAS has not decided those and will not invent them. This page is OAS’s current privacy policy; a future review by outside counsel may revise it, but a future revision does not make what it says today any less current.
When you contact us
What the contact form asks for, where it goes, and what happens to it.
What the form asks for
The site’s contact forms ask for the least they can and still let us have a useful conversation. What follows is everything they ask for, and a shorter form asks for fewer of them. If what they ask for changes, this list changes with it.
- Your nameSo we know who we're replying to.
- Your businessThe business the conversation is about.
- Phone and emailHow we reply. We use whichever you prefer, and a shorter form asks only for your email.
- Your website, if you have oneOptional, and a shorter form does not ask. It tells us where you start.
- What you'd like help withThe areas you select — getting found, estimates and invoices, keeping the business organized, photos and posts, a website, or not sure yet.
- What you're dealing withThe message you write. Please leave out anything sensitive; a form is not the place for it.
Where it goes first
What you send is written into OAS’s own database before anything else happens, and that record is what we mean when we say we got your message. A notification email goes to OAS afterwards; if that email fails, your message is still here and still gets read. We never tell you it arrived unless it did.
The address your connection comes from is used for a few minutes to stop the form being flooded. It is not stored with your message.
What happens to it
It reaches OAS, and we use it to reply to you and to understand what your business needs. It is not sold, rented or passed to anybody trying to sell you something else, and it is not used to advertise to you elsewhere.
Notification emails, provider records and backups are separate copies and may remain after a record is removed from the console. To request deletion, contact support@overheadautomationsolutions.com. We will review your request and explain what can be deleted and any limits affecting retained copies.
If you text OAS’s own number
OAS has a business phone number of its own. This is what happens to a text message you send to it. Sending one does not sign you up to be texted by OAS.
What we keep from each text
When OAS accepts an ordinary text — any text other than the keywords described below — it is written into OAS’s own database before any notification about it is attempted. A text that does not reach OAS, or that OAS cannot record at that moment, is not in OAS’s database unless it is later passed on again and accepted. This is everything we keep from an accepted text:
- The number you texted fromExactly as the phone network reports it. It tells us where the text came from, not who you are.
- The number it reachedOAS’s own.
- What you wroteAll of it. Please leave out anything sensitive; a text is not the place for it.
- How many attachments it carriedThe number of them, and nothing else — see below.
- When it arrivedThe time the small program OAS runs on the texting service received it — or, for a text recovered after a failed delivery, the time the texting service’s own records show — and the time OAS’s database recorded it.
- The texting service’s reference numbersFor the message and for the account that received it, so that the same text is never recorded twice.
- Which enquiry it belongs toThe one it started or joined — see below.
- What became of its notificationWhether an email about it has been sent, has failed or is still to be sent, or that none is owed — see below.
A text carries no name and no email address, so we have neither unless you write them in it.
Where it goes, and who sees it
Your first text becomes an enquiry in OAS’s internal console. A later text from the same number to the same OAS number is added to an earlier enquiry’s history only when exactly one such enquiry has not been closed — an enquiry OAS has marked as spam counts as not closed — and was started no more than 30 days before the text arrived; otherwise it starts a new enquiry. In that console, only people at OAS with an administrator account can open enquiries and read the texts in them.
We use your number and what you wrote to get back to you and to understand what your business needs; a person at OAS may call you back on that number. OAS does not answer a text by text: OAS sends no automatic reply, confirmation or follow-up to your number because you texted us. The texting service answers a STOP or HELP text; OAS has set the wording of its HELP reply to name OAS and its support contact, as described below. What you send is not sold, rented or passed to anybody trying to sell you something else, and it is not used to advertise to you elsewhere.
The email OAS gets about it
Once a text is stored, OAS attempts to send a notification email about it to the mailbox its enquiry notifications are addressed to — the same one the contact form’s notifications are addressed to. It contains the number you texted from, the OAS number it reached, everything you wrote, how many attachments came with it, the time recorded for its arrival and OAS’s own reference numbers for it, and its subject line shows the last four digits of your number and the first words of your text. Each text gets its own attempt, except one added to an enquiry OAS has marked as spam, which is kept and emailed to nobody. A failed attempt does not remove the text: if the email service is temporarily unavailable the attempt may be repeated, and if no mailbox is set up or the email service refuses the email, it is not tried again. The enquiry in OAS’s console shows, for each text, whether its email has been sent, has failed or is still to be sent. An email that is sent is not guaranteed to be delivered or read.
Pictures and other attachments
OAS does not collect attachments. If your text carries a picture, a video or any other attachment, OAS does not download it, store it, link to it or show it in its console or its emails — it records only how many there were. The attachment stays with the texting service the number runs on, so if something in a picture matters, please describe it in words.
STOP, HELP and other keywords
A text that is only STOP, HELP, START or one of the other standard keywords texting services recognize, or that the texting service itself marks as an opt-out, opt-in or help request, is not an enquiry: OAS opens no enquiry for it, adds no entry to any enquiry’s message history and sends no notification about it. OAS’s server log notes only the time, the texting service’s reference number for that message and how it was recognized as a keyword — not your number or what you wrote. The texting service keeps its own record of it, handles those keywords itself, and answers them; OAS has set the wording of its HELP reply to name OAS and its support contact.
How long texts are kept
A text is kept with the enquiry it belongs to, and nothing deletes either of them automatically. OAS has not decided how long enquiries are kept, and will not invent a time. The 30 days above decide only which enquiry a new text joins, and how far back a text that failed to reach OAS can still be recovered from the texting service’s records — nothing is deleted when they pass. The texting service keeps its own record of the messages the number receives, attachments included, under its own arrangements. Notification emails, provider records and backups are separate copies and may remain after a record is removed from the console. To request deletion, contact support@overheadautomationsolutions.com. We will review your request and explain what can be deleted and any limits affecting retained copies.
If you call OAS’s own number
When you call, a short menu lets you speak with our team or leave a voicemail.
Live calls. If you choose to speak with our team, your call is connected to a team member. OAS does not record live calls or enable transcription or AI analysis of them.
Voicemail. If you choose to leave a voicemail, or nobody is available, you hear a message explaining that your voicemail will be recorded before recording starts. You can hang up instead. If you leave a voicemail, the recording, up to two minutes long, is stored by Twilio, our telephone service provider. OAS does not currently collect transcripts of voicemail recordings, and does not use AI analysis of them. Within OAS, access to these recordings and any transcripts is restricted to authorized staff.
How long we keep voicemail audio. We delete voicemail audio after following up, and no later than 30 days after receiving it. Any transcript of a voicemail, and any correction to it, is deleted with the audio. Our team performs deletion on a set schedule; deletion is not automatic. This limit applies to voicemail audio and transcripts, not the separate call and recording metadata described below.
Call details. Twilio maintains records associated with calls, including the calling and called numbers, the time, and the duration, as part of providing its service. Call-detail and recording metadata are handled separately from voicemail audio and may remain after the audio is deleted. The OAS application is not currently collecting call details, voicemail recording references or voicemail transcripts. Details, references and transcripts collected while call ingestion was enabled may remain stored. The application does not store voicemail audio.
Questions and deletion requests. Contact support@overheadautomationsolutions.com to ask about a voicemail or request deletion. We will review your request and explain what can be deleted and any limits affecting retained copies.
If we built a preview for your business
OAS sometimes builds a personalized website preview for a contracting business before that business has agreed to anything. If you were sent one, this is what it is.
Where the information in it came from
Publicly available business information — the sort of thing a customer looking for you would find: your business name, trade, service area, listed phone number and public listing. A preview is a demonstration of what OAS could build. It is not a website that belongs to you, and it does not speak for your business: the legal pages, coverage promises and the working contact form are all switched off in a preview for exactly that reason.
It expires, and it is not indexed
A preview is a short-lived leave-behind. It is given a life of up to thirty days when it is created — seven by default — and it stops working the moment that life runs out. The expiry is checked every time the link is opened, so nothing has to run for the address to go dead. OAS can extend a preview, and can take one down. Every preview is served with instructions telling search engines not to index it, and its address is not linked from anywhere on this site.
If you would like your preview taken down before it expires, tell us and we will remove it. You do not need a reason.
What a preview records
Enough to know whether a preview was worth sending, and nothing that identifies a person:
- That the preview was openedAnd when.
- How long the tab was actually in front of youIdle time is not counted.
- Which design was being shownIf the preview offers more than one.
- When you opened the contact control, and how oftenOne record each time it is opened — not what you wrote in it.
There is no account, no sign-in and no advertising cookie. A preview keeps one random value in your browser’s tab storage so that a page refresh is not counted as a second visit; it is discarded when you close the tab and is never shared with another site. Your IP address, your browser and your location are not stored, and neither is anything you type unless you send it to us as a message.
If you do send us a message from a preview, we keep it: what you wrote, the topic you picked, the email address or phone number you gave us to reply to if you gave one, which page of the preview you were on, and when. It is stored in OAS’s database against that preview so that the people at OAS working with your business can read it and answer you, and OAS is emailed a copy. It is not joined to the visit records above.
Enquiries sent through a website we built
If you are a homeowner who contacted a contractor through a website OAS runs, your enquiry reaches OAS as well as the contractor.
Where it goes
OAS operates the websites it builds, so an enquiry from one is stored centrally by OAS on behalf of the contractor whose site you used. That contractor gets it, and uses it to answer you. OAS uses it to run and support their website.
An enquiry form asks for your name, your phone number, optionally your email, the town you are in, what you need doing and whatever you write about the job. On a larger job it also asks for the address the work is at, the type of home, a rough budget and when you want to start. No website OAS runs currently asks permission to text you about your own request, and none asks about anything promotional either.
If you are a contractor who asked us to text you
A contractor OAS works with can ask to be told about a new enquiry by text. This section covers only the mobile number they give us for those alerts; texts sent to OAS’s own number, and numbers given to be texted about a request, have sections of their own.
What we hold, and what it is used for
Two things: the mobile number they asked us to send alerts to, and the record that they agreed to those alerts — when they agreed, who recorded it, and whether it was the contractor themselves or OAS recording it for them. That number gets exactly two kinds of text: one confirmation message when the agreement is made, and one alert for each new enquiry that arrives for their business afterwards — nothing else, and nothing promotional. Message frequency varies. Message and data rates may apply. OAS does not use this number to text the contractor’s own customers; OAS does not currently offer a customer a way to opt in to text updates about their own enquiry (see “If you asked to be texted about your own request” below). The number is never shown on their website.
It is not shared, and it is never marketing
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Beyond marketing, a mobile number given for these alerts, and the agreement recorded with it, are not sold or rented to anybody for any purpose. No affiliate, advertiser, data broker or other third party receives either. The outside companies that handle the number at all are the ones OAS runs on, and whichever service carries a text; every one of them is named under “Who else handles it” on this page, and each holds it only so that OAS can use it.
Nothing else is sent to that number. There is no newsletter, no offer and no promotion — apart from the one-time opt-in confirmation, a text goes out only when an enquiry for their business arrives.
Stopping them
A contractor can stop the texts at any time by unticking the agreement on their own account page, or by replying STOP to any alert. Changing the mobile number ends the agreement too, because it was given for the number it replaces, and texts start again only once the new number has an agreement of its own. Stopping texts does not stop the enquiry being recorded, and email alerts are a separate choice on the same page.
If you asked to be texted about your own request
This is not something OAS offers today.
Not currently available
No website OAS runs currently offers to text a customer about their own request, and none offers a customer marketing texts either. Because neither is offered, no mobile number is collected for this and no agreement is asked for it.
What this site does not do
Worth stating plainly, because most sites do the opposite.
No advertising, no profiles, no selling
This site sets no advertising cookies and carries no third-party advertising or social tracking. Nothing here builds a profile of you across other websites, nothing is sold or rented, and there is no newsletter to be added to.
There is no account to make
This site is a landing page. It has no customer accounts and no dashboard, so there is no password of yours for us to hold. A contractor with a portal account is different: signing in there takes a password, and Supabase, the identity provider, handles it and stores it only as a one-way hash, never in readable form. OAS’s own application tables hold no password and no hash, only a reference to the Supabase account. Feedback sent through the contractor portal, including any screenshots attached to it, is associated with the submitting account and business and is used by OAS to review and improve its services.
Who else handles it
OAS runs on services it did not build. Every outside service OAS chooses to handle your information, configures to receive it, or hands it to is named below, and it is a short list on purpose. Those services use suppliers of their own, which this page does not undertake to list.
Hosting, and the database
This website and the websites OAS builds are hosted on Vercel, so everything you send passes through it, and OAS’s server logs are kept there. The database that holds enquiries, messages sent from a preview and customer records is Supabase. Both run in the United States. They store this information so that OAS can use it; they do not use it for their own purposes.
Getting a message to us, and where it then sits
OAS is told about a message by email. Resend is the service OAS sends that mail through today, and OAS is set up to move that job to the email service run by Amazon Web Services. OAS sends through exactly one of the two at any time, never both, and which one it sends through is a setting on OAS’s own servers rather than anything you choose or can see. From the help control on a preview, whichever one it is receives what you wrote, the phone number or email address you gave us to reply to, and the name of the business the preview was built for. From a contact form, it receives the notification that one arrived — your name, your business, how to reach you and what you wrote. From a contractor website enquiry, it receives the notification sent to that contractor and OAS — your contact details, what service you asked for and what you wrote about the job. From a booked call, it receives the notification that one was booked — your name, how to reach you, when the call is and anything you added. From a text to OAS’s own number, it receives each notification OAS attempts, as described above — your number, what you wrote and how many attachments came with it.
It then arrives in an OAS mailbox, and OAS’s mail is run by Google Workspace — so your message and your reply address sit there, the same way they would if you had emailed us directly. That is true of anything you send us by email, not only a message from a preview.
A text alert to a contractor
Where a contractor has asked to be told about a new enquiry by text, that text is sent through the messaging service run by Twilio Inc. and carried by its mobile carrier partners. It receives the contractor’s mobile number and the alert itself — the name of the business the enquiry is for, your name and phone number, the service you asked about, your town and the start of what you wrote. It also answers a STOP or HELP reply to those texts on OAS’s behalf.
A text to OAS’s own number
OAS’s business number runs on the messaging service of Twilio Inc., so a text you send it is carried by mobile carriers to Twilio, which receives it and keeps its own record of it — your number, what you wrote and any attachment. Twilio passes it on to OAS through a small program OAS runs on Twilio’s service, which forwards your number, OAS’s number, what you wrote, how many attachments there were, when the text arrived, Twilio’s reference numbers for it and, when Twilio has marked it as a keyword such as STOP, that label — and never the attachments themselves; that program’s log notes only the message’s reference number and whether OAS accepted it. Keywords such as STOP and HELP are handled by Twilio, not by OAS, and Twilio answers them; OAS has set the wording of its HELP reply to name OAS and its support contact. Twilio also carries calls to that number and stores any voicemail recording left on it, as described under “If you call OAS’s own number”.
Booking a call
You can book a call with OAS instead of writing to us. The calendar that shows you the times, takes the booking and sends you the confirmation belongs to Cal.com, a scheduling service, and what it receives is what you give it — your name, your email address, anything else its booking page asks for, and whatever you add about what you want to talk about. The call is then placed on an OAS calendar, which is a Google Calendar, so the booking and your email address sit there too.
Cal.com tells OAS you booked, and that booking is written into OAS’s own database before anybody at OAS is emailed about it — the same order everything else on this page follows. If you cancel or move the call, the calendar is the record of that; the booking OAS stored stays as a note that you got in touch.
Counting how often the forms are used
Every form here is capped, so that one script cannot flood it: so many submissions from one internet connection in ten minutes, and no more. Upstash keeps that count for OAS, and what it receives is the internet address the submission came from and nothing else — not your name, not your message, not what you said. The address is a label to count against, it is not stored next to anything you sent, and it is discarded when the ten minutes are up. Google Cloud carries OAS’s internal work queue. Queue messages identify the work and the database record; they do not contain the record’s contents. OAS runs that queue in the United States (us-west1, Oregon) today, as it is configured — not a residency guarantee: OAS makes no promise of advance notice and no legal commitment to keep it there.
Checking you are not a robot
Our forms are checked by Vercel, using a service called BotID, which Vercel runs together with Kasada. When that check runs, your IP address and some signals about your browser go to Vercel and on to Kasada so they can tell a person from an automated program. It does not ask you to identify traffic lights, it does not set an advertising cookie, and what it sends back to us is a yes or a no — not a profile of you. If the check cannot be reached, your message still goes through.
Paying OAS, for a contractor business
A contractor business that pays OAS can be billed through Stripe, the payment service OAS is set up to use. When it is, Stripe receives the name of the business, the billing email address OAS is given for it, and what it is being charged for. Card and bank details are entered on Stripe’s own pages and never reach OAS. Stripe tells OAS when a payment or a subscription changes, and OAS keeps its own record of what the business has bought. Nothing you send through this website or a contractor’s website goes to Stripe.
What is not connected
Nobody pays OAS through this website — it has no payment form and takes no money. There is no advertising network and no analytics company. What a preview records, it records into OAS’s own database rather than an outside analytics service, and the fonts are served from this site rather than from a font company. If any of that changes, this page changes with it.
How it is looked after
Access to the central database is limited to OAS. The credentials a contractor’s website uses are stored as hashes rather than as recoverable secrets. Diagnostic server logs run through a list of permitted fields, so names, phone numbers, email addresses and message text are not copied into routine failure records.
Ask us about your information
Ask what we hold, ask us to correct it, or ask us to delete it. While there is no policy to point you at, the answer comes from a person — so ask.
Talk to OAS