Privacy policy

Village makes operations software for residential service businesses: scheduling, quotes, invoices, payments, crew coordination, customer records, booking pages, lead forms, messaging, and an AI assistant. This policy uses these terms:

• Provider: a business (or individual operating a business) that creates a Village account to run its business on the Services, including the account owner and any co-owners.
• Team Member: a person a Provider adds to its account, such as crew, a technician, or a manager.
• Customer: a Provider’s own customer or prospective customer, typically a homeowner, who interacts with the Provider through Village hosted pages, forms, texts, or emails. Customers do not have Village accounts.
• Visitor: anyone who visits our websites without an account.

Village has two roles.

• Village as a business (controller). We decide how to use personal information about Providers, Team Members, and Visitors, and information we use to run, secure, and improve the Services. This policy describes those practices.
• Village as a service provider (processor) to Providers. When a Provider stores information about its Customers or Team Members in Village (for example customer contacts, addresses, job history, notes, invoices, or message threads), we process that “Customer Data” on the Provider’s behalf and under our agreement with the Provider. The Provider decides what it collects and how it uses it. The Provider’s own privacy practices apply to that use.

If you are a Customer and want to access, correct, or delete information a Provider holds about you, please contact that Provider. If you contact us, we will forward your request to the Provider or help as our agreement with the Provider and the law allow.

a. Information Providers and Team Members give us

• Account and sign-in: name, email address, phone number, password (stored hashed by our authentication provider), and date of birth (used to confirm age eligibility). On our website you may sign in with Google. In the iOS app you sign in with a phone code or email and password.
• Business profile and booking page: business name, bio, logo and photos, service area (ZIP codes), service menu and prices, availability, portfolio photos and videos, social links, reviews, and other content you choose to publish. Booking page content is public.
• Documents: licenses, insurance certificates, and similar documents you upload. Optional student verification documents, if you use that feature. Stored privately.
• Payments and payouts: to accept payments from Customers, a Provider opens a Stripe account through Village. Stripe collects identity, tax, and bank information directly. We receive account status, capabilities, and verification requirements, not full bank or card numbers.
• Subscription information: your plan, add-ons, billing history, and usage (for example quote, invoice, crew seat, and AI assistant usage). Web billing is handled by Stripe. In-app purchases are handled by Apple and our in-app purchase provider, RevenueCat.
• Team Member information (entered by a Provider or the Team Member): name, phone, email, photo, skills, availability, pay rates, payout method or handle, job assignments, work-time records (for example clock in, pause, and complete events and times), job photos they upload, and messages.
• Integrations you connect: for example a Google Business Profile connection (to request or show reviews), webhook destinations, CRM connectors, and external AI apps you authorize (see Section 4).
• Support and communications: messages you send us, feedback, and survey or call responses, including when you schedule a call with us through Cal.com.

b. Customer Data a Provider stores in Village

On a Provider’s behalf, we store and process: Customer names, phone numbers, email addresses, service addresses and the coordinates derived from them, notes the Provider writes (which may include site access details such as gate codes), custom fields the Provider defines, job and appointment history, quotes, invoices, payment status, service agreements, photos, reviews, form submissions, and message and email threads between the Provider, its Team Members, and the Customer.

c. Information Customers give through hosted pages and forms

When you use a Provider’s booking page, lead form, quote or invoice link, offer (“Present”) link, or review link, we collect what you submit on the Provider’s behalf. That may include your name, phone, email, address, message, photos, the services you choose, and payment (processed by Stripe on the Provider’s Stripe account). When you accept an offer, we also record your typed name, the time, the version of terms you accepted, your IP address, and your browser user agent, as a record of the acceptance.

d. Information collected automatically

