Privacy Policy
Last updated August 18, 2026
Overview
This policy explains what So So Deep Contractor Search("the Service"), operated by the operators of ContractorSearch, collects, why we collect it, and how we handle it. By using the Service you acknowledge this policy.
Information we collect
Account data. When you sign in (via WorkOS AuthKit), we receive identifiers such as your email address and a stable user id so we can create a wallet and keep your session.
Billing data. Payments are processed by Stripe. We store Stripe customer and subscription ids, credit grants, usage events, and invoice references. We do not store full card numbers.
Search data. We process the queries you submit, agent tool activity needed to answer them, and (if you are signed in) search history you choose to keep. Usage metering records token and Places call counts for billing.
Profile data. You can optionally save profile details - a display name, a property address, city/ZIP, property type, approximate year built, and your role (for example, homeowner). We use these to prefill Near Me and to give the search agent context for better recommendations. Saving your address is opt-out: you can turn it off or clear it anytime from your profile, and it is removed if you delete your account.
Technical data. Standard request logs may include IP address, user agent, and timestamps for security, rate limiting, and debugging.
How we use information
We use this information to provide searches, meter and bill usage, prevent abuse, improve reliability, and communicate about your account (for example, billing receipts from Stripe).
Processors and third parties
We rely on service providers to operate the product, including:
- WorkOS - authentication
- Stripe - payments and invoices
- Vercel / AI Gateway - hosting and model inference
- Google Places API - optional contractor contact and rating enrichment
- Neon - application database
Public contractor license data comes from state licensing boards - Arizona Registrar of Contractors and Washington State Department of Labor & Industries. Permit history comes from public city/county sources where available.
Google Places content
When enrichment runs, we fetch live place details from Google. We do not permanently store Places display content (phone, reviews, hours, etc.) in our database. We may store a mapping from license number to Google place_id so repeat lookups can skip an extra search. Google's terms also apply to that content.
Retention and account deletion
Account, wallet, and usage records are kept while your account is active and as needed for accounting, fraud prevention, and legal obligations (for example, payment records Stripe retains under its own policies).
You can delete your So So Deep Contractor Search account from Your account. Deletion removes your app profile, wallet, search history, and related personal data we control, except records we must keep for law, disputes, or accounting. Unused credits are forfeited on deletion and are not refunded as cash.
Sharing
We do not sell your personal information. We share data with processors listed above to run the Service, or when required by law.
What we never do
These are commitments, not current practice that might change quietly:
- We do not sell leads.
- We do not sell, rent, or share what you search or look up with contractors, insurers, brokers, or ad networks.
- We do not accept payment to change organic ranking. If we ever show a paid placement it will be labelled and kept out of the ranked list.
- We do not publish property-owner names.
- We do not publish the street addresses of job sites on public pages.
Data we publish about contractors
Separately from the information we collect about you, the Service publishes public records about licensed contractors. This section covers what those records are and where the limits sit.
What we publish. Business name, license number, class, status, issue and expiration dates, disciplinary history where the issuing board publishes one, city and ZIP, and aggregate counts of permitted work in the cities we cover. The source is each state board's public licensing file plus municipal building-permit records, used under the relevant state public-records law (in Arizona, A.R.S. § 39-121 et seq.). The purpose is to let the public verify a contractor before spending money.
Permit activity is aggregate. We publish how much permitted work a firm has done and what type it was. We do not publish the street addresses of the properties that work was done on, and we do not publish who owns them. Exact job locations are available only to signed-in users for their own research.
Some published names are individuals. A qualifying party is a named person, and a sole proprietor's business name is often their own name. These are published licensing facts. We keep them out of page titles, meta descriptions, and structured data, and the street address on a license file is shown only to signed-in users because for a sole proprietor it is frequently a home.
Disciplinary records. We publish the objective fields - that an action exists, its case number, and the license class - and link to the board's own record for the narrative. We do not reproduce the board's free-text description and we do not characterise an action beyond what the record says.
Corrections. If we have something wrong about your business, see our corrections policy. It sets out what we will change and what we will not.
Search engines and AI crawlers
Our public pages are open to search engines and AI crawlers by design, because being found and cited is how people reach the records. We publish /llms.txt and /agents.json describing how to read and cite the data correctly, and we ask that a citation name the dates shown on the page.
This does not extend to bulk extraction or republishing the compiled database, which our Terms address.
Security
We use industry-standard protections (encrypted transport, sealed session cookies, server-side secrets for Stripe and API keys). No method of transmission or storage is perfectly secure.
Children
The Service is not directed to children under 13, and we do not knowingly collect their personal information.
Changes
We may update this policy by posting a new version on this page with a revised "Last updated" date.
Contact
Privacy questions: email support@sosodeep.net. See also our Terms of Service.