Skip to main content
Legal

Privacy Policy

Last updated: November 17, 2026

The short version

WorkflowUnity LLC builds custom software, websites and business systems. We collect information when you visit our websites, contact us, use our chat or estimate tools, become a client, sign an agreement, pay an invoice, or when we research businesses we think we can help. We do not sell your personal information for money. We do use Google and Microsoft advertising tags that may count as "sharing" for advertising under some state laws, and you can opt out (Section 7.3). If we emailed you about our services, you can stop all future contact with one reply. Questions or requests: [email protected].

1. Who we are

This Privacy Policy explains how WorkflowUnity LLC ("WorkflowUnity," "we," "us," or "our") collects, uses, discloses and protects personal information.

  • WorkflowUnity LLC is a Washington limited liability company (UBI 606205738).
  • Mailing address: 17404 Meridian E, Ste F-1074, Puyallup, WA 98375, USA.
  • Contact: [email protected]

This policy covers:

  • our marketing website, workflowunity.io, including its chat and estimate tools;
  • the public and client-facing pages of app.workflowunity.io (estimates, e-signature pages, payment pages, and our published Client Agreement);
  • our email and other business communications, including outreach to businesses; and
  • our dealings with clients, client staff who sign or use our systems, and vendors.

It does not cover websites, apps or systems that we build or host for our clients. For those, the client's own privacy policy applies (Section 11).

Section 12 (WorkflowUnity Social) explains how we handle information from Facebook, Instagram and YouTube when an organization connects those accounts to WorkflowUnity Social. For that information, this policy applies.

Separate organizations. WorkflowUnity LLC is a for-profit company. It is separate from Mercy House Ministry, a nonprofit organization. Each has its own privacy policy, and we do not share personal information between them.

2. Information we collect

2.1 Website visitors

  • Device and browser data: IP address, browser type and version, operating system, screen size, language, and referring page.
  • Usage data: pages viewed, time on page, links clicked, and how you arrived (for example a search engine or a paid ad, including ad click identifiers such as Google gclid or Microsoft msclkid).
  • First-party analytics: our own analytics records interaction signals such as pages viewed, scrolling, clicks, and which form fields were filled in (not the text you type, except as described under partially completed forms below). It uses a random visitor ID kept in your browser's local storage and a session ID kept in session storage. This data stays on systems we control and is not sold.
  • Partially completed forms: if you start our estimate form and enter your name, email or phone but do not submit it, we save those contact details and any service options you selected, and may send you one follow-up email to help you finish. We send at most one such email.
  • Cookies and similar technologies: see Section 6.

2.2 People who contact us or request an estimate

  • Name, company name, email, phone (optional), and your role.
  • Project information: services you are interested in, the problem you want to solve, features, budget range, timeline, and anything else you choose to tell us.
  • Messages and attachments you send us by email or through forms.
  • Submission details: source (form or chat), time, and IP address, used to prevent abuse and to understand which pages work.

2.3 Chat and AI features

  • Messages you type into our chat or estimate tools, the replies, and the contact details you choose to give.
  • Some of these conversations are processed by an artificial intelligence model (Section 5) to generate replies and draft estimates, and they are kept and reviewed by us so we can follow up and improve our answers.
  • Please do not enter sensitive information (health, financial account or government ID numbers, passwords) into the chat.

2.4 Business prospects (outreach)

We contact businesses and organizations we believe may benefit from our services. To do this, we collect business contact information about people in their professional roles, which may include:

  • name, job title, employer or organization, business email, business phone, business mailing address, and professional profile links;
  • information about the organization: website, services, location, size, public registrations, and public announcements or job postings;
  • notes we write about why our services may be a fit, which may be drafted with the help of AI tools that read the organization's public website;
  • email verification results (for example "valid" or "invalid");
  • email engagement data: whether an email we sent was opened (through a small tracking image) and whether a link was clicked (through a link that passes through our server first), with the date and time, IP address, browser details, and an approximate location (city, region, country and internet provider) that we look up from the IP address using a third-party IP geolocation service (ip-api.com); and
  • replies, opt-out requests, and our record of contacting you.

