Terms of service

Effective date: 10/1/2026

Last updated: 10/1/2026

These Terms of Service (the “Terms”) are an agreement between you and Deacon James, LLC, dba Data Tactical Group, an Idaho LLC, with its principal office at 2611 Indian Mound Blvd, Monroe, LA 71201 (“DTG”, “we”, “us”). They govern your use of the Data Tactical Group Service (the “Service”), our web application and API for county-level labor-market data.

If you use the Service on behalf of an organization, you agree to these Terms for that organization and confirm you have authority to do so. If you do not agree, do not use the Service.

1. Definitions

Service. The Data Tactical Group web application, the Data Tactical Group API, the API sandbox, exports, and any related documentation and support.

Data. The labor-market statistics we make available through the Service, including industry, occupation, and wage figures for U.S. counties and aggregates of them.

Vintage. A complete, labeled release of the Data, identified by a label such as DTG 2026.2. Each vintage is fixed once released. We never edit a vintage after release.

Superseding rebuild. If we find an error after release that changes values, we publish a corrected rebuild of that vintage labeled with an r number: the first correction is r1 (for example, DTG 2026.3r1), the second r2, and so on. The rebuild supersedes the defective build, which is no longer served. A documentation-only correction does not produce a rebuild.

Withdrawn build. If a defect is serious, we may withdraw a build before its rebuild is ready. A withdrawn build is no longer served from the moment we withdraw it.

Current vintage. The vintage (including its latest superseding rebuild, if any) that the Service serves as its default at a given time. A vintage stops being current when (a) we release the next vintage (for example, DTG 2026.3 replacing DTG 2026.2), (b) a superseding rebuild replaces it (for example, DTG 2026.3r1 superseding DTG 2026.3), or (c) we withdraw it. Our release notes use these same terms: each names the current vintage, and a rebuild’s note says which build it supersedes and that the earlier build is no longer served.

Organization. The account through which a customer subscribes. An organization has at least one owner and may have admins and members.

Member. Any person with access to an organization, including its owners and admins.

Credential. A sign-in to the Service or an API key.

Points. The monthly metered unit that measures API and file-export use, as described in Section 9.

Derived findings. Analysis, conclusions, charts, tables, narrative, and reasonable excerpts of Data that you produce in the course of your own work.

Derived database. Any collection of Data, in any form, that could substitute in whole or in part for access to the Service.

2. Accounts and organizations

2.1 Signing in. You sign in with your email address and a password, and may add a second factor. You must give us an address you control and keep it current.

2.2 One person per credential. Each sign-in and each API key belongs to one individual member. You may not share a credential with anyone, including colleagues in your own organization. For your security, each person has one active session: when you sign in, any other session you have open ends without warning.

2.3 API keys. API keys are issued per member, not per organization. Each member with API access may hold up to two live keys at a time, so a key can be rotated without downtime. Sandbox keys are counted separately. You are responsible for keeping your keys secret and for all use made with them.

2.4 Roles. Owners, and any billing contacts they appoint, manage the organization’s subscription. Only an owner may close the organization. Admins manage members and settings. Members use the Service within their organization’s plan.

2.5 Joining by domain. An organization may verify an email domain it controls and allow people with addresses on that domain to join it themselves. The organization is responsible for the people who join this way.

2.6 Ownership claims. If an organization’s owner becomes unreachable, an admin of a domain-verified organization may claim ownership. We send notice to the existing owners, and the claim completes seven days after that notice unless an owner signs in to the Service during that time. Replying to the notice email or using an API key does not stop the claim. We record the claimant’s name and email address at the time of the claim as part of the organization’s records.

2.7 Your responsibility. You are responsible for all activity under your organization and your credentials, and for telling us promptly at support@datatactical.group if you believe a credential has been compromised.

3. Plans, trials, and the sandbox

3.1 Plans. We offer Free, Local, Regional, and National plans, billed monthly or annually. What each plan includes (counties, seats, points, and features) is as published on our pricing page at the time you subscribe or renew.

3.2 API add-on. API access is an add-on available on every paid plan and is sold on annual terms only. If you add it partway through a term, your term restarts on the day you add it and we credit the unused value of your current term toward the new one.

3.3 Trials. We may offer a free trial, and we may decline to offer one. Each person may have one trial. A trial, when offered, lasts seven days, covers one county, includes every data feature except live API keys, and does not require a payment card.

3.4 Sandbox. We provide an API sandbox for development. The sandbox serves synthetic data only. Sandbox keys cannot retrieve real Data, and synthetic data from the sandbox is not Data under these Terms.

4. What you may do with the Data

4.1 Your license. While your subscription is active, and subject to these Terms, we grant your organization’s members a non-exclusive, non-transferable license to access and use the Data through the Service for your internal business purposes and for work you do for clients.

