Privacy

EZBIZI LLC · Last updated 20 November 2026

EzBizi is a field-service CRM operated by EZBIZI LLC, 800 SE 4th Ave Ste 107, Hallandale Beach, FL 33009, United States. Contact: contact@ezbizi.com.

Where EzBizi runs

This notice covers EzBizi wherever you use it: in a browser at app.ezbizi.com, in the Windows desktop app, and in the Android and iPhone apps. They are one product against one account, and they are treated identically here.

Your phone asks you before the app gets any of these. Notifications, so EzBizi can tell you about something assigned to you — you can refuse and keep using the app. The microphone, used only while you are on a call EzBizi placed or answered, and on Android also the phone permission, which Android requires before an app can place or take a call — both only if your organization uses the phone features. And your location, only if your employer has turned on Field tracking for your role — described in full below. And only when you tap Download on a how-to video, permission to add that video to your photos — on an iPhone, and on Android 9 or older; newer Android, the desktop app and the browser just save the file. And only when you tap to take a photo for a job, the camera — your iPhone asks first; on Android the phone’s own camera app takes the picture. EzBizi never reads your photos. We ask for nothing else: no contacts, no calendar. Unless Field tracking is on for you, nothing is collected in the background when you are not using the app.

What we collect

Three kinds of information, and it is worth keeping them apart:

Staff records go further where an organization uses EzBizi for its own people: home address, pay basis, worked hours from clock-in, any bonus or deduction a manager adds to a week’s pay and the reason given, the certifications a person holds (with the issuer, number and expiry date), onboarding documents and signed agreements. Clock-in on its own records when somebody worked, not where they were. Location is collected only through Field tracking, and only if an employer turns it on — see “Location, if your employer turns on Field tracking” below. What a monitored work computer reports about its own network is described under “Monitored work computers”.

Scans of a business’s QR codes

A business can print QR codes made in EzBizi — on a flyer, a van or a door hanger — so it can see how often they are used. When somebody scans one, they pass through EzBizi on the way to wherever the code points.

What we record is the time of the scan, and nothing that identifies the person. To count how many different people scanned on a given day, we also keep a one-way scrambled value made from the scanner’s internet address and browser, mixed with a random key that is changed every day and thrown away after two. That lets us tell two phones apart on the same day, and once the key is gone nobody — including us — can work out which phone it was, or link a scan on one day to a scan on another.

The scan record holds no internet address, no device details and no location. The business sees totals only: scans per day and different scanners per day. Scan records are deleted after thirteen months.

Enquiries from your websites

An organization can put a live chat bubble or a contact form on its own website, through the EzBizi plugin for WordPress or a snippet for any other site. Both are off until the organization switches them on.

Where they are on and a visitor uses one, that visitor’s browser sends what they typed directly to EzBizi: the name, email address and telephone number they give, the text of their messages or their answers to the form’s questions, and the address of the page they were on. It arrives as an enquiry the organization can read and reply to. Because the visitor’s browser makes that request itself, we receive their IP address the way any website they visit does; it is not stored as part of the enquiry, with one exception: where a form offers a box agreeing to receive text messages and the visitor ticks it, we keep their IP address with the time, the website and the exact words they agreed to, as the record of that consent.

This is worth stating separately because the visitor is not our user and did not come to us. They filled in a form on a business’s own website; we hold what they wrote on that business’s behalf, and that business decides how long it is kept and answers requests about it. If you have contacted a business this way and want your enquiry removed, ask the business — they can delete it, and we will help them do it.

If an organization switches both off, none of this happens and the plugin sends us nothing about anybody’s visitors.

Calls and messages

An organization can connect a business phone number to EzBizi. Where it does, we process the number called, the direction and time, how long it lasted, and voicemail and any call recording the organization chooses to keep, so that the call can be attached to the customer it was about. Telephony is carried by Twilio, which handles the call itself.

Transcripts of calls. EzBizi can turn a recorded call into text, so the words can be searched and read beside the customer or enquiry they belong to. There are two ways this happens, and they go to different places:

Labelling calls in a call report. Where call labelling is switched on, the text of a transcribed call behind a call report — never the recording — is sent to Anthropic (Claude) and to xAI (Grok). Each answers with one word: why an existing customer called, or why a new caller did not book. EzBizi keeps only that word, for twelve months.

