Privacy Policy

— 01 · WHICH PART APPLIES TO YOU

Three kinds of people read this

FieldThread is in alpha. Most people who reach this page are in the first group, and only sections 02–04 apply to them.

— 02 · THE SITE AND THE ALPHA INQUIRY

What we collect right now

The form on our home page does not submit anything to us. It composes a message in your own mail app; nothing reaches us until you press send. If you write to us, we receive whatever you chose to put in that email.

This table is our notice at collection under California law. It covers the categories we collect, why, who receives them, and how long we keep them.

That is the entire list for visitors. This site sets no cookies, runs no analytics, and carries no advertising or social-media tracking pixels. We do not collect precise geolocation, biometric data, or any of the categories California treats as sensitive personal information. Because we do not collect sensitive personal information, the right to limit its use does not arise.

One third party does see your IP address when the page loads: the site pulls its typefaces from Google Fonts. If you would rather it did not, a content blocker will stop it and the page will still work in a system font.

— 03 · NO SALE, NO SHARING, NO ADS

The commitment, in the legal terms

We do not sell personal information, and we have not sold personal information in the preceding twelve months. We do not share personal information for cross-context behavioral advertising, and we have not done so in the preceding twelve months. “Sell” and “share” carry the meanings the California Consumer Privacy Act gives them, which are broader than an ordinary reading — they cover disclosures for money or other valuable consideration, and they cover handing data to an ad network. We do neither.

We do not sell or share the personal information of anyone we know to be under 16. We do not use your information, or your project content, to train general-purpose AI models for anyone else's benefit.

If that ever changes, we will not do it quietly: we will update this policy, post a clear opt-out, and tell alpha customers directly before the change takes effect.

— 04 · EMAIL FROM US

We reply; we don't blast

If you write to us, we write back. If we later send occasional notes about the alpha — a new capability, an open slot — every one of them will carry a working unsubscribe, and unsubscribing takes effect within ten business days. We do not add inquiry addresses to a purchased or shared marketing list, and we do not pass your address to anyone else's list.

We will not call or text the phone number you give us for marketing purposes unless you have told us we may. We may use it to reach you about an alpha conversation you started.

— 05 · WHO THE PARTIES ARE

The contractor owns the record

Sections 05 through 10 describe the alpha service itself, and apply once a contracting company has engaged us and pointed us at a project line.

A contracting company (the “customer”) engages us and tells us which WhatsApp thread is the project line. We process the messages on that line on the customer's behalf, to build their project record. The customer decides who has access to the dashboard and what happens to the record. In California terms, the customer is the business and we act as its service provider: we process that content only to deliver the service, under contract, and for no purpose of our own.

If you are a crew member and want your messages removed, the fastest route is to ask the contractor who runs the job. You can also write to us directly at the address in section 12, and we will forward or act on it as the law requires.

— 06 · WHAT WE STORE

What comes in on the project line

We store what is sent to a project line we have been asked to follow, and what we derive from it:

We do not read WhatsApp threads we have not been pointed at, and we have no access to a phone's contacts, location, camera roll or other conversations.

We do not ask for and do not want sensitive personal information — government identification numbers, financial account numbers, health information, precise location, union membership, or the contents of private correspondence outside the project line. If it lands on a project line anyway, tell us and we will remove it.

— 07 · HOW IT IS USED

Building the customer's project record

Messages are processed to produce the project record and to keep it current: sorting entries, transcribing voice notes, translating between English and Spanish, extracting dates and material needs, and tracking what is still unconfirmed. Automated language models are used for that processing.

That processing organizes and translates what people wrote. It does not make decisions about anyone — it does not score, rank, screen, discipline, hire or fire, and it is not used to evaluate a worker's performance. If we ever build a feature that makes or substantially informs a decision about a person, we will say so here first and give the rights that California attaches to it.

During the alpha, our team may read project content to diagnose problems and to check the clerk's accuracy. That is how we find and fix mistakes in the record. Access is limited to the people running the alpha and is logged.

We do not sell project data, we do not use one customer's project content to advertise to anyone, and we do not use it to train models offered to anyone else.

— 08 · WHATSAPP AND META

WhatsApp is the transport, not the record

Messages reach us over WhatsApp, which is operated by Meta. Meta's own terms and privacy policy govern the messaging service itself, including how messages are carried and what Meta retains. We are not affiliated with, endorsed by, or a partner of Meta or WhatsApp.

Because FieldThread participates in the project thread, messages on that thread are visible to FieldThread. Everyone on a project line must be told, before they use it, that the line is recorded and turned into a project record. California law is strict about recording a conversation without everyone's knowledge, and voice notes make that concrete. The customer is responsible for giving that notice; we supply plain-language notice text in English and Spanish, and we ask customers to confirm they have delivered it before we start following a line.

