SiteWorksSign inCreate account

Privacy

SiteWorks is construction project management software. This page describes what the application collects, who processes it on our behalf, and what we do not do with it.

What we collect

Your account. The email address and name you sign up with, and the workspaces and projects you belong to. Passwords are stored and verified by Supabase Auth; we never see them.

What you put in a project. Drawings, photos, RFIs, submittals, schedules, day logs, markups, budgets, contacts and anything else you or your team upload or type. This is your work product. We store it so the application can show it back to you and the people you share a project with.

Your mobile number, if you give us one. Used to text you sign-in codes and SiteWorks messages about your projects (see Text messages, below), and nothing else.

AI usage. When you use an AI feature we record what it cost, so the metering you see in the app is accurate and so we can bill credit correctly.

What we do not do

We do not sell your data, and we do not use your project content to train AI models. There is no analytics, advertising, or session-replay software in this application at all — no trackers, no ad pixels, no third-party scripts watching what you click. The only cookies we set are the ones that keep you signed in; preferences like panel widths live in your own browser and are never sent to us.

Who processes data for us

We use a small number of service providers, each for one job:

The AI features, specifically

The AI features are optional and metered. When you use one, the relevant project content — the drawing, the RFI, the document you asked about — is sent to the AI provider that does that job (listed above) to produce an answer. If you never use an AI feature, none of your project content is sent to an AI provider, with four exceptions you switch on yourself: QuickBooks, if you connect it; a bank or credit card account, if you connect one; mail to a project address; and the texts SiteTalk passes on, if you use SiteTalk. The first three are described below. Your content is not used to train models.

Things you connect yourself

SiteWorks can connect to Procore, QuickBooks Online, Microsoft and Google accounts, and your business bank and credit card accounts. These are off unless you turn them on, they use each provider's own authorisation, and we access only what that authorisation grants. You can disconnect any of them at any time, and disconnecting removes our ability to reach that account.

QuickBooks Online. When you connect it, SiteWorks reads your vendors, your customers and jobs, and the bills, checks, card charges, credits and payments you record there. It changes nothing in QuickBooks except a bank or card charge that a person in your workspace approves, which is written into QuickBooks as an expense (see bank and credit card accounts, below). To help sort each cost to the right job, SiteBrain, our AI assistant, sees the vendor, description, account, amount and date of costs that aren't assigned to a job yet. It does this by itself each time SiteWorks checks QuickBooks for new costs, for as long as you stay connected. If you ask SiteBrain to set up projects from your QuickBooks jobs, it also sees the names of your QuickBooks customers and jobs (never their addresses or contact details) to tell real jobs from everything else, and nothing is created until you accept each one. If you ask SiteBrain to match your QuickBooks vendors and customers to your Directory, it sees their names, whether a vendor is a 1099 vendor, whether each is still active in QuickBooks, and how much was spent with each (never their contact details or tax ids), and nothing is added until you accept it. A customer's or vendor's email, phone number and address are read from QuickBooks only to fill in the new project or Directory entry for you to check; they are not sent to the AI, and a vendor's tax id is never read into SiteWorks. That information is sent only to Anthropic's Claude — directly, or relayed through Vercel's AI Gateway to Anthropic and no one else — used only for that sorting, setting up and matching, and never used to train a model. If you press a button to look a new Directory company up online, its name and where it is (town, state or ZIP) — and nothing else from QuickBooks — are sent to Google and to Brave Search to find its public address, phone number and website. If our own code cannot read those details off the public pages found, a short excerpt of those pages and the company's name go to a small AI model (DeepSeek, through Vercel's AI Gateway, on US servers that keep nothing; or Anthropic's Claude if that is unavailable), and anything it finds is shown for you to check before it is saved. You can disconnect from SiteWorks' settings or from inside QuickBooks, and costs already brought in stay in your SiteWorks records.

Bank and credit card accounts. If you connect a business bank or credit card account, it is linked through Stripe Financial Connections: you sign in to your bank in Stripe's own window, so SiteWorks never sees your bank password. SiteWorks then reads each account you choose — its name, type and last four digits, and its transactions (amount, date and the description your bank gives), up to 180 days back and then each day — and may read its balance, to check that nothing was missed. It cannot move money. To sort each charge to a job or to overhead, SiteBrain sees its description, amount, date and which of your accounts it was on; that is sent only to Anthropic's Claude — directly, or relayed through Vercel's AI Gateway to Anthropic and no one else — and never used to train a model. Nothing is written to QuickBooks until a person in your workspace approves the charge; then it is recorded there as an expense. You can disconnect an account from SiteWorks' Bank & cards page at any time: reading stops at once, and transactions already brought in stay in your SiteWorks records.

