Privacy Policy

About this policy

Wakeman is a product of Fabricate, LLC, a Delaware limited liability company. In this policy, “Wakeman”, “we”, “us” and “our” mean Fabricate, LLC.

This policy explains what information we collect when you visit wakeman.ai, when your business uses Wakeman, and when you call a business that uses Wakeman. It also explains what we do with that information, who we share it with, how long we keep it, and the choices you have.

Our contact details are at the end of this page.

Our role: businesses and their callers

Wakeman answers the phone for home-services businesses, such as plumbers, HVAC companies and electricians. That means two groups of people are involved, and our role is different for each.

Businesses that use Wakeman. For the business and the people who sign in to its account, we decide how their information is used, and we are responsible for it under this policy.

People who call those businesses. When you call a business that uses Wakeman, we process your information on behalf of that business, to answer and handle your call for it. The business decides what your call is for and how long to keep it, and we follow its instructions. If you have a question about your call, the business you called is the best place to start. You can also write to us.

Information we collect from businesses

When a business signs up and uses Wakeman, we collect:

• Account details: the names, email addresses and phone numbers of the people who sign in, and their sign-in details, which our sign-in service handles.
• Business setup: the business name, trade, services, service area, opening hours, phone numbers (including on-call and owner mobile numbers), greeting, the postal address you give for the emails we send in your name, and anything else you tell Wakeman to say or do on calls.
• Billing details: your plan, minutes used, invoices and payment history. Card details go straight to our payment processor, Stripe. We do not see or store full card numbers; we keep the card's brand and last four digits, to show you which card pays.
• What you agreed to: when you add a card for your free trial, or agree to a charge in your account, the exact words you agreed to, the plan and price, when you agreed, and the IP address and browser you used, as a record of your agreement.
• Connected software: if you connect Jobber, or a Google or Microsoft calendar, the access details needed to create and update jobs in it, and the web addresses you add to send calls and jobs to other apps, such as Zapier. For a calendar we also keep the email address of the account you connected and the name of the calendar jobs go on. We encrypt these before storing them. Unless you turn off “Know callers from Jobber”, we also keep a copy of your Jobber customers’ names, phone numbers and service addresses, how many jobs each has had, the title and date of their last job, and their next visit, so Wakeman can greet them by name when they call. We never copy prices, invoices or notes.
• Card payments: if you let your customers pay your fees by card, the ID of the Stripe account you connected, and whether Stripe has it ready to take payments and pay out. The business and bank details you give Stripe go to Stripe, not to us.
• Your Thumbtack business: if you connect Thumbtack, its name and the access details Thumbtack gives us for it, encrypted before we store them. We receive your new Thumbtack leads and the messages in their conversations, and we write only in the conversations of leads that came in after you connected. Disconnecting deletes the access details, and the conversations are yours to carry on in Thumbtack.
• Your Facebook Page: if you connect a Facebook Page, its name and the access details Facebook gives us for it, encrypted before we store them. We receive the answers people give in the Page's lead forms and, while Messenger answers are on, the messages people send the Page and our replies. We don't keep your own Facebook sign-in, and we never post to the Page. Disconnecting deletes the access details and the Messenger conversations we kept.
• Your Google Local Services ads: if you connect Google Local Services, the name, number and time zone of the Google Ads account you chose, and the access details Google gives us for it, encrypted before we store them. We read your Local Services leads and the messages in their conversations, and we write only in the conversations of message leads that came in after you connected. We never change your ads, budget or billing. Disconnecting deletes the access details and asks Google to cancel them, and the conversations are yours to carry on with Google.
• When your calendar is busy: if you connect a calendar, Wakeman reads when the entries on the calendar you chose start and end, and whether they mark you busy, so that it never offers a caller a time you already gave to something else. It also reads the names of the calendars you can add to, so you can pick one. It does not read the titles or details of your entries, and it does not keep what it reads.
• Messages to us: what you send when you email or call us.

Information we collect when someone calls a business

When Wakeman answers a call for a business, we collect:

• Call recordings: the audio of the call.
• Transcripts and summaries: a written record of what was said, and a short summary and details written by AI from it.
• What the caller tells us: usually a name, a phone number, a service address, and a description of the problem — plus the appointment or callback that was arranged.
• Call details: the number the call came from, the number it was made to, and the time and length of the call.
• Texts: whether the caller agreed to a text, the texts we send, and any replies the caller sends back, including photos.