• Device and usage information: IP address, browser and device type, operating system, app version, pages and screens viewed, actions taken, referring URLs, and timestamps.
• Analytics and session replay: we use PostHog to understand how the Services are used. This includes session replay, which records page interactions such as clicks, scrolling, and page changes. Text typed into input fields is masked before it leaves your browser. See Section 8.
• Attribution information on forms and booking pages: when you arrive at a Provider’s booking page or lead form, we may record campaign parameters (such as UTM values), ad click identifiers (such as gclid, fbclid, msclkid, or ttclid), the referring page, and the landing page. This lets the Provider see which marketing brought in the request. It is stored in your browser’s session storage and attached to your submission.
• Push notification tokens: if you allow notifications in the iOS app, we store a device token so we can send you notifications through Apple.
• Error diagnostics: crash and error reports, which may include technical request details.

e. Information from third parties

• Sign-in details from Google (on the web).
• Payment, payout, and verification status from Stripe. Purchase and subscription status from Apple and RevenueCat.
• Address suggestions, place details, and coordinates from Google Places. Travel times and routes from Google Routes.
• Reviews and business information from a connected Google Business Profile.
• Information a Provider imports or enters about its Customers and Team Members.

We use personal information to:

• provide the Services, including scheduling, maps and routes, quotes, invoices, payments, booking pages, forms, offers, reviews, crew coordination, and messaging;
• send and receive texts and emails on behalf of Providers, and send account, security, and service notices;
• operate our AI assistant and AI drafting features (Section 5);
• process subscriptions, usage-based charges, and platform fees, and help Providers accept Customer payments;
• verify eligibility, including age and, for Minor Providers, parental or guardian consent;
• provide support and respond to requests;
• measure, debug, secure, and improve the Services, including through analytics and session replay;
• detect, prevent, and respond to fraud, abuse, spam, and security incidents;
• comply with law, tax, and accounting obligations, and enforce our agreements; and
• for any other purpose we describe when we collect the information or with your consent.

Customer Data is used to provide the Services to the Provider that controls it, and as our agreement with that Provider permits. That includes securing the Services, preventing abuse, and producing aggregated or de-identified statistics. We do not use Customer Data to market to Customers on our own behalf.

We do not sell personal information. To measure our own ads, we share limited information with Meta from our marketing pages and signup (see section 8). Some state laws call that “sharing” for cross-context behavioral advertising, and you can opt out of it. We never share Customer Data or anything from booking pages for advertising. We share information as follows.

With the Provider, its Team Members, and its Customers

• A Provider and the Team Members it authorizes can see Customer Data in its account. Team Members may receive job details, including the Customer’s first name, service address, instructions, and access notes the Provider shares.
• Customers see the Provider information the Provider publishes or sends, such as its booking page, quotes, invoices, and messages.
• When a Customer submits a form, booking, or acceptance, it goes to the Provider.
• Booking pages, portfolios, and reviews a Provider publishes are public.

With integrations a Provider chooses

If a Provider turns on an integration, we send the relevant information where the Provider directs. Examples:

• Webhooks and CRM connectors (for example Housecall Pro): lead and form submissions, including contact details, address, and attribution information.
• Connected AI apps: if a Provider connects an AI app such as Claude or ChatGPT through our Model Context Protocol (“MCP”) connector, that app can access the Provider’s business information as described in Section 5, Connected AI apps.
• Google Business Profile: to request, sync, or display reviews.

The recipient’s own terms and privacy practices then apply.

With service providers (sub-processors)

We use vendors to operate the Services. They may process personal information only to provide services to us.

Stripe also acts as an independent provider of payment services under its own terms and privacy policy. So does Apple for App Store purchases.

Embedded third-party content

Booking pages may display content embedded from YouTube or Instagram. When that content loads, those companies may collect information such as your IP address under their own policies.

Legal, safety, and business transfers

We may disclose information to comply with law or legal process, to respond to lawful government requests, to meet tax and reporting obligations, to protect the rights, property, or safety of Village, our users, or others, or in connection with a merger, financing, acquisition, reorganization, or sale of assets. We may also share information with your consent.

Village includes AI features, including our assistant (“Ask Village” or “Vinny”). They can summarize a Provider’s day, answer questions about its business, draft quotes, invoices, offers, and messages, and help interpret incoming messages. To do this, we send relevant content to our AI model provider, Anthropic. That content includes the Provider’s instructions and relevant Customer Data and message text.

