Privacy Policy

1. Plain-language summary

Pearson operates a human-managed Canadian business-to-business manufacturing marketplace and coordination platform. We collect information needed to respond to inquiries, manage business accounts and workspaces, review quote requests, protect project files, coordinate manufacturing, manage suppliers, administer jobs and quality records, communicate with business contacts, and meet legal and financial obligations.

The most important points are:

people—not an instant-quotation or automatic-award system—review quote requests, prepare quotes, select any manufacturing partner, and make project decisions;
buyers may begin a quote request without an account, but must authenticate before a private file can be uploaded or a request submitted;
project files and business records may be shared with authorized Pearson personnel and an assigned manufacturing partner on a need-to-know basis;
optional Google Analytics is intended to remain off unless it is configured and the visitor allows it through Pearson's privacy choices; the Google Map on the Contact page is intended to load only after the visitor chooses to load it;
information may be processed outside Canada and may then be accessible under the laws of that place;
Pearson uses proportionate safeguards, permission checks, private storage, and short-lived signed access for protected operational files, but no system can promise perfect security;
Pearson does not currently offer a completed self-service privacy-request or deletion workflow, and it does not automatically delete records under fixed schedules; requests are handled through the contact process below and remain subject to legal, quality, financial, dispute, backup, and operational limits; and
optional automated-assistance features, if specifically enabled, support authorized Pearson personnel and do not automatically set prices, issue quotes, route work, award jobs, or make final eligibility or capability decisions.

This summary helps explain the Policy but does not replace the sections below.

2. Who Pearson is and how to contact us

Pearson Manufacturing Ltd. is responsible for the personal information under its control, including information processed for it by service providers.

Privacy contact

Pearson Manufacturing Ltd., 6198 Netherhart Rd. Unit 7, Mississauga, Ontario L5T 2G7, Canada. Email: info@pearsonmfg.com. Telephone: +1 (905) 564-2885.

The privacy contact coordinates questions, access and correction requests, consent withdrawals, complaints, and incident inquiries. Pearson may assign trained personnel or professional advisers to help respond, but the public contact remains the one above.

3. Scope

This Policy is intended to apply to Pearson's public website, contact and recruitment forms, buyer and supplier areas, organization workspaces, quote and job workflows, private document workflows, communications, and related business operations that link to it.

It covers visitors, people who contact Pearson, buyer users, supplier applicants, approved supplier users, organization administrators, invited teammates, job candidates, customer and supplier representatives, and other business contacts. It also explains information that an employer, organization administrator, teammate, buyer, supplier, or other authorized representative provides about another person.

This Policy does not replace a project-specific agreement, an activated Terms of Service, a mutual non-disclosure agreement, a custom NDA, employment privacy terms, or a service provider's own privacy notice. Those documents may add protections or allocate contractual responsibilities, but they do not reduce rights that cannot lawfully be reduced.

4. Key definitions

Personal information means information about an identifiable individual. Depending on context, it can include a name, business contact details, account identifiers, communications, device or network information, and a person's activity in a workspace. Canadian law may exclude certain business contact information when it is collected, used, or disclosed solely to communicate with the person about their employment, business, or profession.

Confidential technical and commercial information includes CAD models, drawings, specifications, GD&T, tolerances, bills of materials, material information, pricing, forecasts, supplier identities, manufacturing methods, quality documents, and similar project information. It may be highly sensitive without being personal information. If it identifies an individual, both this Policy and the applicable confidentiality terms may apply.

Organization means the buyer, supplier, employer, or other business whose authorized users access a Pearson workspace or act through the platform.

Protected files means project and operational files made available through permission-checked private workflows, such as CAD, drawings, quote attachments, inspection records, invoices, certificates, and job documents.

Processing includes collecting, using, accessing, organizing, storing, transferring, disclosing, retaining, correcting, returning, de-identifying, or deleting information.

5. Information we collect

The information collected depends on how a person and their organization interact with Pearson.

5.1 Website, contact, and business-contact information

We may collect names, job titles, employer or organization names, business email addresses, telephone numbers, addresses, preferred language, the subject and content of an inquiry, referral information, and records of our response. A contact form may include information a sender chooses to place in a free-text field. People should not place controlled, restricted, or unnecessary sensitive information in a public form.

For candidates and recruitment contacts, information may include a résumé, work history, education, qualifications, licences, availability, communications, interview notes, references supplied with authority, and other application material reasonably needed for recruitment.

