Privacy Policy

Pacific Yew Automations is responsible for personal information under our control. Privacy questions, access requests, and concerns may be sent to contact@pacificyew.pro.

This policy applies to this website and to personal information Pacific Yew handles while delivering a client service. A client Statement of Work identifies the systems, purposes, access, retention, and responsibilities that apply to a specific workflow.

The fit-call form collects a contact name, company name, email address, optional phone number, preferred response method, service interest, business type, workflow problem, software selections, and a short description of the desired improvement. We use this information to respond, assess fit, and prepare for a requested conversation.

The website may also process basic request, device, and usage information through hosting, security, and analytics services. We do not sell inquiry information or use it to build unrelated advertising profiles.

We design each client workflow with security controls appropriate to the data and systems involved, including encrypted transport, least-privilege access, and secure credential handling. The applicable controls are documented in the client’s Statement of Work and implementation plan.

This public website does not host a client database. Fit-call requests are sent by email to contact@pacificyew.pro through the configured email-delivery provider and may also be passed to a configured business intake system. Those providers may retain delivery and security records under their own terms. If a client workflow requires stored data, its provider, access controls, retention period, and incident procedures are agreed before launch.

Website hosting, analytics, email delivery, and client-selected software providers may process information outside British Columbia or Canada. Their personnel or authorities may access information under the laws that apply where it is processed.

Where a client requires a particular data location, we assess the proposed providers and document the agreed data flow and hosting choices before launch. We do not represent that every third-party service is Canada-resident by default.

Your proprietary operational data remains yours. Before enabling AI in a client workflow, we review the selected provider’s data-use, retention, and training terms with the client and configure available controls accordingly.

No client data is intentionally supplied to a public model-training workflow by Pacific Yew. Provider-specific commitments are documented in the applicable Statement of Work rather than assumed from this website.

In accordance with BC PIPA, individuals have the right to request access to their personal information held under our control. They also have the right to request correction of inaccurate, incomplete, or outdated information.

Individuals may ask us to correct or delete personal information under our control, subject to identity verification and any legal, security, contractual, or record-retention exception that applies. Requests may be sent to contact@pacificyew.pro.

Pacific Yew uses consent and other lawful bases applicable to the message before sending commercial electronic messages. Transactional replies to a requested fit call are used to respond to that request.

Commercial messages sent by Pacific Yew identify the business and provide a way to unsubscribe. Replying STOP opts out of SMS where that channel is enabled. Unsubscribe requests are applied within the period required by applicable law.

Mobile information, SMS opt-in data, and phone numbers collected for messaging are not sold, rented, or shared with third parties or affiliates for their marketing or promotional purposes.

We retain inquiry and client information only as long as reasonably needed to respond, deliver the agreed service, maintain business and security records, resolve disputes, or meet legal obligations. Provider delivery and security logs follow the provider terms and configuration that apply to the service.

When information under our control is no longer required, we delete or anonymize it using the capabilities of the systems in which it is held.