Privacy Notice

This Privacy Notice explains how Stratum Infrastructure Inc. handles personal information in connection with its websites, business-software purchases, accounts, field and office workflows, report delivery, and support. It covers purchasers, administrators, technicians, other workers, report recipients, visitors, business contacts, and people identified in customer records who never create an account. “Personal information” includes information linked or reasonably linkable to a person, including information described as personal data under applicable law.

1.1 Customer records and Stratum's own activities

For operational information handled on a business customer's lawful instructions, Stratum acts as its processor or service provider. We may be a subprocessor where that customer provides services to another organization. For our own account administration, billing, business communications, legal obligations, and protection of our systems, we determine the relevant purposes and perform the duties that apply to those activities. Our role follows the actual processing; paying for the service does not give a customer unrestricted authority over every person's information.

The Terms of Service and Customer Agreement contain the commercial agreement and integrated processing terms. This Notice explains personal-information practices; it does not transfer ownership of records, make a nonuser a purchaser, or make a worker personally responsible for the customer's subscription. Where an employer or another organization determines the processing, that organization's own notices, lawful instructions, and duties also apply. Stratum remains responsible for its own obligations.

1.2 Notice and permission are separate

Reading or acknowledging this Notice, receiving an invitation, continuing employment, or accepting ordinary account terms is not blanket consent to location tracking, unrelated secondary uses, advertising, or model training. We provide the information and separate affirmative choices required for the actual purpose before processing begins. Specific notices at invitations, uploads, location features, and any later optional feature supplement this Notice. An employer's agreement and a browser's device permission do not replace an individual's required notice or consent.

This Notice describes the standard scope identified below. A feature outside that scope is not authorized merely because a file can be uploaded or a clause describes how future features would be reviewed. Earlier information remains subject to the restrictions and permissions applicable to it, as explained in Section 14.

This Notice applies to the website, communications and personal-information processing Stratum actually undertakes. A service capability described here is not a representation that it is currently available. Before Stratum enables a capability or begins the related processing, it must implement the notices, permissions, controls and retention limits stated here; those requirements apply from the first collection and throughout that processing. Publication alone does not activate a capability, establish a customer's acceptance, or change the restrictions applicable to previously collected information.

Customers must have authority for the information they provide, give required notices, and exclude unrelated sensitive information. Uploads and free text can contain information we did not request; the absence of a dedicated health, biometric or payment field does not establish that such information is absent. The standard service does not authorize prohibited or out-of-scope processing.

Required information depends on the requested function. Access credentials support an account; business and billing information support a purchase; an optional image or eligible work-session location supports its separately disclosed task. A facility's business address is distinct from device tracking, but a home address or a site linked to a particular person may still be personal information. We do not purchase consumer profiles or enrich worker records from data brokers under the standard scope.

We use the information reasonably necessary to supply the purchased service; manage access; process and validate authorized records; support field-to-office review and report delivery; diagnose defects and measure reliability or capacity; protect the service and prevent abuse; answer support and payment requests; meet legal obligations; and retain limited evidence of contracts, instructions, permissions and disputes. We limit collection, use and retention to the specified purpose and any compatible or separately authorized purpose permitted by applicable law.

Customer operational processing follows the integrated processing agreement. Our independent business activities include managing our contractual relationship, payments and taxes, communicating with authorized representatives, securing our systems, and establishing or defending legal claims. A payment dispute does not justify retaining every customer file, and a service-processing instruction does not authorize an unrelated person profile.

General nonconfidential feedback, software knowledge and properly qualified nonpersonal statistics can support product development under Section 7. Identifiable content, worker traces, confidential customer pricing and facility facts are not silently converted into a pooled development dataset. Where we determine an independent development purpose, we assess and fulfill the corresponding controller duties; the label “processor” does not change the nature of that activity.

