Privacy Policy

Effective date: September 20, 2026
Last updated: October 26, 2026
Controller: TradesKnow, LLC (“TradesKnow,” “we,” “us,” or “our”)
Product: TradesKnow (tradesknow.com)
Contact: hello@tradesknow.com

This Privacy Policy explains how TradesKnow collects, uses, and shares personal information in connection with TradesKnow. It applies to the marketing site, user accounts, Ask, and Field if enabled for you.

It is a notice for a service that is free to start, with an optional paid plan (Field Paid). It is not a certification of CCPA, GDPR, PCI DSS, or SOC 2 compliance.

By using the Service, you acknowledge this Policy. Our Terms of Service and Acceptable Use Policy also apply.

1. Who is responsible

TradesKnow, LLC is the controller of personal information processed for TradesKnow unless we say otherwise (for example, if we later process data as a processor for a shop under a separate agreement — we do not claim that structure for Phase 1 users without a signed BAA/DPA).

Contact: hello@tradesknow.com.

2. What we collect

We collect information in these categories. We do not collect more than we need for Phase 1 operation.

2.1 Account

• Name, email address
• Shop or employer name if you provide it
• If you sign in with Google, the basic profile information Google shares with us (such as your name and email address). We do not ask for or store passwords.
• Role or trade you self-describe (e.g., electrician, HVAC), if collected

2.2 License metadata (if collected) — no images

Phase 1 does not collect license information. If we collect it later, it will be only:

• license number
• issuing state
• trade
• expiry date

We do not collect license images, ID photos, or scans in Phase 1. License-image intake is on hold. Do not email pictures of licenses to hello@tradesknow.com as a workaround.

License metadata is not state-board verification. We do not operate a government-status “Verified” badge for any trade.

2.3 Ask queries and Outputs

• Prompts you submit to Ask
• Outputs shown to you
• Provenance labels associated with an answer (Verified = drawn from verified corpus; Draft = model draft). These labels are not license or state-board verification
• Safety-refuse events (e.g., we refused a gas / live-panel / structural / confined-space how-to)

2.4 Field job data (if Field is enabled for you)

If Field is available — including if it is loopback-only or otherwise restricted — job captures may include:

• photos, measurements, equipment / part identifiers, voice notes, job notes, site or equipment context you capture
• device and app diagnostics needed to run Field

Field job captures are member job data. They are used to operate the Service for you, not to train models. See Section 4.

If Field is not enabled, we do not collect Field job captures.

Talking with Nico. If you use Talk with Nico, Field sends what you say to a speech-to-text provider (with the customer names and addresses from your jobs, so it writes them correctly), and Nico's answer to a text-to-speech provider, both listed on our [service providers](/service-providers) page. The audio is not kept, and the words are handled like your other job notes. They are never used to train AI models.

When you request an AI feature, we process the photos, messages and other job information you submit, together with relevant context, to provide that feature. We may use, replace or combine AI models and service providers for this purpose. The use, sharing and retention limits in this Policy continue to apply. Ordinary use of Field, including sending a photo for help, does not enroll your content in Teach or authorize model training.

2.5 Usage, device, and log data