A business can also give its customers a request page on wakeman.ai. When you send a request there, we collect the same kind of information for the business, in the same role: your name, phone number, service address, a description of the problem, and the time you picked if you picked one. We check the address with Google. We send the request to the business, and to the job software, calendar or other apps it has connected, if it has connected any. We do not text you because you sent a request, and sending one does not sign you up for texts.

A business can also add its own list of past customers: names, phone numbers, addresses, the work done and when. We hold it for the business, in the same role, and use it only to show the business its own customers and who is due for yearly work. We never contact anyone on a list; the business decides whether to text them, from its own phone. When the business removes a list, its lines are deleted.

A business can also send Wakeman the lead emails it gets, from lead sites such as Yelp or Angi or from its own website. We read each one for the business, in the same role, to text the business about the lead and add it to its list of people to call back. If the business turns on replies, we write back to you in the business’s name, through the lead site’s own messages where it has them or to the email address you gave, to ask what the business needs to book the job. Those emails say they come from an automatic assistant. Reply STOP and we stop writing. We keep that conversation for 90 days after it goes quiet, then delete it.

A business can also have us email you about a quote it gave you, if it has your email address because you emailed it or gave it the address. We send at most two short emails in the business's name, about two and ten days after the quote. Both are the same few lines for every quote, never written by AI, and never include a price. They stop as soon as you reply, call or text the business at a number Wakeman answers, or the business marks the quote won or lost, and after 45 days at the latest. They also stop if an email can't be delivered or is marked as spam. Each email has an unsubscribe link, and a reply asking us to stop works too: we stop that business's quote emails to your address for good, and keep the address on its do-not-email list so they stay stopped. Your reply comes to us, and we pass it to the business by text and by email. We keep the start of what you wrote with the quote for 90 days, then delete it.

A business can also connect its Thumbtack account. When you send it a request on Thumbtack, Thumbtack passes us what you sent the business: your name, the phone number Thumbtack gives the business for you, where the job is, and your answers to Thumbtack's questions, and we text the business about it, in the same role. If the business turns on replies, we answer you inside your Thumbtack conversation, in the business's name, to ask what it needs to book the job, and we read your answers there. Those messages say they come from an automatic assistant. Reply STOP and we stop writing. When someone at the business writes to you in Thumbtack, we stop and leave the conversation to them. We keep our copy of the conversation for 90 days after it goes quiet, then delete it.

A business can also connect its Google Local Services ads. When you message it from its ad, Google passes us what you sent the business: your name, the phone number Google gives the business for you, the kind of job, and your message, and we text the business about it, in the same role. If the business turns on replies, we answer you in your conversation with the business on Google, in the business's name, to ask what it needs to book the job, and we read your answers there. Those messages say they come from an automatic assistant. Reply STOP and we stop writing. When someone at the business writes to you on Google, or you call or book the business through Google, we stop and leave the conversation to them. We keep our copy of the conversation for 90 days after it goes quiet, then delete it.

A business registered for texting in its own name can also have our AI answer people who text it first. When you text such a business, we collect what you send — the words, any photo, your number and the time — and what the assistant writes back, for the business, in the same role. Each text you send is sent to an AI model (Anthropic, listed below) to write the answer, and the first answer says it comes from an AI. The business gets your request and every word you sent. We keep the conversation for 90 days after its last text, then delete it.

A business can also put a chat on its request page and on its own website. The chat is answered by an AI model, and says so. Each message you type is sent to that model (Anthropic, listed below) to write the reply. While you chat, the conversation is held in your browser, not stored by us. If you send your request, the chat is kept with it so the business can read it. If you don't, nothing you typed is kept; we count only how many replies the chat wrote that day.

A business can ask you for a Google review with a link on wakeman.ai. The business sends it from its own phone; we do not text it to you. Opening the link takes you straight to Google, where your review is between you and Google. We count how many times each business's link is opened each day, and nothing about who opened it. When a business asks us to write a reply to a review, we send that review's words, stars and the reviewer's name as Google shows it to our AI provider to write the reply, and we do not keep them.

A business can also let its customers pay its trip fee or after-hours fee by card. On a call, Wakeman may offer to have the business text a link to pay. If the caller says yes, we note it on the call and tell the business, which texts the link from its own phone. The link opens a page on wakeman.ai that shows the business, the fee and its amount, and sends the customer on to a payment page run by Stripe, for the business's own Stripe account. The card number is typed on Stripe's page, and we never see or store it; Wakeman never takes a card number on a call. For the business, we keep what the fee was for, the amount, the name and phone number of the customer it was for, and whether it was paid, refunded or cancelled, which Stripe tells us.