We evaluate materially different purposes before use, including required notices, necessity, source authority, assessments, choices and restrictions. Permission for one lawful purpose is not permission for every later purpose. A prohibition imposed by law or a source agreement cannot be cured by a general consent box.

4.1 Eligible role, work session and advance notice

The location-enabled service collects device coordinates only for an authorized technician or field-service worker while clocked in and performing a disclosed work activity for which location is necessary. An owner, administrator, reviewer, trainee or office role alone does not authorize tracking. A person with multiple roles is eligible only while acting in the authorized field role within the permitted work session. The same rule applies to every collection path, including clock events and training or mentor sign-offs.

Before collection, the worker receives a short notice identifying the customer/employer, the purpose, event or route collection, intended viewers, retention, and the pause/stop and correction controls. Browser or operating-system permission is requested separately. The customer must provide any additional employment-monitoring notice, posting, acknowledgment or lawful authority required for its workforce and workplace. Stratum supplies the stated controls and does not treat the customer's acceptance as a waiver of worker rights.

4.2 Start, pause, stop and stale sessions

The disclosed feature may collect clock-in and clock-out event coordinates and work-session route points within the eligible interval. Sampling varies with device, permission and connectivity; an upload interval does not guarantee a fixed sampling interval. The worker can see when tracking is active and can pause or stop it. New capture stops on clock-out, a break or personal pause, permission withdrawal, loss of eligible role, logout, or expiration of the disclosed stale-session limit. The product requires a fresh eligible work action before tracking resumes after that limit; a background tab, an old browser permission or an abandoned clock entry is not continuing authorization.

The customer's shift-specific stale-session limit is shown before tracking and cannot exceed 16 hours from the latest express clock-in or work-session reauthorization. A reauthorization requires the worker's affirmative action while still working; movement or background traffic alone does not extend the limit. The customer must choose a shorter limit where its work pattern or law requires it. Ending location collection does not itself stop payable time or erase evidence of work.

4.3 Access and limited outputs

Coordinates, accuracy and capture time support necessary work verification, exception review and mileage calculation. Ordinary customer and report-recipient views use the minimum necessary derived totals, permitted work events or site information. An administrator, dispatch or other role does not receive unrestricted raw-route access by default. A customer may explicitly designate a person to access particular retained points or a scoped route interval only where necessary for a disclosed work, mileage, dispatch or correction/review purpose and lawful under its instructions. That assignment, purpose, permitted scope and access are recorded; access ends when the need ends. Designated Stratum personnel may access the minimum necessary points for documented support, security or legal tasks. These exceptions do not authorize general browsing, ordinary report-recipient access, unrestricted route exports or cross-customer access. Disclosure to the worker in response to a lawful request is handled securely.

We do not use worker location for advertising, pooled model training, insurer scoring or cross-customer benchmarking. Raw-route retention and capture-age limits apply to duplicate coordinates in clock, sign-off, audit and diagnostic stores as well as the route table. Necessary nonroute work evidence may be retained separately under Section 8; it must not reconstruct an expired route.

4.4 Corrections and meaningful human review

Location and device records may be absent or inaccurate. Workers can submit a correction and alternative evidence to their customer's authorized reviewer or use the contact in Section 14. The reviewer must consider relevant underlying records, understand the calculation or exception, and have authority to correct or override the outcome. A rubber-stamp approval is not meaningful review.

The service may calculate time or mileage and flag discrepancies. Missing GPS does not automatically cancel payable hours, deny legally owed reimbursement, or make an adverse employment decision final. The customer remains responsible for lawful time, pay, reimbursement, qualification and employment decisions and for responding to a worker's dispute. We supply review and correction records and assist with our processing obligations. Introducing a materially different automated decision process requires the notices, assessments, explanations, opt-outs or other safeguards required for that actual use; an ordinary calculator is not automatically regulated automated decision-making.

4.5 Offline capture and late delivery