• The Provider stays in control. Drafts are not sent to Customers until the Provider confirms, except for time-sensitive relays the Provider directs. Settings changes and marketing outreach require approval.
• AI can be wrong. Outputs may be inaccurate or incomplete and should be reviewed.
• No automated decisions with legal effects. We do not use AI to make decisions about you that produce legal or similarly significant effects.
• Model training. We do not permit our AI model provider to use content from the Services to train its general models.

Connected AI apps (Claude, ChatGPT, and others)

A Provider can connect Village to an AI app it already uses, such as Claude or ChatGPT, through our MCP connector. The Provider signs in to Village and approves the connection. The AI app never receives the Provider’s Village password, and Village never receives the Provider’s password for the AI app.

• What a connected app can access. Only the Provider’s own business account. It can read the business summary, jobs and schedule, availability, services and prices, Customers (including contact details and notes), quotes, invoices, items that need the Provider’s attention, and AI assistant usage. With the Provider’s permission it can also add and update Customers and notes, create draft quotes and invoices, and add jobs to the calendar. Anything it sends to a Customer, such as a quote, an invoice, or a payment reminder, goes out only after the Provider confirms that specific message in the AI app.
• Where the information goes. Information the AI app requests is sent to the company that runs that app (for example Anthropic for Claude, or OpenAI for ChatGPT) and is handled under the Provider’s agreement with that company and its privacy policy. Village does not control how that app stores or uses it.
• What Village keeps. For each request we log which connected app made it, which action it used, whether it succeeded, when, and which record it created or changed. We use this log for security, support, and to show the Provider its connected apps. We do not receive or store the Provider’s conversation with the AI app. We keep the log while the Provider’s account is active and delete it with the account.
• Labels. Records an AI app creates are labeled for the Provider, for example “Drafted in Claude.” Customers never see this label.
• Turning it off. A Provider can disconnect an app at any time in Settings, Connected apps, or from the AI app itself. Access stops right away.
• No sale, no training. We do not sell information accessed through connected apps or use it to train AI models.

Village SMS Program

Village operates a text messaging program (the “Village SMS Program”). Through it, Village sends texts on behalf of Providers to Customers and Team Members, and to Providers themselves. Messages are sent from a shared Village number, currently +1 (404) 918-2012, through our messaging provider, Blooio. Messages may be sent as SMS, MMS, iMessage, or RCS and may include group conversations.

• Message types: appointment and booking confirmations, reminders, quotes, invoices and receipts, payment links, review requests, job and scheduling updates, crew dispatch and status messages, account and security codes, replies from the Provider or its AI assistant, and, only with separate consent, promotional messages from a Provider.
• How consent is given: by providing your phone number on a booking page, form, or account signup where messaging is disclosed, by texting the Village number, or by giving your number to a Provider that has permission to text you about your service. Consent is not a condition of purchase.
• Frequency: varies with your activity and appointments.
• Rates: message and data rates may apply.
• Opt out: reply STOP to any message. Because many Providers use the same Village number, replying STOP stops texts from the Village number for every Provider using it. Reply START to opt back in. For help, email will@jobsonvillage.com.
• Carriers are not liable for delayed or undelivered messages.

Mobile information is not shared with third parties or affiliates for their marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third party, except the vendors that deliver the program for us.

We store message content, media, and delivery records to deliver messages, show conversation history to the Provider, resolve disputes, prevent abuse, and meet legal obligations.

Email

We send account emails (sign-in, password reset, security, and consent invitations). On behalf of Providers, we also send quotes, invoices, receipts, calendar invitations, reminders, and review requests. You can unsubscribe from marketing email using the link in the message. Transactional emails about your service or account may still be sent.

Quiet hours

Providers can set quiet hours. Non-urgent messages to Customers are then held until the next allowed time.

The Village app does not collect your device’s GPS location.

We do use location information derived from addresses:

• service addresses a Provider or Customer enters, which we look up through Google Places to get structured addresses and map coordinates;
• a Provider’s starting location for route planning, if set; and
• service-area ZIP codes.