• Approximate timestamps of access, feature used (Ask / Field / site)
• IP address, user-agent, device type, coarse location derived from IP if our host logs it
• Security and abuse logs (failed logins, rate limits, AUP flags)
• If you turn on Field notifications: a push subscription for your device (an address from your browser's push service and its encryption keys), your notification language and on/off choices, and, for Nico's morning note, only the next time to wake your device. The note itself is written on your device from the jobs saved there. Notifications we send do not include message text, job or customer details, or prices. You can turn notifications off in Account at any time; signing out or deleting your account removes them.
• If you use Field in a language other than the one something was written or said in: the text shown on your screen (your notes, Nico's answers, Crew messages and job names) is sent to our AI inference providers to be translated for display. The original stays exactly as written and is what Nico, prices and documents use. Translations are kept on your device, are never used to train AI models, and are not checked by a person.
• If you sign in to Field with a TradesKnow account to sync your devices: your Field jobs (notes, voice-note text, Nico's answers, photos, estimates, invoices and the customer details you entered), your rates, your profile and your Crew sign-in (your Crew name and team) are stored on our servers, encrypted, so every phone and computer you sign in on shows the same jobs and Crew chats. Your email address is used to sign you in with a one-time code, or Google confirms it if you choose Sign in with Google. You can remove your synced jobs from your account in Account at any time, and deleting your account removes them. Synced jobs are never used to train AI models. If you do not sign in, Field jobs stay on your device.

2.6 Cookies and similar technologies

See Section 10 for the cookies and browser storage we use.

2.7 Communications

• Emails you send us (support, Feedback)
• If we survey users, responses you choose to give

2.8 What we do not intentionally collect in Phase 1

• Full payment card numbers. Card details for Field Paid, and for your customers' payments, are entered on Stripe's pages and kept by Stripe (Sections 2.15 and 2.16).
• License images or government ID images
• Continuous or precise GPS tracking of your person as a product feature. Optional location for Nico is described in Section 2.12. A job-site geotag you choose to capture remains job data under the two-door rule.
• Children’s data (see Section 11)
• Special-category data we do not ask for. Do not submit health information, someone else’s Social Security number, or unnecessary bystander faces.

2.9 Crew chats (if you use them).

If you start or join a Crew chat, we store the name you enter, your messages, the job notes and photos you choose to share, invitation links, and Nico answers in that chat. When you share a job with a crew, the people on it also see the customer's name, address, phone number and email, and the job's prices (estimate and invoice totals, and amounts in Nico's answers on that job); keep that in mind before you add someone. Everything in a chat is visible to all of its current and future members. When a member asks Nico a question in Field, recent messages from that member's Crew chats and the shared job notes, including those details, can be sent with the question to our AI inference providers so Nico can answer with the team's context. Crew content is never used to train AI models. Names are self-reported; we do not verify identity, employment, or licenses. Chats expire after 90 days without activity. Copies that members already saved or downloaded cannot be recalled.

2.10 Text messaging (if you connect a phone)

If you connect a phone to Field messaging, we collect your mobile number, the messages and media links you send and receive through Field messaging, timestamps, delivery status, and records of your consent and of any opt-out. If a business number is assigned to you, we also collect the phone numbers of people who text that number and the content of those conversations, which we process on your behalf.

We use this information only to deliver messages, answer your requests with Nico, show you drafts to review, prevent abuse, and follow messaging rules. Messages you send Nico, and customer messages you ask Nico to draft a reply to, translate, or answer from, are processed by our AI inference providers to produce a response. Messaging content is job data under Section 4.1 and is never used to train AI models.

Mobile information collected for text messaging is not shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third parties. We do not sell phone numbers or messaging data.

If you text a business that uses Field, that business decides how to reply to you. We process your number and messages on its behalf to deliver them and, when the business asks, to help it draft or translate a reply. The business reviews and sends every reply. Reply STOP to stop texts from that number. For privacy requests, contact the business or us at hello@tradesknow.com.

Messages saved in the Field app on your device, or in a backup you set up (such as your own Google Drive), stay there under your own settings and are not removed by the retention periods in Section 6.

2.11 Google Calendar (if you connect it)

If you tap Connect Google in Account and complete Google's consent screen, Field can read the calendar data below. Signing in with Google does not start this.

2.12 Location for Nico (optional)

Location is optional. You can decline and still use Field. We may ask once for location permission after you agree to Field, and you can change or clear it later.

Your area. In Field Classic's Account & Settings you can share an area for Nico. If you use your device location for that, Field reads your coordinates once, sends them through Field to the U.S. Census Geocoder, and keeps only a coarse place: city, county, state, and ZIP. Those coordinates are discarded after that lookup. You can instead set a ZIP or state yourself.

A job's location. You can also set the location of a specific job, either by typing the town and state or by using your device location at the job and confirming it. When you use your device location for a job:

• Field sends your coordinates, rounded to four decimal places (roughly 10 meters), through Field to the U.S. Census Geocoder to find the town, county, and state.
• After you confirm it, the job's town, county, state, and those rounded coordinates are saved with that job on your device.
• The confirmed job location, including those rounded coordinates, is sent with the questions you ask Nico about that job, so Nico can consider state and local codes and the weather at the job.
• If you turn on weather for your jobs, Field sends those rounded coordinates through Field to the U.S. National Weather Service (NWS) to get the forecast and active alerts. Field may check for weather on its own while a job with a confirmed location is open, so it can show weather heads-ups.

We do not track your location continuously, and we do not read your location in the background.

Job map (Field v3, optional). The job map is off until you turn it on. When it is on, Field sends a job's street address, and nothing else about the job, through Field to the U.S. Census Geocoder to find that address on the map. The map point it returns is kept only on your device, is not added to the job, and is not synced to your other devices. Map images are loaded from OpenStreetMap's tile servers, which, like any website, receive your device's IP address and which part of the map is shown. If you tap "Center on me," Field reads your device location once to show it on the map; it is not sent anywhere and is forgotten when you leave the app. Turning the map off in Account erases the saved map points.

Weather for your jobs (Field v3, on unless you turn it off). To show the weather at each job, Field sends the job's street address, and nothing else about the job, through Field to the U.S. Census Geocoder to find where it is. Field then sends that point, rounded to two decimal places (roughly 1 kilometer), through Field to the U.S. National Weather Service (NWS) to get the forecast and active alerts, and checks again from time to time while you use Field. The point and the weather are kept only on your device; they are not added to the job and are not synced to your other devices. If you allowed location, Today also shows the weather where you are: Field reads your device location at most every 15 minutes while Today is open and sends it, rounded the same way, through Field to the NWS; your location is not saved apart from that rounded point with its weather on your device. You can turn this off in Account under Weather for my jobs, which erases the saved weather and, if the map is off, the saved points.

Weather you ask Nico about. When you ask Nico about the weather in a town or ZIP code, Field finds that place in a list of U.S. towns and ZIP codes kept on TradesKnow's servers (nothing is sent to look it up) and sends its point, rounded to two decimal places, through Field to the NWS to get the forecast for that answer. If you name no place, Nico uses the job's confirmed location, or asks which town. The forecast is not saved.

If no location is set, Nico can still use, in this order: a job address you have entered, a company or business address you have saved, or a ZIP or state you set yourself.

A place is not a verified authority having jurisdiction (AHJ), and a weather snapshot is not a jobsite safety assessment. Location and weather information are job data under Section 4.1. They are never used to train AI models.

2.13 Estimate approval links (Field)

When a tradesperson signed in to a TradesKnow account sends an estimate from Field, the message can include a link (for example, tradesknow.com/e/garcia-k7q2) where their customer can read the estimate and approve it, decline it, or ask a question, without an account. The link is the customer's last name and four random characters.

• What the link shows. A copy of the estimate as it was sent: the business name and phone number, the customer's name, the job title, the line items, the totals, and the notes printed on the estimate. It does not show the job's street address, the customer's phone number or email, photos, or the job's notes. When the tradesperson sends a changed estimate, it is saved as a new version under the same link, and the customer is asked to approve it again; earlier versions stay in the record.
• What we record. When the link is first opened; whether the customer approved, declined or asked a question; the name they typed to approve; any message they wrote; the date and time; the exact version of the estimate they saw (identified by a fingerprint of its contents); a keyed fingerprint of their IP address (not the address itself); and their browser's user agent. A tradesperson can also mark an estimate approved when the customer said yes another way, and the record shows that the tradesperson marked it.
• Replies, changes and sign-off. A customer can also approve by replying YES to the text with the link; their reply is kept with the approval. When the tradesperson changes an approved estimate, the customer sees what changed and approves the new version. At the end of a job, the tradesperson can send a similar link where the customer confirms the work is done; that confirmation is kept the same way.
• Who sees it. Anyone who has the link can see the estimate and whether it was approved. The tradesperson's account sees the status, the typed name and any message.
• No payments. The link does not take or move money. The agreement is between the tradesperson and their customer; TradesKnow keeps the record and is not a party to it.
• How long. Approval records are kept for 3 years from the last version sent, then deleted, so both sides have a record of what was agreed even if the job is deleted from a device. Requests about a record can be sent to hello@tradesknow.com and are handled under Section 8.
• Never training data. Approval records are member job data under Section 4.1 and are never used to train AI models.

2.14 Time, punch lists and receipts (Field)

• Clock. When you tap Start or Stop on a job, or tell Nico you are starting or stopping, Field keeps those times on the job. Field never reads your location for this and nothing runs in the background.
• Crew hours. On a job shared with a crew, each crew member's start and stop times and hours go to the job's owner, and only the owner sees them. You see your own times. Hours shown in Field are a work record for the job, not a payroll or timekeeping system.
• Punch lists and day logs. Punch-list items you type or say, the photos you add when you check them off, and the daily logs you choose to save are kept on the job.
• Receipts and job cost. When you send Nico a photo of a receipt, Nico reads the store, total and date; the amount counts toward the job's cost only after you confirm it. The job cost view, including what an hour of work costs you, is visible only to the job's owner.
• These are member job data under Section 4.1 and are never used to train AI models.

2.15 Connections you turn on (Stripe, QuickBooks)

• Stripe (your own account). If you connect your Stripe account or set one up in Field, Field asks Stripe to create an invoice on your account for each invoice you send by card: your customer's name, email and phone (when you entered them), their language, the invoice lines and amounts, the due date and a job reference. Field later asks Stripe which invoices were paid so it can record the payment, and Stripe tells us when an invoice is paid or a payment fails. If you set up Stripe inside Field, Stripe collects the information it needs to open and verify your account (for example your name, business details, tax ID and bank account) directly from you on its own forms; TradesKnow receives your Stripe account ID and whether it can take payments, not those details. Your customer pays you through Stripe; Stripe's privacy notice applies to what Stripe collects. TradesKnow never sees or stores card numbers, does not hold the money and takes no fee.
• QuickBooks Online. If you connect your QuickBooks company, Field sends the invoices you send and the payments you record: the customer's name, email and phone, the invoice lines, amounts and dates.
• We keep the access tokens these services give us, sealed, only to do these things for you. You can disconnect either one in Account at any time; we then ask the service to revoke access and delete our tokens. Records already created in your Stripe or QuickBooks account stay there under your control.
• These connections are optional and off until you turn them on. Data sent through them is never used to train AI models.

2.16 Field Paid (if you subscribe or use a code)

• Checkout and billing are run by Stripe on TradesKnow's Stripe account. You enter your card and billing details (such as name, email and billing address) on Stripe's pages, and you manage or cancel your plan on Stripe's billing page. We send Stripe only an internal account ID, not your name, email or phone.
• What we keep: your plan (Free or Paid), how you got it (subscription, code or crew coverage), the Stripe customer and subscription IDs, status, renewal or end date and whether a payment failed; for codes, the date you used one and a one-way digest of it (we cannot read codes back); for crew coverage, which accounts your plan covers; and daily counts of Free-limited actions (such as Nico questions) so the limit works. If a payment of yours is disputed, refunded or flagged by Stripe for fraud, we keep a record of that event.
• Why: to provide the plan you chose, apply Free limits, prevent abuse of codes and coverage, handle disputes, and meet tax and accounting duties.
• Stripe also processes billing information under its own privacy notice, including for fraud prevention. Billing records are never used to train AI models.

2.17 Street suggestions (Field v3)

When you are signed in to a TradesKnow account and type a street into a Field address box, Field sends what you have typed (up to 120 characters), through Field, to Google's Places service to suggest matching U.S. addresses. When you pick one, Google returns its street, town, state and ZIP, which fill the address boxes. Nothing else about the job or the customer is sent, and Field does not keep or log what you typed or the suggestions. The request comes from TradesKnow's servers, so Google does not receive your device's IP address; Google's privacy policy applies to what Google processes. The address you save is job data under Section 4.1 and is never used to train AI models. If you are signed out or offline, there are no suggestions and you type the address yourself. When you ask Nico to set or change an address, Field sends that address (up to 120 characters) to Google's Places service the same way to check it; the match Google returns is saved with the job, and Nico tells you what Google found.

2.18 What Nico remembers about you (Field v3)

To serve each tech better over time, Nico keeps a short list of your standing preferences and ways of working: for example how you price and bill (rates, minimums, trip fees, terms), the suppliers, brands and materials you use, your service area, rules you give him ("from now on…", "always…", "never…") and how you like answers (short, spoken, detail, language). He learns them automatically from what you tell him in Field and from prices you set by hand for the same line on several jobs, and each answer shows what he kept. He does not keep a customer's details, contact information about anyone, or personal matters such as health or family. The list is kept with your TradesKnow account (encrypted, like your synced jobs) and on your devices, and it is sent with your questions to the AI provider that answers for Nico so the answer fits how you work. Your conversation with Nico on Today is kept with your account the same way, so it follows you to every device you sign in on. You can see, change and remove anything Nico remembers, add something yourself, turn learning off, or have him forget everything, in Field under Account → What Nico knows. It is kept for the life of your account, or until you remove an item, have Nico forget everything, or delete your account. What Nico remembers is your job data under Section 4.1: it is never shared with your crew or your customers and never used to train AI models.

3. Purposes of use

We use personal information to:

We do not sell personal information. We do not use TradesKnow as a lead-gen broker for third-party advertisers.

4. Two-door training rule (core privacy promise)

4.1 Door 1 — member job data: no training

Member job data and Field job captures are never used to train, fine-tune, or otherwise improve foundation models or TradesKnow’s task models.

That includes Ask prompts that are your job-site questions to the extent they are your member work product, and all Field captures. We may process that data through subprocessors to generate an answer or to store a job for you. That is operation of the Service, not training.

We contract with model and hosting providers to prohibit their use of that data to train their models, to the extent we send it to them. If a provider cannot accept that restriction, we will not send member job data to that provider.

4.2 Door 2 — expert / Teach content only, and only when cleared

The only intended path for using content to train or evaluate models is consented expert / Teach content under separate contributor terms.

Those contributor terms are not in production as of this Policy. Until a Teach agreement is in force:

• we do not treat your ordinary Ask/Field use as training consent;
• we do not present a production Teach clickwrap;
• we do not train on member job data “because an expert might have typed it.”

If Teach launches later, consent will be separate, specific, and withdrawable as that agreement provides.

4.3 Feedback vs. job data

Product Feedback (e.g., “this button is broken”) may be used to improve the product. We will not re-label Field job captures as Feedback to evade Section 4.1.

5. Sharing

We share personal information only as follows:

Processors / service providers. Hosting, database, sign-in, text messaging, payment processing, and AI model-inference providers that process data on our instructions, listed in our Service Provider Disclosure. They may not use member job data to train their models for their own purposes.

Legal / safety. If we believe disclosure is required by law, valid legal process, or to protect a person from serious harm, prevent crime, or enforce our Terms (including safety no-gos).

Corporate transaction. If TradesKnow is involved in a merger, acquisition, or asset sale, information may transfer under continuing restrictions consistent with this Policy (including the two-door rule).

With your direction. If you ask us to send something to a shop admin or co-worker we have jointly provisioned.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising as a Phase 1 practice. If that ever changes, we will update this Policy and provide required opt-out.

Our Service Provider Disclosure identifies providers and their roles. We update it as providers change; the limits and notice obligations in this Policy continue to apply.

6. Retention

We may retain records as required by law or to resolve disputes.

How long it stays

Limited Use commitment

Field's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

1. Google user data is used only to provide or improve the user-facing features described above, which are the features the person connected.
2. Google user data is not transferred to others except as needed to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with the user's explicit prior consent.
3. Google user data is not used for serving advertisements.
4. No human reads Google user data, unless the user gives explicit consent for a specific message, it is necessary for security purposes such as investigating abuse, to comply with applicable law, or the data is aggregated and anonymised.

7. Security

We use administrative, technical, and organizational measures appropriate to a small service (access control, TLS in transit, least-privilege for staff; sign-in is handled by Google and we do not store passwords). No method of transmission or storage is 100% secure. Field job photos can be sensitive; treat devices accordingly.

You are responsible for your account credentials and for job-site photos you choose to capture (bystanders, homeowner interiors, etc.).

Report suspected security issues to hello@tradesknow.com. This Policy is not a bug-bounty charter.

8. Your rights — access, delete, export

Subject to law and to verifying your request:

• Access. You may request a copy of personal information we hold about you.
• Correction. You may request correction of inaccurate account or license metadata.
• Deletion. You may request deletion of your account and personal information, subject to legal holds, safety/security logs we must keep, and backup cycles.
• Export. You may request an export of account data and User Content you submitted (Ask history and Field jobs if stored), in a reasonable machine-readable format we support.

Email hello@tradesknow.com from the address on your account. We may decline requests that are unlawful, abusive, or would compromise others’ privacy or our security controls.

If you are a resident of a state with additional consumer privacy rights (e.g., California), we will not discriminate against you for exercising them. Phase 1: we do not sell personal information; “Do Not Sell or Share” is therefore not a monetization toggle, but you may still email us to record a preference.

We do not currently operate an automated “appeal an AI decision that produces legal or similarly significant effects” because TradesKnow does not decide licenses, credit, employment, or housing. Outputs are informational. Safety refuses are product rules, not credit scores.

9. Automated processing and Ask labels

Ask uses automated systems to draft answers and to refuse certain hazardous how-to. That is not a consumer-credit decision.

“Verified” / “Draft” on Ask answers refer only to provenance (verified corpus vs. model draft). They are not a verification of your license, a state board result, or an AHJ approval.

10. Cookies and analytics

Phase 1 does not use analytics tools, advertising pixels, or third-party analytics or advertising cookies, and the marketing site does not identify visitors to ad networks.

The Field app saves your job notes, language choice, and app settings in your browser's local storage on your device so the app works. If you choose Sign in with Google or connect Google Drive, Google's sign-in service runs on the page, and Google's privacy policy governs any cookies or storage Google sets. Our hosting provider may use strictly necessary technical data, such as your IP address, to deliver and secure the site.

If we add an analytics or advertising tool, we will name it here before we turn it on and, where the law requires, ask for your consent or honor your opt-out.

11. Children

The Service is not for anyone under 18. We do not knowingly collect personal information from children. If you believe a minor has created an account, contact hello@tradesknow.com; we will delete it.

12. International

We are a U.S. company (TradesKnow). The Service is operated from the United States. If you access it from outside the U.S., you understand information will be processed in the United States, where laws may differ from those in your country.

Phase 1 is not offered as a GDPR-established EU service. We have not appointed an EU representative. If we later onboard EU/UK users in a systematic way, we will revise this Policy first (SCCs, representative, lawful basis).

13. Changes

We may update this Policy. Material changes will be noticed in-product or by email a reasonable time before they take effect, unless the change is required by law or needed for safety or security. The “Effective date” above will change.

The two-door rule (no training on member job data / Field captures) will not be weakened by a quiet Policy edit. If that promise ever changed, it would be a material change requiring clear notice — and it is not contemplated for this launch.

14. Contact

TradesKnow, LLC
Attn: TradesKnow Privacy
Email: hello@tradesknow.com

For license, permit, or code questions, contact your licensing board or AHJ — not TradesKnow as a licensing authority.