This Privacy Policy explains how CW Works LLC, an Ohio limited liability company doing business as CW Flows (“CW Flows,” “we,” “us,” or “our”), collects, uses, and shares information in connection with the CW Flows platform and related websites and applications (the “Service”). It applies to people who sign in to or interact with the Service.
1. Our Role: Controller and Service Provider
CW Flows is a business-to-business service. We act in two capacities:
- As a controller for account and identity information we collect directly (for example, the name and email used to sign in) and for operating and securing the Service.
- As a service provider / processor for the data that our business customers (each a “Customer”) and their authorized users submit to the Service about their own business, employees, and operations (“Customer Data”). We process Customer Data on the Customer’s behalf and under their instructions. If you are an employee of a Customer, that Customer (your employer) controls that data, so please direct requests about it to them.
2. Information We Collect
Account and identity information
When you sign in, our authentication provider collects information such as your name, email address, organization membership and role, and authentication events. We do not receive or store your password.
Customer Data
Customers, their authorized users, and the automations a Customer runs submit data to the Service. It may include: names, email addresses, and phone numbers of the Customer’s employees and business contacts; work schedules; tasks, their status, notes, and comments; reports from the Customer’s automations about each run and the work it produced; messages, service requests, and replies; files and documents uploaded to tasks, requests, or the Customer’s record (such as photos, PDFs, and contracts); emails sent through the Service; a history of who did what, and when; and records from tools the Customer links, such as Jobber quotes and scheduled visits.
Idle accountability (only if your employer turns it on)
A Customer can ask employees who are on shift, with no active task, to pick up available work or explain the gap after a set number of minutes. When this is on, the Service records each prompt, how long the employee had been idle, and any explanation they give, and the Customer’s managers can see those records.
When team members use the Service
When a signed-in team member uses the Service, we record when each visit starts and when they were last active. The team member, the Customer’s managers and anyone the Customer gives its team page, and our staff can see these times.
Payment information
If you pay for the Service, payments are handled by a third-party payment processor. We receive limited billing details (such as plan, amount, and status) but do not store full payment-card numbers.
Usage and device information
Our hosting and sign-in providers automatically record technical data such as IP address, browser and device type, the pages requested, and timestamps, as part of running and securing the Service (see also Section 8). The Service does not use advertising or analytics trackers.
Communications
If you contact us, we keep your messages and contact details to respond and for our records. If you email us, our monitoring agents may read your message to help us respond (see Section 4).
3. How We Use Information
- provide, operate, maintain, secure, and improve the Service;
- authenticate users and enforce role-based access and permissions;
- send transactional and service-related messages and notifications;
- process billing and payments;
- provide support and respond to inquiries;
- monitor, prevent, and investigate fraud, abuse, and security incidents; and
- comply with legal obligations and enforce our agreements.
4. AI-Assisted Processing
CW Flows works with Claude, an AI assistant made by Anthropic, in these ways:
- Your own Claude. A Customer or its users can connect their own Claude account to CW Flows, and the automations we build may run on a Customer’s own Claude. Claude can then read and change Service data only within the permissions the Customer sets, which CW Flows enforces. Anthropic processes that data under the Customer’s own agreement with Anthropic, not ours.
- Our staff’s Claude. Our staff may use Claude, through an administrator connection under our own Anthropic account, to help operate the Service (for example, to check automation runs or create tasks). When we do, relevant Service data is processed by Anthropic as our subprocessor. We use Claude under settings that do not allow Anthropic to use that data to train its models.
- Our own mailbox. Our monitoring agents can read our own business mailbox through CW Flows, read-only, to help us notice and answer messages. The messages they read are processed by Anthropic through our own Claude account, under the same settings. No copies of mailbox messages are kept in CW Flows; anything an agent writes down from one (a note, a proposed reply, including who the reply is to and the subject) is kept like any other record of that kind. A reply an agent drafts is sent only after we approve it: it goes out from our own business address through DreamHost, a copy goes to our own mailbox, and the reply we sent (not the message it answers) is kept in our email log. We can also read this mailbox ourselves on a private page in CW Flows that only our owner can open; the mail is read live from DreamHost and nothing shown there is kept. That page can mark our own mail as read or unread, and our owner can reply and send new mail from it. Those emails go out from our own business address through DreamHost, a copy goes to our own Sent folder, and in CW Flows we keep the subject, the recipients and the time, not the message. It changes nothing else there.
- A record of the emails we send you. So that we can see everything we have sent you, CW Flows records the emails we send you by hand from our business mailbox (read from its Sent folder) and the invoice and receipt emails our payment processor, Stripe, sends you: the subject, the recipient and the time only, never the message itself. Only we see these records; they are kept and deleted with the rest of your email log.
- Suggested fix steps for our staff. When our owner or one of our staff is working on an alert or a service request (a support ticket), they can click a button that has our own server send some of its text to Anthropic’s Claude, which writes suggested steps for our staff. This happens only on that click. It never happens automatically, and a Customer or an automation cannot start it. For an alert, we send its kind, severity, date, title and details, any fix steps and research notes the Customer’s automation sent with it, the automation’s name and id, and for that automation’s last 3 runs their status, date, summary, errors, warnings, recommended actions and counts. For a service request, we send its category, priority, status, dates, subject, description and the messages the Customer can see. We never send internal notes, attachments or photos, who wrote a message, tasks, mailbox email, billing data, connector keys, or any other Customer’s data. Before the text is sent, we cut links down to the site name and we try to remove text shaped like a key, passwords that are labelled as a password, email addresses, phone numbers written in a usual phone format, the Customer’s name, and the full names of its contact and team members as we have them on record. This is a safety net, not a guarantee. The rest is sent as written, so a first name on its own, a name spelled differently, a password that is not labelled, the name of one of the Customer’s own customers, an address or an amount that appears in an error or a service request can still be included. We have no list of those names to remove. Anthropic processes the text as our subprocessor to write the answer (see Section 6). The suggested steps are shown only to our staff. They are never added to the service request, never emailed, and never shown in the Customer’s portal. For each click we keep a log line: when, which staff member, which Customer, which alert or service request, its size and cost, and the suggested steps. We do not keep a copy of the text that was sent.
AI output can be wrong and should be reviewed before it is relied upon.
5. How We Share Information
We do not sell personal information. We share information only as follows:
- Service providers (subprocessors) who help us run the Service, under their terms of service or data processing agreements (see Section 6);
- With your organization: data is visible to authorized users within your Customer organization according to their role, and a Customer’s kiosk display shows its task board to anyone who has the kiosk link;
- At your direction: for example, with a third-party integration you choose to connect;
- For legal reasons: to comply with law, respond to lawful requests, or protect rights, safety, and security; and
- Business transfers: in connection with a merger, acquisition, financing, or sale of assets, subject to this Policy.
6. Subprocessors
We rely on reputable third parties to provide the Service. Depending on the features in use, these may include:
- Clerk: sign-in and user management;
- Supabase: database and file storage;
- Vercel: application hosting and delivery;
- DreamHost: transactional email delivery, with Resend as a backup sender if enabled, and hosting of our own business mailbox, which our monitoring agents may read and from which replies we approve are sent;
- Stripe: payment processing;
- Anthropic: when our staff use Claude to help operate the Service, and when our staff click a button that has our own server send alert or service request text to Claude for suggested fix steps (see Section 4);
- Slack and Twilio: alert notifications to our own staff, if enabled;
- Pushover (or ntfy): push notifications to our own staff’s phones, if enabled; a notification carries a short title (which may name the Customer), one line of text written by us or by our own monitoring agents, and a link, never the content of messages, requests, emails or reports;
- Photon (komoot): address suggestions when our staff enter a Customer’s business location; and
- Jobber: only when a Customer connects it; CW Flows reads quotes and scheduled visits from it.
This list may change as the Service evolves; we will keep it current on this page.
7. Data Retention
We keep information while the Customer’s account is active, and as needed to comply with legal obligations, resolve disputes, and enforce our agreements. Some records are deleted automatically on a fixed schedule:
- files attached to tasks and service requests: 90 days after upload;
- the log of actions taken through an AI connector: 90 days;
- the log of suggested fix steps our staff ask Claude for on an alert or a service request: 90 days;
- the log of push notifications sent to our staff: 90 days;
- working notes kept by our own monitoring agents (for example, which alerts they have already reported): until the expiry the agent sets on each note (a note without one is kept until the account closes);
- actions our monitoring agents propose for our approval, and our decisions on them: 1 year;
- the daily operations summary our monitoring agents write for our own owner, which may name the Customer: 30 days;
- idle-accountability records: 180 days;
- emails sent through the Service, and email requests: 1 year;
- portal messages: 2 years;
- when team members used the Service (their sign-in times): 2 years, and right away when a person is removed from the team; and
- the activity history (who changed what, and when): about 7 years, including after an account closes, as a business record.
When a Customer’s account closes, we delete its contacts, documents, messages, email records, request attachments, idle-accountability records, AI connector log, log of suggested fix steps, push notification log, its team members’ sign-in times, its alerts (with our monitoring agents’ findings on them), our monitoring agents’ working notes about it, and the actions they proposed for it 30 days later (actions still waiting for our approval are cancelled when the account closes), and remove its organization (team memberships and pending invitations) from our sign-in provider. Tasks, service requests, projects, the team list, and automation run history are not deleted automatically; the Customer can ask us to delete them, and can ask us for an export of its data before, or within 30 days after, the account closes. Deleted data may remain in our providers’ backups for a limited time before it is overwritten.
8. Cookies and Similar Technologies
We use only the cookies the Service needs to work: sign-in cookies set by Clerk to keep you signed in, and a short-lived cookie that protects the step where a Customer connects Jobber. We also keep a few display preferences, such as light or dark mode, in your browser’s storage. We do not use advertising or analytics cookies. You can control cookies in your browser settings, but blocking them will stop sign-in from working.
9. Security
We take reasonable technical and organizational measures designed to protect information, including role-based access controls and encryption in transit. No method of transmission or storage is completely secure, however, and we cannot guarantee absolute security.
10. Your Rights and Choices
Depending on where you live, you may have rights to access, correct, delete, or port your personal information, to object to or restrict certain processing, and to withdraw consent.
- U.S. state privacy laws (e.g., California/CCPA-CPRA): rights to know, access, correct, and delete personal information, and to not be discriminated against for exercising those rights. We do not sell or “share” personal information for cross-context behavioral advertising.
- EEA/UK (GDPR): the rights described above, plus the right to lodge a complaint with a supervisory authority.
- Employee data: if your information was provided to the Service by your employer (a Customer), please direct your request to that employer; we will assist them as their service provider.
To exercise a right, email TyPavia@cw-flows.com. We may need to verify your identity before responding.
11. International Users
We operate in the United States, and our providers may process information in the United States and other countries. If you access the Service from outside the United States, you understand that your information may be transferred to and processed in the United States.
12. Children’s Privacy
The Service is intended for business use and is not directed to children. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us information, contact us and we will take appropriate steps to delete it.
13. Changes to This Policy
We may update this Policy from time to time. When we do, we will revise the “Last updated” date above and, for material changes, provide additional notice where appropriate. Your continued use of the Service after changes take effect constitutes acceptance of the updated Policy.
14. Contact
Questions or requests about this Policy or your information? Contact CW Flows at TyPavia@cw-flows.com.