01Who we are and what this covers
Labor Loader is operated by Deconstruct, Inc., a Delaware corporation ("Labor Loader," "we," "us"). It helps construction subcontractors pull their scope out of a project schedule, forecast manpower, and compare schedule revisions.
This policy explains what information we collect when you use laborloader.com and the Labor Loader application, how we use it, who we share it with, and the choices you have. If you use Labor Loader on behalf of a company, that company controls the project data placed in its workspace, and this policy describes how we handle that data on its behalf. Your use of the service is also governed by our Terms of Service.
02Information we collect
Account information. When you create an account we collect your name, email address, and a password (stored only as a salted hash). If you sign in with Google or Microsoft, we receive your name, email address, and a provider account ID from that provider instead of a password. If you turn on two-factor sign-in, we store the secret your authenticator app uses to make its codes and your backup codes, both encrypted, and delete them when you turn it off.
Schedules and project data. The schedules you upload (PDF, XER, XML, or MPP), the activities extracted from them, the keywords and scope settings you choose, the labor plans and forecasts you build, and the projects you add to a workspace. See "How your schedule files are handled" below. Most of this only reaches our servers when you choose to save it.
Workspace information. Workspace names, and each workspace's members with their email addresses and roles, so that we can check who may see and change the projects in it. When an owner or admin invites someone, we keep the invited email address, the role offered and who sent it, and email that address a link to join. The link works for 7 days, and only for an account with that email address.
Messages you send us. The contact form (name, email, trade, topic, message, and up to three files you attach, which reach us as email attachments and are not stored on our servers), account signup (name, email), mailing-list signup (email), and in-app feedback, including any screenshot you attach to a bug report.
Usage information. Which pages you visit, the features you use, and basic device and browser information, collected through our own page-view counter and the PostHog analytics service. We use this to see what is working and what is not. We do not record the contents of your schedules as part of analytics. Our page-view counter keeps the page, the time, your IP address and the approximate city it maps to (looked up on our own server). For the first page of a visit it also keeps where you came from: the other website's name only (such as google.com, never the full address of the page you were on) and the source tag in the link you followed, if it had one. It keeps all of this for 12 months, then deletes it. We also keep running totals of how many schedules are extracted and compared, in the app and in the sandbox. Your browser tells us only that one was, never anything about the file, and a total is just a number with nothing about you kept beside it, so it counts with analytics turned off too.
Activity records. When someone creates, changes, deletes or downloads something in a workspace (a project, a schedule, a crew plan, a preset, an API key), we record who did it, when, and the IP address and browser they used, so changes can be traced. The record names the item but never holds your schedule's contents. We record sign-ins, failed sign-ins, sign-outs and password resets on your account the same way. When a sign-in is tried with an email address that has no account, we keep only the IP address and browser, not the address. A workspace's owners and admins can see and download its activity records; your own sign-in records are not shown to them.
Error records. When something goes wrong on our servers we keep a short technical record of it so we can fix it: what failed, the address of the request without its query, when it happened, and the ID of the signed-in account involved. Email addresses and quoted text are removed first, and it never includes your schedules. The same goes for a page that crashes in your browser, or content our security policy blocks there: your browser sends us a short report of what failed and on which page, without the rest of the web address. When our security checks see signs of an attack, such as many failed sign-ins, the record also keeps the IP address involved and the ID of any account it targeted.
Cookies and browser storage. A session cookie keeps you signed in. If you use two-factor sign-in and tick "Don't ask again on this device", a cookie remembers that browser for 30 days. Analytics uses a cookie and browser storage to recognise a returning browser. The application also uses your browser's local storage to remember preferences and to keep an in-progress extraction from being lost if you navigate away. You can clear all of this through your browser at any time.
03How your schedule files are handled
This is the part most people ask about, so it deserves to be spelled out.
- Extraction runs in your browser. When you upload a schedule to the Extractor, the file is read and the activities are pulled out on your own device. Nothing about the file is sent to our servers to do this, including the optional in-browser OCR for scanned PDFs.
- Scanned PDFs are read on your device too. If you choose to run OCR on a scanned PDF, your browser downloads the open-source PaddleOCR engine from this site and reads the pages on your own device. The engine is a download to you: no part of your file is sent to us or to anyone else. Your browser keeps a copy, so later scans need no download.
- Files reach our servers only when you save. If you save an extraction to a project, we store the extracted activities and, so you can download it again later, an archived copy of the original file. If you never save, the file never leaves your device. Owners and admins can set a workspace, or a single project, not to keep original files: saves there store the extracted activities only, and the file never leaves your device.
- Deleting a schedule deletes its file. Removing a schedule from a project removes the archived original from our storage as well.
- The public sandbox stores nothing of yours. The try-it-without-an-account sandbox runs entirely in your browser on a schedule you drop in, and does not save or send any of it. It only tells us that a schedule was read, so we can add one to a running total.
- The Schedule Anonymizer sends only what you choose. It removes names from a schedule in your browser. Nothing is sent unless you click "Send to Labor Loader". Then we receive the cleaned copy only, never your original file or your list of names, together with the numbers the cleaning produced (pages, names replaced) and any name, email, or note you choose to add. We use these files to test and improve how Labor Loader reads schedules. They are not used to train any model, and we delete one when you ask.
04Artificial intelligence
Labor Loader does not use generative AI. There are no chatbots or large language models in the product, and nothing from your schedules is sent to an AI service.
- Extraction is written rules. Reading a schedule, filtering your scope, and every crew and manpower calculation are ordinary code and arithmetic that run in your browser.
- OCR uses small pre-trained models. The one exception is reading a scanned PDF. The OCR engine uses two small pre-trained models, one that finds the lines of text on a page and one that reads them, the same kind of text recognition found in scanner software. They run on your device, are the same for every user, and do not learn from your files.
- OCR is your choice. It runs only when you choose to read a scanned PDF, and you can switch it off in Account Settings.
- We do not train on your data. Your schedules are never used to train or improve any model.
05How we use information
- To provide the service: extract scope, build forecasts, keep your projects and workspaces, and let your team collaborate.
- To keep you signed in and secure your account, including verification and password-reset emails.
- To respond when you contact us, and to follow up on bug reports and feedback.
- To send product updates you have asked for (mailing list). Every message has an unsubscribe link.
- To understand how the product is used so we can improve it.
- To test and improve how Labor Loader reads schedules, using the cleaned schedules people send us from the Schedule Anonymizer.
- To detect abuse and enforce our terms.
06Signing in with Google or Microsoft
Instead of a password you can sign in with a Google or Microsoft account. This is optional and started by you. We ask the provider only for what is needed to create and sign you into your account: your name, email address, and the provider's account ID. We store that account ID, and the sign-in token the provider issues, so the link keeps working. We do not read your email, files, calendar, or anything else in that account.
You can revoke Labor Loader's access at any time from your Google or Microsoft account's security settings. Your Labor Loader account and its data are unaffected; you would simply sign in another way.
07Service providers we rely on
We use a small number of companies to run Labor Loader. They process data only to provide their service to us:
- Hosting and file storage: Replit, with files held in Google Cloud storage.
- Database: Neon (part of Databricks).
- Email delivery: Resend, for account, notification, and mailing-list email.
- Analytics: PostHog, for usage analytics.
- Identity: Google and Microsoft, if you choose to sign in with them.
Your browser also downloads this site's fonts directly from Google Fonts. Like any website request, Google sees your IP address and basic browser information. It never receives your schedules or your account information.
09How long we keep information
- Account and workspace data is kept for as long as your account is active. Invitations are kept with their workspace, including ones that were accepted, withdrawn or expired.
- Schedule files are kept until you delete the schedule (or the project it belongs to). In a workspace or project set not to keep original files, they are never stored.
- A project or schedule you delete is removed from our database 30 days later, so a mistaken delete can still be undone in that time. Its original file is deleted at once.
- Schedules sent to us from the Schedule Anonymizer are kept while they are useful for testing, and deleted when you ask.
- If you delete your account, we delete your personal information and the data you own within 30 days, except where we must keep it for legal, security, or accounting reasons.
- Our database keeps a continuous backup history so we can recover from mistakes or outages. The history covers the last 30 days and anything older is deleted automatically, so information you delete can remain in it for up to 30 days.
- Feedback you submit in the app, with any screenshot you attached, and answers to our surveys are deleted 2 years after you sent them.
- Messages sent through the contact form, and the copy of each piece of feedback, reach us by email. We delete them from our mailbox once they are 2 years old, clearing it every 3 months.
- Our record of the emails we send you (your address, which email and when) is deleted after 12 months.
- Our page-view counter's record of each visit (the page, the time, your IP address and city, and the website you came from) is deleted after 12 months.
- Analytics data is kept in aggregate; PostHog's retention rules apply to the underlying events.
- Error records are deleted 90 days after that error last happened.
- Activity records are kept for 12 months. If you delete your account, your sign-in records and the records in the workspaces deleted with it go too, and in workspaces that are kept your name, IP address and browser are removed from them.
10Security
Connections to Labor Loader are encrypted with TLS. Passwords are stored as salted hashes, never in plain text. When you choose a password we check that it has not appeared in a known data breach, using the Have I Been Pwned password list: only the first five characters of a one-way hash of it are sent, never the password itself. You can add two-factor sign-in in Account Settings: a code from an authenticator app, asked for however you sign in, and a workspace's owners can require it of everyone in the workspace. Access to project data is limited by workspace membership and role. Our providers hold their own security certifications. No service can promise perfect security, but if we learn of a breach affecting your information we will tell you without undue delay, and no later than 72 hours after we confirm it. To report a security problem, email security@laborloader.com; our security page explains how.
11Your choices and rights
- Access and correction. Your account details are in Account Settings, where you can change your name and your email address (we confirm the change from both the old and the new address), and "Download my data" there gives you one file with the personal information we hold about you. For anything else, email us and we will provide a copy.
- Deletion. Delete individual schedules and projects in the app at any time, and delete your whole account from Account Settings: we email you a link to confirm, and opening it deletes the account at once. You can also email us to do it for you.
- Marketing. Every mailing-list email has an unsubscribe link.
- Analytics. When you are signed in, analytics events carry your account ID, never your name or email. Turn analytics off in Account Settings (it applies to that browser), or have your browser send a Global Privacy Control or Do Not Track signal, and neither PostHog nor our page-view counter runs. The product works the same either way.
- Sign-in providers. Revoke Labor Loader's access from your Google or Microsoft account's security settings at any time.
Depending on where you live you may have additional rights under laws such as the GDPR or the California Consumer Privacy Act, including the right to object to certain processing or to lodge a complaint with a supervisory authority. We honour those rights; contact us and we will help.
12Children
Labor Loader is a business tool and is not directed at children. We do not knowingly collect information from anyone under 16. If you believe a child has given us information, contact us and we will delete it.
13Where information is processed
Labor Loader is operated from the United States and our providers store data in the United States. If you use the service from elsewhere, your information will be transferred to and processed in the United States.
14Changes to this policy
When we change this policy we will update the date at the top of this page. If a change materially affects how we use your information, we will also tell you in the product or by email before it takes effect.
15Contact
Questions, requests, or concerns about privacy: privacy@laborloader.com. You can also use the contact form.