Privacy Policy

Hazel Dash is business software for restoration and field-service companies. It is operated by R.E.S.C.O. LLC ("we", "us"), a Florida limited liability company. This policy explains what information Hazel Dash collects, how it is used, who it is shared with, and the choices available to you.

Hazel Dash is used by businesses (our "customers") and the people who work for them. A customer decides what business information to put into Hazel Dash or connect to it, and remains in control of that information. We handle it on the customer's behalf to provide the service.

Information we collect

Account information

Accounts are created by us at a customer's request; there is no public sign-up. For each user we store a name, email address, phone number if provided, company and role. Passwords are stored only as a one-way hash, never in readable form.

Sign-in and security records

When you sign in we record the time, and we store your IP address and browser type with your sign-in session as a security record. We count failed sign-in attempts on your account and pause sign-in after too many. Some sign-in errors are written to our server logs with the email address that was entered. Our hosting provider may also keep its own request logs for a limited time.

Business information

Customers use Hazel Dash to work with their own business records, such as their clients' names and contact details, property addresses, jobs, estimates, invoices and balances. This information may come from what users enter, from data the customer sends us directly, or from services the customer connects.

Data a customer sends us directly

A customer can set up its own tool to send us copies of its records automatically, for example its customer list (names, email addresses, phone numbers and addresses) and its invoices (numbers, customers, dates, totals and balances). This uses a private key that only the customer's owner can create or cancel, and each key works only for that customer's account. Each new invoice copy replaces the previous one. This is separate from the connected services below: disconnecting a service does not remove information sent this way.

Connected services

A customer's owner can choose to connect other services. We only access them after the owner approves the connection on that service's own screen, and only for the permissions shown there.

• QuickBooks Online (Intuit). Read-only access. Hazel Dash reads the company's name, and may read its invoices (number, customer name, dates, total and balance). Hazel Dash does not create, change or delete anything in QuickBooks. We do not request bank, card or payment account numbers.
• Slack. If connected, read-only access to the list of channels and their messages, and the list of workspace members.
• Quo. If the owner saves a Quo key, it is stored encrypted, for use in showing the company's calls and texts once that feature is turned on.

Feedback and bug reports

If you send feedback or report a problem from inside Hazel Dash, we store what you write, your name and role, the screen you were on, your browser type and window size, and, if you choose to include one, a screenshot of that screen. A screenshot can show whatever was on your screen, including customer information.

How we use information

• To provide Hazel Dash: sign you in, show your company's information, and run the features you use.
• To keep the service and accounts secure, and to investigate misuse.
• To respond to support requests and fix problems you report.
• To improve Hazel Dash, using records of assistant conversations that have names and contact details replaced as described below, and the ratings and notes you choose to leave on answers, with names and contact details replaced the same way.
• To meet legal obligations.

We do not sell information. We do not use it for advertising. We do not combine one customer's business information with another's. We do not provide customer information to anyone to train artificial intelligence models.

The Ask Hazel assistant

Hazel Dash includes an assistant that answers questions about your work. To produce an answer, your question, the conversation so far, and relevant business information are sent to an artificial intelligence provider (see the list of service providers below).

Before anything is sent:

• Customer names and invoice numbers Hazel Dash knows about, and email addresses, phone numbers and street addresses it can recognize, are replaced with placeholders such as "Client A". The real values are put back only on your own screen.
• Anything that looks like a bank or card account number is removed entirely.
• A final check reads the request about to be sent. If a known name is still present, or the information cannot be safely de-identified, the request is not sent and no answer is given.

Amounts, dates and balances are sent as they are, because the assistant needs them to answer. Names the system does not already know, such as a name you type into a question that is not one of your customers with an open invoice, may not be replaced. Please do not type sensitive personal information, such as health details or government ID numbers, into the assistant.

Your browser keeps a copy of your recent assistant conversation, with real names shown, so it is still there when you return. You can clear it by clearing this site's data in your browser.

Who we share information with

We share information only as needed to run Hazel Dash:

• Vercel, which hosts the application.
• Neon, which hosts the database.
• Artificial intelligence providers used by the assistant: OpenRouter, which passes requests to the model provider it routes them to, and Anthropic, when the assistant is set to work with a customer's real records. They receive the requests described in the Ask Hazel section above, with the limits noted there.
• Slack, which we use for our own internal notifications. When you send feedback, our team's Slack receives your name, role, the screen you were on and the first part of your message. Screenshots are not sent to Slack. It also receives alerts when a connection to another service fails, when data a customer sends us is rejected, or when a customer's data stops arriving. These name the service and the problem but contain no customer records.
• Services you connect, such as Intuit and Slack, which receive the requests needed to read the information you approved.

We may also disclose information if required by law or legal process, to protect the rights, safety or property of our customers, users or others, or as part of a merger, sale or transfer of our business, in which case this policy continues to apply to the information transferred.

Cookies and browser storage

Hazel Dash uses only first-party cookies that the service needs to work:

• a sign-in cookie that keeps you signed in, for up to 14 days;
• short-lived cookies, lasting up to 10 minutes, that protect the steps when an owner connects another service;
• for owners, cookies that remember which role's view they are previewing (up to 7 days) and whether presentation mode is on (up to 1 hour).

Your browser also stores, on your own device: your screen settings and preferences, the layout of your boards and schedule, whether you dismissed the install prompt, and the position of the assistant window together with your recent assistant conversation. We do not use advertising cookies, analytics or tracking tools.

How we protect information

• Credentials for connected services are encrypted, and are never sent to your browser.
• Passwords and sign-in sessions are stored only as one-way hashes.
• Each customer's information is kept separate, and a signed-in user can only see their own company's information.
• QuickBooks access is read-only and enforced in our code, not just by policy.
• Removing a user's access takes effect on their next request.

No system is perfectly secure. If we learn of a security incident affecting your information, we will notify affected customers as required by law, including Florida Statute 501.171.

How long we keep information

We keep information for as long as the customer uses Hazel Dash, or until the customer asks us to delete it.

• When an owner disconnects QuickBooks, we ask Intuit to cancel our access, delete the stored connection credentials, and delete invoice information we fetched through that connection. If Intuit does not confirm the cancellation, Hazel Dash tells the owner, who can finish it by removing Hazel Dash from the connected apps in QuickBooks. Information the customer sent us separately, outside that connection, is not removed by disconnecting and stays until the customer asks us to delete it.
• When an owner disconnects another service, we ask that service to cancel our access where it offers a way to, and delete our stored credentials for it. If the cancellation is not confirmed, Hazel Dash tells the owner how to finish it in that service.
• When a customer stops using Hazel Dash or asks us in writing to delete its information, we will delete it within 30 days, except where we must keep something to meet a legal obligation. Our database provider may keep backup copies for a limited time after that, until they expire.

Your choices

If you use Hazel Dash through your employer, your employer controls your company's information in it, and requests about that information should usually go to them. You can also contact us at support@hazeldash.com to ask for a copy of your information, to correct it, or to delete it. We will respond within 30 days and may need to confirm your identity first.

Children

Hazel Dash is a business tool and is not intended for anyone under 18. We do not knowingly collect information from children.

Changes to this policy

If we change this policy, we will post the new version here with a new effective date. If a change materially affects how we use information customers have already given us, we will notify customers before it takes effect.

Contact

R.E.S.C.O. LLC, Florida. Email support@hazeldash.com.