5.2 Accounts, identity, and workspaces

We may collect an account email address, authentication and email-verification status, user and organization identifiers, profile information, role, permissions, organization membership, invitation and acceptance records, administrator actions, selected active workspace, sign-in and security events, consent and agreement records, notification settings, communication preferences, and account-support communications.

Pearson ordinarily relies on an authentication provider to handle credentials and sessions. We do not need a user's plain-text password. Organization administrators may invite, remove, or manage users and may see workspace activity consistent with their role.

5.3 Quote and project information

We may collect a written project description and structured request information such as part names and numbers, CAD models, drawings, specifications, dimensions, GD&T, tolerances, materials, customer-supplied-material details, quantities, finishes, inspection and documentation needs, requested timing, delivery postal code, budget information, certification or compliance requirements, and NDA status.

Quote and project records may also include clarification messages, internal review notes, assigned personnel or manufacturing partners, capability assessments, quote versions, prices, currency, line items, taxes, estimated lead time, expiry information, buyer decisions, source and acceptance records, and files generated through the workflow. Authentication is required before a private upload or quote submission; a buyer may instead submit a written description without a CAD file.

5.4 Customer-supplied material

Where a customer supplies stock or other material, we may collect material descriptions, ownership and source information, shipment and receiving records, photographs or condition evidence, quantities and weights, heat or lot identifiers where supplied, verification results, custody events, shortages, nonconformance records, instructions, approvals for replacement material, consumption or scrap information, remnant quantities, return or disposal instructions, logistics records, and related communications.

5.5 Buyer jobs and commercial operations

We may collect job, order, part, revision, manufacturing, scheduling, status, message, quality, inspection, certificate, rework, nonconformance, change, packaging, shipping, tracking, delivery, tax, billing, invoice, credit, refund, dispute, and operational-document information. An accepted quote does not itself collect payment; a Pearson administrator converts an accepted quote into a job after review. Live Stripe Checkout is disabled in the present workflow.

5.6 Supplier recruitment, onboarding, and performance

We may collect supplier and contact identity, locations served, capabilities, processes, equipment, capacity, industries, materials, tolerances, quality systems, inspection resources, staffing, ownership or business-registration information, references, insurance, tax, banking or payout-readiness information, WSIB/WCB or other workplace-insurance information, certificates and expiry dates, compliance responses, sanctions or restricted-information screening responses, NDA and agreement acceptance records, and supporting documents.

For approved suppliers, we may also collect RFQ invitations and responses, pricing, availability, capacity, project assignments, communications, job and shipment status, inspection and quality results, corrective actions, performance history, invoices, credits, and payout records. Supplier recruitment and review are manual and do not guarantee onboarding, RFQs, awards, volume, or work. Live Stripe Connect is disabled in the present workflow.

We may collect browser and device type, operating system, page or feature interactions, referring page, approximate location derived from an IP address, IP-derived fraud or security signals, timestamps, session and authentication information, cookie or similar-technology identifiers, application and server logs, error and performance records, rate-limit events, file-access events, permission checks, audit records, consent and agreement records, preference changes, and communications delivery status.

Where optional analytics is enabled and allowed, Google Analytics may collect online identifiers and information about pages and interactions. Section 13 explains the current controls and important limits.

5.8 Information we do not request through the standard workflow

Do not upload controlled goods technical data, export-controlled information, classified or defence-sensitive information, sanctions-restricted information, special-category regulated data, or other unusually sensitive material through the standard website or platform until Pearson has confirmed an appropriate project-specific intake, authorization, storage, access, and handling process. A requested certification field or NDA checkbox is not such confirmation.

6. Where information comes from

We collect information directly from the person who visits, contacts, applies, registers, uploads, submits, messages, or acts in the platform. We may also receive it from:

an employer, organization administrator, teammate, buyer, supplier, customer, shipping provider, inspector, or other authorized representative;
a person who invites a teammate or identifies a project contact;
an assigned manufacturing partner or service provider performing an authorized task;
public business sources and professional directories used for legitimate business contact or supplier review;
authentication, security, email, analytics, mapping, storage, hosting, and similar providers; and
authorities, advisers, or counterparties where permitted or required by law.

Anyone providing another person's information must have authority to do so and must give any notice or obtain any consent required in the circumstances. Pearson may ask the source to confirm that authority.

7. Why we collect and use information

We may process information to:

