Legal

Terms of Service

Effective: 2026-06-06 Last updated: 2026-06-22

Summary (Non-binding)

These Terms of Service ("Terms") govern your use of the PiFlow website and the productized software engineering services you purchase from PiFlow Inc., operating publicly as PiFlow ("we", "us", or "our").

This summary is for convenience only. The sections below are the binding terms. Any signed statement of work, proposal, invoice, checkout summary, or written scope confirmation controls the commercial details for a specific engagement.

Who We Are

PiFlow Inc. is the legal operator of PiFlow, a productized software engineering studio. We build production-ready MVPs and app slices for new projects, rescue and stabilize existing applications, and provide optional monthly support plans.

We are not a commodity hosting provider. When we manage hosting, we coordinate and operate third-party platforms so clients do not have to manage deployment, environment variables, monitoring, vendor setup, or support handoff.

We sell fixed-scope outcomes, not unlimited hourly development, open-ended agency retainers, or standalone hosting-only plans.

Use of the Website

You may use this website for lawful purposes only.

You agree not to interfere with the site's operation, attempt unauthorized access, scrape or misuse the site, or misuse contact forms and scheduling tools.

Services; Statements of Work

If you purchase services from us, the specific scope, timeline, price, payment terms, assumptions, and deliverables will be described in a written scope or statement of work ("SOW"). A SOW may be a signed document, proposal, invoice, checkout summary, or written email confirmation that clearly identifies the package and accepted scope.

If there is any conflict between a SOW and these Terms, the SOW controls for that engagement.

Productized Delivery; Scope and Change Requests

Our packages are designed to deliver a single, scoped outcome within a defined timebox. Launch Sprints, Founder Launch Bundles, Technical Discovery, cleanup/stabilization work, feature packs, and support plans each have defined boundaries.

Before implementation begins, we aim to confirm acceptance criteria, required access, primary users, core workflow, required third-party services, and known exclusions. Changes outside the agreed scope may require a change order, additional fees, and/or additional time.

  • Acceptance criteria: completion is measured against the agreed package description and SOW, not against every possible future feature.
  • Change orders: new workflows, extra feature packs, additional roles, complex integrations, data migration, regulated compliance work, or major design changes may be quoted separately.
  • Technical Discovery: discovery and diagnostic engagements do not include production code changes unless expressly included in the SOW.

Client Responsibilities

To deliver efficiently, you agree to provide timely feedback, access, decisions, materials, and payment information when requested.

  • Provide necessary credentials/access to your existing codebase and accounts, or create new accounts if needed.
  • Provide brand assets, copy, requirements, and decisions in a reasonable timeframe.
  • Confirm acceptance criteria and review deliverables promptly.
  • Ensure you have the rights to any materials, data, content, designs, or third-party assets you ask us to use.
  • Keep payment methods, third-party vendor accounts, domains, DNS, and required subscriptions active unless the SOW states otherwise.

Third-Party Services

We may use third-party providers to deliver parts of the service, such as Vercel, Supabase, Stripe, Resend, Calendly, GitHub, Sentry, analytics tools, AI API providers, domain registrars, and other vendors identified in a SOW or project handover. These providers, not PiFlow, operate the underlying hosting, database, storage, email, payment, monitoring, source-control, AI, scheduling, domain, and infrastructure services.

Your use of those services may be subject to their own terms, privacy policies, pricing, limits, outages, policy changes, and usage charges. Unless a SOW says otherwise, vendor fees, overages, custom domains, premium infrastructure, AI usage, dedicated databases, and similar pass-through costs are your responsibility.

Payments

Pricing is shown on the website or in your SOW and is generally stated in Canadian dollars unless a client-specific quote says otherwise. PiFlow Inc. is the invoice and payment counterparty unless a SOW states otherwise. Applicable taxes, if required, are handled on the final invoice or subscription confirmation; payment processor fees, vendor costs, and overages may be added or passed through where applicable.

Project work, feature packs, bundles, change orders, Code Ownership, and custom work are generally billed as one-time charges or invoices. Monthly support plans are billed as recurring subscriptions. Work may be paused or delayed if payment is late, fails, is disputed, or required billing information is missing.

Delivery, Review, and Acceptance

We will provide the deliverables described in the SOW and/or package description. Timelines depend on timely payment, scope confirmation, client feedback, required access, vendor availability, and the technical condition of any existing systems we are asked to work with.

