What we hold, why, and how to get it out.
Pipecue processes personal information about homeowners on behalf of the plumbing companies that use it. Last updated 6 August 2026.
This policy describes how Jacob Noseworthy handles personal information in Pipecue. It is written for two audiences: the plumbing companies who are our customers, and the homeowners whose details pass through the product.
Who is responsible for what
When a homeowner sends a quote request to a plumbing company, that company decides why the information is collected and what happens to it. Pipecue processes it on their instructions. In practice: the plumbing company answers questions about a specific homeowner's information, and we support them in doing so.
What we hold
- Homeowner details submitted in a quote request: name, email, phone, address or postal code, and the description of the job.
- Derived information: the two scores, the signals behind them, an estimated job value range, and the drafted reply.
- Workspace activity: notes staff write, follow-ups, outcomes, and a record of which leads were shown and when a reply was sent.
- Account information for the plumbing company's own staff: name, email address, role.
We do not use tracking cookies or third-party analytics. The only cookie Pipecue sets is the one that keeps you signed in.
Automated processing
Quote requests are scored automatically, and a reply is drafted automatically. Neither has legal or similarly significant effects on the homeowner, and neither reaches them without a person at the plumbing company reviewing and approving it. The scores are visible to the plumbing company along with the reasons for them.
Who else processes it
These are the services that hold or handle data today:
- Cloudflare: Hosting, database and file storage. All workspace data, including lead details.
- Anthropic: Lead scoring and reply drafting. The text of a quote request, plus your company's services and service area.
- Stripe: Subscription billing. Your billing contact and payment details. Card data never reaches Pipecue.
- Resend: Sign-in links and approved replies. Recipient email address and message content.
We do not sell personal information, and we do not share one company's leads with another. There is no shared lead pool.
Where it is stored
Data is stored on Cloudflare's network and may be processed outside Canada, including in the United States. Information stored in another country can be accessed by that country's courts and law-enforcement agencies under their own laws. If that matters to you, raise it with the plumbing company you contacted.
How long it is kept
Each workspace has a retention window for homeowner personal information, defaulting to one year from the last activity on a lead. When a workspace is closed, its homeowner data is scheduled for deletion. Records we are required to keep for tax or legal reasons are kept for as long as that requirement lasts, and no longer.
Your rights
Under PIPEDA you can ask what personal information is held about you, ask for a copy, ask for corrections, and ask for it to be deleted. Requests are logged and answered within 30 days.
If you are a homeowner, contact the plumbing company you sent your request to. They hold the relationship and can act immediately. If you cannot reach them, or you would rather come to us, write to Jacob Noseworthy at jacobnoseworthy76@gmail.com.
If you are not satisfied with our response, you can complain to the Office of the Privacy Commissioner of Canada.
Security
Access is scoped to a single workspace at the data layer, so one company cannot read another's leads. Sign-in uses one-time links rather than passwords, and sign-in links, sessions and API tokens are stored only as hashes, so a copy of our database would not yield a usable credential. No system is perfectly secure, and we will tell affected customers promptly if a breach creates a real risk of significant harm, as PIPEDA requires.
Changes
If this policy changes in a way that materially affects how personal information is handled, we will say so in the product rather than quietly editing this page.