JobFlow AI

Privacy Policy

This page describes the information JobFlow AI processes for a service business: customers, jobs, estimates, invoices, payments, staff accounts, notifications, and optional AI features.

Complete these details before publishing

  • The legal name of the business that operates JobFlow AI
  • A real contact method for privacy, support, and deletion requests
  • The business location and which law applies
  • Any refund policy you intend to offer
  • Whether the support, phone, or uptime promises shown on the pricing page are actually offered

These are starter policies for the product as it works today. They are not legal advice.

Who this covers

JobFlow AI is used by a business and its staff. The business may also invite its own customers to book a visit, review an estimate, or pay an invoice. This policy describes both of those uses. The operator of JobFlow AI is [Legal entity name — complete before launch].

Information the product processes

  • Staff account details used to sign in, including name and email, handled by the sign-in provider.
  • Business records the company enters, such as customers, jobs, schedules, estimates, invoices, notes, and photos.
  • Customer details collected on a public booking page or customer portal, such as name, email, phone, address, and the requested service.
  • Payment records: amount, status, method, and Stripe identifiers. Card numbers are entered on Stripe’s pages. JobFlow AI stores the payment record, not the full card number.
  • Messages the product sends when email or text messaging is configured, and whether those messages were delivered, opened, or bounced when the provider reports that status.
  • Text a person submits to an optional AI feature, such as a request to draft a job description.

How that information is used

The product uses this information to run the workspace the business signed up for: scheduling work, preparing estimates and invoices, recording payments, inviting staff, sending notifications the business has turned on, and showing each company its own records. Optional AI features send the submitted text to the AI provider so it can return a draft. That draft can be wrong and should be reviewed before it is sent to a customer.

A business that stores its customers’ information in JobFlow AI is responsible for having permission to collect and use that information.

Service providers

JobFlow AI uses these providers for the product as it is built today:

  • Clerk, for staff sign-in.
  • Supabase, for the database and for private storage of uploaded files such as job photos.
  • Stripe, for subscription billing and card payments on invoices.
  • Resend, for email, when email sending is configured.
  • Twilio, for text messages, when text messaging is configured.
  • OpenAI, for optional AI features, when that feature is configured and enabled for the plan.

The application is hosted where the operator deploys it. The current deployment notes use Vercel. A provider receives only the information needed for its part of the product. Email, text messaging, and AI features do not run unless those services are configured.

Security practices in the product

Staff sign in through Clerk. JobFlow AI does not store staff passwords. The application separates records by company, so one company’s customers, jobs, estimates, invoices, and files are not shown in another company’s workspace. Uploaded files are stored in private storage and opened with short-lived links. Card details are collected by Stripe.

JobFlow AI has not published a security certification or an uptime guarantee. These practices are not a promise that information cannot be lost, interrupted, or accessed without permission.

Retention and deletion

Business records remain in the company workspace while that workspace is in use. The product does not currently include a self-serve control to delete a company or download a full copy of the workspace. A person who wants records deleted or a copy of their information needs a published contact method. That contact method is [Support contact — complete before launch]. The operator must decide how those requests will be handled before launch.

Contact

Privacy questions can be sent to [Support contact — complete before launch]. Do not publish this page as a finished policy until that contact, the legal entity name, and the business location are filled in.

Last updated October 13, 2026.