Terms of Service

1. Acceptance and who these terms are for

StatePlan Radar is the prelaunch product name used on this page. Access to the private application is currently by separate invitation only. If you accept an invitation and use the service for evaluation, you agree to these use, evidence, and disclaimer terms together with the written invitation; if you do not agree, do not use the private application. This public page by itself does not create a paid subscription or identify the future contracting provider. The intended service is for business use by safety, health, and compliance professionals and their firms.

2. What the service is

StatePlan Radar is a subscription briefing service designed to check an explicitly configured set of publicly available OSHA State Plan and Federal OSHA sources, summarize what successfully captured official sources state, link each record to its source, keep regulatory lifecycle dates distinct, and deliver weekly briefings in which every reported regulatory change is human-reviewed — including white-label editions that subscribers may forward to their own clients under the terms below. Registry configuration does not prove source activation, reachability, parser health, successful production monitoring, or publication-channel completeness. Separately classified state news/directive coverage is currently 0/29 State Plans until each jurisdiction is qualified, reviewed, activated, and observed. A week with no material changes may receive a monitoring-confirmation edition only when the exact frozen source set qualifies; its coverage receipt discloses unhealthy or missing evidence and does not imply that an unconfigured publication channel was checked. We may adjust source coverage, formats, and features with notice.

3. Informational use only — no advice, no compliance determinations

4. Subscriptions, billing, renewal, cancellation, refunds

No current public purchase. All public payment links are deactivated and no charge can be initiated from this site. A request for pilot review, product discussion, or account invitation is not a purchase.

Future paid activation. A paid subscription may begin only through a separately approved activation flow and customer-specific written terms identifying the contracting provider, exact plan, included capabilities and jurisdiction limits, price, billing interval, renewal, cancellation, refund terms, and acceptance record. The current Briefing pilot scope under review is limited to no more than 10 selected State Plan jurisdictions. Workspace and Firm are future packaging concepts and are not currently offered as separate plans.

Billing, renewal, cancellation, and refunds. Before accepting payment, the final customer agreement and checkout must state the complete commercial terms. The intended policy is to allow cancellation before renewal, continued access through the paid term, a full refund when the first paid briefing is reported as not useful within 7 days of receipt, correction of erroneous charges, and advance notice of price changes. These intended terms are not active billing terms until included in the approved customer agreement.

5. Subscriber license

Subject to your written invitation or paid activation agreement, you receive a limited, non-exclusive, non-transferable license to use the service for the approved evaluation or business purpose and — only when the written scope includes white-label editions — to rebrand and forward briefings to your own clients as described in Section 6. You may not resell, sublicense, redistribute on public platforms, scrape, or extract the service's content into competing products or databases. API access, additional brands/divisions, and volume redistribution require express written approval.

6. White-label addendum (applies whenever you forward under your own brand)

• License. You may reproduce and distribute white-label editions under your firm's branding, solely to your own clients and prospects in direct communications.
• No removal of provenance. You may rebrand headers and footers, but you may not remove official source links, capture dates, effective/status dates, or correction markers.
• Final review. You are responsible for reviewing content before sending it to clients and for tailoring any advice to client-specific facts. If you edit, annotate, excerpt, combine, or suppress parts of the content, the resulting version is your responsibility.
• No vendor compliance opinions. We supply research summaries only; you remain solely responsible for any legal, consulting, or compliance advice you give.
• Correction pass-through. If we issue a material correction, you agree to forward it promptly to anyone who received the affected item from you.
• Indemnity. You will indemnify StatePlan Radar against third-party claims arising from your branding, edits, distribution, client advice, or unlawful use of the content.

7. Correction policy

If we identify an error in a published record, a qualified reviewer assigns severity and immutable notification-preparation and closure deadlines before publishing a successor version in every affected subscriber's authenticated correction center, identifying what changed and why. Escalation and closure evidence are appended without rewriting the original correction; closure requires a stored official-source snapshot or an official HTTPS evidence link and explanatory record. The dated correction also appears alongside each affected report while the original issued PDF remains immutable. The authenticated correction center and report history are authoritative as soon as the correction is published. We also stage an email-notification draft for each affected subscriber; an operator must review and send it, and until then it remains a draft. Drafted, sent, and recipient-delivered are distinct statuses. Email is a convenience notice, not the authoritative correction record. Subscribers should not wait for email before acting on a correction visible in the hub. White-label subscribers must pass corrections through to their recipients (Section 6). This policy reflects how we work; it does not create a duty to monitor every legal development or every downstream use.

8. Intellectual property and government sources

The service's compilation, structure, summaries, and formats are owned by StatePlan Radar. Underlying federal government materials are public domain; state materials may be subject to state-law protections and are quoted sparingly with linked attribution. We do not use OSHA or state-agency logos or seals, and nothing in the service implies any government endorsement.

9. Acceptable use

You agree not to: share access credentials beyond your plan's users; use the service to build or train a competing product; scrape or bulk-extract content; misrepresent the service's outputs as government communications; or use the content in a way that violates law or third-party rights.

10. No warranty

11. Limitation of liability

