Privacy Policy

Benchmark Restoration & Construction
Florida Certified General Contractor, License CGC1541207
Serving Miami-Dade, Broward and Palm Beach counties

Last updated: October 2, 2026


Who "we" are

"Benchmark Restoration & Construction" is a registered fictitious name (a DBA). It is not a company in its own right. It is registered with the Florida Department of State, Division of Corporations, Registration No. G26000026734, Broward County, and that registration runs through December 31, 2031.

Two owners stand behind that name, and both of them are responsible for the information described in this policy:

  • Erick Lynch, individually; and
  • Florangel Lynch, PLLC, a Florida limited liability company, Document No. L14000001319, FEI/EIN 46-4412007.

The construction work itself is performed under Florida Certified General Contractor license CGC1541207.

Everywhere below we say "Benchmark" or "we", and that means those two owners together. You can reach us by post at 4206 Fox Run Court, Weston, FL 33331, or by email at support@benchmarkrestore.com.


Read this first

We run three different websites, and they collect very different things. Before anything else, here is which is which:

WebsiteWho it's forWhat it collects
benchmarkrestore.comAnyone. Our public marketing site.What you type into the "request a proposal" form. No accounts, no analytics, no cookies, no embedded third-party video and no third-party fonts.
jobs.benchmarkrestore.comJob applicants and subcontractors. Public, no login.A full employment application, or a subcontractor prequalification. This is the most detailed information we collect about anyone.
os.benchmarkrestore.comOur own staff, and clients we give a portal login to. Password-protected.Employee records, payroll, daily job reports, site photos, client and CRM records, subcontractor records, and job applications, because the dashboard reads the applications workbook and shows applicants to staff.

If you are a job applicant, the section you want is Applying for a job. We have written it in detail on purpose.

We do not sell personal information. We do not run advertising trackers on any of the three sites. We have no analytics, no tag manager, no advertising pixels and no session-replay software anywhere.

About language. This page is written in English only. The job application and the subcontractor form are available in English, Spanish and Brazilian Portuguese, and the short privacy notice printed on the job application is professionally translated into all three. Because this long page exists only in English, nothing you do on one of our forms binds you to it, and submitting a form does not accept our Terms of Service. This page describes what we do with your information. It is not a contract for anyone who only reads one of our public sites or sends us a form; it becomes part of an agreement only for the people who accept our Terms of Service when they sign in to BenchmarkOS, our staff dashboard. If you would like any part of it explained in Spanish or Portuguese, email us and a person will explain it.


1. Our public website: benchmarkrestore.com

This is a single marketing page. You can read all of it without giving us anything.

If you fill in the proposal request form, you give us your name, your email address, the name of the property or association and a message describing the project, and, if you choose, your phone number, your role, the city, the services you need, whether you have an engineer's report or bid documents, and your bid due date. The name, email, property name and message are required; the rest are optional.

Where that goes. Our website has no database and no server of its own. When you press send, your browser posts the form directly to Web3Forms, a third-party form service, which turns it into an email and delivers it to us at support@benchmarkrestore.com. Because your browser makes that request, Web3Forms also sees your IP address. We do not control what Web3Forms keeps or for how long; that is set by their own terms, not by us.

Nothing on the site contacts a third party when a page loads. The page's typefaces, code and photos are all served from our own site, so browsing it discloses nothing to Google or anyone else. The only third-party request is the one you make yourself by sending the form, to Web3Forms, as described above.

Cookies: the marketing site sets none. It embeds no third-party video, map or player, so nothing on the page sets cookies of its own either. The photos on the page are served from our own site.

Our team on the homepage. The homepage names five members of our team with their roles (Gabriel, Erick, Juan Torres, David and Jakson) in About, How we work, the FAQ and the client reviews. Reviewers are identified by role and building, not by name.


2. Applying for a job: jobs.benchmarkrestore.com

This is where we ask for the most, so this is where we owe you the most detail. The form is available in English, Spanish and Brazilian Portuguese. Anyone can open it; there is no account and no password.

What we ask you for

About you First name, middle name, preferred name, last name, home street address, city, state, ZIP code, mobile phone, home phone, email address, and how you prefer to be contacted.

What we stopped asking for (changed September 23, 2026) We used to ask for your date of birth, your driver's license number and its issuing state. We removed all three from the application on September 23, 2026. The form no longer asks for any of them, in any language, and nothing you send us now can contain them.

Applications sent to us before that date are a different matter, and we will not pretend otherwise. Whatever was entered then is still sitting in the spreadsheet row, in the email that was sent at the time, and in the PDF filed in OneDrive. We have not gone back through old records to strip those fields out. Those values disappear when the record holding them is deleted (two years for an application from someone we did not hire, under How long we keep things) or sooner if you ask us. If you applied before that date and you want your date of birth and license number taken out of your record now, email us and a person will do it by hand.