A point's capture time and server receipt time can differ. Before accepting a delayed point, the service validates its customer/user association, eligible original interval and permitted purpose, as well as a later withdrawal or restriction relevant to its use. Local GPS points expire no later than 24 hours after capture and are removed sooner when no longer needed or permitted. A late upload cannot authorize off-duty capture or restart the raw-data retention clock. Clock corrections preserve review history; they cannot transform unauthorized capture into authorized on-duty collection.

4.6 Photographs, signatures and evidence

Photographs may show people, premises and sensitive site facts and may contain EXIF/GPS metadata. Justified original evidence is preserved under restricted access with its permitted record purpose. Ordinary external report or portal delivery uses a separately identified copy with unnecessary embedded location and other metadata removed. Sharing original metadata requires a specific lawful evidentiary need and authorized recipient; it is not the default for every report recipient. Creating a safe delivery copy does not silently alter the source evidence.

Signatures are retained as flattened images and associated identity/time evidence, not biometric signature templates. Face recognition, biometric identification and audio recording are outside the standard scope. A customer's authorization to store an image does not authorize extracting a biometric identifier. No worker must grant pooled-training rights to clock in, receive the purchased service, or exercise a privacy right.

The standard website and product use functional first-party storage and ordinary hosting/security requests. They do not deploy advertising pixels, cross-site behavioral advertising or session-replay tracking under this scope. Visits, sign-in and communications still disclose request and contact information to the services identified in Section 6.

Infrastructure providers such as Cloudflare may receive IP addresses and request information when you use our service and other websites or services they support. Their network-security activities may involve analyzing traffic over time and across those properties to identify threats and prevent abuse. This is separate from advertising tracking and does not authorize unrelated reuse of customer work records.

Authentication cookies and tokens support sign-in and authorization. Service-worker caches and browser storage support necessary offline files and changes. Local records are associated with the proper organization and user and are inaccessible to another signed-in identity. Logout and reassignment end that identity's ordinary access; pending work is either safely synchronized or kept in an encrypted, identity-bound recovery area, not exposed to the next user.

GPS queues follow the 24-hour limit in Section 4. Other unsynchronized work is placed into restricted recovery after seven days of inactivity, with user/customer warning and a recovery or synchronization route. That event is not automatic erasure of the only copy of accepted work. Recovery records receive a documented owner, purpose and next review within 30 days; any further retention requires a specific continuing recovery need and another dated review. Before lawful disposal, we provide a reasonable retrieval warning where practicable. Account-exit, valid deletion and hold rules still apply. We do not keep a local recovery copy indefinitely merely because synchronization failed.

You can restrict permissions or clear local site data in your browser. Clearing data may destroy work that has not synchronized; check the synchronization status or contact your administrator first. Browser clearing does not erase server records, cancel billing or recall downloaded reports. An offline device may not receive a server revocation immediately, so local identity restrictions, lockout and expiry operate without waiting for a network request.

Stripe/Link checkout and destinations you open have their own storage and privacy practices. Before adding a nonessential tool, we review its actual collection and recipients and provide required notices and choices. Standard “Do Not Track” browser signals do not change necessary account processing; legally recognized opt-out preference signals, including Global Privacy Control where applicable, are addressed in Section 10. These signals are not instructions to delete every operational record.

We disclose information only to recipients with a permitted purpose and scope. These include the customer's authorized users and selected recipients, service providers and contractors subject to appropriate obligations, professional advisers, and authorities where required or otherwise legally justified. A site address, shared facility identifier or an invitation does not authorize access to another contractor's private records.

Roles differ by operation: hosting on customer instructions is different from a payment participant's independent fraud or tax duties. We maintain the actual service, contracting-entity and onward-recipient information for our processing and provide the information required by the Agreement or an applicable rights request. A provider's public list alone does not establish that each listed optional service receives Stratum information. We do not authorize a provider to use protected customer content for its own generalized model training through an ordinary service-processing instruction.

