Skip to content
MaintenanceBlueprint

Legal notice

Last updated:

Publisher

Maintenance Blueprint is published by 17335920 Canada Inc., a business established in Quebec, Canada, which operates under the name Induscoat.

Quebec enterprise number (NEQ): 1181313082.

Canada corporation number: 1733592-0.

Business Number (BN): 733674964RC0001.

Publication director: Hicham.M, P.Eng., PMP.

Contact: contact@maintenanceblueprint.com, or through the contact form on this site.

Protection of personal information

The person in charge of the protection of personal information, as Quebec Law 25 requires a business to designate, is H. Marouazi, for 17335920 Canada Inc.

Requests concerning access to, correction of or deletion of personal data — and withdrawal of consent — are answered within 30 days, the deadline set by that Act.

What this site collects, and what it does not, is set out in full in the privacy policy; what is stored in your browser is listed in the cookie policy.

How this content is produced

Articles, calculators and diagrams are written by practising professionals — engineers working in corrosion protection, industrial coatings and mining maintenance. The technical positions, the judgement calls, and the decision of what a standard means when you have to apply it come from that experience.

That work is then checked with the assistance of an AI system, Claude, developed by Anthropic. It is used to verify internal consistency, to cross-check figures and standard equivalences against the sources cited, to flag any claim carrying no source, and to correct errors. It has caught substantive mistakes: a standard cited under the wrong reference number, and a diagram that showed the opposite of what its own text described.

Nothing is published on the strength of that check alone, and an assisted correction remains a correction made by the publisher, who is responsible for it. Where a value could not be confirmed against a primary source, the page says so rather than presenting it as verified — several pages on this site carry exactly that reservation.

Editorial responsibility

The publisher answers for everything published here, including what was produced with assistance and what was corrected after publication.

Substantive errors are corrected and logged publicly in the corrections log, with their date and what changed. If you spot one, please report it through the contact form — including on a page that names a product or a brand.

What the content can and cannot be relied on for, and the limits of the publisher’s liability, are set out in the terms of use.

Hosting

This site is hosted by Netlify, Inc., 512 2nd Street, Suite 200, San Francisco, CA 94107, United States.

It is a static site: pages are pre-generated and served from a content delivery network.

Intellectual property

Editorial content — articles, calculators, tables and diagrams — is the property of the publisher, except where a source is credited.

Content may be quoted and cited with clear attribution to Maintenance Blueprint and a link to the source page. Calculators and standard equivalence tables are designed to be referenced; each carries a stable URL and a citation note.

Wholesale reproduction of an article, or republication without attribution, is not permitted. The terms of use set out what quotation covers and where it stops.

Trademarks and third-party standards

Standards referenced on this site — ISO, AMPP (formerly NACE and SSPC), ASTM and others — remain the property of their issuing bodies. This site quotes and interprets them; it does not reproduce their text and is not a substitute for buying the standard.

Product and manufacturer names are cited for identification purposes only. Their trademarks belong to their respective owners. Citing a product implies neither endorsement nor any commercial relationship.

Accessibility

The site is built to WCAG 2.1 level AA as a working target, and the accessibility statement says what has been verified, what has not, and which barriers remain.

If something here is unusable for you, reporting it through the contact form is treated like reporting an error: it is acted on, and a substantive fix is logged publicly.