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.
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. We ask for nothing else: no camera, no photo library, no contacts, no calendar. Unless Field tracking is on for you, nothing is collected in the background when you are not using the app.
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, 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”.
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.
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.
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.
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:
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.
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.
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 five a 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.
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.
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. We store the address of the stream and a label for it; the video is the organization’s, on its own equipment.
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.
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. We use that access only to provide the Social Media Poster and related account connection. We do not sell that access. You can disconnect a network in EzBizi; you should also revoke the app in that network’s own settings.
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, rent it, or share it with any third party, and we never show one customer’s data to another.
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.
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.
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.
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.
EzBizi is business software sold to organizations. It is not directed at children, and we do not knowingly collect information from anyone under 16.
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.
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.
Write to contact@ezbizi.com, or by post to EZBIZI LLC, 800 SE 4th Ave Ste 107, Hallandale Beach, FL 33009, United States.