Antelope Data Campus, LLC

Terms of Service

Effective date 1 January 2026 · Last updated 26 October 2026

Contents

  1. Agreement to These Terms
  2. Definitions
  3. Eligibility and Authority
  4. Campus Services
  5. Scopes of Work and Scheduling
  6. Fees, Invoices and Taxes
  7. Client Obligations
  8. Edge Hardware and Node Housing Rules
  9. Certification Records
  10. Acceptable Use
  11. Intellectual Property
  12. Confidentiality
  13. Data Protection and Privacy
  14. Campus Tours and Visitors
  15. Warranties and Disclaimers
  16. Limitation of Liability
  17. Indemnity
  18. Suspension and Termination
  19. Force Majeure
  20. Governing Law and Disputes
  21. Changes to These Terms
  22. General Provisions
  23. Contact Information

1. Agreement to These Terms

These Terms of Service govern the use of the website of Antelope Data Campus, LLC and the delivery of campus services by Antelope Data Campus, LLC to a client. By browsing the website, submitting a contact form, signing a scope of work or using a campus service, a person or organisation agrees to these terms. A person who does not agree should stop using the website and should not sign a scope.

These terms work alongside a signed scope of work and a service agreement for a specific engagement. Where a signed agreement conflicts with these terms, the signed agreement controls for that engagement, because a negotiated document written for a particular project is more specific than a general page. Where the signed agreement is silent, these terms fill the gap.

Nothing on this website is an offer capable of acceptance in itself. A page that describes a service, a price range or an availability window is an invitation to begin a conversation. A binding engagement begins only when the campus and the client have both signed a scope that describes the work, the fees and the run window.

2. Definitions

The terms below carry the meanings given here throughout these terms. A definition should be read in the way that makes the surrounding sentence work rather than in a way that creates an unreasonable result.

The Campus means the prairie data camp operated by Antelope Data Campus, LLC, including the node rooms, the calibration bench, the certification desk and the office at 201 S Main St Ste 2025, Salt Lake City - 84111-2268, United States (US). The Company means Antelope Data Campus, LLC. The Client means the organisation or individual that has signed a scope of work with the Company.

Services means the campus offerings described on the services page, namely telemetry audit sprints, dataset certification runs, edge node housing, sensor calibration days, data lineage reviews and campus tour sessions, together with any related work described in a scope. Client Data means the telemetry, dataset slices, sensor readings, node logs, lineage materials and other information that a client provides to the campus for the purpose of an engagement. A Certification Record means a signed certificate and its associated panel results issued after a certification run.

A Run Window means a scheduled period reserved on the campus calendar for a specific service. Deliverables means the written documents the Company agrees to provide, such as a findings brief, a lineage map, a score sheet or a tour walkthrough. Business Hours means the hours published on the contact page, currently Monday to Friday from 08:00 to 18:00 Mountain Time with a shorter Friday schedule.

3. Eligibility and Authority

The website is intended for organisations and for individuals acting in a professional capacity. A person who uses the website represents that the person is at least eighteen years of age and has the legal capacity to enter into a contract. The campus does not knowingly allow a minor to enter into a scope of work.

A person who signs a scope on behalf of an organisation represents that the person has authority to bind that organisation. If authority is later disputed, the organisation remains responsible for the obligations that were accepted in its name, and the person who signed may be asked to confirm the position in writing.

The Company may decline a request for any lawful reason. Examples include a request that would require the campus to break a law, a request that conflicts with an existing reservation, a request that concerns a stream the campus cannot access safely and a request from a party that has an unresolved payment dispute with the Company. A decline will be explained in writing where it is appropriate to do so.

4. Campus Services

The Company provides six campus services, each described on the services page and each offered under a separate scope. The description on the website is an outline rather than a complete specification, and the signed scope is the document that defines what will be done.

A telemetry audit sprint examines one stream and produces a dated findings brief that separates blocking items from attention items. A dataset certification run tests a frozen slice across integrity, completeness, reconciliation and plausibility panels and either issues a signed certificate or returns the slice for correction. Edge node housing provides rack space, power, cooling and monitoring for client hardware on the campus.

Sensor calibration days drive probes through reference conditions and produce a score sheet for each probe. Data lineage reviews rebuild the map of a dataset from source to table and flag unexplained gaps. Campus tour sessions bring a client team onto the floor for a half day and end with a written walkthrough.