The customer is responsible for selecting lawful report recipients. A scoped portal link can act as a bearer credential and must be protected from forwarding. Revocation restricts future supported access; it cannot recall a file already downloaded or an attachment already delivered. Recipient access does not confer account ownership or management authority.

Necessary due diligence in a merger, financing, acquisition or similar corporate transaction is limited and protected. A successor remains subject to applicable obligations, source restrictions and promises attached to the information. A corporate transaction does not authorize unrelated reuse. Any independent data-licensing program must satisfy Section 7 before it begins.

Primary U.S. hosting does not mean that every network, email, support or onward-provider operation stays in one region or country. We assess actual locations, transfers and access and apply the required restrictions. A U.S. data-center address alone does not resolve foreign access or transfer restrictions.

7.1 Standard service and limited development

The standard service uses deterministic document parsing, calculations and human review; it does not include a direct external-model extraction service, pooled customer-content training pipeline or generalized personal-data contribution program. Employee learning and qualification modules are not machine learning. Staff handling of support or development material is subject to the same source and purpose limits even when a separate manual tool is used.

Within the Agreement and applicable law, we use limited operational information to troubleshoot defects, validate outputs, protect the service and measure reliability and capacity. General software improvements may benefit other customers without disclosing the underlying customer's records. Under the standard service scope, we do not collect, use or sell personal information for training large language models.

7.2 Qualified Statistics and technical knowledge

The Agreement permits use of lawful Qualified Statistics and nonconfidential technical knowledge for development, evaluation, general technical models and nonidentifying benchmarks. Before independent reuse, the material must meet the Agreement's qualification standard: it must not identify or reasonably permit identification of a person, customer, site or asset; disclose confidential information; reproduce restricted source content; or allow reconstruction of protected records. It must also have a lawful source and permitted purpose. Pseudonyms, hashes, aggregation, model weights and the word “anonymous” do not establish qualification.

We take reasonable measures to maintain deidentified status, commit to use qualifying deidentified information without attempting to reidentify it, and impose corresponding restrictions on recipients where it is disclosed. The only exception is testing expressly permitted by applicable law solely to determine whether the deidentification process satisfies the applicable requirements; it does not permit operational use, person profiling or reuse of an identified result for another purpose. We review qualification and restrictions when the use or available information changes. If the standard ceases to be met, the material is handled as protected information and the independent reuse stops until lawfully resolved. Existing source rights and earlier permissions remain controlling; qualification does not erase contractual restrictions.

7.3 Separate optional contributions and connectors

A future optional contribution may authorize evaluation, customer-specific adaptation or shared-model training only on specifically eligible material. Before it begins, the authorized grantor receives the source scope, purpose, recipients, exclusions, retention, withdrawal and deletion treatment, and any required separate choices. An invited worker cannot approve company-wide training, and a customer cannot grant rights held by another person or a source licensor. Declining an optional contribution does not reduce an already-purchased subscription’s capacity or increase its agreed price. Beta feedback does not require contributing confidential records.

Raw worker location, signatures, compensation, credentials, identifiable confidential reports and restricted connector material are not pooled training inputs under the standard program. A provider's processing to produce an output and its reuse for its own training are separate purposes. Restrictions follow copies, extracted text, annotations, normalized records and other derivatives.

Google Drive, Sheets, QuickBooks or other customer-account connectors require their own enabled scope, authorized account, provider compliance and just-in-time disclosures before use. Google API and Workspace Limited Use restrictions continue to apply to covered information and derivatives; a Stratum checkbox cannot waive them or authorize prohibited shared-model training. Disconnection, revocation, deletion and retained copies must follow the applicable source rules. Optional external extraction, generalized training, connectors and personal-data licensing remain unavailable unless separately introduced with these safeguards.

7.4 Surviving artifacts and new uses

