Public review draft, pending legal and technical approval
Terms of use · review draft
A detailed B2B draft covering worker rights, organization scopes, record evidence and the limits of current product features.
Reviewed 2026-11-06 · No approved effective date
01. Purpose and scope
DailySafe supports TBM, worker participation, hours and related records. Public site, beta and contracted operational service terms can differ. The applicability and priority of negotiated agreements must be specified.
02. Definitions and roles
Distinguishes company, contractor, work team, foreman, worker, site, TBM, workday, confirmation, dispute and correction. Participation on the same site does not imply shared employment or unrestricted data access.
03. Registration and phone verification
Phone/SMS authentication is currently handled by the existing manager application. Verification, organization setup, invitations and permissions are separate steps. Users must not impersonate another person or organization.
04. Tenant access and confidentiality
A company may view authorized site TBM but not a team's private hours, payroll, costs or roster merely by sharing a site. Creating a project does not transfer ownership of another organization's records. Enforcement must match server permissions and contracts.
05. Acknowledgments, disputes and corrections
TBM sign-off records a particular acknowledgment, not automatic completion of all statutory safety duties. Confirming hours does not waive wages, statutory rights or employer liability. Errors require a correction and dispute process.
06. Record integrity and legal effect
Records and signatures can support evidence review, but admissibility and weight depend on context and authority assessment. The service does not promise automatic immunity, absolute immutability or guaranteed judicial acceptance.
07. Videos and safety guidance
Videos and checkboxes can document exposure but do not by themselves prove comprehension or replace required training, supervision or risk assessment. Applicability depends on site conditions and law.
08. User duties and prohibited conduct
Fake TBM sign-offs, false hours, unauthorized uploads, permission bypass and unlawful publication of personal data are prohibited. Organization administrators must manage invitations and revoke obsolete access.
09. Changes and interruptions
Beta functionality may change. Significant changes, outages, notification methods and continuity arrangements require defined operational and contractual procedures. Roadmap features are not guaranteed live.
10. Fees, contracts and cancellation
Pilots, paid plans, billing, termination and refunds require approved commercial terms. Viewing the site or demo does not itself create a paid subscription. Automatic billing terms must match a real enabled mechanism.
11. Export and deletion after termination
Termination must distinguish export, access revocation, required preservation and deletion. Immediate permanent erasure of all evidence cannot be promised without assessing legal obligations and third-party rights.
12. Intellectual property and uploads
Software and brand rights are distinct from user-uploaded photos, documents and logos. A directory application does not imply approved partnership or verified logo rights.
13. Privacy and security
Personal information is governed by the privacy policy and mandatory law. These terms do not waive statutory individual rights or controller obligations. Collection must be proportionate to the purpose.
14. Liability and disputes
Safety duties, wages and site supervision remain subject to law and contracts. These terms do not purport to exclude non-excludable liability, willful misconduct or gross negligence. Governing law, jurisdiction and dispute steps need legal approval.
15. Revisions and effective date
Material revisions require appropriate notice and any required consent, effective dates and version history. This draft does not claim a binding final effective date.