Projects can also receive email at a project address. Mail sent to one is stored with the project so the team can see the correspondence a question came from. SiteBrain reads mail that arrives there, by itself, to tell an RFI from a document from something a person needs to see, and to file what it is sure about. The models that do this are listed above, and anything SiteBrain is unsure of is left for a person.

Connected mailboxes, and Google user data

If you connect a mailbox — Microsoft or Google — SiteWorks reads it so your work email can sit alongside the job it is about. This section describes exactly what that means, and it applies to Google user data in particular.

What we read. With the permission you grant on Google's own consent screen, we read the headers of your messages — who each one is from, who it was sent to, the subject and the date — together with the short preview line the provider generates. We also ask for permission to send mail as you. We ask for it when you first connect so that you are never made to sign in a second time later; nothing is ever sent without you writing it and choosing to send it.

Permission to tidy your mailbox. We also ask for permission to organise mail inside your mailbox — to archive it, label it, move it between folders or delete it — so that you can clear out what you do not want without leaving SiteWorks. We ask for this when you connect, for the same reason as sending: so you are never made to approve a second time later. We never move, archive or delete anything unless you tell us to. There is no automatic tidying, nothing acts on your mailbox on a schedule, and an AI feature can propose that something is junk but cannot act on that proposal by itself — only you can.

What we store, and what we deliberately do not. We store those headers and a preview of up to 255 characters. We do not store the body of your email, and we do not store its attachments. When you open a message, its body is fetched from your provider at that moment, shown to you, and not written down. This is enforced by the way we ask for the data, not merely by policy: the request we make for indexing cannot return message bodies at all.

What we use it for. Showing your mail inside SiteWorks, and suggesting which project a message probably belongs to so you do not have to file it by hand. Both are features you see and use in the application. We do not use your mail for advertising, we do not sell it, and we do not use it to train AI models.

Who can see it. Only you. A connected mailbox belongs to the account that connected it, and the people you share a project with cannot see it — including messages we have suggested for their project. Marking a mailbox as being for one of your companies only decides which mailbox you are shown; it grants nobody else access. The one thing that moves a message where your team can read it is you filing it against a project, which is a deliberate action and copies that message into the project's record.

AI, if you use it. When you ask an AI feature to summarise a mail thread, the messages in that thread are sent to Anthropic's Claude (directly, or relayed through Vercel's AI Gateway to Anthropic only) to produce the answer and are not stored there or by us. When you ask SiteBrain to set up projects from your QuickBooks jobs, it may look a new client up in your own connected mailboxes to suggest their email address and phone number; the few messages it reads are sent to Anthropic's Claude the same way, are not stored, and nothing is saved until you accept it. If you do not use an AI feature on your mail, none of your mail is sent to an AI provider.

Turning it off. You can disconnect a mailbox whenever you like. Doing so deletes the credential that lets us reach it, so no further mail is read. The index we already built stays, because it is your own record of what arrived — and you can choose to delete that too.

SiteWorks' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Text messages

SiteWorks texts a mobile number only for two reasons: a sign-in code you asked for, and a notice about a project you are part of. Project notices go only to a number whose owner opted in themselves, by ticking the "Text me SiteWorks messages" box when they joined a project — the exact box and wording are on our Text messages page. Nobody else, including the person who invited you, can opt your number in. We never send marketing texts.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. Twilio delivers our texts as our service provider and may not use your number for anything else.

Message frequency varies. Message and data rates may apply. Reply STOP to stop texts from SiteWorks at any time, and HELP for help, or email support@siteworks.app.

Keeping and deleting it

We keep your project content for as long as your account is open, because the point of the application is that a job's record is still there next year. If you want your data exported or deleted, email us and we will do it.

Contact

Questions about any of this, or a request about your data: support@siteworks.app

SiteWorks is operated by SkyJett Studios LLC, 2490 East Meadow Wood Court, Meridian, Idaho 83646, United States.

Privacy — SiteWorks