Independently developed software and lawfully qualified nonpersonal artifacts may remain after cancellation while their rights and qualification remain valid. Cancellation does not create new rights in retained personal or confidential data. A withdrawal or lawful deletion is evaluated across retained sources and derivatives. Deleting a source dataset does not itself prove removal of its influence from a model; an optional program must explain and lawfully support its actual withdrawal treatment before material enters it.

Customer-directed operational sharing is distinct from training or commercial distribution. A photograph, original report, route, licensed form or restricted contact list does not become general technical knowledge when included in feedback. New identifiable-data products, insurer or employment scoring, cross-customer access, new recipient purposes and materially different uses require separate assessment and any required authority, notice or consent. A prohibited sale or use remains prohibited even if a person offers consent.

8.1 Purpose-based schedule

We retain information for its identified purpose and the periods or criteria below. A maximum is an outside limit, not a reason to keep unnecessary information until that limit. We delete or minimize it earlier when its purpose ends, or deidentify it only where applicable law and lawful Customer instructions permit, subject to a specific lawful retention requirement or hold. Hypothetical future development, a subscription renewal or possible future dispute is not a blanket basis for indefinite retention.

8.2 Account exit, return and recovery copies

Unless a shorter legal deadline or valid earlier instruction applies, the normal account-exit process provides 30 calendar days after the paid service ends to request basic return. A timely request protects the necessary requested information through delivery and at least seven calendar days for retrieval, subject to the shorter category-specific limits explained below. Eligible primary copies are deleted within 30 calendar days after the applicable return/retrieval period ends. A delayed Stratum return does not cause the timely requested information to expire before delivery and the retrieval period. We provide the customer return required by the Agreement; an index without the promised record content is not a complete return.

Shorter category-specific limits, including the raw-coordinate capture-age ceiling, also govern return and retrieval copies. We identify an approaching deadline and promptly coordinate secure staged delivery and an appropriate shorter retrieval route while the requested information remains eligible. We do not deliberately delay a return or delete information to frustrate a valid request. An export request alone does not extend a category limit or create a legal hold. Retention beyond that limit requires an independently applicable legal preservation duty or a documented, scoped lawful hold relevant to the specific request; it is limited to the necessary records, restricted to that purpose and ended when its basis ends under Section 8.3. A request cannot restore information already lawfully deleted.

Restricted product recovery copies expire no later than 90 calendar days after primary deletion. They are isolated from ordinary use, analytics and development. On restoration, completed deletion and access restrictions are reapplied before ordinary access. A shorter category-specific limit, including the capture-age limit for raw coordinates, also applies to recovery copies. A mandatory earlier deletion deadline controls; backup status does not create an automatic legal or contractual exemption.

Business-mail support correspondence is a separate data flow. Where the applicable Google Workspace account contract permits residual provider deletion processing of up to 180 days after a deletion instruction, that bounded residual cycle applies only to those restricted provider copies of correspondence already deleted from our active mailbox, and only where applicable law permits it. We send the instruction promptly after the correspondence's retention purpose ends and do not use the residual copy. It is not a longer lifecycle for product records, raw routes or ordinary backups. If a shorter duty applies, we use a compliant process or restrict the affected intake. An account-termination recovery option does not authorize us to delay a required deletion instruction.

8.3 Exceptions, corrections and actual deletion

A legal requirement, an existing claim or a valid hold may require particular information to remain. We record the matter, categories, responsible owner and review date, restrict retained information to that reason, review the basis at least every 90 days, and dispose of it when that basis ends under the applicable schedule. A hold is not a permanent label on an entire tenant and cannot revive already deleted data. We do not substitute a reusable development dataset for information that must be deleted.

Deactivation, cancellation, an audit label, hashing or a queued job is not completed erasure. Disposition considers originals, structured fields, extracts, indexes, local stores, logs, provider copies and backups. A correction may require an accurate, minimized history rather than silently overwriting evidence. When required records must be retained after a worker leaves, the retained record and access remain limited to that duty. We explain an applicable deletion exception without disclosing another person's protected information or privileged material.