We use this to show jobs on a map, plan routes, and estimate travel time (through Google Routes). We may also derive approximate location from IP address for security and analytics.

We use:

• essential cookies and local storage for sign-in, security, preferences, and language;
• analytics cookies and similar technologies (PostHog) to measure usage and record masked session replays; and
• session storage on booking pages and forms to keep campaign attribution for the length of your visit; and
• advertising measurement (Meta Pixel and Meta Conversions API) on our own marketing pages and signup, to learn which of our ads bring in new Providers. When a Provider signs up, we send Meta a signup event with their email and phone number in hashed form and the ad click identifier, if there is one.

We do not load ad pixels inside the Village app, in our iPhone app, on Provider booking pages, or on any page a Provider’s Customers use. If your browser sends a Global Privacy Control signal, we do not load the Meta Pixel and do not send your signup to Meta.

Your choices: you can block or clear cookies in your browser settings. Blocking analytics cookies will not affect core features.

Provider websites: if a Provider embeds a Village form on its own website, the Provider is responsible for the privacy notices and cookie consents on that site.

We keep personal information only as long as reasonably needed for the purposes in this policy, unless the law requires or permits longer.

Deleting your account (Providers). In the app or on the web, go to Settings > Account and deactivate your account. We will verify it’s you with an email code. Your account is signed out, your booking page is taken offline, and your data is scheduled for permanent deletion after 30 days. Contact us during that window if you change your mind. Some records are kept longer where the law requires (for example financial records) or where Stripe or Apple keep their own records.

Customer Data is deleted with the Provider’s account, or earlier if the Provider deletes it. Customers should ask the Provider directly to delete their information.

Depending on where you live, you may have the right to:

• know and access the personal information we hold about you, and get a copy;
• correct inaccurate information;
• delete your information;
• opt out of the sale of personal information (we do not sell it), sharing for cross-context behavioral advertising, or targeted advertising. Turning on Global Privacy Control in your browser opts you out of the ad measurement in section 8, or you can email us;
• limit use of sensitive personal information (we use it only as needed to provide the Services); and
• appeal a decision we make about your request.

How to make a request: email will@jobsonvillage.com with the subject “Privacy Request.” We will verify your identity before acting. You may use an authorized agent where the law allows. We will not discriminate against you for exercising your rights.

Customers: where we hold your information as a service provider to a Provider, we will direct your request to that Provider or help it respond.

Other choices:

• Update your account information in Settings.
• Reply STOP to texts.
• Turn off push notifications in your device settings.
• Disconnect integrations or connected AI apps in Settings.

The Services are not directed to children under 16, and we do not knowingly collect personal information from anyone under 16.

Providers aged 16 or 17 (“Minor Providers”) may use the Services only after a parent or legal guardian reviews and approves their participation. As part of that process we collect the parent or guardian’s name and contact details, a record of their consent, and an identity document they upload, which is stored privately.

A parent or guardian of a Minor Provider may contact us to review, correct, or delete the Minor Provider’s information. Deleting it closes the Minor Provider’s account. The parent or guardian may also be able to view some account activity through the Village messaging program.

If we learn we collected personal information from a child under 16, or from a Minor Provider without the required consent, we will delete it.

We use administrative, technical, and physical safeguards designed to protect personal information. These include encryption in transit and at rest, hashed passwords, private storage with time-limited signed links for documents and job photos, signed webhooks, access controls scoped to each Provider account, and monitoring. No system is completely secure, and we cannot guarantee absolute security. If we learn of a security incident that affects your personal information, we will notify you as the law requires.

Village is based in the United States, and our vendors primarily process information in the United States. If you use the Services from outside the United States, your information will be transferred to and processed in the United States.

We may update this policy from time to time. If we make material changes, we will give notice before they take effect, for example by email, in the app, or on this page. The “Last updated” date shows when the policy last changed. We keep prior versions and will provide them on request.

Village Technology Services, LLC
131 Continental Dr, Suite 305, Newark, DE 19713, New Castle County
Email: will@jobsonvillage.com (privacy requests: subject “Privacy Request”)
Text: +1 (404) 918-2012