Reading enquiries in Leads. The conversation on a lead — the customer’s and the business’s messages, the transcripts of its calls, including Google Local Services messages and calls — and the contact’s name, where known, are sent to xAI (Grok). It is used to sort the lead (wants work, an existing customer, or nothing to act on), write a one-line summary, pick out the customer’s name and ZIP code where they said them, and draft a suggested reply. A draft is never sent on its own: somebody on the team reads it, can change it, and decides whether to send it. EzBizi keeps the sorting, the summary and the name and ZIP code on the lead. Call transcripts are also sent to xAI to divide each call into the phone menu, the staff member and the customer, and to assess how staff handled the call, for coaching; those assessments appear in the organization’s performance reports to the people allowed to see them. Each day and each week, a staff member’s scores from those assessments, the checklist items they missed and the short notes written about each call — not the transcripts, and not the staff member’s name — are sent to xAI again so it can write a coaching summary for that person. The summary is kept for twelve months. Data retention is switched off on our xAI account.

Drafting replies to reviews. When somebody on the team presses Draft with AI on a Google review, or on several at once, when one of the organization’s automation rules is set to write a reply with AI, or once a day for reviews that have no reply yet, EzBizi sends xAI (Grok) the business’s name, the reviewer’s name, the star rating and the review’s text to write a reply. A draft is not posted until a person reads it, changes it if they want, and publishes it. The one exception is a listing where somebody has switched on automatic replies, which are off for every listing until they do: there, a rule can post the reply on Google by itself to a review less than 30 days old, and once a day EzBizi posts replies by itself to up to 50 four- and five-star reviews of any age. Neither posts over a published reply or a draft a person wrote. For reviews of three stars or fewer, the daily job only leaves a draft for a person to read.

A weekly summary. Each Monday EzBizi sends xAI (Grok) the organization’s figures for the week before — jobs, sales and deposits for each branch, the same totals for each technician by name, the profit and loss, and how many calls there were for each reason — so it can write a short summary in plain English. The organization’s own automation rules decide who receives it, for example by email or in a WhatsApp group. Data retention is switched off on our xAI account.

Figures questions on WhatsApp. Somebody with access to Reports can text a question about the business’s figures to the WhatsApp staff line, such as how much a branch sold last week. The question, and that branch’s figures for the period — jobs by source, sales, each technician’s sales and deposits by name, and how many enquiries arrived from each source other than Google Local Services — are sent to xAI (Grok) to write the answer. No customer’s name or contact details are sent.

Sorting Facebook ad campaigns. Each day, the names of the campaigns in an organization’s connected Facebook ad accounts, and the names of its own service categories, are sent to xAI (Grok) to suggest which service each campaign advertises. Nothing about a customer is sent.

Reading a photo of expenses. Somebody who can edit Financials can photograph a list of a branch’s expenses for a period, in the app or by sending it to the WhatsApp staff line, and the photo is sent to xAI (Grok) to read each line, its amount and the total printed on it. A person checks what was read, and nothing is saved unless the lines add up to that total. A saved record keeps its photo for seven years, as tax records are kept. Data retention is switched off on our xAI account.

Answering staff questions from the app. When somebody on the team types a question into the AI tab in the app, or sends it to the WhatsApp staff line or their organization’s Telegram bot, and the Library cannot answer it, EzBizi lets xAI (Grok) choose up to three places in the app to look, reads them as that person — so only records their role lets them see — and sends the question and what it found to xAI to write the answer. That can be any record the person may see, including customers, jobs, calls, staff records, details of monitored computers, the contents of connected mailboxes, and Google Ads, Local Services and Business Profile data. Only text is sent — never audio, images or files — and it is read only: nothing is changed. On the WhatsApp staff line, an answer can also bring photos from the organization’s previous jobs, or a training video, sent after the text over WhatsApp — so they pass through Meta, which runs WhatsApp. xAI receives only their links, as text. Data retention is switched off on our xAI account.

Call recordings on WhatsApp. Somebody with access to Reports can ask the WhatsApp staff line for the calls with a phone number. Their message is sent to xAI (Grok) only to read the number and the dates they asked for. EzBizi then sends them that number’s calls from the business’s phone system, and each recording as audio, over WhatsApp — so the recordings pass through Meta, which runs WhatsApp. The recordings are not sent to xAI.

Report files on WhatsApp. Somebody with access to Reports can ask the WhatsApp staff line to send them a report, such as last month’s figures for a branch or job profitability, as a PDF or Excel file. Their message, and the names of the branches they may see, are sent to xAI (Grok) only to read which report, branch and dates they asked for. EzBizi then sends the file to them over WhatsApp — so it passes through Meta, which runs WhatsApp. The report itself is not sent to xAI.