4.2 Derived findings are yours. You own your derived findings. You may use them, publish them, and share them however you like, subject to the attribution requirement in Section 5. This expressly includes:

• consultants, economic developers, workforce boards, and similar professionals using the Data to prepare reports, studies, presentations, grant applications, and other deliverables for clients;
• publishing charts, tables, and figures drawn from the Data in reports, articles, websites, and presentations;
• building public-facing tools, dashboards, and web pages that show Data or derived findings to the public. We encourage these.

You do not need separate approval from DTG for each publication or public-facing tool, as long as your use complies with these Terms.

4.3 A derived database is not yours. The line is this: your conclusions belong to you; a copy of our Data does not. You may not assemble, keep, or distribute a derived database except as Section 8 allows for caching.

For example, a report, study, or dashboard that uses the Data for the areas and topics it analyzes is permitted, and so is a public tool that displays Data to its users within Section 8. A searchable or downloadable repository that reproduces a substantial portion of the Data is not, and neither is a feed, file, or service that lets others obtain the Data without using the Service.

5. Attribution

When you publish or share Data or derived findings outside your organization, including in client deliverables and public-facing tools, you must credit Data Tactical Group as the source.

What to write: “Source: Data Tactical Group” together with the vintage label, for example “Source: Data Tactical Group, DTG 2026.3”. Public-facing tools may also show a “Powered by Data Tactical Group” badge; it is welcome but not required.

Where it goes: in a report or document, in the source note or caption of each chart or table that shows the Data, or in a single sources section that clearly covers them; in a public-facing tool or web page, a visible source line on each page or screen that displays the Data. On those screens a short form such as “Source: DTG 2026.3” is enough, as long as the full attribution appears on the tool’s about or sources page. Our spreadsheet exports carry this attribution on their Source sheet; please keep it when you reuse them.

6. Prohibited use

You may not, and may not allow anyone else to:

6.1 Extract in bulk. Extract Data in a systematic or regular manner so as to assemble a collection comprising all or part of the Data, whether by API, by export, by copying from the web application, or by any manual process, and whether or not you stay within the published limits. Bulk extraction is defined by how and why Data is taken, not by how much.

Ordinary use is not bulk extraction. These are permitted:

• retrieving the areas, industries, and occupations a specific project, report, or client engagement needs;
• running queries to explore and analyze the Data;
• exporting tables for a deliverable;
• refreshing a public-facing tool or dashboard within the caching allowance in Section 8.

These are bulk extraction:

• systematically enumerating every combination of area, industry, or occupation;
• repeatedly downloading Data to build an offline store beyond what Section 8 allows;
• designing automated queries whose main purpose is to reconstruct the Data;
• coordinating members, credentials, or organizations to assemble a collection that none could assemble alone.

6.2 Build a substitute. Use the Data to build a derived database, or to build, train, or supply any product or service that competes with or substitutes for the Service.

6.3 Redistribute. Sell, resell, rent, sublicense, or redistribute the Data itself, or give access to the Service or the Data to anyone who is not a member of your organization. Sharing derived findings under Section 4.2 is not redistribution.

6.4 Circumvent limits. Work around any limit, quota, or restriction of the Service, including by using the web application to obtain what API limits prevent, by spreading requests across credentials or organizations, or by creating additional accounts or trials.

6.5 Share credentials. Share a sign-in or API key, or let more than one person use it.

6.6 Interfere or misuse. Probe, scan, or test the vulnerability of the Service without our written permission; interfere with its operation; reverse engineer it except where the law forbids that restriction; or use it in violation of any law.

7. Limits

The Service enforces published limits so that it stays fast for everyone. At launch these include a maximum of 400,000 cells and 10,000 series per request; 120 requests per minute for each API key, and 120 per minute for each person across all of their browser sessions; and 300 requests per minute per organization. When a limit is reached or the Service is busy, it answers with HTTP status 429 and a Retry-After header; your software should wait the time indicated before retrying. A request larger than the per-request limits is refused with status 400 and should be narrowed rather than retried. We may change limits under Section 12. Staying within the limits does not make an otherwise prohibited use permitted.

8. Caching and keeping Data

8.1 The allowance. You may store Data retrieved from a vintage, and serve it to your own users (for example, in a public-facing tool), for as long as that vintage is the current vintage, and for 30 days after it stops being current.

8.2 When the clock starts. The 30 days run from the day the vintage stops being current, whether that happens because we release the next vintage, because a superseding rebuild replaces it, or because we withdraw it. They do not run from the day you downloaded the Data. We announce each release, each superseding rebuild, and each withdrawal in our release notes, and when we withdraw a build we also tell the organizations that exported Data from it.

8.3 After the 30 days. You must refresh stored Data from the current vintage or delete it. Derived findings you have already published (such as a finished report or a dated chart labeled with its vintage) may stay as published.