To the fullest extent permitted by law: (a) StatePlan Radar's aggregate liability arising out of or relating to the service is capped at the fees you paid in the 12 months before the event giving rise to the claim; and (b) we are not liable for indirect, incidental, special, consequential, or punitive damages, or lost profits, revenue, data, or goodwill.

12. Indemnity

You will defend and indemnify StatePlan Radar against third-party claims arising from your use of the service in violation of these Terms, including the white-label obligations in Section 6.

13. Privacy and AI

We collect what we need to run the service: your contact details, firm and brand details you provide during approved activation or in your subscriber account (including an uploaded logo), watchlist configuration, and service emails. Authorized operators may view those account details together with plan, billing/status, watchlist, branding/readiness, and current or latest issue status in a protected internal operations screen when needed to administer access, configuration, publication, billing, or support. If paid activation is later approved, Stripe processes payment details; we never see full card numbers. We don't sell your data or use tracking pixels in briefings. A report may be opened through an authenticated subscriber account, an invited client-portal session, or an expiring and revocable read-only link to one exact released edition created by an authorized workspace member with delivery permission. Anyone who receives an active read-only link can open that edition, including its published company identity, so share it only with the audience you intend.

Service activity and product analytics. To restore each member's report workflow, we keep the first and most recent time that member opened an issued report and whether and when they marked it reviewed. The application's first-party analytics ledger also records selected workflow events—such as edition opens, official-source clicks, edits, approvals, suppressions, exports, deliveries, correction views, client assignments, and recorded follow-ups—together with the workspace actor type and, where relevant, the member or portal-user ID, client profile, edition, issue or source record, event time, application route, and limited event metadata. We use these records for workflow history, operational audit, deduplication, workspace analytics, and customer-requested value reports. This ledger does not collect IP addresses or user-agent strings, and we do not use third-party analytics or tracking pixels.

Share-link requests. For an authorized-member-created read-only link, we keep its successful request count and first and latest request times. The released-edition share ledger also keeps one access event with its timestamp for each successful request. Security scans, automated previews, and reloads can be included, so this activity does not prove that a guest read the report. The application share ledgers do not store the guest reader's identity, IP address, or user-agent details; infrastructure providers may process routine request data to deliver and protect the service. These report, analytics, and link records remain with the related membership or issued history for service continuity and audit. Separately, sign-in abuse controls keep a secret-keyed, one-way network fingerprint for no more than 25 hours; the raw network address is never stored.

API security audit. Scoped API requests append an immutable security-audit record containing the key and workspace IDs, route template, status, timing and rate-limit result, a SHA-256 digest of a submitted request body, and secret-keyed one-way fingerprints of the forwarded network address and user-agent string when supplied by the hosting boundary. Raw request bodies, network addresses, and user-agent strings are not stored in that ledger. No automatic deletion period is enabled today; API access must remain limited to an approved scope until counsel and the owner approve the retention period and deletion/export treatment.

To request a copy or correction of your account data, or to ask us to delete data that is no longer needed, email info@stateplanradar.com. We may retain issued briefing snapshots, product-analytics and workflow audit records, share-access events, correction and security audit records, and billing records where needed to preserve the service's historical record, meet legal obligations, resolve disputes, or enforce these Terms. Some audit and issued-history ledgers are designed to be immutable. We will explain any retention that prevents a requested deletion.

Your data is never AI training data. We do not use your firm's name, branding, watchlist, client information, or communications to train AI models — ours or anyone else's. AI tools may assist our internal research and drafting, but no AI-drafted change is published without human review against the official source (Section 3), and no customer data enters that tooling.

Subprocessors. We rely on a short list of infrastructure providers: Stripe (payments), Google Workspace (email delivery), Cloudflare (public website), Supabase (database and private object storage), Vercel (authenticated application and API hosting), and GitHub Actions (scheduled build and operational processing). We'll update this list here if it changes materially.

14. Suspension and termination

We may suspend or terminate invited evaluation access for material breach of these terms (including license violations) after notice and a reasonable opportunity to cure where practicable. You may stop an evaluation and request account closure by emailing the contact below. Any future paid cancellation and post-termination terms must be stated in the approved customer agreement; this preview does not create them.

15. Contracting identity, governing law, and disputes

This public prelaunch preview does not select a contracting entity, governing law, or venue. Those details must be stated in the separate written invitation or customer agreement before private evaluation or paid activation, with any required legal review. Before filing a claim relating to an invited evaluation, the parties should first attempt good-faith resolution by email except where applicable law requires otherwise.

16. Changes to the service or these Terms

We may revise this prelaunch draft by posting an updated version and date. Material rules for an invited evaluation must be communicated under its written invitation, and changes to any future paid service must follow the notice and acceptance process in the approved customer agreement. A website edit alone does not replace customer-specific terms.

17. Contact and notices

StatePlan Radar (prelaunch product name; contracting identity to be confirmed before paid activation) · info@stateplanradar.com. Legal notices regarding an invited evaluation must be sent by email with "Legal notice" in the subject line. Any future customer agreement will provide the contracting party's formal notice details.