Privacy Policy
This policy explains what Jobflo LLC ("we") collects when an organization and its people use Jobflo Labs, what we do with it, and what we do not do with it. It is written for the people who sign in to Jobflo Labs and for the organizations ("Tenants") whose data the service holds. Words defined in the Terms of Service, such as Tenant Data, Connected Service, AI client, and Plan, mean the same here. If this policy conflicts with a signed business associate agreement ("BAA") or data processing agreement, the signed agreement governs.
1. Two kinds of data, two roles
Platform data is what we need to run the service: user accounts, your organization's account details, billing, usage metrics, and service logs. We decide what platform data is collected and why.
Tenant Data is what a Tenant and its users put into Jobflo Labs, and what we retrieve from Connected Services on the Tenant's instructions: records, files, page content, and the tables the Tenant defines. The Tenant decides why this data exists and how it may be used. We process it only to provide Jobflo Labs to that Tenant and on its instructions. Under US state privacy laws we are the Tenant's service provider for this data; where European law applies, we are its processor. A Tenant must not put protected health information into Jobflo Labs unless a BAA is signed; once it is, we act as the Tenant's business associate for the PHI that BAA covers (Section 4).
We do not sell Tenant Data, use it for advertising, use it to train or improve AI models, or use it for other customers or for our own purposes. Our authorized personnel access Tenant Data only to provide and support the service, to respond to the Tenant's requests, to prevent or fix a technical or security problem, or as the law requires.
If you are a resident, patient, customer, client, or employee of a Tenant and have a question about information that Tenant holds about you, please ask the Tenant. We will help it answer.
2. Platform data we collect
| Data | Why | How long |
|---|---|---|
| Name, work email, sign-in credentials, and multi-factor settings (passwords are stored only as hashes) | Sign you in and protect your account | For the life of the Tenant. Deactivating a user ends their sessions and access tokens; the account record stays with the Tenant |
| Organization name and web addresses; the name, email, and IP address of the person who signed up; the terms version accepted | Run and identify the Tenant and show which terms were accepted | For the life of the Tenant, then only as Section 9 describes |
| Billing details held by Stripe, such as card type, last four digits, and invoices. We never receive the full card number | Charge for Plans and show invoices | As Stripe and tax law require |
| Usage metrics, such as daily counts of tool calls and emails sent and storage used | Show usage, enforce Plan limits, and plan capacity | For the life of the Tenant |
| Service logs and error reports, which include an IP address and the user's and Tenant's identifiers, names, and email addresses, and can include the contents of a request that failed | Keep the service running, fix faults, and investigate abuse | Up to 90 days, unless a specific record is needed longer for a security investigation or a legal duty |
| A bot check when you sign up, run by Cloudflare Turnstile, which reads technical information about your browser and device | Block automated signups | Processed by Cloudflare under its privacy policy; not used for advertising |
| Feedback you send from inside the product, with your name, email, and organization | Answer you and improve the product | Until resolved, then up to 24 months |
| Referral codes, commission records, and tax information a Partner submits | Pay what is owed and meet tax duties | As tax law requires |
| Cookies, described in Section 6 | Keep you signed in, protect against forged requests, and remember display choices | As Section 6 describes |
We do not use third-party advertising or analytics tools in Jobflo Labs. Please do not put protected health information or secrets into feedback or support email.
3. Tenant Data we process for Tenants
A Tenant decides which Connected Services it connects, what it retrieves and how often, what it stores, which pages it builds, and which users and AI clients may read or change any of it. We process Tenant Data by:
- retrieving it from Connected Services on the Tenant's schedule and storing it for that Tenant;
- showing it to the Tenant's signed-in users, and to the AI clients those users authorized, within the permissions the Tenant set;
- running the Tenant's tools against Connected Services when a user or AI client asks;
- receiving events the Tenant set up a Connected Service to send;
- rendering previews of the Tenant's pages, which can include the records shown on them;
- keeping a history of changes to the Tenant's records, including the values before and after each change, for as long as we keep that Tenant Data;
- backing up databases for disaster recovery.
The Tenant is responsible for having the right to collect Tenant Data and for telling the people it is about. We follow the Tenant's instructions given through the product, the Terms of Service, and any signed BAA or data processing agreement. If we believe an instruction breaks the law, we tell the Tenant and do not follow it.
4. Health information
Some Tenants, including healthcare and senior-living providers, may use Jobflo Labs to process protected health information ("PHI"). A Tenant must sign a BAA with us before it puts PHI into the service. Once the BAA is signed, we act as that Tenant's business associate for the PHI it covers, and we:
- use and disclose that PHI only to provide and secure Jobflo Labs and as the BAA and HIPAA allow, using no more of it in our own operations than that purpose requires;
- do not sell PHI, use it to train AI models or for advertising, de-identify or aggregate it except as the BAA permits, or use it for any purpose of our own;
- store and process PHI only in the United States;
- require a business associate agreement from any service provider that creates, receives, maintains, or transmits PHI for us, before it does so;
- help the Tenant respond to an individual's request about their PHI;
- return or delete PHI when the Tenant leaves, as Section 9 describes.
An individual who wants to see, correct, or receive a copy of their PHI should ask the provider that holds it. We help that provider respond.
5. AI clients
When a Tenant's user connects an AI client, such as Claude, requests from that client run under that user's permissions, and the Tenant Data the client reads is sent to the AI provider the user chose. That transfer is the Tenant's decision and is governed by the Tenant's agreement with that provider, including a BAA with that provider where the data includes PHI. We run no AI model of our own, and we do not use what an AI client reads to train any model.
6. Cookies
Jobflo Labs uses cookies only to run the product: a session cookie that keeps you signed in, a security cookie that stops other sites from forging requests as you, an optional remember-me cookie, a cookie that remembers which organization you are signed in to, and cookies that remember display choices such as theme. We do not use advertising or tracking cookies. Because we do not sell or share personal information for advertising, there is nothing for a Do Not Track or Global Privacy Control signal to turn off.
7. Service providers
We share data only with the providers below, only to run Jobflo Labs, and each under a written agreement that limits its use of the data to providing services to us and requires appropriate security. Where a provider may handle PHI, we also require a business associate agreement before it does.
| Provider | What it does for us | Where |
|---|---|---|
| Laravel Cloud | Application hosting, databases, file storage, queues, and cache, through its providers Amazon Web Services, Neon, and Cloudflare | United States; stored files on Cloudflare's network |
| Cloudflare | Domain name services, network security, the signup bot check, and rendering previews of Tenant pages | United States and Cloudflare's global network |
| Stripe | Billing, payments, and invoices | United States |
| Resend | Sending our transactional email; it sees the recipient, subject, and body | United States |
| Flare | Error monitoring and service logs | European Union |
| Oh Dear | Uptime checks and scheduled-task status, including a short failure message when a task fails | European Union |
Connected Services and AI providers that a Tenant connects are the Tenant's providers, not ours, and are not listed above. We remain responsible for the work our providers do for us. We email Tenant administrators before we add a provider that will process Tenant Data, at least 15 days ahead when we can.
We do not sell personal information or share it for cross-context behavioral advertising. We disclose data when the law requires it, to protect the service or other customers from abuse, or to a successor of our business under the same commitments. Where the law allows, we notify the affected Tenant before we disclose its Tenant Data in response to a legal demand.
8. Security and incidents
We protect data with administrative, technical, and physical safeguards, including:
- each Tenant's data is kept separate from every other Tenant's data;
- data is encrypted in transit and at rest;
- credentials a Tenant registers for Connected Services are encrypted and never shown back;
- the Tenant's own permissions decide which user or AI client can run a tool or read a record;
- people who administer Jobflo Labs must use strong sign-in (a passkey, or a password plus an authenticator app), and the same methods are available to every user;
- administrative actions in the product are recorded;
- access to production systems is limited to the people who operate the service.
No system is perfectly secure. If we discover unauthorized access to, or acquisition, use, or disclosure of, Tenant Data, we notify the affected Tenant's administrators without unreasonable delay, describe what happened, the kind of data involved, and what we are doing about it, and update them as we learn more. For a breach of unsecured PHI, we give that notice no later than 60 days after discovery, or sooner if the Tenant's BAA requires.
9. Retention and deletion
- Tenant Data is kept while the Tenant is active or suspended.
- A Tenant may be archived on request, after an unpaid trial, or after a long suspension or lapse in subscription, as the Terms of Service describe. Archiving ends access to the Tenant.
- For 30 days after archiving, the Tenant may ask us to restore it so its administrators can export query results and download stored files. After those 30 days, or sooner on written request, we delete its Tenant Data, including the change history described in Section 3, from our active systems. Backup copies are deleted as those backups expire, within 30 further days.
- If the law or a legal hold requires us to keep a copy, we keep it only for that purpose and delete it when the duty ends.
- After a Tenant is deleted, we keep platform data only where billing, tax, security, or proof of the accepted terms requires it, and delete or de-identify the rest.
- A deactivated user's sessions and access tokens end at deactivation. Their account record stays with the Tenant until the Tenant is deleted. References to them in service logs expire on the schedule in Section 2.
10. Your rights
Depending on where you live, you may have the right to access, correct, delete, or receive a copy of personal information about you, to appeal our decision on a request, and to complain to a regulator.
For platform data, write to hello@jobflolabs.com. We respond within 45 days, or sooner where the law requires, and may need to confirm the request comes from you. We will not discriminate against you for exercising your rights.
For Tenant Data, including PHI, the Tenant that holds it is the party to ask. We help that Tenant respond within the time the law gives it.
11. Where data is processed
We host Jobflo Labs and its databases in the United States; stored files are kept on Cloudflare's network through our hosting provider. Our error-monitoring and uptime providers operate in the European Union, and Cloudflare's network is global. Before we sign a BAA, we make sure the PHI it covers will be stored and processed only in the United States and will not reach those monitoring providers. Jobflo Labs is offered to organizations in the United States; if you need a data transfer agreement, email hello@jobflolabs.com.
12. Children
Jobflo Labs is for organizations. We do not knowingly collect personal information from anyone under 18 as a user. A Tenant may hold information about people under 18 only where its own law and authority allow; that information is Tenant Data, and the Tenant is responsible for it.
13. Changes
We publish each new version of this policy on this page with its effective date and email Tenant administrators about material changes. Earlier versions are available on request at hello@jobflolabs.com.
14. Contact
Jobflo LLC, 683 N Pollasky Ave, Clovis, CA 93612. hello@jobflolabs.com.
Write to that address for a privacy request, a BAA, a data processing agreement, or a security question; it reaches the person responsible for privacy and security at Jobflo LLC.
Effective October 16, 2026. Previous versions on request at hello@jobflolabs.com.