Last updated October 20, 2026

Privacy Policy

AIforBC, operated by Boost Commerce Group, collects information you choose to provide through inquiry, assessment, Project Brief review, solution-request, provider-application, training-interest, learning-program, cohort, and newsletter forms. This may include your name, work email, company, industry, role, team size, objectives, workflow information, readiness inputs, priorities, and implementation constraints.

How we use information

We use submitted information to respond to requests, qualify training or implementation needs, operate the service, improve our offerings, and—where you separately consent—send the AIforBC Brief. We do not claim that assessment submissions are anonymous.

Service inquiries and notification records

When you submit a service inquiry, we store its details, service-contact consent, source page, and request ID. The request ID helps recognize repeat submissions and lets you refer to a saved inquiry. We also store records for the operator notification and your acknowledgement, including the recipient, message content, retry status, and email-provider reference where returned. A saved inquiry does not book a service, authorize implementation, take payment, or subscribe you to marketing. Email-provider acceptance is not proof of inbox receipt.

Separate newsletter consent and confirmation

Newsletter signup is separate from a service inquiry. New website signups use beehiiv's hosted signup page. You request the newsletter there and must confirm by email. You are not an active marketing subscriber until you use a valid confirmation link. Beehiiv processes your address, consent, signup source, subscription status, confirmation and unsubscribe events, and delivery records. The weekly Brief may include clearly labelled advertising. Submitting a service inquiry does not subscribe you.

Confirmation and newsletter messages include private, tokenized confirmation or unsubscribe links. Do not share those links. Unsubscribe links allow withdrawal of newsletter consent. Use the unsubscribe link supplied in your message, or make a privacy request through the contact form if you cannot access it. Withdrawing marketing consent does not delete a separately saved service inquiry. An unconfirmed signup is not permission to send marketing editions.

Historical signup, consent, suppression and delivery records in AIforBC's existing system are retained; this website change does not import or automatically resubscribe those addresses to beehiiv. Existing confirmation and unsubscribe links remain supported. Use the link in the relevant message, or contact us to request withdrawal across historical records.

Assessments and aggregate research

Assessment responses and generated scores are stored as identifiable business records so we can provide the report, respond to requests, improve the assessment, and understand implementation needs. If you request implementation support, we may record qualification, matching, pilot-baseline, follow-up, and observed-outcome notes as private operating records. If we later publish aggregate research, we will separate reporting from direct identifiers and disclose the sample size and methodology. We will not present a small or unrepresentative sample as a definitive BC-wide statistic.

Solution matching and provider applications

Public Project Brief planning fields, fictional workflow exercises, and calculator assumptions are handled in the browser while you use the tools. The planning text is not sent as a service inquiry unless you deliberately submit an optional review/help request. Printing, downloading, or copying a brief produces your own copy; consider where you store or share it. Public-tool interaction events may still be recorded as described below, without the free-text planning content.

Project Briefs and direct solution requests may include your workflow, owner, frequency, inputs, approved output, success measure, business problem, desired outcome, current tools, timing, budget range, and the sensitivity of information involved. We use those details to review possible software, provider, or training paths. We do not make a provider introduction solely because a form was submitted. Provider applications include contact, service, pricing-model, customer-fit, and evidence information. Contact details and private review notes are not published as part of a public profile.

Analytics and service providers

The current service uses Vercel for hosting, Neon for the application database, Resend for service-notification and historical newsletter-confirmation email, and beehiiv for new newsletter signup and delivery. Opening the hosted signup page connects your browser to beehiiv and its service providers, which may process technical browser/network information. Beehiiv also processes newsletter delivery and engagement information, such as opens and link clicks. Approved campaign labels and a fixed label for the public page where you entered the site may accompany the signup link. We do not forward arbitrary query values, full referrer URLs or email addresses in that link. Beehiiv records subscription status. A website visit or signup link click does not count as confirmation. See beehiiv's Privacy Policy. Hosting may process technical requests and logs; the database stores submitted records and operational state; email processing includes recipient addresses, message content, delivery attempts, and provider references. Provider processing is governed by the applicable service terms and configurations. Naming these providers is not a claim of Canadian-only storage, absolute security, or legal compliance. Payment processing, where enabled, is described separately below.

Learning programs, cohorts, and evaluation

Learning requests may include the program, requester type, organization, role, expected group size, preferred format, timing, location, experience level, planning needs, and accessibility or language considerations you choose to share. Please do not submit medical records or other sensitive details. We use this information to review fit, plan delivery and support, operate a cohort, and evaluate the program. Pilot evaluations may record confidence, completion of fictional learning tasks, verification and privacy behaviours, accessibility friction, and feedback. A request does not create a learner account, confirm a cohort, or authorize payment.

We use first-party product measurement to understand whether visitors reach useful outcomes, such as viewing an Action Plan or selecting a next step. These records may include an automatically generated browser identifier, page path, referral or campaign information, and the choices made in the Navigator. The identifier is stored in your browser so repeat visits can be counted without asking for contact information. We do not include names, email addresses, or free-text form answers in these product-event records. This release does not load Google Analytics or forward events to third-party analytics, even when an analytics ID is configured. Product measurement excludes learner, operator, private payment, evaluation, and newsletter confirmation/unsubscribe routes. Allowed public paths have query strings and fragments removed; only selected categorical event and campaign fields are retained. Hosting and security providers may still keep technical request logs; this is not a promise of anonymous browsing.

Self-serve course accounts and progress

Self-serve courses are separate from proposal-based team bookings. Email sign-in creates a learner record and an expiring session. We store your email, verification time, hashed session and challenge tokens, code-verification HMACs, expiry and retry-limit records. The session cookie is HTTP-only. Authorized course records include access status and expiry, course version, lesson pass status, score and completion time. These records are linked to your account, not anonymous.

Free sample feedback does not require an account. Practice drafts and workbook notes stay in the current page; they are not submitted as product events or saved as course progress. Structured quiz answers are sent for grading; saved paid-course progress records contain results, not your freeform draft. Use fictional information and do not enter private customer or employer data.

Retention and safeguards

We retain information only as long as reasonably needed for the purpose collected, legal obligations, and legitimate business records. No internet service can guarantee absolute security.

Transactional email and payments

When transactional email is configured, we send request and payment messages through our email provider. For self-serve course receipts and refunds, we record queued, sending, provider-accepted or failed states and use bounded retries; uncertain older attempts require operator reconciliation. Provider acceptance is not proof of inbox delivery. Marketing consent is separate. For an accepted learning proposal, a private payment page may send you to Stripe's hosted checkout. Stripe collects payment and billing details under its privacy terms. AIforBC records the proposal reference, agreed amount, payment status, provider identifiers, and refund status; it does not ask you to email card numbers or banking credentials.

When self-serve checkout is enabled, course orders also retain the accepted terms version, course and price snapshot, access period, tax policy, provider references and transactional notice records. Authorized operators can review orders, current access, completion counts and failed notices. Payment-provider confirmation, current access and email acceptance are separate states.

Your choices

You can request access, correction, or deletion, or withdraw newsletter consent, through the contact form for privacy requests. Include a request ID if available and only the details needed to describe the request; do not upload identity documents, passwords, confidential records, or personal information about someone else. We may need to verify a request before acting. Some records may be retained where legally required. For an error in an educational page, use the resource-correction form.