Answering questions from the Library. When somebody types a question into the AI tab in the app, or texts it to a business’s WhatsApp assistant line and the Library has no matching answer, the question is sent to xAI (Grok) together with the Library answers that person is allowed to read and the details of up to five matching branches (name, phone, address and service area), so it can answer in its own words. Someone texting the WhatsApp line can be a member of the public: the text of their message is sent, their phone number is not. Nothing is posted anywhere.

The tech assistant. When somebody on the team asks about a unit or a part on the WhatsApp staff line, or through their organization’s own Telegram bot where it has connected one, the question is sent to xAI (Grok) together with the organization’s name, the matching rows of the organization’s parts list, the matching pages of its manuals, up to five Library answers that person may read, and what the assistant has noted about the unit they are working on (brand, model, serial number, fuel and ignition, and the parts already discussed). A photo they send, such as an appliance’s rating plate, is sent to xAI to be read. A manual added in the app is sent to xAI to read its pages when our server cannot read the file itself. Each question and answer is kept so the organization can review it. An organization can switch the tech assistant off. Data retention is switched off on our xAI account.

When xAI is not available. Where this page says something is sent to xAI (Grok), it is sent instead to Anthropic (Claude), for the same purpose, whenever xAI is not available to EzBizi. Anthropic receives the same information, or less: it is never sent a manual to read.

Telegram. An organization connects its own Telegram bot in the app. A staff member links it by sharing their phone number with it, and it must match the number on their EzBizi profile; /unlink disconnects them. Their messages and photos to the bot, and its answers — which can include any record they may see, as described above — pass through Telegram, which runs that service.

Recording a call is the organization’s decision and the organization’s legal responsibility — some places require every party’s consent. EzBizi provides the capability; it does not provide the consent.

Job-visit recordings. Where an employer turns it on, a field technician can choose to record a job visit for safety and quality. The audio is transcribed on our own servers and deleted as soon as it has been transcribed. Audio that could not be transcribed is deleted within a day. We do not keep recordings. The resulting text is sent to xAI (Grok) to produce a short summary of the visit for the employer. The summary is never sent to the customer. Transcripts and summaries are kept for 90 days unless the employer keeps one for a safety incident or training. In states where every party must consent, recording is blocked unless the employer chooses to have the technician tell the customer first.

Weekly Google posts. Once a week, for each Google Business Profile listing an organization has connected, the business’s name, the listing’s city, state and category, and the listing’s recent posts are sent to xAI (Grok) to draft a new post. Nothing about a customer is sent. The draft waits for somebody on the team to approve, edit or turn it down, unless the organization has switched on automatic posting for that listing.

WhatsApp, Facebook and Instagram messages. An organization can also send and receive WhatsApp messages through EzBizi, and, where it connects a Facebook Page or Instagram account for messages, receive and answer the direct messages people send it. We store what each message says, in both directions, with the sender’s phone number or account identifier, so the organization can see the conversation and reply. These messages are carried by Meta Platforms, which runs WhatsApp, Facebook and Instagram. A WhatsApp message is kept for 24 months and then deleted. A Facebook or Instagram message is kept with the enquiry it arrived as, and deleted when that enquiry is.

Text messages we send you

Separately from any business phone line, EzBizi can text you a one-time code to verify it is you — signing in, confirming a new device, or resetting your password. These come from EzBizi’s own number, not from your company’s.

We only send them if you ask us to. You enter your mobile number and tick the box yourself, on your account page under Signing in; nothing is sent to a number that has not been entered there, and never to a phone number an administrator put on your profile. You can turn it off again on the same page, without a password, or reply STOP to any message. Reply HELP for help. Messages go out only when a code is asked for — typically fewer than 5 messages per month — and your mobile carrier’s message and data rates may apply.

We do not share or sell the mobile number you give us for these messages, or your consent to receive them, to anyone for marketing purposes. It goes to Twilio, which carries the message, and nowhere else.

Email we send you

EzBizi emails a confirmation link to the address you sign in with, so an account is tied to an address somebody can actually read. The same channel carries a password reset you ask for, the invitation that brings you into an organization, and — if your organization turns it on — a copy of a notification you are already shown in the app.

These are EzBizi’s own messages about your account. An organization can also have EzBizi send mail on its behalf: an automation rule can email a saved report, an inspection report, or a message the organization writes — to the recipients that rule names, or to an address held on the record it fired on, which may be a customer’s. Those leave from EzBizi’s own address rather than the organization’s, and the body says which business the work is about. A newsletter is not one of these: a mailing goes through your own Mailchimp account, on your list and your sending reputation.