You may be in our records even if we have never emailed you. We often collect and verify business contact information before deciding whether to reach out, and many records are never used. Section 3 explains where this information comes from, and Section 7 explains how to have it deleted.

2.5 Clients, client staff and signers

  • Account and project data: names, business contact details, roles, project requirements, files and content you send us, meeting notes, change requests, and support or bug reports (which may include screenshots, page addresses, browser details, and a description of what happened).
  • E-signature data (when you approve an estimate, change order or other document in app.workflowunity.io): your name, email, title, a statement of your authority to sign, your typed or drawn signature and initials, the date and time of each step, your IP address and browser details, a SHA-256 fingerprint of the signed record, and the signed PDF itself, which reproduces the terms, the selected scope and payment schedule, and an audit trail. We keep this to prove what was agreed and by whom.
  • Estimate and invoice email data: delivery status and, for some emails, whether the email was opened or a link was clicked.

2.6 Payments

  • Payments are processed by Stripe. When you pay by card or bank transfer, you give your payment details to Stripe, not to us. We do not receive or store full card numbers or bank account numbers.
  • We receive and keep: your name, billing email and address, the amount, invoice and payment status, the last four digits and brand of the card or bank, and Stripe's customer, invoice and payment identifiers.
  • If you pay by check, we keep the information on the check that is needed to record and deposit it.
  • Sales tax: we keep the billing address and tax details needed to calculate and report Washington sales tax.

2.7 What we do not collect on our own sites

We do not knowingly collect consumer health data as defined by Washington's My Health My Data Act on our own websites, and we ask you not to send it to us through our forms or chat. We do not knowingly collect government ID numbers, precise geolocation, biometric identifiers, or full payment card numbers on our own sites. If a client project involves such data, it is governed by the client's agreement with us, not this policy (Section 11).

3. Where we get information

SourceExamples
YouForms, chat, email, signed documents, files, support requests.
Your device and browserCookies, local storage, tracking images and server logs (Section 6).
Our clientsContact details of client staff or the client's customers when a client asks us to build, host or support a system (Section 11).
Public sourcesOrganization websites, public business registries, public procurement and grant notices, nonprofit filings, news, professional social media profiles, and public directories.
Business contact data vendorsHunter.io and Apollo.io (business contact and company data); MillionVerifier (checks whether an email address can receive mail).
Advertising and analytics partnersGoogle and Microsoft, for reports on ad clicks and conversions.
Payment processorStripe, for payment status and partial card details.
ReferralsPeople who introduce us to you.

4. How we use information

  • To respond to you and provide estimates, proposals and answers.
  • To deliver services: build, host, maintain and support client systems, and manage projects, change requests and bug reports.
  • To form and keep records of agreements: e-signature evidence and signed documents.
  • To bill and collect: invoices, installment plans, receipts, sales tax, and collections.
  • To run business outreach: find and research organizations we may be able to help, verify email addresses, send a limited number of business emails, measure whether those emails are opened or clicked, and honor opt-outs.
  • To operate and secure our sites: keep them working, prevent spam, fraud and abuse, and fix errors.
  • To measure and improve marketing: understand which pages, ads and channels bring inquiries, including through Google and Microsoft advertising tags.
  • To improve our services: review chats, analytics and feedback.
  • To comply with law and protect our rights, including tax, accounting, and legal claims.

AI processing. We use AI models to answer chat messages, draft estimates, summarize information, and draft outreach notes from public information about organizations. We review outreach before it is sent. We do not use AI to make decisions that produce legal or similarly significant effects about individuals. We use AI models under commercial terms that do not permit the provider to train its models on the content we send.

5. How we disclose information

We do not sell personal information for money. We disclose personal information to the following categories of recipients:

