Terms of Service

1. Acceptance and who these terms are for

RuleCue is the prelaunch product name used on this page. Private-application access is not currently authorized. If a future invitation is approved through the complete readiness process and you accept it 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 access or a paid subscription, and it does not identify or bind a contracting provider. The intended service is for business use by safety, health, and compliance professionals and their firms.

2. What the service is

RuleCue 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 consultants 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 checkout and customer agreement must disclose the approved billing, renewal, cancellation, and refund rules. This nonbinding prelaunch preview does not promise a refund window, credit, or usefulness guarantee.

5. Customer 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.
• Proposed responsibility allocation. Any indemnity for branding, edits, distribution, client advice, or unlawful use would exist only if stated in a counsel-approved written invitation or customer agreement naming the legal parties. This public draft creates no indemnity obligation.

7. Correction policy

Designed policy for a future approved evaluation. If the approved service identifies an error in a released record, the designed workflow requires a qualified reviewer to assign severity and immutable notification-preparation and closure deadlines before a successor version is published in every affected consultant workspace's authenticated correction center, identifying what changed and why. Escalation and closure evidence would be appended without rewriting the original correction; closure would require a stored official-source snapshot or an official HTTPS evidence link and explanatory record. The dated correction would appear alongside each affected report while the original issued PDF remains immutable. The authenticated correction center and report history would become authoritative when the correction is published. The workflow would also stage an email-notification draft for each affected customer; an operator would have to review and send it, and until then it would remain a draft. Drafted, sent, and recipient-delivered remain distinct statuses. Email would be a convenience notice, not the authoritative correction record. Any approved white-label terms must require customers to pass corrections through to their recipients. This designed policy is not currently operating for customers and does not create access, a monitoring duty, or a duty concerning every downstream use.

8. Intellectual property and government sources

Any rights in the service's compilation, structure, summaries, and formats, and the legal entity that owns or licenses them, must be identified in the applicable counsel-approved written agreement. Underlying federal government materials are generally public domain; state materials may be subject to state-law protections and are quoted sparingly with linked attribution. The proposed service does not use OSHA or state-agency logos or seals, and nothing on this site implies 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

Proposed draft allocation only. Any limitation or exclusion of liability must be supplied by counsel in a written invitation or customer agreement that identifies the contracting legal entity, governing law, and accepted commercial terms. No liability cap is created by this public preview.

12. Indemnity

Proposed draft allocation only. Any defense or indemnity obligation must be stated in a counsel-approved written invitation or customer agreement naming the legal parties. This public preview creates no defense or indemnity obligation.

13. Privacy and AI

Designed data boundary for any future approved access. Subject to counsel-approved privacy materials and the written invitation, the service is designed to process contact details, firm and brand details supplied through approved access (including an uploaded logo), watchlist configuration, and service emails. Authorized operators would be able to view bounded account and service-status details when necessary to administer access, configuration, publication, billing, or support. If paid activation were later approved, Stripe would process payment details; the application is designed not to receive full card numbers. The service is designed not to sell customer data or use tracking pixels in briefings. Reports could be opened only through the approved authenticated workspace, invited client-portal session, or an expiring and revocable read-only link to one exact released edition.

Service activity and product analytics. For future approved access, the designed first-party ledger would record bounded report-workflow and service events for continuity, operational audit, deduplication, workspace analytics, and customer-requested value reports. It is designed not to collect IP addresses or raw user-agent strings and not to use third-party analytics or tracking pixels. Exact collection, use, retention, access, and deletion terms remain subject to counsel-approved privacy materials before any invitation.

Share-link requests. For a future authorized-member-created read-only link, the designed ledgers would keep bounded successful-request counts/times and one timestamped access event per successful request. Scans, previews, and reloads could be included, so that activity would not prove a person read the report. The application ledgers are designed not to store the guest reader's identity, IP address, or raw user-agent details; infrastructure providers may process routine request data subject to the approved provider/privacy terms.

API security audit. If scoped API access is later approved, the designed immutable audit record would contain bounded key/workspace IDs, route template, status, timing/rate-limit result, a submitted-body digest, and secret-keyed one-way network/user-agent fingerprints supplied by the hosting boundary—not raw bodies, network addresses, or user-agent strings. API access must remain disabled 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@rulecue.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.

Current and planned service providers; legal roles pending counsel review. The public website currently uses Cloudflare, business email uses Google Workspace, and development and release operations use GitHub, Supabase, and Vercel within the documented prelaunch boundary. Stripe payment processing, Resend transactional email, scheduled application processing, and isolated transactional-email intake are future-only capabilities that remain disabled pending separate approval. Before any activation, the approved privacy materials must classify each provider's legal role and name any additional isolated-ingress hosting or logging provider that can process service-request metadata. The list will be updated 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

RuleCue (prelaunch product name; contracting identity to be confirmed before any evaluation invitation or paid activation) · info@rulecue.com. Any future written invitation or customer agreement must provide the contracting party's formal notice details.