9.1 How to make a request

Email dallas@stratuminfra.ai or write to the business correspondence address in Section 14. Identify the relevant organization or relationship, information or period, and what you would like us to do. “Privacy request” is helpful but not required. You do not need a subscription, payment, a new account, acceptance of new terms or consent to unrelated data use. An accessible alternative is available through the same contact if you cannot use the ordinary method. Do not send passwords, full card/government identifiers or unnecessary sensitive documents by ordinary email.

You may ask about our processing, request access or a portable copy, seek correction or deletion, withdraw a consent, or request a processing restriction or opt-out. Section 10 explains state rights, including rights concerning recipients and certain automated decisions. We evaluate requests under the applicable law, our actual role and our commitments; we also review concerns from people who are outside a particular state's statutory consumer definition.

9.2 Verification, agents and customer records

We verify identity and an agent's authority proportionately to the risk and as the law permits, preferably using information already held. An authorized agent, legal guardian or other lawful representative may act to the extent permitted. We do not require access-request identity proof for an opt-out where the law does not permit that requirement. We explain what additional verification is necessary and why. Verification information is used only for that purpose and related required accountability.

For customer-controlled information, we identify or contact the responsible organization where appropriate and assist its response under law and the Agreement. We handle our own independent obligations directly and do not send you in an indefinite loop. We protect another person's information, account security and legally protected material when giving access. A company invoice dispute does not delay a privacy response. A request that also clearly cancels a subscription is routed to both processes.

9.3 Response, appeal and complaint

We acknowledge receipt within 10 business days and ordinarily complete an applicable access, correction or deletion response within 45 calendar days from receipt. Where the governing law allows an extension and it is reasonably necessary, we explain the reason and permitted additional period before the original deadline expires. A shorter legal deadline controls, including applicable opt-out or consent-withdrawal deadlines. Internal routing or verification does not restart the receipt date. New device capture stops under Section 4 when permission is withdrawn; the general response window does not authorize continued capture.

A denial identifies its basis and how to seek review. You may appeal by replying or contacting Section 14 and explaining the concern; no special subject line is required. We review the appeal and respond in writing within 45 calendar days, or sooner if required, with reasons and information about complaining to the relevant state attorney general or privacy regulator. You may contact a regulator without completing an optional review or surrendering a legal remedy. California residents may contact the California Privacy Protection Agency; other residents may use their state's attorney general or responsible regulator.

We do not retaliate or unlawfully discriminate for exercising rights. Requests are free where required; any permitted fee or refusal for a manifestly unfounded or excessive request is explained and supported, not inferred from subscription status. We do not offer a financial-incentive program in exchange for personal information under the standard service.

10.1 Coverage and common rights

Rights depend on the relevant law's effective date, covered entity and activity, data, purpose, residence and exclusions. A customer's billing state is not the only relevant location. A business account does not eliminate all worker or nonuser rights. Many comprehensive state laws exclude information used solely in a commercial or employment context; California does not apply that general exemption. Other monitoring, security, breach, confidentiality and employment duties may apply even when a comprehensive consumer law does not.

Where applicable, Oregon and Minnesota residents may request the specific third-party recipient information provided by their laws; Delaware provides its applicable third-party-category disclosure.

Where Connecticut law applies, you may access inferences about you and learn whether covered profiling is used for decisions with legal or similarly significant effects. If feasible, you may question a covered profiling result, receive its reason, and review the underlying data; housing decisions carry the further correction and reevaluation right provided by law. You may request the statutory list of third parties to which your personal data was sold, or the permitted alternative list if applicable, subject to lawful exceptions.

Minnesota's covered profiling rights include questioning a result, obtaining the required explanation, reviewing and correcting the underlying information, and reevaluation where required. We provide any additional recipient or decision information required by another applicable law. No category-only summary replaces a legally required specific-recipient response.

10.2 California information categories