CategoryWhoWhat they receiveWhy
Cloud hosting and AIAmazon Web Services (app.workflowunity.io, databases, file storage, backups, and AI models through Amazon Bedrock)Data held in our app; chat messages and estimate details for AI featuresHosting, storage and AI features
Website hostingAmazon Web Services (our Unity Hosting servers)Website form submissions, chat records, first-party analytics, server logsHosting workflowunity.io
Network and securityCloudflare, Inc.IP address, request data, security checks, page performance dataDNS, content delivery, security, spam protection
EmailGoogle (Google Workspace), Brevo, Amazon Simple Email ServiceEmail addresses, names, message content, delivery and engagement eventsBusiness email, estimate, invoice and system emails
Prospect data and verificationHunter.io, Apollo.io, MillionVerifierNames, domains and email addresses we look up or verifyFinding and verifying business contacts
IP geolocationip-api.comIP addresses from email opens and clicksApproximate location of engagement
PaymentsStripe, Inc.Billing details, invoice amountsPayment processing and invoicing
Analytics and advertisingGoogle LLC (Google Analytics, Google Ads), Microsoft Corporation (Microsoft Advertising)Cookie IDs, IP address, pages viewed, ad click IDs, conversion eventsAnalytics, ad measurement and advertising
Professional advisersAttorneys, accountants, insurersAs neededLegal, tax and insurance
Authorities when requiredCourts, regulators, law enforcementAs requiredLegal process, protecting rights, preventing fraud
Business transferA buyer or successorRecords related to the businessMerger, acquisition or sale of assets, with notice to affected people

6. Cookies, pixels and similar technologies

We do not show a cookie banner. Our sites use these kinds of technologies:

TechnologySet byPurposeHow to control it
WordPress and security cookiesUs and CloudflareSite function, form and spam protection, bot checksBrowser settings; needed for forms and security
Visitor and session IDs in browser storageUsFirst-party analytics (Section 2.1)Clear site data in your browser
Google AnalyticsGoogleSite traffic statisticsGoogle Analytics opt-out add-on; browser settings
Google Ads tagGoogleAd click and conversion measurement; may support remarketingGoogle My Ad Center; Section 7.3
Microsoft Advertising tagMicrosoftAd click and conversion measurement; may support remarketingMicrosoft ad settings; Section 7.3
Cloudflare page analyticsCloudflarePage performance, without cookiesAd blockers
Email tracking images and tracked linksUs and BrevoWhether an email was opened or a link clickedBlock remote images in your email app; ask us to stop
Payment page scriptsStripeFraud prevention on payment pagesRequired to pay online

We do not respond to "Do Not Track" signals because there is no common standard for them.

7. Your choices and rights

7.1 Rights we offer to everyone

Wherever you live, you can ask us to:

  • access the personal information we hold about you and tell you where we got it;
  • correct inaccurate information;
  • delete your information (subject to the exceptions in Section 8, such as signed contracts and tax records);
  • stop marketing, including outreach email; and
  • opt out of advertising tags (Section 7.3).

Email [email protected] with your request, or write to the mailing address in Section 1. We will confirm receipt within 10 business days and respond within 45 days (we may extend once by up to 45 more days when reasonably necessary and will tell you why). We will verify your identity in a way that fits the request, usually by replying to the email address in our records. You may use an authorized agent; we may ask for proof of the agent's authority. We will not discriminate against you for using these rights. If we deny a request, you can appeal by replying with "Appeal" in the subject line. We will respond to an appeal within 45 days and explain how to contact your state attorney general if you disagree.

7.2 Washington and other U.S. states

  • Washington residents. We offer the rights in 7.1 to you. Washington's My Health My Data Act gives specific rights over consumer health data; as explained in 2.7, we do not knowingly collect that data on our own sites.
  • Other states with privacy laws. Where a state privacy law applies to us, you may have additional rights, such as the right to know the categories of information we collect and disclose, to opt out of "sale," "sharing," or "targeted advertising," to limit use of sensitive information, and to appeal. Several of these laws apply only to businesses above revenue or volume thresholds, and several exclude information about people acting in a business or employment role. We honor the requests in 7.1 whether or not a law requires us to.

7.3 Opting out of advertising tags