provide, secure, troubleshoot, and administer the website, accounts, invitations, authentication, organization membership, permissions, and workspaces;
receive inquiries and recruitment submissions and communicate with the relevant business contact;
receive and review quote requests, ask clarifying questions, assess project-specific capability, prepare and revise quotes, and record buyer decisions;
coordinate in-house manufacturing or source an authorized manufacturing partner after human review;
create and administer jobs, parts, changes, quality requirements, inspections, nonconformance, rework, documentation, logistics, and delivery;
receive, verify, track, use, replace with approval, return, or otherwise follow instructions for customer-supplied material;
recruit, review, onboard, verify, communicate with, and monitor suppliers, including capacity, certificates, insurance, workplace coverage, tax, quality, shipment, and payout readiness;
generate and maintain quotes, invoices, credits, tax records, payout records, financial reconciliation, and dispute evidence, while live online checkout and connected payouts remain disabled;
protect confidential information and intellectual property, control protected-file access, generate short-lived signed access, and investigate suspected misuse;
maintain consent, agreement, audit, security, access, quality, and incident records;
prevent fraud, abuse, unauthorized access, malware, infringement, and prohibited or controlled-information intake;
improve usability, reliability, content, workflows, and business operations, including through optional analytics when allowed;
support authorized personnel with limited automated-assistance tools when specifically enabled and subject to the safeguards in section 20;
establish, exercise, or defend legal claims, manage insurance, perform professional audits, and complete corporate transactions; and
comply with laws, lawful orders, tax and accounting duties, manufacturing and quality record obligations, and regulatory requirements.

We will not use personal information for a materially different purpose without providing appropriate notice and obtaining consent where required, unless law permits or requires the use.

Canadian privacy law generally requires meaningful consent for the collection, use, or disclosure of personal information, subject to exceptions. Pearson seeks consent in a form appropriate to the sensitivity of the information and the reasonable expectations of the person.

Some processing is necessary to provide a requested service or administer a business relationship. For example, Pearson cannot privately receive a project file without authenticating the user, cannot submit a quote request without retaining its contents, cannot provide a workspace without security and membership records, and cannot manufacture a part without sharing necessary specifications with authorized personnel or an assigned partner. If a person does not provide necessary information, Pearson may be unable to open an account, review a request, issue a quote, onboard a supplier, or perform a job.

Other choices are optional. Optional Google Analytics is intended to remain disabled unless a visitor affirmatively allows it. Marketing choices must be kept separate from transactional communications and access to core service. An unchecked box, inactivity, or merely viewing a legal page is not agreement acceptance.

A person may withdraw consent to future processing on reasonable notice by using an available preference control or contacting Pearson. Withdrawal does not invalidate prior authorized processing and may be limited where retention or processing is required or permitted by law, a contract, a legal hold, a quality obligation, an active project, security needs, or the rights of others. Pearson will explain material consequences where practicable.

9. Organizations, administrators, and shared workspaces

Business accounts are associated with organizations. Authorized organization administrators may manage membership, roles, invitations, workspace settings, and some records for their organization. Teammates may see project, quote, job, message, quality, invoice, or file information according to their permissions and the active workspace context.

Pearson records the user and organization associated with important actions. An active-context cookie is only a workspace selector; it does not replace current authentication, membership, role, or file-level authorization checks. People should use only the correct organization context and promptly report an incorrect membership or suspected unauthorized access.

If a person uses an organization-controlled account, that organization may independently control or receive account and workspace information. Questions about an organization's own use should also be directed to that organization.

Pearson does not disclose information merely because it could be useful to another marketplace participant. We may disclose only what is reasonably needed in the circumstances to:

Pearson personnel and contractors: authorized people who need information to review, quote, administer, manufacture, inspect, invoice, secure, or support a project;
organization members: administrators and authorized teammates within the relevant buyer or supplier workspace;
manufacturing partners: an assigned or prospective authorized partner given need-to-know project information for capability review, quotation, manufacturing, inspection, fulfillment, or logistics. Pearson uses human review; there is no automatic supplier routing or award;
service providers: providers supporting hosting, private storage, authentication, database, email, security, document generation, analytics, mapping, and—only if enabled—automated assistance. They process information under their terms and applicable contractual restrictions;
shipping, inspection, and project providers: carriers, inspectors, laboratories, material providers, or other providers authorized for a confirmed project;
professional advisers and insurers: lawyers, accountants, auditors, consultants, insurers, and financial institutions subject to professional, contractual, or legal duties as appropriate;
authorities and legal recipients: courts, regulators, law enforcement, tax authorities, or another person where Pearson reasonably believes disclosure is required or permitted by law, necessary to protect rights or safety, or needed to investigate misuse; and
corporate successors: a prospective or completed purchaser, investor, lender, reorganized entity, or successor involved in a financing, merger, reorganization, sale, or transfer, subject to appropriate confidentiality and lawful handling.