— 09 · SERVICE PROVIDERS

Who else touches the data

We rely on third-party infrastructure to run the service. By category:

Each of these is engaged under a written contract that limits them to processing data on our instructions for the purpose of delivering the service, forbids them from selling it, forbids them from using it for their own purposes, and requires them to delete or return it. Disclosure to a service provider on those terms is not a sale or a share. We do not permit language-model providers to train on project content.

We may also disclose information if we are legally required to — a subpoena, court order, or law enforcement demand — or where necessary to protect someone's safety or defend a legal claim. Where we are permitted to tell the affected customer first, we will.

If Sky Link Solutions LLC is ever acquired or merged, customer records may transfer as part of that transaction. Any acquirer would be bound by this policy for information collected before the transfer, and we would give notice before any change.

— 10 · RETENTION

How long we keep it

The project record is designed to be durable — that is the point of it. We keep a project's messages, media and derived record for as long as the customer's account is active, so the history stays complete.

The record is append-only: corrections are filed alongside the original rather than overwriting it. That means a deletion request is a deliberate act, not an edit — we remove the material and note that a removal occurred, so the record does not silently change shape.

We may keep information longer where the law requires it, or where it is needed to establish or defend a legal claim — and no longer than that.

— 11 · SECURITY

Honest about where we are

Dashboard access is by sign-in link scoped to a single organization or project. Data is encrypted in transit and at rest. Access to production data is limited to the people running the alpha, is granted on a need-to-know basis, and is logged.

We hold no security certifications and make no compliance claims. FieldThread is an alpha-stage product from a small company, and you should treat it that way. Do not send material to the project line that you would not want stored — payment card numbers, government identification, or medical information.

If personal information we hold is exposed in a breach, we will notify affected people and any authority we are required to notify, in the most expedient time possible and without unreasonable delay, as California law requires. Alpha customers will hear from us directly, not through a posted notice.

— 12 · YOUR CALIFORNIA RIGHTS

What you can ask for

If you are a California resident, the California Consumer Privacy Act gives you the rights below. We extend the same rights to anyone in the United States who asks, whether or not their state grants them — it is simpler than sorting people by ZIP code, and fairer.

How to make a request. Write to [email protected], or to the postal address at the bottom of this page. Because we operate exclusively online, email is our designated method. Tell us what you want, and tell us the phone number you texted from or the email address you wrote from, so we can find your entries.

How fast we answer. We acknowledge every request within 10 business days and tell you how we will handle it. We complete it within 45 calendar days. If a request is complex we may take up to 45 more days, and we will tell you why before we do. There is no charge; if a request is manifestly unfounded or repetitive we may charge a reasonable fee or decline, and we will say so and why.

Verification. We will ask you to confirm details that match what we already hold — typically the phone number or email the information is attached to. We ask for the least we can get away with, we do not require identity documents, and anything we collect to verify you is used only for that and then deleted.

If your request concerns a project record, that record belongs to the contracting company that engaged us. We will act on the contractor's instruction, and we will tell you that we have passed it on and to whom, so you are never left without a route.

You may also complain to the California Privacy Protection Agency or the California Attorney General. We would rather you came to us first, but you are not required to.

— 13 · DO NOT TRACK AND GPC

Some browsers send a Do Not Track signal or a Global Privacy Control signal. We do not track visitors across websites or over time, and we do not sell or share personal information, so there is nothing for either signal to switch off. We honor them by construction. If we ever add anything that a GPC signal would need to stop, we will process the signal as an opt-out and say so here.

We do not allow third parties to collect personally identifiable information about your activity across other sites through this one.

— 14 · CHILDREN

FieldThread is a tool for construction businesses. It is not directed to children, and we do not knowingly collect personal information from anyone under 16. If you believe a minor's information has reached us, write to [email protected] and we will delete it.

— 15 · WHERE WE OPERATE

FieldThread is offered in the United States only, and information is stored and processed in the United States. The service is not directed to, and we do not knowingly accept customers in, the European Economic Area, the United Kingdom, or other jurisdictions with data-export regimes we are not set up to satisfy. If you are outside the United States, please do not use the service or send us personal information.

The alpha is running in California. As we expand across the United States, additional state privacy laws will apply to us. Where another state gives its residents a right this policy does not already provide, we will extend it rather than run separate policies.

— 16 · CHANGES

FieldThread is in alpha and this policy will change as the product does. The effective date at the top of this page tells you which version you are reading. Material changes — anything that broadens what we collect, what we use it for, or who receives it — will be sent to alpha customers directly and posted here before they take effect. We review this policy at least once a year.