We use Google Ads and Microsoft Advertising tags on workflowunity.io to measure which ads lead to inquiries. These tags let Google and Microsoft recognize your browser, and those companies may use that information to show you our ads on other sites (remarketing) or to build audiences, and for their own purposes as described in their privacy policies. Under some state laws this may be "sharing" or "targeted advertising." To opt out:

  1. email [email protected] with the subject "Do not share" and we will tell you how we have applied your request; and
  2. use Google My Ad Center and Microsoft ad settings, or industry tools at optout.aboutads.info.

7.4 If you received a business email from us

  • Every outreach email identifies WorkflowUnity LLC, includes our mailing address, and tells you how to opt out. Reply "unsubscribe" (or any message asking us to stop) and we will stop. We honor opt-outs permanently, and in any event within 10 business days.
  • We do not use false or misleading sender information or subject lines.
  • To be deleted entirely, write "Delete my data" and we will delete your record from our systems and ask our prospect-data vendors (Hunter.io, Apollo.io) to remove records we created there.
  • Suppression record. So that we never contact you again, we keep a minimal suppression record: your email address (or a one-way hash of it), the date, and the reason. We keep it indefinitely and use it only to prevent future contact. If we deleted it, we could not recognize you if your address turned up again in a public source or vendor list.

7.5 European Economic Area and United Kingdom

Our services are directed to organizations in the United States. If GDPR or UK GDPR applies to our processing of your information, our lawful bases are: performance of a contract or steps before a contract (estimates, projects, billing); legal obligation (tax and accounting records); legitimate interests in running, securing and marketing our business, including business-to-business outreach, which we balance against your rights; and consent where we ask for it, which you can withdraw at any time. You also have the rights to object to processing, including direct marketing at any time, to restrict processing, to data portability, and to complain to your data protection authority. Information is processed in the United States.

8. How long we keep information

We keep information only as long as needed for the purposes in Section 4, then delete or de-identify it. Backups roll off on their normal schedule.

InformationHow long we keep it
Signed agreements, change orders, e-signature evidence and signed PDFs7 years after the agreement ends or the final payment, whichever is later
Invoices, payment records, tax and accounting records7 years after the tax year they relate to
Client project data, files, support and bug reports, change requestsFor the engagement, then up to 36 months after it ends, unless the client's agreement says otherwise
Website inquiries, estimate requests and chat transcripts (non-clients)36 months after our last interaction with you
Partially completed estimate forms12 months if you never complete the form
Prospect (outreach) records, including email open and click events36 months after our last interaction with you (an email sent, a reply, or a verification), then deleted
Suppression (do-not-contact) recordIndefinitely, limited to the minimum in 7.4
First-party analytics eventsUp to 36 months
Google Analytics dataPer our Google Analytics data-retention setting, no longer than 14 months for event-level data
Server and security logsFor a limited period, generally no longer than 12 months

Where we must keep information longer to comply with law, resolve a dispute, or enforce an agreement, we keep only what is needed for that purpose.

9. Security

We use administrative, technical and physical safeguards appropriate to the information we hold, including encryption in transit (HTTPS), encryption at rest where our cloud providers support it, access limited to people who need it, multi-factor authentication where available on administrative accounts, logging, and regular updates. E-signature records are sealed with a SHA-256 fingerprint so later changes can be detected. No system is perfectly secure.

10. Security incidents

If we learn of a breach of security that compromises personal information we hold, we will investigate, contain it, and notify affected people as required by law. For Washington residents, we will notify affected individuals in the most expedient time possible and no more than 30 calendar days after we discover the breach, and if more than 500 Washington residents must be notified as a result of a single breach, we will also notify the Washington State Attorney General within the same 30 days. We will notify residents of other states as their laws require. Where we hold information for a client (Section 11), we will notify that client without undue delay so the client can meet its own obligations.

11. When we process data for our clients

When we build, host, maintain or support a website, app or system for a client, we handle the personal information in that system on the client's behalf and under the client's instructions. In that role:

  • we act as a service provider, contractor or processor, and the client is the business or controller responsible for that information;
  • our handling is governed by our agreement with the client, including the Data Processing Addendum in our Client Agreement;
  • the client's own privacy policy governs that information, not this policy;
  • we use it only to provide the services the client asked for, and we do not sell it, share it for advertising, or use it for our own marketing; and
  • if you want to access, correct or delete information in a client's system, please contact that client. If you contact us instead, we will forward your request to the client promptly and help the client respond as our agreement requires.