The Company may adjust the detail of a service to suit a client situation, provided the adjustment is recorded in the scope or agreed in writing before the work begins. The Company may also subcontract a discrete task such as equipment maintenance, but it remains responsible to the client for the delivery of the service.

5. Scopes of Work and Scheduling

Every engagement begins with a scope of work. A scope identifies the service, the stream or hardware concerned, the deliverables, the fees, the assumed start date and the person who will sign any certification record. A scope takes effect when both parties have signed it, and a signature may be electronic where the parties agree to that method.

Run windows are reserved on a cohort calendar and are limited by the physical capacity of the bench and the node rooms. A reserved window is held for the client named in the scope and is not offered to another client while the reservation is active. A window that is released by agreement returns to the calendar.

A client may request a change to a reserved window. A change request should be made as early as possible, and the Company will confirm whether the change is possible without disturbing another reservation. A change that is requested close to the start date may be treated as a cancellation under the termination section of these terms, particularly where the campus has already reserved crew time.

Estimates of duration are made in good faith and are based on the information available at the time of the scope. A stream that reveals unexpected complexity may require more time, and the Company will discuss the effect on the schedule before extending a window. The Company will not extend a window and charge for the extension without the written agreement of the client.

6. Fees, Invoices and Taxes

Fees are set out in the signed scope. Unless the scope states otherwise, fees are quoted in United States dollars and are exclusive of any sales, use, value added or similar tax that applies. The client is responsible for any such tax, except a tax on the income of the Company.

The Company issues invoices according to the schedule in the scope. A typical engagement is invoiced partly at signature and partly on delivery, and a recurring housing arrangement is invoiced on a regular cycle. Payment is due within the period stated on the invoice, and the period is never shorter than fifteen days from the invoice date.

A client who disputes an invoice should notify the Company in writing within ten days of receiving it and should describe the item in dispute. The undisputed portion remains payable on the original due date. The parties will work to resolve the dispute promptly, and the Company will issue a corrected invoice where an error is confirmed.

Late payment may attract interest at a modest rate described in the scope, and the Company may pause a scheduled run where an undisputed invoice remains unpaid after a written reminder. The Company will not withhold a deliverable that has already been paid for as a way of pressuring payment of a separate disputed invoice, except where the law allows a lien or a similar remedy.

7. Client Obligations

A client is responsible for providing accurate information about the stream, the hardware and the decision the data must support. An audit sprint built on an incomplete hardware profile is likely to miss a hop, and a certification run built on an incorrect sample rate is likely to return a false completeness result. The client should correct an earlier description as soon as an error is discovered.

A client must have the right to provide Client Data to the Company. Where Client Data includes personal data, the client must have a lawful basis for the transfer and must have complied with any notice or consent requirement that applies. The client should not send credentials, secret keys or regulated categories of data unless the scope expressly provides for them and a secure channel has been agreed.

A client must nominate a contact who can respond to technical questions during a run window and a signer who can approve a scope or a certification record. A delay caused by an unavailable contact may extend a run window, and the Company will record the delay in the run history rather than absorb it silently.

A client must pay the agreed fees, respect the acceptable use rules in these terms and cooperate with a reasonable security request from the Company. The client should also tell the Company about any known defect in its own pipeline that could affect the work, because a known defect that is disclosed early is easier to handle than one that surfaces late.

8. Edge Hardware and Node Housing Rules

Hardware accepted for node housing must be safe, clearly labelled and accompanied by a hardware profile that describes its power draw, cooling requirement and network configuration. The Company may refuse a unit that is damaged, leaking, unusually noisy, electrically unsafe or incompatible with the available rack space.

The client retains ownership of its hardware at all times. The Company does not acquire a lien on a unit merely by housing it, except where a lien or a similar remedy is created by law or is expressly agreed in the scope. The Company may hold a unit after an unpaid invoice only where the law permits and after written notice to the client.

The Company will handle client hardware with reasonable care. A unit that fails during its residence will be reported to the client with the monitoring history, and the client may request a physical inspection, a restart or a return. The Company is not responsible for a failure that is caused by a defect in the unit, by a firmware decision made by the client or by a component reaching the end of its service life, though it will help the client diagnose the failure.

