Privacy Policy

How Mowstitch uses information

Mowstitch uses information to provide account access and landscaping workflows, keep business records available to authorized users, process billing, send transactional email, respond to support and feedback, and measure the documented marketing and usage events described below.

Account and authentication information

Account information includes a user's name and email address, authentication records, email-verification records, and session information. Session records can include the IP address and user-agent reported by the request. This information supports account creation, sign-in, verification, and session handling.

Business and field-work records

Users can enter customer and worker contact details, service addresses and notes, work schedules, crew assignments, jobs, estimates, invoices, costs, and field checklist information. These records support landscaping operations and coordination inside the workspace.

Job check-in location

When a crew member initiates a job check-in and grants the browser's geolocation permission, Mowstitch requests precise location coordinates for that check-in. The current workflow makes a one-time position request; it does not continuously track a worker's location.

Images and feedback

Field checklist photos and screenshots attached to feedback are uploaded through the Polsia R2 file proxy. Feedback submissions can include a contact email and a description. These items help document field work and let Mowstitch respond to feedback.

Offline browser storage

For offline field work, the browser can keep job-checklist caches, drafts, and queued updates in localStorage. Queued checklist-photo metadata and photo blobs are kept in IndexedDB until they sync or are removed. This browser storage supports work when a network connection is unavailable.

Feedback and job applications

Feedback can include a contact email, description, and screenshot. Public hiring applications can include an applicant's name, email, optional phone number, location, availability, and skills. Mowstitch uses these submissions to review and respond to feedback or applications.

Billing and transactional email

Subscription checkout and customer invoice payments use Stripe-hosted billing flows. Mowstitch stores billing and payment status and identifiers. Transactional email supports email verification, worker invitations, and estimate and invoice messages.

Marketing and usage measurement

The Meta Pixel is loaded across the site and receives page-view events. Signup sends a Lead event, and successful subscription checkout sends a Purchase event. If a deployment enables the Polsia visitor beacon with its analytics slug, the beacon stores a random visitor ID in localStorage and sends that ID with the beacon.

Services used to provide Mowstitch

Polsia provides app hosting and database infrastructure, transactional email, the R2 file proxy, and the optional visitor analytics beacon. Stripe provides hosted checkout and billing flows. Meta provides the Pixel used for the page-view, signup, and successful-subscription events described above.

Privacy details to confirm before launch

• [PLACEHOLDER: confirm the privacy contact. The existing Mowstitch contact, mowstitch-2@polsia.app, is provisional.]
• [PLACEHOLDER: document verified retention, deletion, and export practices.]
• [PLACEHOLDER: confirm provider legal names, roles, and other required legal details.]
• [PLACEHOLDER: confirm storage regions.]
• [PLACEHOLDER: counsel to add privacy-rights language required in each applicable region.]