12. WorkflowUnity Social (Facebook, Instagram and YouTube)

WorkflowUnity Social is our tool that lets a church or other organization ("the organization") approve short videos and pictures made from its own content, post them to its own Facebook Page, Instagram account and YouTube channel, and answer messages sent to its Page or Instagram account. This section applies to the information we receive through Facebook, Instagram and YouTube for this tool, and to the service videos and transcripts the tool works from. For this information, WorkflowUnity LLC is responsible, and this section applies even though the tool serves our clients. The organization decides what is posted to its own accounts and is the publisher of those posts and of its own answers to messages; WorkflowUnity provides the tool and acts on the organization's instructions.

12.1 What we receive

  • From Facebook and Instagram, when the organization connects: the name and ID of the Facebook Page it picks, the username and ID of the linked Instagram professional account, and access keys that let us post for it.
  • From Facebook and Instagram, if the organization turns on the message helper: messages people send to the organization's Page or Instagram account, the sender's display name or username, and the ID Facebook or Instagram uses for that sender on that Page.
  • From YouTube, when the organization connects and while it stays connected: the channel name and ID; an access key that lets us upload the videos its approver says yes to, add them to its playlists, and take down a video we posted when asked; the titles of its own top videos; whether the videos we posted for it are still on YouTube; and YouTube Analytics reports for its own channel (its total views, and views by the YouTube searches that led people to its videos, by traffic source, by country, by subscribers and non-subscribers, for its top videos and for the videos we posted for it).
  • From the organization itself: the service and event videos it uploads to us, the written transcripts we make from them, and its answers on the upload page about the people, children and music in each video.
  • When the organization connects YouTube: a record that it ticked the box agreeing to the YouTube Terms of Service and this policy, with the time, the wording version, the name it typed (if any), and a one-way code made from its internet address (never the address itself).
  • Links to and status of the posts we publish for the organization.

