Chain of custody, sent.
After field collection, the inspection record and chain of custody move directly to the configured laboratory partner.
Environmental consulting
Field inspections. Lab handoffs. Professional review.
Inspectors can create projects, capture samples, and track submissions from one focused mobile workspace, even when the connection is unreliable.
Illustrative product view · sample project data
3 samples · Updated today at 10:42 AM
8 samples · Updated yesterday
Riverside renovation · 6 samples
From the first field observation to the final client report, the project record stays connected. Professional judgment stays with your team.
After field collection, the inspection record and chain of custody move directly to the configured laboratory partner.
Explore a discipline. Asbestos inspection software
Illustrative photography
Final Report Generated. Your final report is ready to review, share, or archive.
Completed final report with approved laboratory results.
Track whether results are added and when the client copy is sent.
Preview, stage, and deliver the final report from one focused administrative workspace.
Illustrative product view · sample project data
Find stored final reports without digging through folders, inboxes, or disconnected file systems.
Illustrative product view · sample project data
Search by project number or user name. Use the calendar fields to filter stored dates.
Harbor Medical Suite Renovation
Originating user: Jordan Ellis
Stored: Jul 15, 2026 at 5:03 PM
2 reports
Riverside Kitchen Survey
Originating user: Casey Morgan
Stored: Jul 4, 2026 at 8:04 PM
Requirements, citations, and configured thresholds beside the project record.
Federal, state, local
Requirements and citations
Results against configured thresholds
Your professional confirms what applies.
Every Almic Systems engagement is shaped around the organization using it.
Pricing depends on your team size, inspection workflows, reporting requirements, and rollout needs. We learn how your operation works, configure the right workspace and implementation plan, then provide a quote built for your organization.
We review your team size, inspection disciplines, current process, and reporting requirements.
We map the workspace, branding, laboratory flow, report setup, onboarding, and launch support.
You receive clear implementation and ongoing platform pricing based on the configuration your team needs.
See how a project moves from field capture through laboratory coordination to final delivery. Bring your current process and reporting requirements.
Prefer email? Contact our team.
Almic is built around multidisciplinary environmental consulting teams, with discipline-specific field data and a connected operational record. We configure your workspace around the inspection disciplines, laboratory partners, review responsibilities, and reporting requirements of your organization.
Yes. Full offline capability as a progressive web app. Create projects, collect samples, and take photos without internet. All data syncs when connectivity is restored.
Labs send results via email. Our system automatically parses the data, matches results to sample IDs, and populates them into the report. PLM, XRF, and spore count formats are all supported.
iOS, Android, macOS, Windows, Linux, and any modern browser. No app store required; install as a progressive web app from any link.
The system validates sample data, generates the COC document, and dispatches it to your configured partner lab via email, with the PDF attached and delivery confirmation tracked.
Contact us at contact@almicsystems.com. We'll configure your workspace, user roles, and laboratory integrations.
See why connected field records, laboratory results, compliance checks, and final reporting matter. Then explore the cases and rules shaping environmental inspection work.
Selected reading from public agencies, with the operational lesson for environmental inspection teams.
EPA found hundreds of renovations where required certification, training, and lead-safe documentation could not be established or produced. The settlement required an electronic compliance system and detailed checklists.
Read the official case
Georgia settlements cited alleged failures to complete asbestos inspections or provide written notice before work began. The survey, notice, and project record need to move together.
Read the enforcement brief
EPA says reports, pamphlet-distribution records, and compliance documentation must be retained for three years after a renovation. Searchable archives make that repeatable.
Review the record list
OSHA requires exposure-monitoring records, document access, and regular inspections by a competent person. Centralized evidence helps the record survive handoffs and scrutiny.
Read the standard
A proposed nationwide settlement requires a corporate program for contractor qualifications and lead-safe work practices after alleged violations across hundreds of homes.
Read the settlement
EPA alleged Scranton schools lacked complete, updated asbestos management plans in required locations. The settlement required demonstrated compliance across all buildings.
Read the school case
NIOSH says visual inspections and musty-odor detection can be more reliable than short-term air sampling. Its assessment tool helps teams track conditions over time.
Read the guidance
EPA guidance describes an accurate written trail from collection through disposal, including each transfer, receipt, condition check, and analysis performed.
Read the sampling guideEducational content only. Requirements vary by jurisdiction and project; consult the applicable agency rules and qualified legal or compliance professionals.
Last updated: September 28, 2026
Almic Systems LLC, a Texas limited liability company (Almic), provides the Services covered by this Privacy Policy. This Policy describes information Almic handles for its own website, account, billing, support, and security purposes. For project and inspection information submitted by a customer, that customer generally decides what is collected and how it is used; Almic processes it to provide the Services under the applicable agreement and any signed Data Processing Addendum.
Information may include account and contact details, walkthrough booking details, professional credentials, support messages, billing identifiers and payment status, and technical information such as device details, access logs, and service usage. Customer-submitted information may include project and site details, property addresses, sample locations, field notes, photos (including EXIF data), floor plans, laboratory reports, chains of custody, AI extraction information, and correction records. We receive information from users, customer administrators, laboratories and integrations used for a project, and automatically from devices that access the Services.
The Services use browser or device storage for sign-in and offline work. This public page also loads fonts and scripts from third-party hosts, which receive basic request information such as an IP address and browser details.
We process information to provide and configure the Services, manage accounts and billing, generate and deliver documents, support users, maintain audit history, troubleshoot issues, secure the Services, and improve them as permitted by the applicable agreement and privacy terms. Customers retain ownership of Customer Data and are responsible for its legality, accuracy, and the notices and permissions needed to provide it. Almic does not sell Customer Data.
When enabled for a customer's workflow, document-processing and AI features may use AWS services, including Textract or Bedrock, or the OpenAI API. Some configurations may disable AI processing. For applicable requests sent directly to the OpenAI Responses API, Almic sets store:false, which instructs that API not to retain the response for later application-state retrieval. This does not eliminate all provider logging or retention; provider practices depend on the service, contract, and account settings in use.
Almic Systems does not currently use identifiable Customer Content to train generalized cross-customer Almic models and does not currently operate a generalized training, fine-tuning, or cross-customer learning pipeline. Almic may use aggregated or deidentified information to operate, analyze, secure, develop, and improve the Services if it does not reasonably identify a customer or individual. Any future use of identifiable Customer Content for generalized cross-customer training requires separate affirmative authorization and appropriate product and privacy controls.
Almic Systems maintains reasonable safeguards including schema-based tenant isolation, tenant-prefixed object-storage keys, role-based access controls, authenticated webhook signature verification, transport encryption for applicable service connections, presigned object-storage URLs, and controls that reduce personal information in error monitoring. No system is completely secure.
Offline field data may be stored in browser or device storage. Local drafts are not currently encrypted by Almic at the application layer. Unsynchronized information may remain after logout and may be lost if local data is cleared or a device is lost before synchronization. Customers are responsible for device security and confirming synchronization. Almic does not promise remote device wiping.
Customer Content is generally retained while the applicable service is active. Project deletion currently has a 30-day recovery period before applicable primary project records and associated objects become eligible for permanent deletion. Account and support records are retained for the relationship and as needed to resolve requests or disputes; billing records for applicable accounting and legal obligations; and audit, security, and correction records for investigation, integrity, and contractual needs. Backups remain until their scheduled rotation. We delete or deidentify information when it is no longer needed for those purposes, subject to legal holds, deletion processing, failures, and provider retention.
The applicable signed agreement controls the time and supported method for retrieving available reports and files after termination. Project-deletion recovery is separate from termination access and does not guarantee complete organization export or immediate deletion from every backup or provider.
Almic shares information as needed to provide the Services: account and contact information with hosting, authentication, support, and email providers; walkthrough booking details with the scheduling provider when you request a meeting; billing identifiers and transaction status with billing providers; project documents and results with storage, configured laboratory, email-delivery, and enabled document-processing or AI providers; and technical logs with security and monitoring providers. The public page's font and script hosts receive basic website request information. A customer may direct Almic to share project information with its selected recipients. Almic may also disclose information when legally required, with notice where permitted.
Almic and its providers may process information in the United States and other jurisdictions where they operate, subject to applicable contractual and legal safeguards. Access to confidential information is limited to personnel and providers with a need to know and confidentiality duties. For details on providers used for a particular customer configuration, contact connect@almicsystems.com.
Depending on applicable law and the information involved, you may request access, a copy, correction, or deletion of personal information, or opt out of certain uses. Contact connect@almicsystems.com to make a request; we may need to verify your identity and will respond within the period required by applicable law. For project data controlled by an Almic customer, contact that organization first; Almic will assist it as required by the agreement or law.
If Texas privacy law applies to your request and Almic denies it, you may appeal by emailing the same address with the subject “Privacy Appeal.” If the appeal is denied, you may submit a complaint through the Texas Attorney General's privacy page.
We will update the date above when this Policy changes and provide additional notice when required by law. A new use of identifiable Customer Content for generalized cross-customer model training requires the separate authorization described in Section 4.
Last updated: September 28, 2026
Almic Systems LLC, a Texas limited liability company (Almic), provides the Services described below.
These public terms describe general conditions for Almic's website and workflow and reporting software. Pilot and paid Services, when purchased, are governed by a separate signed agreement. Your signed Paid Pilot Agreement, Master Subscription Agreement (MSA), Order Form, and applicable signed addenda govern purchased Services and control over these public terms if they conflict. An Order Form controls its specific scope and commercial terms; a Data Processing Addendum or AI Features Addendum controls its specialized subject where applicable. Features are included only within your agreed scope. Preview, beta, experimental, roadmap, and future-discipline features are not commitments to delivery or availability. Viewing the website does not create an order or subscription.
Access is for authorized personnel and contractors acting for the customer for its internal business purposes. Customers are responsible for their users, credentials, devices, permissions, and lawful use, and must have the rights and permissions needed for submitted data. Do not resell, sublicense, reverse engineer, bypass access controls, introduce malicious code, interfere with the Services, or violate another person's rights, except where a restriction is prohibited by law. Under the applicable agreement, Almic may proportionately suspend access for material security risks, unlawful use, or material breach, with notice where practicable.
Almic provides workflow automation, document processing, information extraction, report preparation, organizational tools, and AI-assisted features. Almic is not an environmental consultant, inspector, licensed professional, laboratory, regulatory authority, attorney, engineer, or professional report approver. Jurisdiction-specific thresholds, templates, warnings, and rules are workflow aids and may not apply to every project.
Qualified customer personnel must independently review field data, original source documents, extracted results, sample matches, values, classifications, findings, conclusions, recommendations, regulatory statements, signatures, certifications, and final reports before relying on, approving, issuing, transmitting, signing, filing, or submitting them. Customers remain responsible for professional judgment, corrections, legal and regulatory compliance, report suitability, client delivery, filings, licenses, and certifications. Almic does not guarantee professional, regulatory, legal, or agency acceptance of output.
When enabled, Almic may use third-party AI and document-processing services, including AWS Textract, AWS Bedrock, or the OpenAI API. Automated output may contain errors, omissions, incorrect sample matches, or unjustified confidence. The absence of a warning does not establish accuracy or compliance. Compare extracted information against original source documents and correct discrepancies before use.
Customers retain ownership of their data, source documents, project and inspection information, laboratory documents and results, branding, customer-provided templates, credentials, customer-specific content, and generated final reports containing customer project information. Customers grant Almic limited rights to host, copy, process, transmit, render, back up, and transform that data as reasonably necessary to provide, secure, maintain, support, and improve the Services, subject to the applicable agreement and privacy terms.
Almic and its licensors retain ownership of the software, workflow engines, generic report-generation technology, prompts, AI orchestration, reusable templates and components, algorithms, internal tools, product design, documentation, and improvements. Customer-specific configuration does not transfer that underlying technology.
Under the applicable agreement, Almic may use voluntary feedback to improve the Services without identifying customers or disclosing their confidential information. Almic may use aggregated or deidentified information to operate, analyze, secure, develop, and improve the Services where it does not reasonably identify a customer or individual. Almic does not sell Customer Data and does not currently use identifiable customer documents to train generalized cross-customer Almic models. Any future use of identifiable Customer Content for that training requires separate affirmative authorization and appropriate product and privacy controls.
Confidential information is protected with at least reasonable care and used for the purposes permitted by the applicable agreement. Disclosure is limited to personnel and providers with a need to know and confidentiality duties, or legally required disclosure with notice where permitted. Contractual exclusions and confidentiality periods remain governed by the signed agreement. Almic relies on providers for hosting, storage, authentication, email, billing, AI processing, monitoring, and related functions. Personal-data processing is described in the Privacy Policy and any applicable signed Data Processing Addendum.
Signed agreements determine fees, included users, scope, payment dates, taxes, refunds, support, implementation, and special benefits. Pilot-to-production transitions and any pilot refunds are governed by the applicable signed agreements.
The applicable signed agreement and Order Form determine the subscription period, cancellation notice, renewal, price changes, and any price protection. Public policy updates do not change signed commercial terms.
Field data may be stored locally in the browser or device for offline use. Local drafts are not currently encrypted by Almic at the application layer. Unsynchronized information may remain after logout and may be lost through local-data clearing, storage eviction, private browsing, device loss or damage, or failure to synchronize. Customers must secure devices and verify successful synchronization.
The applicable signed agreement determines any period and supported method for retrieving available reports and files after termination; access may be disabled afterward as that agreement permits. This does not promise a complete one-click organization export, remote device wiping, or immediate deletion from every system or backup. Retention and deletion remain subject to applicable policies, legal obligations, provider retention, and technical capabilities.
Express warranties and remedies in the applicable signed agreement remain in effect. Except for those express warranties, Services are provided as is and as available to the maximum extent permitted by law. Almic does not promise uninterrupted operation, perfect AI output, or regulatory compliance.
The applicable signed agreement governs exclusions and limits of liability, remedies, and indemnification obligations, subject to applicable law. These public terms do not add to or reduce the rights and obligations in that agreement.
The applicable signed agreement determines governing law, venue, and formal notice procedures. Public legal and privacy inquiries: connect@almicsystems.com. Viewing these policies or receiving or opening an email does not by itself sign or amend a customer agreement.
Almic may update these public terms and will change the date above when it does. Material changes will receive additional notice where required by law. An update to this page does not amend a signed customer agreement.