A client who wishes to remove a unit should provide reasonable notice so that the removal can be scheduled and the node history can be printed. A unit left on the campus after the end of an engagement may be stored for a limited period and then handled under the unclaimed equipment procedure described in the scope.

9. Certification Records

A certification record is a statement about a specific frozen slice of data at a specific time. It is not a statement that the client pipeline will remain correct in the future, and it is not a guarantee of any business outcome. A reader should treat the record as evidence about the slice it describes and no more.

The Company signs a record only when the panel results support the signature and any exception has been annotated with a reason. The Company will refuse to issue a record where a blocking defect remains unresolved, and it will explain the basis for the refusal in writing. A refusal is not a finding of fault against the client; it is a statement that the evidence does not yet support the record.

A record is issued to the client named in the scope and is entered in the register maintained by the Company. The client may share a record with an auditor, a regulator, an investor or a partner. A recipient may verify a record with the Company, and the Company will confirm the record and describe the slice it covers.

A record may be reissued after a pipeline change. A reissue replaces the earlier record for future use but does not erase the earlier record from the register. The register keeps the full history so that a reader can see when a change was made and what the position was before and after the change.

10. Acceptable Use

A person may use the website and the campus services for lawful professional purposes. A person must not use the website to attempt unauthorised access to a system, to interfere with the availability of the website or to transmit a malicious file. Automated scraping that places an unreasonable load on the website is not permitted.

A client must not use a campus service to store or process information that the client has no right to hold, to violate a third party right or to break an export control rule. A client must not ask the Company to sign a record that the client knows to be unsupported by the underlying data, and a client must not alter a certification record in a way that misrepresents the panel results.

A person must not present a certification record as the work of another organisation or remove the attribution that identifies the Company as the issuer. A person who quotes a record in public material should reproduce it accurately and should make clear which slice and date it covers.

The Company may suspend access to the website or pause a service where a credible breach of these rules is suspected. A suspension will be explained in writing, and the Company will lift the suspension where the concern is resolved or shown to be unfounded.

11. Intellectual Property

The Company owns the website, its text, its design and the tools and methods used to deliver the campus services. A visitor may read the website, print a page for personal or internal professional use and share a link, but may not republish the content as its own or incorporate it into a competing product without written permission.

The client owns its Client Data and continues to own it throughout the engagement. The client grants the Company a limited licence to process Client Data for the purpose of the engagement, and that licence ends when the engagement ends, subject to any retention obligation described in the service agreement.

A deliverable such as a findings brief, a lineage map or a tour walkthrough is licensed to the client for internal and professional use, including sharing with an auditor or a partner where the client sees fit. The Company retains ownership of the template and methodology behind a deliverable, and the client may not resell a deliverable as a standalone product without written permission.

The client grants the Company permission to name the client in a general client list and to describe the type of work performed, unless the client asks in writing to be omitted. The Company will not publish the substance of a client dataset or the content of a certification record in promotional material without written permission.

12. Confidentiality

Each party may receive information that the other treats as confidential. Confidential information includes a client dataset, a hardware profile, a scope of work, a fee schedule and the internal notes of a certification run. Information that is already public, that a party already held without a duty of confidence or that a party develops independently is not confidential under these terms.

Each party will use confidential information only for the purpose of the engagement and will disclose it only to people who need it and who are bound by a duty of confidence. The crew is small and access is limited to the people who do the work. A party will protect confidential information with care that is reasonable in the circumstances and no less than the care it uses for its own confidential material.

A party may disclose confidential information where the law requires it, after giving notice to the other party where notice is lawful and practical. The disclosing party will narrow the disclosure as far as possible and will cooperate with any effort to obtain a protective order.

Confidentiality obligations survive the end of an engagement. They do not expire with a contract term, though the obligation on ordinary business information may be limited to a period that the scope describes. The obligation on a client dataset and on a certification record continues as long as that material remains confidential.

13. Data Protection and Privacy

The Company handles personal data as described in the Privacy Policy published on this website. The Privacy Policy forms part of these terms by reference, and a person who agrees to these terms should also read the Privacy Policy to understand how personal data is handled.

Where the Company processes personal data on behalf of a client as part of an engagement, the Company acts as a processor and the client acts as the controller. The service agreement sets out the permitted purposes, the security commitments and the assistance the Company will provide for a request from an individual. Where the Company processes personal data for its own purposes, such as replying to an inquiry, the Company acts as a controller and the Privacy Policy applies.