Information we collect on our website

When you visit wakeman.ai or use the Wakeman dashboard, we and the analytics companies we use collect:

• Usage information: the pages you visit, the links and buttons you press on our marketing pages, and when.
• Device information: your IP address, browser, device type and similar technical details.
• Session recordings: recordings of how pages are used, such as scrolling and clicks, to help us fix problems. Anything typed into a form is hidden from these recordings, and we mark the parts of the dashboard that show callers' details to be hidden as well.
• Error reports: technical details when something on a page breaks.

We do not run these tools on the page a caller uses to confirm their address, on a business's request page or its chat, or on the page its customers pay a fee on.

When you talk to Wakeman itself

Calls to Wakeman's own sales and support line, (775) 278-6674, are answered by our AI assistant and recorded, and conversations on our Talk to Wakeman page are answered by the same assistant and transcribed, so we can follow up on what you asked and improve how it answers. The assistant says so at the start of every conversation.

If you ask our AI assistant to call you, we keep the number you gave, the time you picked, the exact words you agreed to and when, and the page, IP address and browser you agreed from, or the recording of the call where you said yes. We use them to place the calls you asked for and to show that you asked. Those calls are recorded and transcribed like calls to our line, and what you tell the assistant goes to our team. If you tell us to stop, we stop calling, and we keep the record so the stop holds.

How we use information

We use information to:

• answer calls for businesses, take down callers' details, arrange appointments or callbacks, and send the texts callers agree to;
• try to alert a business's on-call person during a call about a possible emergency;
• show businesses their calls, and send them call summaries and alerts by email and text;
• email a business's customers about a quote it gave them, when the business turns that on;
• bill for the service and keep account records;
• call people who asked us to, about Wakeman's own service, with our AI assistant;
• answer questions and give support;
• keep the service safe, spot spam calls, and prevent fraud and misuse;
• find and fix mistakes and improve how Wakeman answers calls, including by reviewing recordings and transcripts; and
• follow the law and enforce our terms.

We do not sell personal information. We do not use callers' information for advertising, and we do not build profiles of callers across businesses. A call to one business is not visible to any other business.

AI and your calls

Wakeman uses AI to answer calls. Speech recognition turns what the caller says into text, an AI model decides what to say and what to do next, and a computer voice speaks the reply. To do this, call audio and transcripts are sent to the AI and voice companies listed below.

We do not use recordings, transcripts or texts to train AI models of our own. We may review them to find and fix mistakes and to improve how Wakeman answers.

We do not create voiceprints. Returning callers are recognised by their phone number only: from their earlier calls, or from the business’s own customer list in software it has connected.

AI can make mistakes. A summary or a detail taken from a call can be wrong, so businesses should check their calls.

Text messages

Five texts can follow a call, and they are only ever about the job that caller phoned about: a booking confirmation, a reminder the day before that booking, a link to confirm an address Wakeman could not place, a note that a request was received and the business will call back, and a follow-up when a call dropped before the job was captured. The first four are sent only when Wakeman asked the caller, out loud on that call, whether it could text them and the caller said yes. The fourth goes to the number the caller dialled from and does not wait for a yes — by then the call has already ended, and it is the only way to reach them about what they started — but it is not sent to a caller who was asked on that call and said no. The exact words, both answers, and what is recorded are published at wakeman.ai/legal/sms-consent. We do not send marketing texts, and nobody is added to a list.

Where a business has connected its own job-management software, a yes is also passed to that software, which may then text the caller about the same appointment under the business's own messaging registration. A caller who said no, or who was never asked, is marked in that software as not to be texted.

Every message names the business it comes from and says to reply STOP. STOP takes effect at the messaging platform that carries the texts, for that number, across every message that business sends. Nothing in our system sends an automatic answer to a HELP text, so a caller wanting help should write to us or call the business back. Message frequency varies and depends on what happens with the job — most callers receive one message. Message and data rates may apply. Carriers are not liable for delayed or undelivered messages.

What a caller texts back — the words, the number it came from, the time, and any photo — is passed to that business, and to no one else. Where we can tell which call a reply is about, it is stored with that call. Where we cannot, it is kept as a separate message for that business, and never attached to a call it might not be about. Nothing sends an automatic answer to a reply, except where a business registered for texting in its own name has turned on text answers: then its AI assistant answers people who text it first, in the words printed at wakeman.ai/legal/sms-consent.