Right to work One yes/no question: are you authorized to work in the United States? We do not ask for a visa type, a status category, a document, or a country of origin.

Your emergency contact Their full name, their relationship to you, their phone number and an alternate number. This is a third person who never visits our site. See If someone else gave us your details.

The job Positions you're applying for, desired pay, the date you can start, and four screening answers: whether you have a valid driver's license and reliable transportation (a yes or no; we do not ask for the license number), whether you're comfortable working at heights, whether you can repeatedly lift 50 lbs or more, and whether you're available for overtime and weekends.

Work history. Up to five employers, and for each one: company, position, start and end dates, your supervisor's name, your supervisor's phone number, your reason for leaving, and whether we may contact them.

Education and skills. Education level, school, field of study, years of experience, trade skills, certifications held (OSHA 10/30, fall protection, scaffold, lift, forklift, confined space, first aid/CPR, HAZWOPER and so on), and any others you write in.

Documents you upload. Up to 8 files, 10 MB each, in PDF, JPEG, PNG, WEBP, HEIC or HEIF. We ask for certification cards and similar documents. Please do not upload anything we didn't ask for. We do not need medical records, social security cards or immigration documents, and our system does not inspect or filter what you send.

Two references. For each: name, relationship to you, company, phone and email. Both are required.

Your signature. You tick a box certifying the information is true, then type your name and the date. The tick box itself is checked and then discarded; it is not stored.

Automatically. A submission ID, a timestamp, and the language you used. Your IP address is held briefly in the server's memory purely to stop one machine from submitting more than five times an hour. It is never written to a file, an email or a database, and it disappears when the server recycles.

Why we ask for all of this

We use your application to decide whether to interview and hire you, to contact you about the role, to check the certifications you list, and, only where you told us we may, to speak to the employers and references you named. A person reads every application. No part of the decision is made by software, we do not score or rank you automatically, and we do not use your information to build a profile of you or to market anything to you.

We do not run background checks. Ever.

We do not obtain background checks, criminal record checks, credit reports, motor vehicle records or drug screens about applicants or employees, not from a screening company, not from anyone. We check the certifications you list and, where you told us we may, we telephone the employers and references you named, and we do that ourselves.

Because we obtain no consumer reports of that kind, there is no Fair Credit Reporting Act disclosure for you to sign, and nothing on our form is a disguised consent to one. If we ever decided to change this, we would ask your permission first on a separate form written for that purpose alone, and we would update this page before we did it.

We also do not send your application to any advertiser, recruiter network, background-check service or data broker.

What the short notice on the form means

The application form carries a short privacy notice, in all three languages, saying your information will be used only to evaluate your application and will not be shared with third parties without your consent. That is correct, and this section is the longer version of it. The companies named in Who else touches your information, chiefly Microsoft and Cloudflare, store and move your application for us, on our instructions, and for no purpose of their own. Nobody receives your application to use for themselves.

Where your application actually goes

Three things happen when you press submit. All three are inside our own Microsoft 365 account:

  1. An email to support@benchmarkrestore.com containing every answer above, with a PDF of your application and every file you uploaded attached to it. There are two mail copies from the moment you press submit, not one: the message is created in the sending mailbox before it is sent, so a copy sits in that mailbox's Sent folder as well as in the support inbox.
  2. A row in a spreadsheet: Applications.xlsx, in the HR/Recruiting folder of our company OneDrive.
  3. A folder in OneDrive, named with your first and last name plus part of the submission ID, holding the PDF and the files you uploaded.

There is no other database.

Who inside the company can see it

Our staff dashboard reads that spreadsheet and shows applicants to staff with the right role. What it displays includes your name, phone, email, city and state, the positions you applied for, your skills and certifications, your desired pay, and your answers about work authorization, driver's license, heights and lifting. Your uploaded documents and the PDF stay in OneDrive; who can open that folder is controlled by our Microsoft 365 account permissions. There is one further honest caveat about that, in How we protect it.

Honest limits you should know about

  • There is no button to edit, correct or withdraw an application once it is sent. If you need something changed or removed, email us. See Your choices. A person handles it by hand.
  • Nothing expires automatically. Our software has no scheduled deletion. Every deletion is done by a person.
  • If a file upload fails, our error log records your name. Those logs are held by Cloudflare, our hosting provider.
  • Deleting your application is how you withdraw it. There is no separate withdraw button. If you ask us to delete it, we delete it and we stop considering you, and the copy already read by whoever opened the email cannot be un-read, though we do delete the message itself from both mailboxes.

3. Applying as a subcontractor: the prequalification form on the same site