The client is responsible for the lawfulness of the personal data it provides and for any notice to, or consent from, the individuals concerned. The Company will not use client personal data for its own marketing and will not transfer it to a third party except as the engagement requires or the law demands.

A security incident that affects client personal data will be handled under the breach response described in the Privacy Policy. The Company will notify the client without undue delay and will cooperate with the client own notification obligations.

14. Campus Tours and Visitors

A tour session is subject to a booking and a visitor list. A visitor must follow the safety instructions given by the crew, must stay with the group and must not touch equipment without permission. Closed footwear is required in the node rooms, and a visitor who arrives without it may be asked to wait in the office.

Photography is permitted in the office and in designated areas of the floor, but a visitor must not photograph client equipment, access credentials or a screen showing client data. The crew will point out the areas where photography is restricted. A visitor who wishes to record a presentation should ask the desk in advance.

The Company may reschedule a tour where a safety concern, a staffing issue or an emergency requires it. A rescheduled tour will be offered a new date, and the client may cancel without charge if no suitable date is available. The Company is not responsible for travel costs that a client incurs for a tour that is rescheduled for a reason outside the Company control, though it will give notice as early as possible.

15. Warranties and Disclaimers

The Company will perform each service with the reasonable skill and care of a competent data systems practice. This is the principal promise the Company makes, and it is the promise a client should rely on when planning an engagement.

Except for that promise, the website and the services are provided as available and without any additional warranty, whether express or implied. The Company does not warrant that the website will be uninterrupted or error free, that a dataset will be free of every defect after certification or that a certified dataset will produce a particular business result. A reader should not treat a certification record as a guarantee of accuracy beyond the panels it describes.

The Company does not warrant that a third party system used by a client will continue to operate in a particular way. A change made by a cloud provider, a device manufacturer or a network operator is outside the control of the Company. Where such a change affects an engagement, the Company will help the client understand the effect and will agree a remedy in writing.

The client is responsible for the decisions it makes using a dataset. The Company provides evidence and analysis, not a substitute for the judgement of the client or of a qualified professional in the client field.

16. Limitation of Liability

To the fullest extent permitted by law, the Company is not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost goodwill or lost opportunity, even if the Company has been advised that such a loss is possible.

The total liability of the Company arising out of or in connection with an engagement is limited to the total fees paid by the client for the service that gave rise to the claim during the twelve months before the event. Where a scope sets a different cap, the scope controls.

Nothing in these terms limits liability for fraud, for wilful misconduct, for death or personal injury caused by negligence, or for any other liability that the law does not allow a party to limit. Where a liability is excluded in one jurisdiction but not another, the exclusion applies only to the extent permitted in the jurisdiction concerned.

A party must bring a claim within the period stated in the scope or, where the scope is silent, within two years of the date on which the party knew or should reasonably have known of the facts giving rise to the claim. A claim brought later is barred to the extent the law allows.

17. Indemnity

The client will indemnify the Company against a claim, loss or expense that arises from Client Data that the client had no right to provide, from a breach of the acceptable use rules by the client, from a breach of the client obligations in these terms or from a decision the client makes using a dataset.

The Company will indemnify the client against a claim that a deliverable, in the form provided by the Company, infringes the intellectual property of a third party. This indemnity does not apply where the claim arises from a modification made by the client, from a combination with a client system or from use of the deliverable outside the purpose described in the scope.

A party seeking indemnity must give the other party prompt notice of the claim, must allow the other party to control the defence where that is reasonable and must cooperate in the defence. The indemnifying party will not settle a claim in a way that admits fault on the part of the indemnified party without written consent.

18. Suspension and Termination

Either party may terminate an engagement for convenience by giving the notice period stated in the scope. Where the scope is silent, a notice period of thirty days applies. A client remains responsible for fees for work performed before the termination and for any non cancellable cost the Company has incurred in reliance on the booking.

Either party may terminate an engagement immediately by written notice where the other party commits a material breach that is not remedied within ten days of a written request, where the other party becomes insolvent or where the other party engages in conduct that makes continued performance unsafe or unlawful.

The Company may suspend a service while a serious breach is investigated, while an undisputed invoice remains unpaid after a written reminder or while a safety concern requires action. A suspension will be lifted once the concern is resolved, and the Company will take reasonable steps to minimise disruption and to reschedule a delayed run window.