A business's own people — the owner, and whoever is on call — also receive texts about their jobs, including emergency alerts. Those go to numbers the business entered in its own account.

Everything above is about texts sent for a business. Wakeman also texts, as itself, people who are setting up a Wakeman account and say yes on a call with our assistant: the link to finish signing up and, when enabled, help with setting up call forwarding. Those texts start with “Wakeman:”, come from Wakeman's own sales numbers, and are described at wakeman.ai/legal/sms-sales.

No mobile information is sold or rented to anyone. Mobile information and messaging consent are not shared with third parties or affiliates for marketing or promotional purposes. Mobile numbers and message contents go only to the carriers that deliver the message, to the business whose customer it is, and to the job-management software or calendar that business has connected, where it has connected one — subcontractors acting as our service providers, such as the messaging carrier, may receive them solely to deliver the message, and for no other purpose.

Who we share information with

The business the call was for. A caller's information goes to the business they called. It is their customer and their job.

Companies that help us run Wakeman. We use the service providers below. Each receives the information it needs to do its job for us.

• Twilio: phone numbers, connecting calls, and sending and receiving texts.
• Vapi: running the voice assistant during calls.
• OpenAI: an AI voice model that holds the conversation on some calls.
• Anthropic: an AI model that decides what Wakeman says and does, writes the answers to texts where a business has turned them on, and writes the replies to reviews a business asks for.
• AssemblyAI: speech recognition, turning speech into text.
• Cartesia: the computer voice Wakeman speaks with.
• Google: checking service addresses and finding a business's own Google listing and its reviews (Google Maps Platform), and website analytics (Google Analytics).
• Cloudflare: private storage for call recordings.
• Railway: hosting for our servers and database.
• Vercel: hosting for our website, and website traffic counts.
• Clerk: sign-in and user accounts.
• Resend: sending email, and receiving the emails that reach a business's Wakeman address, such as its lead emails and answers to its quote emails.
• Stripe: payments and billing, and the card payments a business takes from its customers (see below).
• PostHog: product analytics, session recordings and error reports for our website and dashboard.
• Meta: advertising measurement: visits to our marketing pages only if you allow it, and new accounts unless you say no (see Cookies below).
• Google Ads: measuring which Google ads lead to sign-ups, only if you allow it (see Cookies below).
• TikTok: advertising measurement: visits to our marketing pages only if you allow it, and new accounts unless you say no (see Cookies below).

Software the business connects. If a business connects its job-management software, such as Jobber, we send each booked job to it with the caller's name, phone number and service address, a summary of the call, and a link to the call recording. While the business has “Know callers from Jobber” on, we also read its customers’ names, phone numbers, service addresses, recent jobs and upcoming visits from Jobber, and keep a copy for the business, so Wakeman can greet a customer by name and tell them when the business is coming. That software is run by another company, under its own terms and privacy policy.

Thumbtack. If a business connects its Thumbtack account, the replies we write for it go into the customer's conversation on Thumbtack, which Thumbtack keeps under its own terms and privacy policy.

Facebook. If a business connects its Facebook Page, we read the answers a person gives in that Page's lead forms and pass them to the business as a lead. If the business turns on Messenger answers, our AI replies to people who message the Page, says it is an AI, and passes their name, number and request to the business. Facebook is run by Meta, under its own terms and privacy policy.

Google Local Services. If a business connects its Local Services ads, the replies we write for it go into the customer's conversation with the business on Google, which Google keeps under its own terms and privacy policy. Wakeman's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

A calendar the business connects. If a business connects its Google or Microsoft calendar instead, each booked job becomes one entry on the calendar it chose, with the caller's name, phone number and service address, the problem they described, any call-out price quoted, and a link to the call in the Wakeman dashboard, which opens only for people signed in to that business's account. No recording link is put on a calendar, and the caller is not sent an invitation. Google and Microsoft run those calendars, under their own terms and privacy policies. Wakeman's use of information received from Google APIs, and its transfer to any other app, follows the Google API Services User Data Policy, including its Limited Use requirements.

Apps the business sends calls and jobs to. If a business adds a web address on its dashboard, such as one from Zapier, we send it each call Wakeman answers for the business and each new job or request: what the caller told us, such as their name, phone number, service address and what they need, the appointment if there is one, and a summary of the call. We never send the recording or the transcript, and we send nothing about calls marked as spam. The business chooses that software. It is run by another company, under its own terms and privacy policy, and the business decides what happens to the information there.