Monitored work computers

An organization can install the EzBizi desktop agent on computers it owns, and monitor them. This is the most intrusive thing EzBizi does, so it is set out here in full rather than summarised. It is the organization that decides whether to run it, on which machines, and who may look.

Where an agent is installed, we hold about that machine and the person signed in on it:

Someone with the right role can also watch a machine live and take control of it, and someone with a separate permission can browse the files on it and download them — reading only, never changing or deleting anything, with each folder opened and file downloaded recorded against the person who did it. A person can be exempted from screen monitoring, and a machine that is exempt reports no window or tab titles at all.

Whether anybody is told is the organization’s choice, and the answer is no unless they change it. EzBizi can show a notice on a machine while somebody is controlling it — in the app and in the Windows notification area — but that setting is off unless an administrator turns it on, and watching a screen or browsing its files shows no notice either way. We say so plainly because a person is unlikely to find it out otherwise.

Whether any of this is lawful where you are — and what you must tell staff before switching it on — is the organization’s responsibility, not ours. Several countries and some US states require notice, consent, or both. EzBizi provides the capability and no advice.

An organization can also point EzBizi at camera streams it already runs on its own premises, or run the EzBizi app on a computer at a site to pass on that site’s cameras. We store the address of each stream and a label for it. EzBizi does not record: the recordings stay on the organization’s own equipment. While somebody is watching a camera through such a computer, the video passes through EzBizi’s server on its way to them and is not kept, and that computer also sends one small still picture per camera every ten minutes, which we keep, each replacing the last.

Location, if your employer turns on Field tracking

An employer can use EzBizi to see where its field staff are, so that somebody in trouble can be found and a team can be routed to the next job. Employees are tracked only if their employer turns it on for their role. An organization’s administrators are included automatically — they are tracked within the same window as everyone else, without anyone switching it on for them.

When. The employer chooses one of three windows: while you are clocked in (the default), during your scheduled work hours, or always. Whenever the app is sharing your location your phone shows it — a notification on Android, the location indicator on iPhone. A point sent outside the chosen window is refused by our server and not kept.

What. Your latitude and longitude, how accurate the reading is, your speed and heading, and the time of each point. If you press SOS, your position at that moment. With each upload the app also describes the phone: its battery level and whether it is charging, whether it is Android or iPhone and which version, its model, and which version of EzBizi it runs — so a manager can tell a flat battery from a lost signal. Only the latest description is kept, not a history of it.

Why. To keep you safe — SOS, and an alert if you have stopped for too long or lost signal. To know when you arrive at and leave a job. And to suggest the quickest route between your jobs.

Who sees it. People in your employer’s organization who have been given the Field Map permission and whose area covers you. Nobody outside your employer.

How long. Your location trail, your last known position and the phone description that goes with it, and any safety alerts are kept for three months and then deleted automatically. If your personal data is erased, your trail is deleted with it immediately.

Google. To show jobs on a map and plan routes, EzBizi sends Google Maps Platform the addresses and locations of the jobs and your current position in two cases: as the starting point when today’s route is planned while your position is current, and when somebody in your organization asks how long you are from a job. Your location trail — where you have been — is not sent to Google; it stays on our servers.

Whether tracking your staff is lawful where you are, and what you must tell them first, is the employer’s responsibility. Several US states and many countries require notice, consent, or both.

Connected social accounts

If you connect a social network (for example TikTok, LinkedIn, Facebook, Instagram, YouTube, X, Pinterest, Threads, or Bluesky), we receive the tokens and profile identifiers that network issues so EzBizi can compose, schedule, and publish posts you authorize, and so it can show the comments and replies people leave on your posts and mentions of your account, and reply to, hide or delete one when somebody at your organization asks. Those comments are read from the network each time the Comments inbox is opened and are not stored by EzBizi; when somebody replies to, hides or deletes one, the activity log records who did it and the comment’s id. We use that access only to provide the Social Media Poster, its Comments inbox and related account connection. We do not sell that access. Disconnecting a network in EzBizi deletes its tokens and the profile identifiers we hold for it straight away; until then they are kept for as long as the account stays connected. A note that it was connected and disconnected, with the account’s name, stays in the organization’s activity log for three months. Disconnecting does not withdraw the permission at the network’s end, so you should also revoke EzBizi in that network’s own settings.

YouTube

When you connect a YouTube channel, EzBizi uses the YouTube API Services. By connecting, you agree to be bound by the YouTube Terms of Service, and Google’s handling of your information is governed by the Google Privacy Policy.

