Terms
Terms of use
The intended rules for accessing and using the Forjdeck production workspace.
Status: Pre-launch draft · Last reviewed 20 July 2026
Important pre-launch notice
These terms are a product draft, not final legal terms. Forjdeck's legal entity, contracting party, paid plan details, governing law, liability terms, support commitments, and formal notice process must be supplied and reviewed before launch.
Accounts and invitations
Users are responsible for accurate account information, protecting their credentials, and promptly reporting suspected misuse. Invitations are intended for their named recipient and should expire after a limited period. Team administrators control workspace and project access subject to server-enforced permissions.
Customer content
Customers retain ownership of their production content. They must have the rights needed to upload, review, share, and request the media they place in Forjdeck. The service needs only the limited permission required to store, process, display, transmit, and delete that content as instructed and as described by the final terms.
Reviews and approvals
Comments, resolved notes, reviewer completion, requests for changes, and formal approval are distinct actions. Users are responsible for confirming that the people making approval decisions have the authority to do so. Forjdeck should preserve the version, actor, and time associated with each recorded decision.
Raw-footage requests
Raw footage is intended to be provided only after staff approval, through protected temporary access, and for 60 days after the package is uploaded. Clients are responsible for downloading authorised material before expiry. The final agreement must define fulfilment scope, delivery timing, fees if any, permitted use, and any legal or contractual retention exception.
Acceptable use
Users must not use Forjdeck to violate law or third-party rights; upload malicious, unlawful, or unauthorised material; bypass access controls; probe or disrupt the service; share another person's credentials; or attempt to access another team or client's information.
Service operation and third parties
Features that depend on authentication, email, video streaming, object storage, or hosting rely on configured third-party services. Availability, processing time, file limits, and retention can be affected by those providers. The prototype does not represent those external integrations as live until they are configured and tested.
Suspension, termination, and exports
The final terms should explain when access may be suspended, how an account may be closed, what export period applies, and which audit or security records may remain. Administrators should use recoverable archive behaviour before permanent deletion wherever practical.
Warranties, liability, and governing law
No warranty disclaimer, liability cap, indemnity, dispute process, or governing-law clause is asserted in this draft. Those terms depend on the actual operating entity, customer contracts, jurisdiction, insurance, and professional legal review and are therefore a launch blocker rather than something to invent in the interface.