If your company applies to work for us as a subcontractor, this is what the form collects and where it goes. This page is the privacy notice for that form.

What we ask for

  • The people. The name, job title, mobile number and email address of your main contact, and an optional after-hours contact, which usually names a second person.
  • The company. Legal and W-9 name, DBA, entity type, office and remit-to addresses, website, years in business, and the trades you work in.
  • Tax and licensing. Your EIN; your contractor license number, type and expiration; the county competency card number; and the qualifier's name: a named individual whose personal license your company's application depends on, who is often not the person filling in the form and who may never have seen it. See If someone else gave us your details.
  • Insurance. Carriers, policy numbers, limits and expiration dates for general liability, workers' compensation (including any exemption number), auto and umbrella.
  • Safety. EMR, OSHA citations and the detail behind them, safety manual, drug testing, competent person, and whether you use E-Verify.
  • Capability and commercial terms. Crew capacity, equipment, counties served, payment and commercial terms, bonding.
  • References. Up to three recent projects, each with a contact person at another company.
  • The certification. The name, title and date of whoever certifies the form.
  • Automatically. A timestamp. We do not store the IP address your submission came from; the hiring site uses it only in memory to limit how many submissions one machine can send in an hour, and it is never written down. (Our dashboard records the address of the hiring site's own server call, which says nothing about you.)

Only a handful of these are actually required: legal company name, contact name, contact mobile, contact email, at least one trade, and the certification at the end. Everything else can be left blank.

Where it goes, and how it differs from a job application

Two things happen, plus a hand-off:

  1. An email to support@benchmarkrestore.com with a PDF of your submission attached (again with two copies from the start, one in the support inbox and one in the sending mailbox's Sent folder).
  2. A row in a second OneDrive spreadsheet, separate from the job applications workbook.
  3. A server-to-server hand-off to our staff dashboard, where it becomes a roster record so we can track when your insurance is due to expire.

This is not identical to a job application, and the draft of this policy used to say it was. Unlike a job application, the subcontractor route does not save a folder of files to OneDrive. There is no OneDrive folder holding your PDF, only the spreadsheet row, the two mail copies, and the record in our dashboard.

Once you are on our roster, our office can add private notes to that roster record which you will not see.

If we turn your company down

Being declined does not make the record go away, and you should know that.

We keep the declined application (including your EIN, contractor license number, insurance policy numbers and the qualifier's name) together with a free-text note explaining why we declined it, written by whoever made the decision. Nothing in our software deletes any of it.

Our practice is to delete a declined prequalification after 2 years, the same period we apply to an application from someone we did not hire. That is a practice a person carries out, not something a computer enforces. You can ask us to delete it sooner, and we will.


4. Our staff dashboard: os.benchmarkrestore.com

This site is not public. It requires a password, and only accounts we create can sign in. Most people reading this policy will never see it, but it holds real information about real people, so here is what is in it.

About people with a login: email address, name, role, whether the account is disabled, the last time they signed in, and a password stored as a PBKDF2-SHA256 hash with 100,000 iterations and a random salt per person. We never store the password itself.

And what you do in it. The dashboard keeps an attributed history of changes: who moved a field-tracker cell and from which state to which, who changed a project, a drop, a contract value or an estimate and what the old and new figures were, who recorded progress, who wrote a survey question, who uploaded each photo, who generated each report PDF, who set a pay rate, who edited a customer record, and who approved or declined a subcontractor, each with a name and a timestamp. It is how a figure is traced back months later. Nothing trims that history by age or volume; it accumulates for as long as the record it describes does. Two things do remove it: deleting a scope item from a job deletes that item's history with it, and a cell moved and moved back on the same day leaves no line on that day's report.

Staff accounts are disabled, not deleted. When someone leaves, we disable their account: it can no longer sign in, and every session on it ends immediately. The row itself stays, indefinitely, so that the change history above still has a name attached to it rather than a blank.

About our crew: name, trade, hire date, phone number, personal email address, an emergency contact written as free text, office notes, the full history of hourly pay rates with the date each took effect, imported payroll history (period, hours, rate and the paycheck amount actually paid), and day-by-day attendance, hours and which job those hours went to. The emergency contact names a third person who never touched any of this. See If someone else gave us your details.

Pay rates and payroll are owner-only. An administrator can see trades and phone numbers but not money: the pay figure is stripped out on the server before the page is ever sent to a non-owner's browser.

Daily job reports: who was on site and for how long, and six free-text fields (work performed, delays or issues, materials delivered, visitors or inspections, safety observations and quality-control observations). The foreman signs the report by drawing his signature on a phone screen; we store the path his finger took as a list of coordinates and redraw it onto the report.

Site photographs taken on site, stored in the job's folder in our OneDrive. Our crews work on occupied buildings, so residents, visitors or passers-by may appear in a photo. If you live or work in a building where we are working and you would rather not appear in a photograph, tell the foreman on site or email support@benchmarkrestore.com. We will stop photographing you and remove you from any report we can still change. We never use site photographs in our advertising, on our website or on social media where an identifiable person appears, unless that person has given us written permission. We use them to document the work for the client and for our own records, and for nothing else.

One technical note about photos: the browser re-encodes each picture before uploading it, which normally drops the camera's embedded metadata, but if that step fails, the original file is uploaded unchanged, and any location metadata inside it travels with it.

Two PDFs per report. The internal copy lists every crew member by name with their hours and carries the safety and quality observations. We never publish a link to it (unlike the client copy, it gets no shareable link at all), and it is reachable only through the dashboard or by whoever our Microsoft 365 permissions let into the project's OneDrive folder.

The client copy shows a crew count instead of names, and leaves out the safety and quality observations. It is not otherwise a redacted document, and this next point matters:

The "visitors or inspections" note prints on the client copy. That field is free text, written on a phone by a foreman, and its whole purpose is to record who came to the site: a city inspector, an engineer, a board member, a resident who raised something. Those names appear on the copy that leaves the company. The client copy also carries the site photographs, the foreman's handwritten signature and typed name, and the name of whoever submitted it.

Please read this if you are a client or a resident: the client copy of a daily report is shared through an anonymous OneDrive link. Anyone who has that link can open the report without signing in, and anyone who has the link can forward it. That is how we send you your report without making you create an account. Our software does not expire or revoke those links automatically. It does record every client link it issues, against the report it belongs to, and re-filing a day reuses the same link rather than creating a second one, so we can find every link we have handed out and withdraw any of them by hand in OneDrive. What we cannot do is know who a link was forwarded to, or recall a copy somebody has already downloaded. If you would like a link withdrawn, ask us and we will remove it.

About our clients, and the work we chase: company or individual name, postal address, named contacts with title, email, phone and notes, and, where a QuickBooks job is linked, the QuickBooks customer name and the income and cost booked against that job. Separately, our CRM holds our estimates and the work we are pursuing: project name, client name, the contract value, whether it was sent, signed or lost, the dates, a reference, a follow-up date, and free-text notes about the prospect. Most client contacts are entered by our own office from a contract, an email or a phone call, not by the person named. Clients with a portal login can only ever see their own jobs; the portal code cannot load cost or margin figures at all.

Security records: if someone fails to sign in, we record the email address they typed and their IP address. Those rows are cleared as soon as the next failed sign-in is recorded, which in practice keeps the table to roughly the last quarter of an hour; but nothing runs on a timer, so if no further sign-in fails, the last few rows stay until one does. All rows for an address are deleted the moment that address signs in successfully. The two machine-to-machine endpoints keep a similar record of the calling IP address for about 60 minutes, cleared the same opportunistic way.

Cookies on the dashboard: one sign-in cookie (bmk_dash) and, briefly, one security cookie during the QuickBooks connection handshake. Both are strictly necessary. There is no other browser storage anywhere in the application.

Weather on reports: we automatically record the day's weather against each report so a weather-delay claim can be evidenced. To do that we send the job site's address to Open-Meteo: the full street address first, and, if that does not resolve to a place, the city and state, and then the resolved latitude and longitude. No name, no account, no cookie and no identifier of any kind goes with it.

Passwords by email: when we create or reset a staff account, the temporary password is emailed in plain text and a copy sits in our Sent folder. It must be changed at first sign-in, and issuing it ends every existing session on that account. We delete that message from the Sent folder once the person has signed in and changed it.


5. The QuickBooks connection

We connect our staff dashboard to a QuickBooks Online company file so the dashboard can show financial figures without anyone retyping them. This section is deliberately specific.

Who can use this connection? Only us. BenchmarkOS connects to exactly one QuickBooks Online company: our own. No other business connects its books to it. The integration is not offered to, marketed to, or supported for any other QuickBooks company. Everything in this section describes us reading our own accounting data; it is not a notice to anyone else about theirs, because there is nobody else.

Only the owner can connect or disconnect it. Both actions require the owner-level account.

What we ask QuickBooks for, and what we keep of it. We make four kinds of read:

  1. Estimates: total amount, transaction date, accepted date and status.
  2. The company's accounting preferences.
  3. The Customer Income report: income and expense totals per customer and sub-job.
  4. The customer list.

The customer and preferences queries are whole-record reads, so Intuit's response carries every field it holds on a customer, including any address, email or phone on the record. Of that response we read and keep only four things: the customer ID, the display name, whether it is a sub-job, and its parent. The rest is discarded in memory and never written down. We are describing this precisely because what crosses the wire and what we retain are not the same thing, and only the retention claim is the narrow one.

What we store from it: the customer or sub-job name, its ID and parent, the income and cost totals, the accounting method, the period those figures cover, and when we fetched them. Where a job in our dashboard is linked to a QuickBooks customer, we also store that customer's name and ID on the job record.

It is read-only. Every call our software makes to the QuickBooks Accounting API is a read: a GET, never a create, edit or delete. We never create, edit or delete anything in QuickBooks: no invoices, no customers, no payments, nothing. The only other calls we make to Intuit are the OAuth ones that obtain, refresh and revoke our own access token. We request Intuit's standard accounting scope (com.intuit.quickbooks.accounting), which technically permits writing; our software contains no code that writes.

What it is used for. Exactly two things:

  • Counting our own signed contracts against our annual goal. That figure, and the signed-contracts page it sits on, are visible to every staff account that can sign in except foremen. Client portal logins cannot see it.
  • Showing cost and margin per job on our internal billing page. That page is restricted to owner and administrator accounts.

It is never sold, never shared and never sent anywhere else. We traced every place this data goes: it is read from Intuit, stored in our own database, and rendered on internal pages. It is never emailed, never written to OneDrive, never given to another service, and never shown in the client portal; the portal is structurally incapable of loading it.

Credentials, described as they actually are today. The connection uses OAuth. The tokens Intuit issues are held in our hosted Cloudflare D1 database, protected by that platform's storage security and by access controls that restrict those routes to the owner account; our application does not yet add a further layer of its own encryption on top. Adding application-level encryption, with the key held in our hosting platform's secret store rather than in the database or the source code, is a change we intend to make. We would rather state the position accurately than describe a control we have not built. The connection handshake itself is protected by a one-time random state value in a short-lived cookie.

Error records. If a QuickBooks call fails, we store up to 500 characters of Intuit's own error response, Intuit's trace ID, and the endpoint path with the query string stripped off (so the dates someone was looking at are not recorded). Only the 200 most recent are kept, and that trim runs when the next error is written, so after a disconnect, when no new errors are ever written, whatever is in there stays until a person clears it.

Disconnecting. Deletion is triggered by an owner disconnecting inside BenchmarkOS. When the owner does that, we first ask Intuit to revoke the token, then delete the stored tokens and every cached cost and income row, whether or not the revoke succeeded, because a connection nobody can use is worse than none. If Intuit cannot be reached at that moment we still delete our copy and record the failure, and the token then expires on Intuit's own schedule.

Removing the app at Intuit's end is not the same thing. The connection can also be removed from the connected-apps list inside QuickBooks. That ends it immediately at Intuit's end and stops any further reads, but our own stored tokens and cached figures stay where they are until an owner signs in to BenchmarkOS and disconnects on our side, because only that action runs the deletion. We would rather say that plainly than promise a deletion our software does not perform.

Two things are not removed by the disconnect itself: the QuickBooks customer name saved against any job that was linked, and the stored error records. We clear both by hand within 30 days of a disconnect, and sooner if asked.


6. If someone else gave us your details

Some of the people in our records never filled in one of our forms, never signed in to anything, and may not know we hold anything about them at all. If that is you, this section is yours.

Who this covers. At least these people:

  • An applicant's emergency contact, named on a job application by the applicant.
  • An employee's emergency contact, written into our staff records by our own office, as free text.
  • A former supervisor named in an applicant's work history, with a phone number.
  • A reference named on a job application.
  • A subcontractor's after-hours contact, usually a second named person at that company.
  • A subcontractor's qualifier: the individual whose personal contractor license the company's prequalification depends on. Often not the person who filled in the form, and often someone who never saw it.
  • A project reference at another company, named by a subcontractor.
  • A client contact: the named person at a condo association, a management company or an owner. Usually entered by our own office from a contract, an email or a call, not by that person.
  • Visitors and inspectors named in a daily report (a city inspector, an engineer, a board member, a resident who raised something), written in free text by a foreman, and printed onto the client copy of that report.
  • Anyone who appears in a site photograph taken on one of our jobs.

Why we hold it, and what we do with it. In every case we hold your name and whatever contact details came with it because somebody else gave them to us, or because our own office wrote them down to run a job. We use them for one thing only, the reason the form or the record says: to reach an emergency contact in an emergency, to check a reference where the applicant said we may, to verify a license, to run the job, or to record what happened on a day. We do not add you to any list, we do not market to you, and we do not pass you to anyone else.

We know that most of the people above were never told, at the time, that we would be holding their details. That is why this section exists and why the removal route below is open to anyone, whether or not they ever dealt with us.

How to have your details removed. Email support@benchmarkrestore.com and tell us where you think your name appears. Where the record is one we can still change (a client contact row, an emergency contact field, a CRM note, a roster record, a reference on a stored application), we remove your details by hand and confirm when it is done.

Where we cannot, and we will not pretend otherwise. A daily report that has already been signed, turned into a PDF, filed to OneDrive and sent to a client is a record of what happened on a day, and our system deliberately does not alter reports that have been signed and sent. If your name is in one:

  • we can stop it being written into future reports;
  • we can revoke the share link for a report you identify, so that link stops working;
  • we can tell you what the report says about you;
  • but we cannot make a PDF that has already been delivered say something different, and we cannot recall a copy somebody has already downloaded or forwarded.

That is a limit of how the system is built, and we would rather say so than make a promise we cannot keep.


7. Your choices, and how to use them

Whoever you are (applicant, subcontractor, employee, client, someone who filled in the proposal request form, or someone named by another person), you can ask us to:

  • Tell you what we hold about you, and where it is.
  • Correct anything that is wrong.
  • Delete it, where we are not required to keep it.
  • Remove your details if someone else gave them to us as a reference, emergency contact, supervisor, qualifier or client contact.
  • Remove a photograph of you, if you appeared in a site photo and would rather not have.
  • Withdraw a shared report link, if you are a client and would rather a link stopped working.
  • Withdraw your job application: deleting it is the withdrawal; there is no separate button.

How to ask. Email support@benchmarkrestore.com, or write to us at 4206 Fox Run Court, Weston, FL 33331. Put "Privacy request" in the subject line or on the envelope if you can; it helps us find it. Both routes reach the same person. We will confirm we have your request and finish it within 30 days. We may need to check who you are before we hand over or delete anything, so that nobody else can make a request in your name.

What a deletion can and cannot reach. If you ask us to delete a job application, a person deletes the row in the spreadsheet, the OneDrive folder holding your PDF and uploaded files, and the email, in the support inbox and in the Sent folder of the mailbox that sent it, because there are two mail copies. Three copies are not ours to clear on the same day, and you should know about them:

  • the Excel workbook keeps a version history that Microsoft controls, and an older version can still contain the deleted row;
  • OneDrive keeps a recycle bin, which holds a deleted folder for a period Microsoft sets before purging it;
  • anything a person already printed, saved or forwarded is outside our system entirely.

We will tell you when the copies we control are gone, and we will not claim the others vanished at the same moment.

Some things we cannot delete on request. Payroll and tax records, hiring records and records tied to a construction contract have to be kept for set periods. Where that applies we will tell you what we are keeping, and why, rather than simply refusing.

We also have to hold on to anything relevant to a legal claim, charge, investigation or dispute that is under way or that we reasonably expect (an EEOC or Florida Commission on Human Relations charge, a workers' compensation claim, an OSHA matter, or a dispute about a construction contract) until it is resolved. Where that applies, the retention periods in the next section pause, and we will tell you that is the reason rather than leaving you guessing.

Asking for deletion does not hurt your application. If you ask us to delete an application we will delete it, which means we can no longer consider you for the role, but it is not held against you and you can apply again.


8. How long we keep things

We are being straight with you: our software deletes almost nothing automatically. Most of the table below is a company practice carried out by a person. Three rows are trimmed by the software opportunistically: failed sign-in records, machine-to-machine call records and QuickBooks error records, each trimmed the next time that table is written to rather than on a schedule. Two more are deleted by the software outright at the moment an owner disconnects QuickBooks inside BenchmarkOS: the OAuth tokens and every cached cost and income figure.

WhatHow long
Job application from someone we did not hire2 years from the date you applied, then deleted from the spreadsheet, the OneDrive folder, and both mail copies
Job application from someone we hiredKept as part of the employment file
Personnel and payroll records4 years after employment ends
Form I-9 and E-Verify records (where E-Verify applies to us)Kept with the personnel file: 4 years after employment ends, which is longer than the federal and Florida minimums
Subcontractor prequalification (company on our roster)While you are on our roster, and 7 years after you come off it
Subcontractor prequalification (company we declined)2 years, including the note recording why we declined
Daily reports, site photographs and job records7 years after the job closes
Client, CRM and estimate records (client names, contract values, follow-up dates, notes about prospects)7 years after the job closes, or after the last activity on an estimate that never became a job
Staff user accountsNot deleted. An account no longer needed is disabled so it cannot sign in; the record stays indefinitely so the change history below remains attributable
The dashboard's attributed change history (who changed what, when)Kept for as long as the record it describes. Nothing trims it by age or volume; deleting a scope item from a job deletes that item's history with it
Estimate-request emails from the marketing site2 years
QuickBooks financial data (customer names and IDs, income and cost totals, accounting preferences, period)Deleted by the software the moment an owner disconnects inside BenchmarkOS. Removing the app at Intuit's end stops further reads but leaves our copy until an owner disconnects on our side. The job-to-customer names left behind are cleared by hand within 30 days
QuickBooks OAuth tokensDeleted immediately when an owner disconnects inside BenchmarkOS; removing the app at Intuit's end stops further reads but leaves our stored copy until then
Failed sign-in recordsAbout 15 minutes, cleared on the next failed sign-in, not on a timer
Machine-to-machine call recordsAbout 60 minutes, cleared on the next call, not on a timer
QuickBooks error recordsThe 200 most recent, trimmed when the next error is written, and not trimmed at all after a disconnect until a person clears them

We answer an access, correction or deletion request within 30 days.

A note about the fields we removed. Applications received before September 23, 2026 may still contain a date of birth, a driver's license number and an issuing state. Those values age out with the record that holds them (two years for an application from someone we did not hire) or sooner if you ask us to strip them out.

Records we are legally required to keep are kept for whatever period that requirement sets, even if it is longer than the table above.

Copies outside our control. Microsoft and Cloudflare keep their own copies (workbook version histories, OneDrive recycle bins, platform backups and request logs) on their schedules, not ours, and a deletion we perform does not necessarily reach those copies at the same moment. Cloudflare logs every request to our staff dashboard. Web3Forms keeps whatever it keeps from the marketing form under its own terms.


9. Who else touches your information

Most of the companies below handle information on our behalf and under our instructions. Two do not, and we have marked them.

  • Microsoft (Microsoft 365, OneDrive, Exchange Online, Microsoft Graph): stores every job application, subcontractor application, uploaded document, daily report PDF and site photo, and sends our email. On our behalf.
  • Cloudflare: hosts all three websites and the dashboard's database, and logs requests to the dashboard. On our behalf.
  • Intuit (QuickBooks Online): our own accounting system, read-only, as described in The QuickBooks connection. On our behalf.
  • Open-Meteo: receives a job site's address or coordinates to return the weather. Nothing identifying a person is sent. On our behalf.
  • U.S. Department of Homeland Security and the Social Security Administration: receive new-hire verification details through E-Verify, where Florida law requires us to use it. This happens only after you accept an offer, never at application stage.
  • Web3Forms: receives and forwards the proposal request form on our marketing site. Not on our behalf in any meaningful sense: it holds submissions on its own terms, and we do not control what it keeps or for how long.

We have not audited any of these providers' own retention or sub-processor arrangements.

When we hire you. Federal law requires us to complete a Form I-9 and to examine documents proving your identity and your right to work, which means we hold copies of what you show us, including your date of birth, which we no longer ask for on the application form. Florida law (Fla. Stat. § 448.095) requires private employers of a certain size to run each new hire through E-Verify, which sends your name, date of birth, Social Security number and document details to DHS and the SSA. Where that applies to us we do it only after you have accepted an offer, never at application stage, and never to re-check someone already working for us.

Three other things can happen, and we would rather you knew now.

  • When the law requires it. We may disclose information in response to a subpoena, court order, warrant or lawful request from a government agency, and to our own lawyers, insurers, auditors and accountants where they need it to advise or defend us. We will tell you if we receive a demand for your information unless we are legally barred from doing so.
  • To protect people. We may disclose information where we believe in good faith that it is needed to prevent physical harm, fraud or a crime, or to bring or defend a legal claim.
  • If the business changes hands. If Benchmark Restoration & Construction is sold or merged, or its assets are transferred, the records described in this policy would transfer with the business. We would require the buyer to honor this policy for information collected before the transfer, and we would post notice on this page before it took effect.

Apart from those, nobody else receives your information, and we do not sell it or trade it.


10. How we protect it

  • Passwords are never stored, only a PBKDF2-SHA256 hash with 100,000 iterations and a random salt per person.
  • Sign-in sessions time out after two hours of inactivity. Disabling an account or changing a password ends every session on it immediately, everywhere.
  • Repeated failed sign-ins are throttled in two tiers, every failure is padded to a constant delay so timing gives nothing away, and a wrong email address and a wrong password produce the same message so the form cannot be used to find out who has an account.
  • Access is by role. Pay rates and payroll are owner-only, and the pay figure is removed on the server before a page reaches anyone else's browser. Client portal accounts are granted nothing by default, and every portal query is filtered by that client's own ID.
  • The dashboard sets a Content-Security-Policy that confines every fetch, image, font and form to our own origin and forbids the page being framed at all; the script directive still has to allow the inline tags our framework writes, so framing and origin confinement, not script filtering, are what that policy is doing. It sends no third-party scripts, fonts or trackers of any kind.
  • The machine-to-machine endpoints require a shared secret compared in constant time, cap the size of what they will accept, and fail closed if no secret is configured.
  • Everything travels over HTTPS.

Where we fall short, so you know

We would rather tell you exactly where the edges are than imply there are none.

  • Our applications add no encryption of their own on top of the storage they use. These sit as ordinary fields in a Cloudflare database, an Excel workbook or a file in OneDrive, protected by those platforms' own security and by our access controls: pay rates and payroll figures; employees' personal phone numbers and email addresses; emergency contact names and numbers; applicants' names, addresses, phone numbers, emails, work histories and their references' contact details; in applications received before September 23, 2026, dates of birth and driver's license numbers and issuing states; subcontractors' EINs, contractor license numbers, insurance policy numbers and qualifier names; stored signatures (the coordinate path); client contact details, contract values, and job cost and margin figures; the QuickBooks figures and the OAuth tokens; and the uploaded documents and report PDFs held in OneDrive.
  • The driver's license numbers in older applications are the most legally significant of those. A driver's license number stored next to a name is exactly the pair that triggers Florida's breach-notification statute, Fla. Stat. § 501.171. We stopped collecting it on September 23, 2026; the values already held are the reason the two-year rule and the deletion route in Your choices matter.
  • The Microsoft app registration used by our hiring site holds file and mail permission across our whole Microsoft 365 account, rather than being scoped to the Recruiting folder alone. So the honest answer to "who can reach my application file" is: the people our Microsoft 365 permissions let into that folder, plus anyone who obtained the hiring site's server credentials. Narrowing that permission is work we have identified and not yet done.
  • Temporary passwords are emailed in plain text. They must be changed at first sign-in, and we delete the message from the Sent folder once that happens.
  • Client daily-report PDFs are shared by a link anyone holding it can open, and nothing expires those links automatically. We do record every one we issue, so we can withdraw any of them by hand, but we cannot control where a link has already been forwarded.
  • We hold no privacy certification and have had no third-party security audit.

No system is perfectly secure.


11. If something goes wrong

If we find that personal information we hold has been reached by someone who should not have it, we investigate straight away and we tell the people affected.

Where the Florida Information Protection Act (Fla. Stat. § 501.171) applies, we will notify each affected person in writing within 30 days of determining that a breach occurred. If 500 or more Florida residents are affected we will also notify the Florida Department of Legal Affairs within 30 days, and if more than 1,000 people are affected we will notify the national consumer reporting agencies. Our notice will say what happened, when, what information was involved, and what we have done about it.

This commitment holds whether the failure was ours or one of our providers'. If a breach touches anything read from our QuickBooks Online connection, we will notify Intuit without undue delay as well.


12. Children

None of our sites are for children, and we do not knowingly collect information from anyone under 13.

We do not hire anyone under 18, because the work our crews do is treated as hazardous under federal child labor rules. The application form no longer asks for a date of birth, so we confirm age at interview rather than on the form; if we learn that an application came from someone under 18, we delete it and tell them why.

If you are a parent or guardian and you believe your child has sent us something, email support@benchmarkrestore.com from any address. We will delete it and confirm that we have, and we will not ask you to prove anything first.


13. Where your information is

We are a Florida business and we operate in the United States. Our hosting and file providers, Cloudflare and Microsoft, run global networks, so information may be processed at their facilities in more than one location. This policy is written for US and Florida law. We do not claim compliance with the EU GDPR, and we hold no privacy certification or third-party audit.


14. Changes to this policy

If we change how any of this works, we will update this page and change the "Last updated" date at the top. If the change is significant and affects people whose information we already hold, we will say so directly rather than relying on you to re-read the page.


15. How to reach us

Benchmark Restoration & Construction, a registered fictitious name (Registration No. G26000026734, Broward County, Florida), owned by Erick Lynch, individually, and Florangel Lynch, PLLC, a Florida limited liability company (Document No. L14000001319). Florida Certified General Contractor, License CGC1541207

4206 Fox Run Court Weston, FL 33331

Email: support@benchmarkrestore.com. This is the address for every privacy question, access request, correction or deletion request. You can send the same request by post to the address above, marked "Privacy request"; both reach the same person.

Phone: Main Office (954) 932-7870 · Broward (954) 616-7241 · West Palm (561) 931-1923

This privacy policy sits alongside our Terms of Service at benchmarkrestore.com/terms. Those terms cover all three of our sites (benchmarkrestore.com, jobs.benchmarkrestore.com and BenchmarkOS at os.benchmarkrestore.com), but they bind only the people who accept them when signing in to BenchmarkOS. For those people, this privacy policy forms part of that agreement. Reading our public sites or submitting a form on them does not make you a party to those terms, and for you this page is a description of what we do, not a contract. For help with either document, email support@benchmarkrestore.com.