Card payments the business takes. If a business lets its customers pay its fees by card, each payment is made to the business's own Stripe account, on a page Stripe runs. We send Stripe the amount and what it is for, and Stripe tells us whether it was paid or refunded. Stripe handles the payment for the business, under its own terms and privacy policy.

When the law requires it. We share information if we are legally required to, for example by a court order. When that involves a business's data, we tell the business unless the law forbids it.

AI assistants you connect

If an account owner or administrator enables assistant access and a user connects an AI assistant, such as ChatGPT or Claude, that assistant can read the connected business's calls, summaries, transcripts, bookings, business hours, on-call team and current usage. Depending on the request, the returned information can include callers' names, phone numbers, service addresses and what they said. We share that information with the assistant provider to answer the user's request.

The connection is read-only. It cannot contact a caller or technician, create or cancel a booking, change settings or make a payment. Sign-in and connection consent are handled by Clerk. Never give an assistant your password, a verification code or a payment card number.

An account owner or administrator can turn assistant access off in Dashboard → Integrations → Your AI assistant. This blocks further account reads by connected assistants. It does not remove information already returned to an assistant; that provider's privacy policy, retention rules and user controls apply to those copies.

We keep technical request logs to operate the connection and investigate failures, including the requested method, tool name, client software and request identifier. The request logger does not record OAuth tokens, tool arguments or returned transcripts. Turning assistant access off stops further account reads but does not erase existing technical logs; deletion requests follow the privacy rights process below.

Cookies and similar technologies

Needed to run the site. Our sign-in service uses cookies to keep you signed in to the dashboard.

Analytics, only if you say yes. PostHog, Google Analytics and Vercel use cookies, browser storage or similar tools to measure how our website and dashboard are used. They run only after you choose “Accept all” on the cookie card or turn on the Analytics switch in Cookie preferences, and you can turn them off again the same way at any time. Your answer is kept in that browser. You can also block or delete cookies in your browser settings.

Advertising measurement on our pages, only if you allow it. When this is turned on for our website, we ask your permission first. If you say yes, we tell Meta when you visit certain public marketing pages, when you click to sign up, and when an account is created after a sign-up click you allowed. We send Meta only the page's address, without any extra codes added to the end of it. We never send dashboard pages, account details, names, email addresses, phone numbers, call recordings, transcripts or callers' information this way, from your browser.

Meta receives your IP address and browser details with these requests and may recognise you through its own cookies. It may use this information for advertising, under Meta's own privacy policy.

New accounts, unless you say no. When you create an account, our server tells Meta, and it tells Meta again when your Wakeman number receives its first forwarded call. This lets Meta measure our ads and show them to businesses like yours. With each report we send your email address and phone number in scrambled (hashed) form, a random code for your account, and the time. With the sign-up report we also send the IP address and browser of the sign-up, and the ad-click code Meta added to the page address if you came from a Meta ad. We never send your business's calls, recordings, transcripts, bookings or callers' information. Meta may use this information for advertising, under Meta's own privacy policy. Our server also tells TikTok about the same two moments, with your email address and phone number in scrambled (hashed) form, a random code for your account, and the time, and nothing else. TikTok may use this information for advertising, under TikTok's own privacy policy.

You can say no before you sign up, with “Don’t share mine” under the sign-up button or with the Cookie preferences button, and at any time afterwards, with the Cookie preferences button on this page while you are signed in or by emailing us. If your browser sends a Global Privacy Control or Do Not Track signal, we treat that as no. Accounts created before 6 October 2026 are not reported.

TikTok, only if you allow it. If you say yes, TikTok's script runs on our public marketing pages. It tells TikTok which of those pages you view, with each page's full address, what you click there, and when you click to sign up. TikTok receives your IP address and browser details and sets its own cookies. Before you move on to the sign-up form, your dashboard or any other page that isn't public, we tell the script to stop, so it reports nothing about those pages. The script never gets your account details, email address, phone number or your business's calls. TikTok may use this information for advertising, under TikTok's own privacy policy.

If you arrived from a Google ad and say yes, we also tell Google Ads that you visited, including the ad-click code Google added to the page address, and later that an account was created, with the same random code we use for Meta. Google sets its own advertising cookies and may use this information under Google's own privacy policy.