8.4 Caching is not a derived database. The caching allowance exists so your tools can perform well. It does not permit keeping Data you would not otherwise be allowed to extract.

8.5 Public-facing tools. A public-facing tool may display Data to its users during the period Section 8.1 allows. It may not give users a downloadable or otherwise extractable copy of a substantial portion of the Data. A live tool that displays Data is stored Data under this section, not a published derived finding under Section 8.3.

9. Points

API requests and file exports (CSV and spreadsheet) use points, which your plan grants each calendar month (UTC). Browsing the web application does not use points. A data value that is zero, empty, or rounds to zero as displayed never counts toward points. How points are calculated and how many each plan includes are as published. When your organization’s points for the month are used up, API requests and exports stop until the next month begins. Unused points do not carry over to the next month.

10. Monitoring, suspension, and audit

10.1 Monitoring. We monitor use of the Service to operate it, enforce these Terms, and protect it, and we may apply rate limits at any time.

10.2 Suspension. If use of the Service appears to us to breach these Terms, we may suspend access for a whole organization or for one person’s account. A person’s suspension ends that person’s sessions and refuses that person’s API keys; it does not change the organization’s membership, seats, subscription or billing, and we can reverse it at once. Where the concern is one person, we may instead end that person’s access by closing their account; that is not a suspension and is not reversed by this section. We will tell you when we suspend an organization or a person and why. Suspension ends active sessions and disables access; it does not cancel or change your subscription, and billing continues. We can reverse a suspension at once, and we will when the concern is resolved. If we conclude that the use did not breach these Terms, we will credit your organization’s account with its subscription fees for the days the suspension lasted, applied to its next invoice.

10.3 Audit. On reasonable notice, you agree to cooperate with our reasonable requests to confirm your compliance with these Terms, including by describing how you store and use the Data. Our requests will be in writing and proportionate to the concern, and you may answer them in writing; they do not include on-site inspection. Our audit rights continue for one year after your subscription ends or is terminated.

11. Fees, billing, and refunds

11.1 Payment. Paid plans are billed in advance through our payment processor, Stripe. We do not see or store your full card details.

11.2 Annual pricing. An annual subscription costs ten times the monthly price of the same plan.

11.3 Renewal. Subscriptions renew automatically for the same term unless canceled. You can cancel at any time; cancellation stops the next renewal, and you keep access until the end of the period you have paid for.

11.4 No refunds on annual terms. Annual subscriptions are non-refundable.

11.5 Reserved.

11.6 Seats and counties. Adding seats or counties takes effect at once and is charged prorated for the rest of the period. Removing seats or counties takes effect at the end of the period and is not credited. Removed counties are processed together once a month. Swapping which counties you have, without changing how many, is not a billing change.

11.7 If a payment fails. If a payment fails, your subscription becomes past due. While past due, your organization keeps its account, members, and settings, but county detail, file exports, API access, and editing of custom regions pause at once; national and state figures remain available and nothing is deleted. You have 16 days to update your card; as soon as payment succeeds in that time, everything is restored at once. If payment has not succeeded after 16 days, we end the subscription and your organization moves to the Free plan. Your organization’s records are kept, and you can subscribe again at any time.

11.8 Taxes. Reserved.

12. Changes to prices, limits, and features

Prices and plan contents, including points allowances and how points are calculated, are as published at the time you subscribe or renew. We will not raise the price of a term you have already paid for, and we will not reduce your plan’s points allowance during it. We will give you at least 30 days’ notice before a price increase or a reduction in your plan takes effect at your next renewal. The request limits in Section 7 are the one exception: we may tighten them sooner when needed to protect the Service, and will tell you when we do.

13. Closing and termination

13.1 Closing. An owner may close the organization at any time. Closing takes effect at once: it cancels the subscription immediately, without a refund, and the rest of the paid term is forfeited. To keep access until the end of the paid term, cancel the subscription under Section 11.3 instead.

13.2 Termination by us. We may terminate your organization’s access for material breach of these Terms. Termination for breach is without refund.

13.3 What happens at close or termination. API keys are revoked, memberships are removed, and the subscription is canceled without a refund. You must stop using the Data, and within 30 days you must delete all Data you have stored, including cached Data under Section 8. On request, you must confirm the deletion in writing. This 30-day period never extends the time Section 8 allows: Data that Section 8 requires you to refresh or delete sooner must be refreshed or deleted on that schedule. Derived findings you have already published may stay as published.

13.4 Your organization’s records. We keep the organization’s records after it closes, so a former owner can reopen it at any time. A reopened organization starts on the Free plan, and other members must be invited again. Individuals may ask us to erase their personal information as our Privacy Policy describes.

13.5 What survives. Sections 4.3, 5, 6, 8.3, 8.5, 10.3, 13, 14, 15, and 16, and any other terms that by their nature should survive, continue after close or termination.

14. About the Data

