Privacy Policy

Effective October 29, 2026

Daywright is scheduling and operations software for inspection businesses, made by Fine Folk (“we,” “us”). This policy explains what information Daywright handles, why, and the choices you have. We try to say it plainly: we collect what the product needs to work, we don’t sell anyone’s data, and we don’t use it for advertising.

Who Daywright serves, and whose data this covers

Daywright’s customers are inspection companies. Two kinds of information flow through the product:

Account information about the people who sign in (company staff and inspectors): name, email address, role, password (stored only as a secure hash), and settings.
Business records a company keeps in Daywright to run its operations: orders, appointments, client and agent contact details, service catalogs, invoices and payment records, messages, and documents. This information belongs to the company that entered it; we process it on that company’s behalf and use it only to provide the service to them. For this information the company is the controller (the “business,” under California law) and Daywright is its processor (its “service provider”), under our Data Processing Addendum. If you are a client or contact of an inspection company and want to see, correct, or delete your information, contact that company; if you contact us, we will pass your request on to them.

Google user data

Daywright offers an optional Google Calendar connection. Each team member connects their own Google account individually; nothing is connected unless you choose to connect it. When you do, Daywright requests two Google scopes:

Calendar events (calendar.events), used in two directions: Daywright writes your assigned job appointments to your own primary Google calendar, and reads your calendar to learn when you are busy so the schedule can respect your other commitments.
Email address (userinfo.email), used only to show which Google account is connected on your settings page.

What we store from your calendar, and what we deliberately don’t:

We store only the start and end times of your busy periods and an opaque event identifier. We do not store event titles, descriptions, locations, or attendee lists. Your colleagues see only that you are “Busy.”
The credential Google issues us (a refresh token) is stored encrypted at rest and is never visible to anyone, including your company’s administrators.
Calendar data is never used for advertising, never sold, and never used to train artificial-intelligence models. No human reads it except as needed for security or support with your permission, or where required by law.

Disconnecting: you can disconnect Google Calendar at any time from your account page. Disconnecting revokes the credential with Google and deletes it from our systems, along with the stored busy periods and the links between your appointments and calendar events. You can also revoke Daywright’s access from your Google Account security settings.

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

Sharing, transfer, and disclosure of Google user data

We do not sell Google user data, and we do not share, transfer, or disclose it to anyone, with these narrow exceptions:

Cloud hosting. The busy periods and encrypted credential described above are stored on the cloud infrastructure that runs Daywright. Our hosting providers process that data only to store and serve it on our instructions; they have no right to use it for their own purposes.
Your own team, inside the product. Colleagues on your company’s Daywright account see the times you are unavailable as “Busy” blocks on the schedule; they never see event titles, details, locations, or attendees.
The AI assistant. When a member asks the in-app assistant about the schedule, the busy periods for the days in question (start and end times and the colleague’s name; never event titles, details, locations, or attendees) are sent to Anthropic, the provider of the assistant’s language model, solely to answer that question. Anthropic processes this data on our instructions and may not use it for its own purposes, including training models.
Legal requirements. We may disclose information where the law requires it, such as in response to a valid legal process.
Change of ownership. If Fine Folk or Daywright is ever part of a merger, acquisition, or sale of assets, Google user data may be transferred to the successor, which must continue to honor this policy. We will notify account holders before any such transfer takes effect.

There is no other sharing. Google user data is never given to advertisers or data brokers, never sold, and never transferred to any other app or third party except as described above, consistent with the Limited Use requirements.

Payments

Card and bank payments are processed by payment providers (Stripe and Authorize.net, depending on the company’s setup). Card numbers and bank credentials go directly to the payment provider; Daywright never sees or stores them. We store the resulting payment records: amounts, timestamps, statuses, and the provider’s reference identifiers.

Service providers we rely on

Daywright runs on carefully chosen service providers that process data only on our instructions to operate the product: cloud hosting, databases, and backups; file storage; email delivery; address lookup; error monitoring; and Anthropic, which powers the AI assistant features. The full list, with what each one processes and where, is on our subprocessor list. Some features work through services a company connects under its own account, such as its payment processor (Stripe or Authorize.net), its phone and texting system (Twilio, Aircall, or Quo), or a staff member’s own Google Calendar. Business records sent to the AI assistant are used to answer the request at hand; we do not permit our providers to use your data for their own purposes, such as advertising or training models on your data.

How long we keep information

Business records are kept for as long as the company’s account is active, because they are the company’s operating history. Calendar busy periods are kept only for a rolling scheduling window and are deleted when you disconnect. Some operational records (such as payment-provider delivery logs) are pruned automatically on a fixed schedule, and free text such as assistant conversations and inbound text messages is deleted after a retention period each company chooses. When a company leaves Daywright, its data is deleted as described in our Data Processing Addendum.

Security

Every company’s data is isolated from every other company’s at the database layer. Credentials and tokens are encrypted at rest. Access to production systems is limited and audited. No system is perfectly secure, but isolation and least access are design principles of the product, not afterthoughts.

Your choices and rights

You can connect or disconnect the Google Calendar integration at any time.
You can ask us to access, correct, export, or delete your personal information, subject to your company’s role as the owner of its business records.
Clients and contacts of a Daywright customer can opt out of communications using the unsubscribe mechanisms in those messages, or by contacting the company that serves them.

Children

Daywright is business software and is not directed to children under 16. We do not knowingly collect information from them.

Changes to this policy

If we make material changes, we will update this page and the date above, and notify account holders when the change meaningfully affects them.

Contact

Questions about privacy, or requests regarding your data: hello@daywright.io.