Depending on your relationship with us and the enabled features, the information described in Section 2 can fall within these California categories: identifiers and customer-record information; commercial information; internet or electronic-network activity; geolocation; visual information such as photographs and signature images; professional or employment information; and inferences such as mileage or work-status exceptions. Sensitive information can include precise geolocation and account credentials that permit access. Unexpected uploads can contain other categories outside our intended intake. Sections 2, 3, 6 and 8 identify the corresponding sources, purposes, recipient relationships and retention criteria, including business contacts and nonusers.

We use sensitive information only for the permitted, necessary purposes described here and do not use it to infer unrelated personal characteristics. A use requiring an additional sensitive-information limitation or choice is not enabled through ordinary account acceptance.

10.3 Sale, advertising and privacy signals

We do not sell personal information or share it for cross-context behavioral advertising, and we do not conduct targeted advertising using cross-service personal profiles under the standard scope. We do not knowingly sell or share the personal information of people under 16. Customer-authorized delivery and ordinary provider processing are evaluated by their actual purpose and legal role; they are not automatically advertising “sharing,” nor automatically exempt simply because called a service.

We recognize legally required opt-out preference signals, including Global Privacy Control, for the applicable browser/device and any known linked profile where required, and maintain the standard no-sale/no-targeted-advertising restriction. A valid opt-out is not blocked by a general terms checkbox, a login demand where prohibited, or a conflicting default preference. We explain any additional choice legally needed before changing a preference. Standard Do Not Track is different from a legally recognized opt-out signal and does not alter necessary operational processing.

We do not sell precise worker location. Covered Oregon consumer precise-geolocation sales are prohibited, and Connecticut's corresponding prohibition takes effect October 1, 2026. Covered Maryland sensitive-data processing must meet its strict-necessity requirement and sensitive-data sales are prohibited; consent does not cure prohibited processing. Other states impose their own sensitive-data conditions. These distinctions do not imply that every worker automatically meets the relevant consumer definition.

Any future personal-data sale, targeted advertising, regulated health-data use, biometric identification or qualifying automated-decision feature requires a separate legal and source review, necessary notice and choices, recipient records and working rights/signal controls before activation. A notice update alone does not enable it. Enacted future requirements, including Oklahoma's January 1, 2027 consumer law and Vermont's January 1, 2028 law, will be applied when effective to covered activity; their inclusion here does not represent that those future statutes are already operative.

We maintain administrative, technical and physical safeguards appropriate to the information and processing risks and the integrated Agreement. These include controlled and purpose-limited access, authentication and authorization, protection of transmission and stored records, tenant separation, secure staff handling, recovery and incident procedures. We assess and address material risks rather than relying only on a vendor certification.

The service uses password hashing and authenticated application/database access. Privileged access is restricted and protected with appropriate strong authentication. We do not promise a universal user-MFA feature, administrator-proof history, a particular recovery-time guarantee, continuously staffed monitoring or a Stratum SOC 2 certification unless expressly supplied for the service. No online service is risk-free. Customers must protect their own credentials and devices, but that does not transfer Stratum's own duties to them.

Report a suspected incident to Section 14 without sending passwords or unnecessary sensitive files. We investigate, contain and remediate relevant incidents and give the customer and affected persons notices required by law and the Agreement, with updates as facts become known. Any shorter or immediate statutory duty controls over an ordinary contractual timeline; investigation is not permission to ignore a running notice deadline. Security records are retained for the justified incident/security purpose and schedule, not as a general development dataset.

The standard offer is for authorized U.S. business operations and adult professional users. It is not directed to children, and customers must not intentionally use the standard service to collect children's information. Participation by a minor apprentice or any child-related workflow requires a separate scope review before use; a work role does not remove applicable child protections. If prohibited information is discovered, we restrict access and handle it lawfully, including necessary deletion or other disposition. The uploader's acceptance does not authorize every category contained in a file.