EzBizi asks Google for three permissions. Read-only access (youtube.readonly) is used when you connect, to read the channel’s id, title and handle so EzBizi knows which channel it is posting as. Upload access (youtube.upload) is used only to publish a video you choose to publish to that channel from EzBizi; nothing is uploaded otherwise. Manage access (youtube.force-ssl) is used to delete a video you choose to delete from EzBizi, to read the comments on the channel’s videos so they appear in EzBizi’s Comments inbox, and to reply to, hide or delete a comment when somebody at your organization asks. Comments are read each time the inbox is opened and are not stored by EzBizi. We do not read your subscribers or analytics.

We store the channel’s id, title and handle and the access and refresh tokens Google issues, encrypted, until the channel is disconnected. To stop EzBizi’s access you can disconnect the channel in EzBizi, which deletes those stored tokens and channel details at once, or revoke EzBizi at Google on the Google security settings page. Doing both is best.

Google user data

When a business connects its Google Ads account to EzBizi, EzBizi reads from that account using the Google Ads API. This section says what we do with what we read.

Raw Google user data. We read Local Services Ads enquiries — who contacted the business, whether it was a call or a message, the call recording or the message thread, and when it arrived — together with the account’s name, currency and time zone, and campaign performance figures such as cost, clicks, impressions, interactions and conversions, and the value of those conversions. It is shown only to the business whose account it came from, and only to the people that business has given access to. It is used for one purpose: so the business can answer its own enquiries and see what its own advertising cost. We do not sell it or rent it, and we never show one customer’s data to another. We share it with one service provider: xAI (Grok). The text of Local Services messages and call transcripts, with the contact’s name, goes to it to sort and summarise each enquiry, draft a reply for the business to review, and assess how the business’s own staff handled the call, for coaching. And when somebody at the business asks a question in the AI tab or on the WhatsApp staff line, any of this Google data their role lets them see — Local Services enquiries, advertising figures and Business Profile details — can be sent to it as text to answer them. Both are described under Calls and messages. Data retention is switched off on our xAI account. Nobody else receives it.

Aggregated or anonymised Google user data. We do not aggregate or anonymise Google user data, and we do not combine it across customers for any purpose — not for benchmarking, not for statistics, not for product analytics, and not for advertising.

Machine learning. We do not use Google user data to develop, improve or train generalised artificial intelligence or machine learning models.

Retention and deletion. Enquiries are held so the business can act on them over time. A business can disconnect its Google Ads account at any time, which immediately stops EzBizi reading anything further from it, and can ask us to delete what we hold for it.

Who sees it

Data belongs to the organization that entered it. People in that organization see what their role and assignments allow, and access is enforced on the server rather than hidden in the interface. Two organizations using EzBizi can never see each other’s records.

We do not sell personal information, we do not use it to train anything, and we do not use it to advertise to anyone.

Who we rely on

We keep this list short on purpose, and these are all of them:

EzBizi is hosted in the United States. If you use it from elsewhere, your information is processed there.

Retention and deletion

We keep records while the organization has an account, and for a limited period afterward as security, backups and legal obligations require. You can ask us to export or erase personal data at the address above.

How to delete your account and your data is a page of its own — what gets erased, what has to be kept and why, and how long a deleted record can survive in a backup. Start there; it answers more than this paragraph can.

Children

EzBizi is business software sold to organizations. It is not directed at children, and we do not knowingly collect information from anyone under 16.

Keeping it safe

Traffic is encrypted in transit, and backups are encrypted at rest and held off-site, with restores verified rather than assumed. Access tokens for connected accounts are encrypted and are never displayed or returned by our API. No system is perfect, and we would rather say that than imply otherwise.

Actions from WhatsApp. Staff an organization has given the “Do things from WhatsApp” permission can ask the WhatsApp staff line to do a small, fixed set of things — such as answering a review, moving a job, changing a lead’s status or adding a scheduling note. The line repeats exactly what it is about to do and waits for a YES. It does not ask for the app’s second sign-in step. It knows who is asking because the message came, through WhatsApp, from the phone number on that person’s EzBizi profile — so anyone holding that person’s unlocked phone can do those things as them. Keep your phone locked, and an organization can withhold the permission from anyone who does not need it.

Changes

We will update this page when the product or our practices change. This notice is provided so our integrations can show a public policy; it is not legal advice.

Contact

Write to contact@ezbizi.com, or by post to EZBIZI LLC, 800 SE 4th Ave Ste 107, Hallandale Beach, FL 33009, United States.

Home · Terms of service · Delete account · Social Media Management · Download