The Data are statistical estimates. They are revised from vintage to vintage. Where the source statistics withhold a value to protect confidentiality, we provide our own estimate of it, and each industry value carries a disclosure code and a reliability score that you should take into account. An earlier vintage may differ from a later one because estimates are revised, methods change, or new source information becomes available, so an earlier vintage is not a statement about current conditions. The Data are provided for information and analysis. We do not warrant that the Data are fit for any particular decision, and you are responsible for your derived findings and for decisions you make with them.

15. Legal terms

15.1 Business use. The Service is for business, government, academic, and nonprofit use. By accepting these Terms you confirm that you are using the Service for one of those purposes and not as a consumer.

15.2 Ownership. We and our licensors own the Service and the Data, including all intellectual property rights in them. Apart from the license in Section 4.1, these Terms give you no rights in the Service or the Data. If you send us suggestions or feedback, we may use them without any obligation to you.

15.3 Disclaimer of warranties. Except as these Terms expressly state, the Service and the Data are provided “as is” and “as available.” To the fullest extent the law allows, we disclaim all other warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, accuracy, completeness, and non-infringement. We do not promise that the Service will be uninterrupted or error-free, or that any particular figure is free of estimation error. Unless we agree otherwise in a signed written agreement, the Service comes with no service-level commitment. The Free plan, trials, and the sandbox are provided without any warranty or service commitment.

15.4 Limitation of liability.

(a) Neither party is liable to the other for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, revenue, goodwill, or data, arising from these Terms or the Service, even if told such damages were possible.

(b) Each party’s total liability for all claims arising from these Terms or the Service is limited to the fees your organization paid us for the Service in the 12 months before the event giving rise to the claim. If your organization has paid nothing (for example, on the Free plan or a trial), our total liability is limited to $100.

(c) These limits do not apply to your obligation to pay fees, to your indemnity under Section 15.5, to a breach of Section 6 (Prohibited use), or to liability that the law does not allow to be limited.

15.5 Your indemnity. You will defend and indemnify DTG against third-party claims, and the resulting losses, damages, and reasonable legal costs, arising from: (a) use of the Service in breach of Section 6; or (b) your breach of law in using the Service. We will notify you promptly of any such claim, let you control its defense, and cooperate reasonably at your expense. You may not settle a claim in a way that imposes an obligation on DTG without our consent.

15.6 Public entities. If you are a government body or other public entity and the law that governs you prevents you from accepting any part of Section 15 or 16 (for example, the indemnity, the choice of law, or a limit on liability), that part applies to you only to the extent the law allows, and the rest of these Terms continues to apply.

16. General

16.1 Changes to these Terms. We may update these Terms. We will give owners of paid organizations at least 30 days’ notice of a material change by email or in the Service before it takes effect, and the “Last updated” date at the top will show when the Terms last changed. If you do not agree to a change, you may cancel before it takes effect, and Section 11.3 applies. Continuing to use the Service after a change takes effect means you accept it.

16.2 Governing law and venue. These Terms are governed by the laws of the State of Louisiana, without regard to its conflict-of-laws rules. Any dispute arising from these Terms or the Service will be heard only in the state or federal courts located in Ouachita Parish, Louisiana, and each party consents to those courts’ jurisdiction. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

16.3 Assignment. You may not assign or transfer these Terms or your subscription without our written consent. We may assign these Terms as part of a merger, acquisition, or sale of all or substantially all of our business or assets, with notice to you.

16.4 Entire agreement and order of precedence. These Terms, our Privacy Policy, and the plan details on our published pricing page at the time you subscribe or renew are the entire agreement between you and DTG about the Service. If they conflict, these Terms control, except that a signed written agreement between your organization and DTG controls over these Terms for the matters it covers. Terms in your purchase orders or other documents do not apply even if we accept or sign them.

16.5 Severability and waiver. If any part of these Terms is found unenforceable, it will be enforced to the maximum extent possible and the rest will stay in effect. Our failure to enforce a provision is not a waiver of our right to enforce it later.

16.6 Events beyond our control. We are not responsible for delays or failures caused by events beyond our reasonable control, including outages of internet, hosting, or payment providers, delays or changes in government data releases, natural disasters, and acts of government.

16.7 Notices. We send notices to the email address of your organization’s owners, and notices are effective when sent. Send notices to us at support@datatactical.group, or legal notices in writing to the address in Section 17.

16.8 Export and sanctions. You may not use the Service, or allow it to be used, in violation of U.S. export control or sanctions laws, including by anyone in a country or on a list subject to U.S. sanctions.

16.9 Independent parties. You and DTG are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency, or employment relationship, and there are no third-party beneficiaries.

17. Contact

Questions about these Terms: support@datatactical.group

Deacon James, LLC, dba Data Tactical Group
2611 Indian Mound Blvd, Monroe, LA 71201