Your contracts, margins and clients stay yours.
A construction company’s system holds its prices, its margins, its clients’ addresses and its subcontractors’ tax IDs. Here is how SmartyBuild is built to keep all of that separate, controlled and recoverable.
Your own installation and database
Every company gets its own copy of SmartyBuild with its own database. Your figures never sit in a shared table next to another contractor’s.
Google sign-in for staff
Staff sign in with their Google account, so your company’s own account security, including two-step verification, protects SmartyBuild too.
Roles and permissions you define
Access is set per module and per action. Branch admins see only their branch. Approvals put a second pair of eyes on anything you choose.
An append-only activity log
Meaningful actions are recorded and never rewritten, and a reopened job posts an adjustment instead of editing the past.
Money never passes through us
Client payments run through your own merchant account and settle straight to your bank. Card details are entered on the payment processor’s own form.
Tax IDs encrypted
Subcontractors’ SSNs and EINs from their W-9s, and their bank account numbers, are encrypted at rest.
Releases that do not surprise you
- Every change runs 211 automated checks, against a database built from empty, before it can be released.
- Updates are tried on a staging copy first and roll out on a schedule, with notice inside the app — not in the middle of somebody signing a contract.
- The system goes looking for its own failures: a signed PDF that did not render is rebuilt, a call recording that never arrived is fetched back, a payment taken while a browser crashed is found and applied.
Backups and leaving
- Backups of your database are included in every plan.
- You can export your data at any time while your account is active, and for 30 days after it ends.
- Your payment, phone and bank accounts are in your name, so they stay with you.
How SmartyBuild uses Google
Staff sign in with their Google account. Beyond sign-in, SmartyBuild asks for access only where a feature needs it, and each permission below maps to one thing the software does. Nothing here is used for advertising, and none of it is sold.
| Permission | What it is used for |
|---|---|
userinfo.emailuserinfo.profile |
Signing in, and matching the person signing in to their staff account. |
calendar.events |
Putting a booked appointment on the assigned team member's calendar, and keeping it in step when it is rescheduled. |
contacts.readonly |
Importing a company's existing contacts so a new install is not started from an empty address book. |
chat.spaces.createchat.membershipschat.messageschat.messages.createchat.bot |
Delivering internal notifications — a signed contract, a matched payment — to the team's own Google Chat instead of by text message. |
admin.directory.user.readonly |
Letting an administrator see their own organisation's users when setting up staff accounts. Read-only, and only for the administrator's own domain. |
webmasters.readonly |
Showing a company its own Search Console performance next to the leads that came from it. |
SmartyBuild's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data received from Google APIs is not used to develop, improve or train generalised artificial intelligence or machine learning models, and is not shared with any third-party AI service. The privacy policy sets out exactly how each of these is handled.
Questions from your IT person
We are happy to answer them directly: support@smartybuild.com.
See it for yourself
Book a 30-minute walkthrough and ask anything, including what it does not do.