A buyer's or supplier's identity can itself be confidential project information. Pearson does not promise that every project will use a partner, and it will not disclose more project information than is reasonably needed for the reviewed purpose.

11. Confidential manufacturing files and intellectual property

CAD, drawings, specifications, quotes, inspections, invoices, certificates, messages, and other operational documents may contain valuable confidential information and intellectual property. Pearson uses permission-checked private workflows and short-lived signed access for protected files. Access links can still be copied, screens can be photographed, authorized recipients can mishandle information, and no technical control eliminates every risk.

Pearson may use confidential project information only for the business purposes described in this Policy and the applicable Terms, NDA, custom NDA, project document, or supplier agreement. Authorized recipients must protect it and use it only on a need-to-know basis. Pearson does not obtain ownership of a customer's intellectual property merely by receiving it.

Users must have lawful authority to provide files and must not place confidential information in public forms or unprotected messages. Downloaded copies are controlled by the recipient's systems and obligations, not by Pearson's signed-link expiry alone.

12. Service providers and platform dependencies

The platform presently uses or contains integrations for providers that may include Supabase for authentication, database, and storage functions; hosting and infrastructure providers; transactional email providers; and Google for optional Analytics and a user-loaded Map. Feature-gated code also supports Anthropic for authorized administrator RFQ-field extraction and OpenAI for embeddings if those tools are deliberately enabled and configured.

The presence of integration code does not establish that a feature, vendor, model, or data flow is active in every deployment. Provider regions, production configuration, subprocessors, contractual settings, and retention settings have not all been verified for production. Pearson does not promise that information remains only in Canada or that every provider follows a particular deletion schedule unless that promise is expressly confirmed in an identified document.

13. Cookies and technologies

Pearson uses cookies, browser storage, signed links, pixels, scripts, and comparable technologies for the following purposes.

13.1 Essential and functional technologies

Supabase authentication and session technologies maintain sign-in, session continuity, and security. Their exact cookie or browser-storage format can vary with the authentication flow.
pearson_active_context remembers the selected authorized buyer, supplier, or administrator workspace. It is a server-set, HTTP-only selector and does not grant permission on its own.
cx_locale remembers a visitor's selected language preference.
pearson_privacy_preferences remembers whether optional analytics was allowed or declined.
Security, load-balancing, rate-limit, and application technologies may help keep the service reliable and detect misuse.

Essential technologies are used because the requested account or platform function would not work securely without them. Blocking them in a browser may prevent sign-in, private-file access, workspace selection, or other features.

13.2 Google Analytics

Google Analytics is an optional website-measurement feature. The current application behaviour is that analytics must be enabled by Pearson through its analytics feature configuration, a Google measurement identifier must be present, and the visitor must choose Allow analytics before the Google Analytics script loads. The implementation requests IP anonymization and may create Google cookies such as _ga and _ga_*. A visitor can choose Essential only initially or reopen Privacy choices in the footer and withdraw permission; Pearson attempts to remove first-party Google Analytics cookies it can identify, although a withdrawal cannot retrieve data already transmitted or erase every provider-side record.

If a deployment does not present those controls or loads analytics before permission, that deployment does not match this Policy and requires correction and separate privacy review. Google determines aspects of its own processing, retention, and international transfers under its terms. Browser privacy tools may provide additional control.

13.3 Embedded Google Maps

The Contact page provides a Google Map. The current application behaviour is that the embedded map does not load until the visitor selects Load Google Map. Opening directions in a new tab also takes the visitor to Google. Once chosen, the browser connects to Google and may send IP address, browser, device, referrer, location-related, cookie, and interaction information under Google's terms. The map choice is separate from the Analytics preference.

14. Processing outside Canada

Pearson and its providers may process or store information in Canada, the United States, or other jurisdictions in which an authorized provider, subprocessor, partner, adviser, or recipient operates. Information outside Canada is subject to the laws of that jurisdiction and may be lawfully accessible to courts, governments, law enforcement, or national-security authorities there.

