Closed beta agreement.

This is the form of agreement. A signed copy names the customer, the agreement date, and any fees, which are shown below in square brackets. To request access and a signed copy, write to support@roadcase.tools.

This agreement is between Technically Creative LLC, a Michigan LLC (“Provider”), and [Customer legal name] (“Customer”), effective [agreement date].

Provider operates RoadCase, a logistics platform for touring and live events, currently in closed beta. Customer wants to use it for real productions during the beta. This agreement sets the deal for that period. The RoadCase terms of service apply. Where this signed agreement conflicts with them, this agreement wins.

Provider grants Customer access to RoadCase for Customer’s internal logistics operations during the beta term. Access covers the crew members and administrators Customer enrolls. The service is under active development: features may change, and Provider may need maintenance windows without notice.

[Fees]. If left blank, no fees are payable during the beta term.

The service is provided as is, with no uptime, support, or response-time commitment. Provider will make reasonable efforts to keep the service running and to warn Customer of planned disruption, but Customer should plan productions so that a RoadCase outage is survivable. Printed manifests and truck signs are part of the product for this reason.

• Customer owns the data it puts in: cases, items, trucks, manifests, photos, scan history, and its crew’s profile data.
• Provider processes crew personal data on Customer’s behalf and on its instructions, as described in the privacy policy and its retention schedule.
• Hosting is in the United States. Current providers, including Supabase (AWS us-east-2) and Vercel, are listed on the subprocessor list. Provider will notify Customer before adding a subprocessor.
• Backups: database backups are daily on a rolling seven-day window, and weekly encrypted backups of uploaded files are being put in place. Point-in-time recovery is not enabled.
• Scan and audit records are append-only by design and are retained indefinitely as the integrity ledger. Erasure of a person’s identity is handled by pseudonymization, as described in the privacy policy.
• Provider will notify Customer without undue delay of a personal data breach affecting Customer’s data.
• Customer is responsible for having the right to enroll its crew and for instructing crews not to photograph people when photographing equipment.

Provider does not enroll crew in the European Union or the United Kingdom. If Customer is subject to the EU or UK GDPR and needs to enroll crew there, the parties will execute a data processing agreement before that crew is enrolled.

Each party will keep the other’s non-public information confidential and use it only for this agreement. This covers Customer’s logistics data and Provider’s product plans and pricing. Standard exceptions apply: information that is public, independently developed, already known, or required to be disclosed by law (with notice where lawful). This obligation survives termination by 3 years.

Customer’s feedback about the service may be used by Provider to improve the product, without obligation or attribution. Feedback does not include Customer’s data.

Sections 05 (beta status, no warranty) and 06 (limitation of liability) of the terms of service apply in full. In short: the service is provided as is, all implied warranties are disclaimed to the maximum extent the law allows, and rights that cannot lawfully be excluded are not excluded.

To the maximum extent permitted by law, each party’s total aggregate liability under this agreement is capped at the fees Customer paid in the 12 months before the event giving rise to liability, or USD 100 if no fees were paid. Neither party is liable for indirect or consequential loss, lost profits, or lost data. These limits do not apply to breach of section 05 (confidentiality), to liability that cannot be limited by law, or to Customer’s violation of the acceptable use terms.

This agreement runs until the earlier of: the end of the beta program, termination by either party on 14 days written notice, or immediate termination by Provider for breach or security risk. Provider will give Customer reasonable notice before the beta program ends and an offer of onward terms if the product continues.

For 30 days after termination, Provider will on request make Customer’s data available in a machine-readable format: structured export of cases, items, trucks, scan history, and photos. After the export window, Provider may delete or pseudonymize Customer’s data, except the records retained per the retention schedule.

Governing law: the State of Michigan, United States. Neither party may assign without the other’s consent, except to a successor of the business. This agreement plus the referenced documents is the entire agreement for the beta. Amendments must be in writing and signed.