You agree to review deliverables and provide feedback within a reasonable period so we can finalize work. If feedback is delayed, the project timeline may shift and the engagement may be paused until we receive what is needed.

  • Handover: package-appropriate handover may include deploy notes, environment/secrets notes, service links, known limitations, and next-step recommendations.
  • Acceptance: a deliverable is accepted when it materially satisfies the agreed acceptance criteria or when you use it in production without reporting an in-scope issue within the review period stated in the SOW.
  • Day-5 checkpoint: for eligible new-build sprints, if you are not confident by the day-5 checkpoint that we can deliver the agreed scope, you may request cancellation and a full refund of PiFlow service fees paid for that sprint, subject to the SOW conditions and exclusions.

Support Plans

If you subscribe to a monthly support plan, it provides managed hosting, monitoring, reporting, and/or incremental improvements as described in the selected plan. Managed hosting means PiFlow manages deployment, configuration, monitoring, vendor coordination, and support on third-party platforms. It is included with active support plans; PiFlow does not sell a standalone hosting-only plan.

Support plans are not unlimited retainers. They are bounded by the plan description, business-hours response commitments, outcome lane, and any SOW-specific limits.

  • Response commitments: support response times are response targets during business hours, not guaranteed resolution times.
  • Care: managed hosting, monitoring, reporting, email support, and maintenance fixes/small corrections.
  • Launch Partner: Care plus a scoped enhancement lane, roadmap reviews, and a 48-hour business-hours response target.
  • Growth: Launch Partner plus active feature iteration, a 24-hour business-hours response target, quarterly performance/security review, and monthly analytics review.
  • Unused monthly support lanes do not roll over unless the SOW says otherwise.
  • Self-hosted support is quoted individually. Self-hosting requires Code Ownership.

Hosting, Code Ownership, and Self-Hosting

When PiFlow manages hosting, we operate the deployment on third-party platforms as part of an active support plan and may retain administrative access needed to configure, deploy, monitor, troubleshoot, and support the application. PiFlow manages the operational layer; it is not the underlying hosting, cloud, database, or infrastructure provider.

Code Ownership is the path for repo/deployment/self-hosting transfer. It does not transfer PiFlow's pre-existing tools, templates, starter-kit code, reusable patterns, internal processes, or know-how except as expressly licensed or embedded in the deliverables.

If you choose self-hosting, you are responsible for your own hosting account, vendor billing, uptime, backups, security operations, updates, and incident response unless a separate self-hosted support SOW says otherwise.

Intellectual Property

You retain ownership of materials you provide to us, including your brand assets, content, product information, customer data, and pre-existing code or designs.

Unless a SOW says otherwise, client-specific deliverables created for you transfer to you when all fees for the applicable engagement are paid in full. Drafts, unused concepts, internal notes, tools, templates, starter-kit components, generalized code, processes, and know-how remain PiFlow's property.

Where PiFlow-owned or third-party materials are included in a deliverable, you receive the rights needed to use the deliverable for your business, subject to any third-party license terms and SOW limits.

Confidentiality

If you share confidential information with us, such as product plans, credentials, customer lists, business records, unreleased product information, or private code, we will use reasonable care to keep it confidential and use it only to provide the services.

We may sign a separate mutual NDA where appropriate. A separate NDA or SOW may add stricter rules for sensitive projects, credentials, regulated data, or unreleased product information.

Disclaimer

The website and services are provided on an "as is" and "as available" basis, except as explicitly stated in a SOW.

We provide software engineering services, not business-outcome guarantees. We do not guarantee revenue, funding, rankings, traffic, conversion rates, user growth, uninterrupted third-party platform uptime, or that a project will satisfy a law or regulatory framework unless the SOW expressly includes that work.

Limitation of Liability

To the maximum extent permitted by law, PiFlow will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, including lost profits, lost revenue, loss of data, loss of goodwill, business interruption, or third-party platform failures.

To the maximum extent permitted by law, PiFlow's total liability for a claim related to a paid engagement is limited to the fees you paid PiFlow for the specific SOW or service giving rise to the claim. Some jurisdictions do not allow certain limitations, so some limits may not apply to you.

Termination

Either party may terminate an engagement as described in the applicable SOW.

Unless a SOW says otherwise, fees for completed work, committed support-plan fees, third-party costs, and accepted deliverables are not refundable. On termination, we may revoke access we control, preserve or return client materials as appropriate, and provide a reasonable transition path for paid deliverables.

Governing Law

These Terms are governed by the laws of New Brunswick and the federal laws of Canada that apply there, without regard to conflict-of-law rules. The parties will first try to resolve disputes informally and in good faith. If a dispute cannot be resolved informally, it may be brought in the courts with jurisdiction in New Brunswick, Canada, unless a SOW requires a different process.

Changes to These Terms

We may update these Terms from time to time. The "Last updated" date indicates when changes were made.

Contact

If you have questions about these Terms, contact PiFlow Inc.:

Email: contact@piflow.ca

This page is provided for general informational purposes and should be reviewed with counsel if you have specific legal requirements.