Pearson remains accountable for personal information transferred to a provider for processing under its control and uses contractual, organizational, and technical measures appropriate to the service and sensitivity. Those measures cannot prevent every lawful foreign demand. Because production vendor regions and settings require verification, this Policy makes no Canadian data-residency promise. Contact Pearson to ask about current processing arrangements relevant to a particular service.

15. Retention, legal holds, and deletion limits

Pearson retains information only as long as reasonably needed for the purposes described in this Policy and for legitimate legal, contractual, security, financial, quality, insurance, dispute, and operational requirements. Relevant criteria include:

whether an inquiry, account, supplier review, quote, job, warranty, quality issue, shipment, invoice, dispute, or business relationship remains active;
manufacturing traceability, inspection, certificate, nonconformance, rework, customer-supplied-material custody, and product-liability needs;
tax, accounting, corporate, insurance, employment, limitation-period, and regulatory obligations;
security, fraud, access, agreement, consent, and incident evidence;
a litigation, audit, investigation, preservation notice, or legal hold;
the sensitivity, volume, location, and format of information and whether it can reasonably be de-identified; and
provider backup cycles, technical dependencies, and the feasibility and risk of deletion.

Pearson does not presently operate an automated retention or deletion engine or promise fixed deletion periods for platform categories. Internal retention entries are planning records, not automatic deletion instructions. Financial, manufacturing, quality, regulated, dispute, and customer-supplied-material custody records may need to be kept after an account closes. Legal holds override ordinary deletion activity.

Deletion from active systems may not immediately remove information from secure backups, immutable acceptance receipts, security evidence, or records another organization independently controls. Backup copies may remain inaccessible until overwritten in the ordinary cycle. Pearson retains breach records for the period required by applicable law; federal breach regulations currently require certain breach records to be kept for at least 24 months.

16. Safeguards and incident response

Pearson uses safeguards proportionate to the sensitivity, amount, format, location, and foreseeable risks of the information. Depending on the system and role, safeguards can include authentication, role and organization checks, row-level database policies, private storage, permission-checked short-lived signed access, encryption in transit, provider access controls, audit records, rate limits, backups, staff procedures, confidentiality obligations, and incident review.

Security is a shared responsibility. Users must protect credentials and devices, verify recipients, use the correct workspace, avoid public links for protected files, and promptly report suspicious access. No safeguard, transmission, provider, or storage system is perfectly secure, and Pearson does not guarantee that an incident will never occur.

Pearson investigates suspected incidents, contains and remedies them as appropriate, preserves required records, and assesses whether notification or reporting is required. Pearson will keep records of breaches of security safeguards as required by applicable law, including breaches that do not meet the reporting threshold. Where Canadian law applies, Pearson will report a breach of security safeguards posing a real risk of significant harm to the Office of the Privacy Commissioner of Canada and notify affected people as soon as feasible, and will notify another organization or government institution where required to reduce or mitigate harm.

17. Access, correction, withdrawal, and deletion requests

Subject to identity verification and legal exceptions, a person may ask Pearson to:

explain whether Pearson holds personal information about them and how it has been used or disclosed;
provide access to personal information under Pearson's control;
correct inaccurate or incomplete personal information;
withdraw consent for future processing where consent may lawfully be withdrawn;
change an optional communications or analytics preference; or
delete personal information where deletion is applicable and not overridden by a lawful reason to retain it.

Send a request to info@pearsonmfg.com with enough information to identify the person, the organization and workspace involved, the requested records, and the action sought. Do not email unnecessary identity documents or protected project files. Pearson may use a safer method to verify identity, authority, and account ownership. An organization administrator cannot automatically exercise an individual's privacy rights without authority, and Pearson may need to consult an organization that controls the relevant business record.

Pearson does not currently provide a completed self-service privacy-request, export, or account-deletion workflow. Administrative request records are tracking and review tools; a deletion request does not trigger automatic erasure. Pearson will respond within the period required by applicable law, may charge only a lawful and disclosed fee, and will explain a refusal or material limitation where required. Access may be limited to protect another person's information, confidential commercial information, legal privilege, security, an investigation, or information that cannot reasonably be severed.

18. Questions, complaints, and regulatory escalation

Please raise a question or complaint with Pearson's privacy contact first. Include the relevant date, organization, account or project context, the concern, and the requested outcome without sending unnecessary confidential files. Pearson will review the issue, may ask clarifying questions, and will explain its findings and any appropriate corrective step.