12.2 How we use it

  • To publish posts at the scheduled time to the organization's own accounts. On Facebook and Instagram we publish the posts a named person at the organization approved, or posts released under the default the organization chose in its signed agreement when no one answers by the deadline. That default applies to Facebook and Instagram only, and it never releases a post the tool flagged for a person's look (for example a video the organization said shows children up close or may have music its license does not cover). On YouTube we upload a video only after a named approver presses "Yes, post it". If no one answers, the YouTube video is held and is not uploaded.
  • For each YouTube video, the approval page shows the channel it will go to, a visibility choice (Public, Unlisted or Private, starting from the organization's setting) and a "Made for kids?" yes or no. We send those choices to YouTube with the video. We add "#Shorts" at the end of the description, and the approval page says so.
  • To show the organization which account is connected, whether each post went live, and whether the YouTube videos we posted are still there.
  • To show messages to the organization's staff, send the organization's own written answers to simple questions (the helper says it is automated), and pass every other message to a person. Prayer, money and personal messages are never answered by the helper. At most, the sender gets an automatic note that the message was passed to the organization's staff. A message that sounds like a crisis gets one automatic note with the 988 crisis line, and the organization's staff are alerted at once.
  • To take a post down when asked. The organization's approver, or our staff at the organization's request, can make a YouTube video we posted private, or delete it after a second confirmation. We do not change or delete any other video, comment, caption or rating.
  • To pick moments for clips, suggest titles, and prepare topic ideas for the organization's next videos, using its transcripts and the words people search for on YouTube. We use the search phrases as YouTube reports them to choose which of the organization's own moments to suggest. We do not calculate new statistics from YouTube data.
  • To prepare a monthly report about the organization's own YouTube channel. Our system prepares it, and our staff review it and share it with the organization. It is not emailed automatically.

We do not sell this information. We do not use it for advertising, and we do not build profiles of the people who message an organization. We do not use it to train AI models, and our agreement with our AI provider does not allow it to train its models on this information.

12.3 Who helps us and who can see it

  • Amazon Web Services stores and runs the tool in the United States (Oregon region).
  • Anthropic, an AI provider, receives the text of a message only after our safety filter has cleared it, so the AI can choose which of the organization's written answers fits. The filter is designed to keep out messages about prayer, health, crisis, money and personal topics, but it works from word lists and it can miss some.
  • Anthropic also receives search phrases from the organization's YouTube Analytics reports, only to pick and title clips, and transcripts of the organization's own service videos, to pick moments for clips and write post text. Transcripts are the organization's own content, not information from Google. Anthropic does not receive access keys, account IDs or sender names. Our AI provider deletes what we send it within 30 days and may not train on it.
  • WorkflowUnity staff may view the organization's YouTube search phrases to prepare topic ideas, review the monthly report before sharing it with the organization, and take a post down when the organization asks. Only staff who work on the organization's account have this access, and they use it only for these tasks. The connect page tells the organization about the AI provider and staff access before it connects YouTube.

12.4 How we protect it and how long we keep it

  • Access keys are encrypted and are deleted at once when the organization presses Disconnect.
  • Messages and conversations are deleted automatically 90 days after the last message. Message text is never put in our emails or system logs.
  • Uploaded videos are deleted after 30 days. Clips, pictures and transcripts are deleted 90 days after they are made.
  • Each day we check that our YouTube access still works, which also refreshes the stored channel name, and we check whether the videos we posted are still on YouTube. If one is gone, we drop our record of its video ID and link. Stored YouTube report and search files are deleted when they are 28 days old, and the report numbers are cleared from the posts and topic ideas they helped plan at the same time. If our daily check has not succeeded for 25 days, we delete the stored YouTube data and the access key.
  • When the organization presses Disconnect for YouTube, or asks us to delete its data, we ask Google to cancel our access (we try once more if that fails, and a failure alerts our staff), delete the access key, delete the YouTube data we stored, and remove the YouTube video IDs and links from its post records. We keep only that a post went to YouTube on a given date, and our own record of who approved it. Stored search phrase records are removed. Titles the organization approved stay with its posts as its own content.
  • If the organization removes our access in its Google account instead, our daily check finds out, usually within a day, and we then do the same deletion. This always happens within 30 days.
  • The record of who approved each post, the upload page answers, and the record of who agreed to the YouTube terms on the connect page are kept for the length of the organization's agreement with us plus 6 years, and then deleted.
  • When an organization connects Facebook, Instagram or YouTube, the connect page sets one short-lived cookie in its browser so we can confirm the sign-in came back to the same browser. It expires after 15 minutes, is used only for that connection, and is not used for advertising or analytics.

12.5 Your choices

12.6 Google and YouTube

WorkflowUnity Social uses YouTube API Services. By connecting YouTube, the organization agrees to the YouTube Terms of Service, and the Google Privacy Policy applies.

WorkflowUnity Social's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use information received from Google APIs to develop, improve or train general AI or machine learning models.

13. Children

Our sites and services are for businesses and adults. They are not directed to children under 13, and we do not knowingly collect personal information from children under 13. We also do not knowingly sell or share information of anyone under 16. If you believe a child has given us information, email us and we will delete it.

Our sites link to other websites and services, including client sites in our portfolio. We are not responsible for their privacy practices.

15. Changes to this policy

We may update this policy. We will change the "Last updated" date and post the new version on this page. If we make a material change, we will also give notice on our website and email our active clients before the change takes effect where practicable. Changes apply going forward; we will not use information in a materially different way from what we said when we collected it without notice and, where required, your consent. Prior versions are available on request.

16. Contact us

WorkflowUnity LLC
17404 Meridian E, Ste F-1074
Puyallup, WA 98375, USA
Email: [email protected]

For privacy requests, use the subject line "Privacy request" (or "Delete my data," "Do not share," or "Appeal").

See also our Privacy Policy, Terms of Use and Client Agreement.