You can say no, or change your answer at any time, with the Cookie preferences button on our public pages and on this page. If your browser sends a Global Privacy Control or Do Not Track signal, we keep advertising measurement off. Changing your answer stops future requests; it cannot take back requests already sent. Your choice is saved in your browser, along with a note that stops the same sign-up being reported twice. A signed cookie that lasts 30 minutes links an allowed sign-up click to the new account, and that sign-up is reported from your browser with a random code, not your account details. If you came from a Meta ad, Meta's ad-click code is kept in your browser for that visit, unless you said no. The Cookie preferences button also has the switch for the analytics above.

How long we keep information

• Call recordings, transcripts and call details: kept until the business asks us to delete them, or until we act on a verified request from a caller. We do not delete them automatically after a set time. If our records do not show that a caller heard the recording notice, we delete that call's recording and transcript.
• Copies held by call-handling companies: the companies that carry and handle calls may keep their own copies for a time set by their own rules. We keep our own copy of each recording in our private storage.
• Account and business details: kept while the account is open. When an account is closed, sign-in access ends. We delete the account's data when the business asks us to.
• Billing records: kept as long as tax and accounting rules require.
• Your permission for our AI assistant to call you: kept for as long as we may need to show that you gave it or took it back, so a stop keeps holding.
• A business’s copy of its Jobber customers: deleted as soon as the business turns “Know callers from Jobber” off or disconnects Jobber, and when we have not been able to check it with Jobber for a week.
• Card payment links: what each link was for, its amount and what became of it, kept with the business's calls on the same terms. The payments themselves are kept by Stripe, in the business's own account.
• Website analytics: kept by our analytics companies under their own settings.

Information we delete may remain in our backups until those backups are removed. We may also keep information where the law requires it, or where it is needed to settle a dispute or prevent fraud.

Your privacy rights

Depending on where you live, you may have the right to:

• know what personal information we hold about you, and get a copy of it;
• ask us to correct it;
• ask us to delete it; and
• opt out of the sale of your personal information, or its sharing for targeted advertising.

California residents have these rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act. Residents of several other states have similar rights under their own laws. We will not treat you differently for using them.

We do not sell personal information. The only sharing for advertising is the Meta, TikTok and Google Ads measurement described above. Measurement on our pages is off unless you allow it, and reports of new accounts to Meta and TikTok are on unless you say no. You can say no to both with the Cookie preferences button or by emailing us, and we honour Global Privacy Control signals.

How to make a request. Email info@wakeman.ai. We will check who you are before we act — for a business, that you are an owner or administrator of the account; for a caller, that the call is yours. You can also ask someone to make the request for you, if you give them permission. We will reply within the time the law requires.

For businesses. You can download your call log as a spreadsheet from your dashboard. While the account is active, an account owner or administrator can also download a copy of the business's records from Dashboard → Account → Export your business data; that page lists what the copy includes and leaves out. For a full copy of your data, or to close your account and delete its data, email info@wakeman.ai.

If you called a business that uses Wakeman

Your call belongs to the business you called, and we handle it for them. To see, correct or delete information from your call, contact that business. You can also email us at info@wakeman.ai. We will check that the call is yours, tell the business, and help it respond. Where the law gives you a right to have us act directly, we will.

How we protect information

• Our website and dashboard use encrypted connections (HTTPS).
• Call recordings are kept in private storage, and the dashboard shows a business only its own calls. A recording is played through a link that is not publicly listed, but anyone who has that link can play it — so keep recording links private. If a business connects job-management software, a copy of the link is added to the job's notes there.
• The access details for software or a calendar a business connects, such as Jobber or Google Calendar, and the web addresses it sends calls and jobs to are encrypted before we store them and are never sent back to the browser.
• When a business's customer pays a fee by card, the card number is typed on Stripe's own page and never reaches us.

No system is perfectly secure, and we cannot promise that information will never be accessed without permission. If you think something is wrong, email info@wakeman.ai.

Children

Wakeman is a service for businesses. It is not directed to children under 16, and we do not knowingly collect personal information from children under 16 through our website or accounts. If you believe a child has given us personal information, email info@wakeman.ai and we will delete it.

United States only

Wakeman is offered only to businesses in the United States, and it works with US phone numbers. Our website is not directed to people outside the United States.

Changes to this policy

We may update this policy as Wakeman changes. When we do, we will change the “Last updated” date at the top. If we make a significant change, we will also let account owners know by email.