If a concern is not resolved, a person may contact the Office of the Privacy Commissioner of Canada. The regulator's processes and jurisdiction determine whether it can investigate a particular matter. Using Pearson's complaint process does not remove any right to contact a regulator.

19. Transactional email, marketing, and CASL choices

Pearson may send service and transactional communications reasonably connected to an inquiry, authentication event, invitation, quote, project, job, quality issue, shipment, invoice, supplier review, security event, legal notice, or requested support. These are different from optional marketing, although some Canadian anti-spam requirements may still apply depending on the message.

Pearson will send commercial electronic messages only where it has the consent or other lawful basis required by Canada's Anti-Spam Legislation and will include required sender identification and a working unsubscribe mechanism when required. Unsubscribe requests must be given effect within the legally required period. Withdrawing marketing consent does not stop necessary transactional or security messages.

A supplier application or account setting may store an optional marketing preference. A stored preference alone does not establish that Pearson currently operates a complete marketing campaign or self-service unsubscribe workflow. Pearson must confirm the consent evidence, message content, sender identification, unsubscribe process, and operational suppression controls before using that preference for optional marketing. Until then, the platform's email workflow is intended for approved operational and transactional categories, not broad commercial marketing.

20. AI and automated assistance

Pearson's core quote, supplier, and project workflows are human managed. The platform does not provide instant quotations, automatically award work, automatically route buyers to suppliers, automatically confirm capability or compliance, or guarantee an outcome.

The codebase contains feature-gated tools that may, only when deliberately enabled and configured, assist authorized Pearson administrators by:

sending relevant inbound RFQ text to Anthropic to extract proposed structured fields for human review; and
sending approved, sanitized text to OpenAI to create embeddings used for internal, administrator-only similarity suggestions.

Those features are off when their controlling feature flag or provider credential is absent. Their outputs are suggestions and must be reviewed by a person. They do not determine prices, lead times, supplier routing, awards, onboarding, capability, compliance, or final project decisions. Pearson must verify the actual production flags, provider contracts, regions, data settings, sanitization, access controls, and notices before either feature handles personal or confidential information.

Pearson does not authorize personnel, suppliers, or other recipients to place confidential project information into public, shared, or general-purpose AI services or to use it to train a public or shared model. That restriction does not itself prove what an external provider does; provider use and retention must be governed and verified through the applicable configuration and contract. A person may ask for information about any enabled automated assistance relevant to their information through the privacy contact.

21. Business use and age limitations

The website and platform are intended for business use by adults acting for themselves or an organization and are not directed to children. A person creating an account, accepting an agreement, or submitting a project must have legal capacity and authority to do so. Do not provide a child's personal information through the standard workflow. If Pearson learns that such information was submitted without appropriate authority, it will assess reasonable removal and preservation steps subject to legal and operational requirements.

22. Third-party links and embedded services

The site may link to or, after a user's choice, load services operated by Google, shipping providers, authentication providers, social or professional sites, and other third parties. Their privacy notices and settings govern information they independently collect. Pearson does not control every third-party site, browser extension, downloaded file environment, or recipient system and is not responsible for a third party's independent practices merely because the platform links to it.

Before sending information to a third party or loading an embedded service, consider the nature of the information and the third party's terms. Project-specific transfers by Pearson remain subject to the sharing and accountability provisions above.

23. Changes to this Policy

Pearson may propose changes to reflect legal, operational, vendor, security, or platform developments. A proposed draft, placeholder, future-effective version, deprecated version, blank version, or hash-mismatched version is not an activated policy.

Before a material revision is activated, Pearson will identify its title, version, effective date, last-updated date, review and publication state, authoritative source, and server-computed SHA-256 content hash. Pearson will provide notice appropriate to the significance of the change and obtain a new affirmative choice or agreement where law or the applicable acceptance process requires it. Continuing to view a public page is not, by itself, acceptance of contractual terms.

Archived or cached text may differ from the authoritative activated version. The exact version displayed in an acceptance workflow must match the exact body and hash recorded in the acceptance receipt.

24. Contact information

Questions, requests, complaints, and incident reports about privacy may be sent to:

Pearson Manufacturing Ltd., 6198 Netherhart Rd. Unit 7, Mississauga, Ontario L5T 2G7, Canada. info@pearsonmfg.com. +1 (905) 564-2885.