This Privacy Policy explains how Local-Flow App LLC (“Local Flow,” “we,” “us,” or “our”) collects, uses, discloses, and protects information in connection with the Local Flow website, mobile apps, and related services (the “Service”).
Local Flow is business software for home-service companies — plumbing, HVAC, electrical, lawn care, cleaning, and similar trades. It is used by a business to schedule work, manage its customers, send reminders, take payments, and run its operations.
Read Section 2 first. It explains the single most important thing in this Policy: which information is ours to answer for, and which information belongs to the business using Local Flow.
Local Flow handles two different kinds of information, and our responsibilities are different for each.
Account Data — we decide how this is used. This is information about the business that subscribes to Local Flow and the people who log in: the owner, admins, and employees. We determine the purposes and means of processing it, which under California law makes us a “business,” and under the GDPR a “controller.” This Policy governs it.
Customer Data — the business decides how this is used. This is the information a business enters or uploads about its own customers: names, addresses, phone numbers, job history, photos, invoices, and notes. We process it only on that business’s instructions, to provide the Service to them. Under California law that makes us a “service provider”; under the GDPR, a “processor.” We do not use Customer Data for our own purposes, do not sell it, do not use it to advertise, and do not use it to train artificial-intelligence models.
If you are the customer of a business that uses Local Flow — a homeowner whose plumber runs on our software — then that business, not Local Flow, decides what information it keeps about you and how long. Requests to access, correct, or delete that information should go to the business you hired. If you contact us instead, we will refer you to them and assist them in responding, as the law requires of a service provider.
Nothing in this Policy makes Local Flow responsible for how a business runs its business. See Terms of Service §11.
The table below lists each category of personal information we handle, where it comes from, why we handle it, and who receives it. Categories are described using the labels California law uses, so the disclosure lines up with the rights described in Section 16.
| Category | Examples | Where it comes from | Why we handle it | Who receives it |
|---|---|---|---|---|
| Identifiers | Name, email address, phone number, postal address, account ID, device identifiers, IP address | You, when you sign up or use the Service; the business that invited you; your customers’ records entered by the business | Create and secure accounts, authenticate sign-in, provide the Service, support | Hosting, authentication, email and SMS providers |
| Customer records (California “customer records” category) | Service address, job history, appointment times, service notes, equipment and warranty records, invoice and payment status | Entered or uploaded by the business using Local Flow | To provide the Service to that business, on its instructions only | Hosting and database providers |
| Commercial information | Subscription plan, trial status, billing history, invoices, purchase and cancellation records | You; our payment processors | Billing, subscription management, accounting, fraud prevention | Payment processors, accounting providers |
| Internet and network activity | App version, pages and features used, session activity, crash logs, diagnostics, security logs | Automatically, as you use the Service | Keep the Service working, fix defects, detect abuse and unauthorized access | Hosting, error-reporting and analytics providers |
| Geolocation data | Approximate location from IP; precise device location when a user enables it — see Section 8 | Your device, with your permission; IP address | Arrival records, routing and drive-time estimates, service-area features | Mapping and geocoding providers |
| Visual information | Job photos, before/after photos, equipment and property photos, receipt images, video attached to messages | Uploaded by users of the business | Document work performed, support quotes and invoices, resolve disputes | Storage providers; an AI provider only as described in Section 7 |
| Professional or employment information | Role and permissions, schedule, hours, skills and certifications, pay and commission settings, time and job records | The business that employs you; your own use of the Service | Scheduling, dispatch, payroll support, and permissions within that business | Hosting providers; the business that employs you |
| Financial information | Payment method type, last four digits and processor tokens, payout and deposit records, financing documents a business stores — see Third-Party Financing Policy | You; payment processors; documents uploaded by the business | Take payments, reconcile deposits, keep the business’s job records | Payment processors; storage providers |
| Audio and communications content | Message text, recipients, delivery status, opt-out status, support conversations | Messages a business sends through the Service; your contact with support | Deliver the messages a business asks us to send; provide support | SMS and email providers |
| Inferences | Suggested services, suggested parts, scheduling and routing suggestions, draft quote estimates | Derived from the records above within a single business’s account | Provide suggestion and drafting features to that business | Not shared; see Section 7 for AI processing |
We do not collect: government identification numbers, Social Security numbers, immigration or citizenship status, union membership, religious or philosophical beliefs, racial or ethnic origin, sexual orientation, health or genetic information, or full payment-card numbers. Full card numbers are handled entirely by our payment processors and are never stored on our systems.
California law defines a narrower set of information as “sensitive personal information.” Of that set, Local Flow handles only two things:
We use both only to provide the Service, secure it, and prevent fraud. We do not use or disclose sensitive personal information to infer characteristics about anyone, for advertising, for profiling, or for any purpose beyond those permitted without a right to limit under California law. Because of that, there is nothing here for a “Limit the Use of My Sensitive Personal Information” request to restrict — but you may still turn precise location off at any time, and we will honor a request rather than argue about it.
Local Flow does not collect, receive, store, or have access to your fingerprint, face scan, or any other biometric identifier.
When you enable Face ID, Touch ID, or a passkey, the biometric check happens entirely on your own device, performed by your device’s operating system. Your device tells us only that it verified you. The biometric data itself never leaves your device and never reaches us. We store only a public key and the fact that you enabled the feature.
We state this plainly because several states regulate biometric identifiers specifically. Local Flow is not in possession of any.
We do not use Customer Data to train artificial-intelligence models, do not sell it, and do not use it for advertising.
Some optional features use an artificial-intelligence provider. The clearest example is draft quote generation: when a business chooses to use it, a photo and description submitted by that business’s customer are sent to an AI provider so a draft estimate can be produced for the business to review.
What this means concretely:
We derive approximate location from IP address for security and fraud prevention. Precise device location is collected only where a user grants operating-system permission, and only for a specific feature.
Employees and technicians should read this part. When a technician marks an appointment as arrived, the app may record the device’s location at that moment, so the business has an accurate arrival record for the job. This is a location record tied to a specific job event.
We share information only as described here. We do not share it for money and we do not share it for advertising.
| Recipient | What they receive | Why |
|---|---|---|
| Hosting, database, and authentication providers | All data required to run the Service | Store and serve the application and its data |
| Payment processors | Payment details, amounts, and identifiers | Process subscription and customer payments |
| SMS and voice providers | Phone numbers, message content, delivery status | Deliver verification codes and the messages a business sends |
| Email providers | Email addresses, message content | Deliver the emails a business sends and our own service email |
| Mapping and geocoding providers | Addresses and coordinates | Address lookup, routing, and drive-time estimates |
| Artificial-intelligence provider | Only the photo and description for a draft-quote request | Generate a draft estimate — see Section 7 |
| Marketing platforms a business connects | Only what that business authorizes when it connects the account | Run campaigns that business chooses to run |
| App stores | Purchase and app-delivery information they handle themselves | Distribute the mobile apps |
| Professional advisers | As needed | Legal, accounting, and audit services |
Within a business: owners and admins can see their business’s data; employees see what their role permits. Permissions are enforced at the database level, not merely hidden in the interface.
Legal and safety: we may disclose information where required by law or legal process, or where we reasonably believe disclosure is necessary to protect rights, safety, security, or to investigate fraud. Where we are permitted to notify the affected business first, we will.
Business transfers: in a merger, acquisition, financing, or sale of assets, information may transfer as part of the transaction, subject to this Policy or a successor policy with comparable protections.
Aggregated and de-identified information: information that cannot reasonably identify a person or business may be used and shared for analytics and product improvement. We do not attempt to re-identify it.
Sometimes a government agency, a court, or law enforcement asks a company for information about the people who use it. This section is our commitment about what we do when that happens. It applies to every request, foreign or domestic, whether it arrives as a subpoena, a warrant, a court order, or a letter.
We review every request for legality before we respond to any part of it. A request is not self-executing because it is on letterhead. We check that it comes from an authority with jurisdiction over us, that it was issued under a law that actually authorizes it, that it is properly served, and that it is specific about what it seeks. A request that fails those tests does not get answered because it looked official.
We challenge requests we believe are unlawful, overbroad, or improper. Where we can object, narrow, or move to quash — and where the law does not forbid us from doing so — we will, including at our own cost. We treat “we could probably comply” and “we are required to comply” as different things.
We disclose the minimum the request actually compels, and nothing more. We do not hand over an account because a request mentions it. We produce the specific records described, for the time period described, about the people described. Where a request would sweep in information about people it does not name — a business’s employees, or its customers — we narrow it or object rather than over-produce for convenience.
We document every request and what we did about it. For each one we record what was asked for, who asked, the legal authority cited, our assessment of it, who at Local Flow made the decision, what we disclosed, and when. That record exists so the answer to “what happened, and why” is written down at the time rather than reconstructed later.
We tell the affected business wherever we are permitted to. Our default is to notify before we disclose, so they have a chance to respond themselves. We stay silent only where a valid legal order forbids notice, and where such an order expires or is lifted, we give notice then.
We do not volunteer information. Absent a legal obligation, we do not provide personal information to public authorities on request, informally, or as a courtesy. The exception is a genuine emergency involving a risk of death or serious physical injury, where we may act on the information necessary to address it.
Nothing here is a promise that we can refuse a lawful order — we cannot, and we will not pretend otherwise. It is a commitment about the standard an order has to meet first, and about how little we hand over when one does.
Local Flow does not sell personal information, and does not share personal information for cross-context behavioral advertising, as those terms are defined by California law. We have not done so in the preceding twelve months, including for anyone under 16.
There is no “Do Not Sell or Share My Personal Information” mechanism on our site because there is nothing to opt out of. If that ever changes, this Policy will say so before it happens and the mechanism will be provided.
If you sign in with Google or Apple, we receive your name, email address, and an authentication identifier as authorized by that provider. We use it to create and secure your account and to sign you in.
Local Flow’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not use Google user data for advertising, do not sell it, and do not transfer it except as needed to provide the Service, comply with law, or as part of a business transfer with comparable protections.
We send our own service messages: verification codes, security alerts, billing notices, and support replies. You cannot opt out of essential service and security messages while you hold an account, but you can opt out of marketing messages at any time.
We also deliver messages that a business asks us to send to its customers — appointment reminders, quotes, receipts, and similar. For those, the business decides the content and the recipients, and the business is responsible for having the consent required to send them and for honoring opt-outs. Details are in the SMS & Customer Communication Policy.
Message and data rates may apply. We may block or limit messaging that appears to violate law, carrier rules, or our policies.
We keep information for as long as needed for the purpose it was collected, then delete or de-identify it. Because we hold Customer Data on a business’s behalf, that business’s own retention choices govern much of it.
| Information | How long |
|---|---|
| Account and business records | For the life of the account, then deleted or de-identified following a verified deletion request |
| Customer Data held for a business | Until the business deletes it or closes its account, then handled under the Data & Account Deletion Policy |
| Billing, tax, and accounting records | As long as required by tax and accounting law, typically several years, regardless of account closure |
| Security, audit, and fraud-prevention logs | A limited period appropriate to the purpose, then deleted or de-identified |
| Message delivery records | As needed to prove delivery, handle disputes, and meet carrier and regulatory obligations |
| Backups | Deleted data may persist in routine backups for a limited period before being overwritten on the normal backup cycle |
We use administrative, technical, and organizational safeguards designed to protect information, including encryption in transit and at rest, access controls enforced at the database level rather than only in the interface, role-based permissions, and audit logging of sensitive actions.
No system is perfectly secure and we do not claim otherwise. You are responsible for using strong credentials, managing who has access to your account, protecting your devices, and telling us promptly if you suspect unauthorized access.
Depending on where you live, you may have some or all of the following rights regarding personal information for which we are the business or controller:
These rights apply to Account Data. For Customer Data, the business that collected it is the one to ask — see Section 2. We will assist that business in responding, as a service provider must.
Email Support@local-flow.app with the request and the account’s email address or phone number. Account deletion can also be started in the app under Settings.
Verification. We will ask you to verify your identity, usually by confirming control of the account’s email or phone number, and for a request covering specific pieces of information we may ask for more. We do this to avoid handing someone’s information to the wrong person, and we will not use what you provide for verification for anything else.
Authorized agents. An agent may submit a request on your behalf with written permission signed by you; we may also ask you to confirm it directly.
Timing. We confirm receipt within 10 business days and respond within 45 calendar days, extendable once by a further 45 days where reasonably necessary, in which case we will tell you before the first period ends.
Free of charge, unless a request is manifestly unfounded or excessive, in which case we will explain why before charging or declining.
Because we do not sell or share personal information, an opt-out preference signal such as Global Privacy Control has nothing to act on. We nevertheless recognize such signals and treat them as a valid opt-out request, and we will not treat a browser sending one differently from any other.
There is no consensus standard for “Do Not Track” browser signals, and we do not respond to them separately from the above.
Local Flow is operated from the United States and is intended for businesses in the United States. If you use it from elsewhere, your information will be processed in the United States, where privacy laws may differ from those where you live.
Where the GDPR or UK GDPR applies to our processing of Account Data, we rely on these legal bases:
Where we process Customer Data, we act as a processor on the instructions of the business, which is the controller. Businesses subject to the GDPR that require a data processing addendum should contact us.
In addition to the rights in Section 16, you may object to or request restriction of certain processing, and you may lodge a complaint with your supervisory authority. Where we transfer personal data out of the EEA or UK, we use an approved transfer mechanism such as the Standard Contractual Clauses.
Local Flow is business software and is not directed to children. We do not knowingly collect personal information from anyone under 16, and the Service is not intended for anyone under 18 to hold an account. If you believe a child’s information has been provided to us, contact us and we will delete it.
If we become aware of a security incident affecting personal information we hold, we will investigate, take steps to contain and remediate it, and notify affected businesses and, where required, individuals and regulators, within the time the applicable law requires. Where we hold information on a business’s behalf, we will notify that business without undue delay so it can meet its own obligations.
We may update this Policy. The “Last Updated” date at the top will change, and for material changes we will give notice in the Service, by email, or by another reasonable method before the change takes effect. Continuing to use the Service after a change takes effect means the updated Policy applies.
Privacy questions and requests: Support@local-flow.app, or Local-Flow App LLC, 14153 S Lasso CT, Draper, UT 84020.
If you are the customer of a business that uses Local Flow and your question is about the records that business keeps, please contact that business directly — see Section 2.