On termination, the Company will return or delete Client Data as the service agreement directs, provide any deliverable that has been paid for and issue a final invoice for work performed. A certification record already issued remains valid for the slice it describes, and the register entry continues to exist so that a recipient can verify the record.

19. Force Majeure

A party is not liable for a failure or delay caused by an event outside its reasonable control, such as a natural disaster, a severe storm, a fire, a flood, a widespread power failure, a network outage, an epidemic, civil unrest, a labour dispute, a change in law or an act of a public authority.

The affected party must notify the other party promptly, describe the event and estimate the likely effect on the engagement. The parties will work together to reduce the disruption, for example by moving a run window, using a backup connection or rescheduling a tour.

Where an event continues for more than sixty days and makes performance substantially impossible, either party may terminate the affected engagement on written notice without liability for the unperformed part, while remaining responsible for fees for work already performed. A force majeure event does not excuse a payment obligation that arose before the event.

20. Governing Law and Disputes

These terms and any engagement are governed by the laws of the State of Utah in the United States, without regard to a conflict of laws rule that would point to another jurisdiction. A party who wishes to raise a dispute should first write to the other party and describe the issue clearly.

The parties will attempt to resolve a dispute through good faith discussion for a period of thirty days after a written notice of dispute. A discussion may include a call between the campus desk and the client contact, a written exchange of positions or a mediation if both parties agree to one.

If a dispute is not resolved within that period, the parties submit to the exclusive jurisdiction of the state and federal courts located in Salt Lake County, Utah. Each party waives a right to a jury trial to the extent the law allows, and each party agrees that a claim must be brought in an individual capacity rather than as part of a class action.

Nothing in this section prevents a party from seeking urgent relief to protect confidential information or to prevent an infringement of intellectual property. A request for urgent relief does not waive the discussion requirement for the rest of the dispute.

21. Changes to These Terms

The Company may update these terms from time to time to reflect a change in the services, a change in the law or a clearer way of describing an existing practice. The date at the top of the page records the most recent update.

A change to these terms takes effect when it is published, except where the change is material to an existing engagement. A material change does not apply retroactively to a signed scope; the scope and the terms in force when it was signed continue to govern that engagement unless both parties agree otherwise in writing.

A person who continues to use the website after a change is published accepts the revised terms for future use. The Company will keep a copy of a superseded version on request and will provide it in writing to a client or a regulator that needs it.

22. General Provisions

These terms, together with a signed scope and the Privacy Policy, form the entire agreement between the parties on the subject and replace any earlier discussion or representation. A statement made during a sales conversation does not bind the Company unless it is written into the scope.

If a provision of these terms is held invalid or unenforceable, the remaining provisions continue in full force, and the invalid provision is read down to the minimum extent needed to make it enforceable. A failure to enforce a provision on one occasion is not a waiver of the right to enforce it later.

A party may not assign an engagement without the written consent of the other party, except where a client transfers the engagement to a successor in connection with a merger or a sale of substantially all its assets. The Company may use a subcontractor as described in the services section but remains responsible for delivery.

Notices must be in writing and sent to the address in the scope or, where none is stated, to the address for the Company given in these terms and to the client contact named in the scope. A notice sent by email is effective when delivered to a working mailbox, and a notice sent by post is effective three business days after posting.

No third party has a right to enforce a provision of these terms. The headings are for convenience only and do not affect interpretation. These terms are written in English, and an English version controls if a translation is ever produced.

23. Contact Information

Questions about these terms, a scope of work or a certification record are welcome at any time. The campus desk is the normal point of contact and will route a legal or technical question to the right member of the crew.

Written correspondence Antelope Data Campus, LLC
201 S Main St Ste 2025
Salt Lake City - 84111-2268
United States (US)

Email messages should be sent to certify@antelopedata.buzz. Telephone inquiries can be made on +19862880713 during the business hours published on our contact page.

A client who cannot locate a signed scope should write to the desk with the client name, the service and the approximate date of the engagement. The desk will find the record, confirm the terms that apply and send a copy in writing.

Home Services Contact Privacy Policy

Antelope Data Campus, LLC · 201 S Main St Ste 2025, Salt Lake City - 84111-2268, United States (US) · certify@antelopedata.buzz · +19862880713 · 2026 All rights reserved.