Information about a child can also appear incidentally in a photograph, contact record or other nonuser content. Adult-only account eligibility does not eliminate our duties concerning that information. A parent or lawful guardian may contact Section 14 about a child's information without creating an account. If we learn that we collected information online from a child under 13 in circumstances subject to the Children's Online Privacy Protection Act, we stop the unapproved activity and follow the applicable parental-notice, consent, access and deletion requirements. Incidental information supplied by an adult is not automatically the same as collecting information online from a child; we evaluate the actual source and use and any other applicable protections.

International operations, foreign-law protected information, restricted government or export-controlled information, regulated health information, consumer health inferences, genetic information and biometric identification are outside the standard intake unless separately approved with the necessary protections and instruments. A standard clause cannot replace a required business-associate agreement, specialized health notice, biometric release, assessment or transfer restriction. Unexpected sensitive information is evaluated by actual content and use, not simply the field name.

A technician visiting a hospital is not automatically seeking healthcare. We do not use location to infer a worker's or another person's health, treatment, reproductive status or other sensitive characteristics. Any future health-related inference or health-facility geofencing requires separate review under applicable state and federal rules. Ordinary images and flattened signatures are not automatically biometric identification; extracting identifiers or recognition templates is a different, separately restricted purpose.

Where data or provider access involves another country, we assess applicable transfer restrictions, source agreements and U.S. restrictions on certain sensitive-data transactions. Describing information as deidentified or storing a primary copy in the United States does not automatically remove those restrictions.

Essential account, security, invitation, password, billing and requested operational communications are distinct from marketing. Opting out of marketing does not necessarily stop notices needed to operate or secure an account, but essential messages are not used as a cover for an advertising campaign. You can use a message's unsubscribe method or contact Section 14 to stop applicable marketing.

We handle requested sales follow-up according to the actual channel and authorization and honor applicable opt-outs and suppression requests. Accepting Terms, sharing a business card, requesting a receipt by text or allowing browser notifications does not authorize every automated marketing channel. Automated marketing calls, texts and push-notification programs are not enabled by this Notice; any such program requires the particular permissions and controls that apply.

Founder or staff communications outside the application remain subject to the same purpose, security and retention limits. An absence of an application communication integration does not mean the company never sends email, makes a call or keeps business contact information in an approved tool.

14.1 Versions, earlier information and new purposes

This Notice identifies its last-updated date and, when effective, its effective date in the document information below. We retain earlier editions. We provide notice of material changes appropriate to their significance and applicable law, including direct notice where required. Before a materially different purpose, more intrusive location use, new recipient purpose or material retention change begins, we provide the required information and obtain any necessary new agreement or specific consent.

Previously collected information remains subject to the permissions, promises, source restrictions and legal duties that apply to that collection. We do not rely on this edition alone to expand earlier service-only or no-training commitments. Where earlier terms require a separate signed election, that requirement continues unless validly changed; ordinary account acknowledgment is not a replacement. Customer or worker acceptance cannot waive another person's rights, a provider restriction or a statutory prohibition. If a valid change is not established, the earlier restriction remains.

Routine login, continued employment, a browser permission already granted, a payment or silence does not select an unrelated new purpose. Declining an optional use does not remove rights-request or cancellation access or change an already-purchased subscription’s limits. We may keep the same public document routes as the product evolves, but a new feature can require a separate collection notice, supplemental document or choice and its own recorded version.

14.2 Contact and accessible requests

Stratum Infrastructure Inc.
Privacy, cancellation, billing and legal: dallas@stratuminfra.ai.
Business correspondence address: 15482 S Revolutionary Way, Bluffdale, UT 84065.

Include enough information to identify the organization or relationship, the relevant records or time period and the request. No new account or payment is required. We can arrange an accessible method and proportionate verification through an appropriate channel. Do not send passwords, full card details or unnecessary identity documents. A customer's separate employer-monitoring or records contact may also be relevant; contacting that organization does not eliminate Stratum's own duties.