Terms and Conditions

1. Scope, agreement, and contract order #

These Terms and Conditions (the Terms) govern access to and use of this Timeline installation and its enabled modules, public links, websites, APIs, and related services (together, the Service). Operator means the legal person identified in the operator card above. Customer means the organization or person that obtained, licensed, hosts, or administers the Service. User means anyone who accesses the Service through an account, API credential, invitation, public link, or other authorized route.

A signed order form, licence schedule, deployment agreement, service-level agreement, data-processing agreement, or other written contract may add to these Terms. If documents conflict, the signed agreement controls for its subject matter, followed by these Terms, then product documentation. Mandatory rights under applicable law always prevail. Merely making these Terms available does not replace any separate consent, pre-contract information, or signed agreement required by law.

If you use the Service for an organization, you confirm that you are authorized to act for it. If you do not agree, do not use the Service and contact the Operator or your organization administrator.

2. What Timeline provides #

Timeline is a modular Rails-based platform for organizational records and collaboration. Depending on the licence, configuration, deployment profile, and administrator choices, it may include timelines and spaces, attachments, comments, notifications, chat and calls, file exchange, documentation, websites and public forms, reservations, garage operations, calendars, automation, APIs and webhooks, AI-assisted tools, security and infrastructure controls, licensing, customer-VM management, backups, and audit records.

Only features enabled for the relevant installation are included. Screenshots, roadmaps, demonstrations, documentation, beta labels, and references to disabled or separately licensed modules do not promise that those features are available under a particular order. The Operator must identify material technical requirements, interoperability limits, geographic restrictions, and separately configured providers before a consumer contract is concluded where law requires that information.

3. Accounts, administrators, and authority #

Users must have legal capacity to use the Service and must provide accurate account information. Accounts are personal unless the Operator expressly provides a service account. Users must protect passwords, recovery methods, API keys, access tokens, public-link secrets, and connected-provider credentials; use multi-factor authentication where available; and notify the Operator promptly of suspected compromise.

Customer administrators control users, groups, permissions, modules, retention, integrations, public exposure, and customer-managed infrastructure. The Customer is responsible for granting only necessary access, reviewing privileged activity, promptly removing access that is no longer required, and ensuring that its administrators and invited Users are authorized.

4. Acceptable use #

You must use the Service lawfully and only within your authorization. You must not:

• access another account, organization, project, server, vehicle file, booking, customer record, or public-link scope without permission;
• upload or distribute malware, exploit code, unlawful content, deceptive material, infringing material, or data you have no right to process;
• interfere with availability, bypass security or licence controls, probe systems without authorization, overload the Service, or use automated access outside documented limits;
• misuse chat, notifications, forms, public websites, file shares, email, SMS, webhooks, or integrations for spam, harassment, fraud, surveillance, or impersonation;
• use the Service to make unlawful vehicle modifications, defeat safety or emissions obligations, falsify service or financial records, or conceal legally required information; or
• represent AI output, generated documents, status indicators, estimates, availability, diagnostics, or automation results as professionally verified when they have not been reviewed by an appropriately qualified person.

Security research requires the Operator's prior written authorization and an agreed scope. The Service is not designed as an emergency, medical, life-support, or other safety-critical system.

5. Customer content and instructions #

As between the parties, the Customer and Users retain their rights in content they submit or create, including text, files, images, messages, website content, reservations, vehicle and workshop records, documents, configuration, and structured data (Customer Content). They grant the Operator and its contracted processors only the rights reasonably necessary to host, secure, back up, transform, transmit, display, support, and otherwise provide the Service as instructed and permitted by the applicable agreement.

The Customer is responsible for the legality, accuracy, quality, notices, permissions, intellectual-property rights, and retention instructions for Customer Content. The Operator may restrict or remove content where reasonably necessary to comply with law, protect people or systems, enforce these Terms, or respond to a valid rights complaint, while providing notice where lawful and practicable.

6. Public links, websites, forms, and communications #

Timeline can expose selected information through public websites, contact and booking forms, calendars, file-transfer links, upload requests, customer portals, estimates, invoices, and other tokenized links. The Customer chooses what to publish, who receives a link, and how long access remains available. The Customer must verify recipients, avoid placing unnecessary personal or confidential data in public content, rotate or revoke compromised links, and provide all legally required business, privacy, cookie, marketing, booking, and consumer information for its own public-facing activities.

A public-link token is a credential. Anyone who obtains it may be able to use the access it grants until it expires or is revoked. The Operator does not become a party to bookings, repairs, estimates, invoices, sales, or other transactions between the Customer and its own clients merely because Timeline provides the workflow.

7. AI-assisted and automated features #

AI and automation features assist with drafting, translation, classification, extraction, review, planning, summaries, and operational workflows. Output can be incomplete, inaccurate, outdated, biased, or unsuitable. It is advisory unless a signed agreement expressly states otherwise. Users must review output, source evidence, permissions, destination, and real-world consequences before applying, publishing, sending, deploying, or relying on it.

The configured AI provider and access policy determine what data leaves the installation. Customer administrators are responsible for selecting providers, reviewing provider terms and data handling, limiting sensitive inputs, obtaining any required authorization, and deciding which Users may use AI. Timeline's guarded proposal flows do not grant an AI provider shell, repository, publication, or deployment authority unless a separate, explicit, permission-checked workflow provides it.

AI features are not legal, medical, financial, safety, emissions-compliance, cybersecurity, or professional engineering advice. Qualified human review remains required for decisions in those areas.

8. Third-party services and integrations #

The Service may interoperate with providers selected by the Customer or Operator, including identity providers, LDAP, SMTP, SMS, push, chat webhooks, object storage, WebDAV, Git services, DNS and proxy managers, certificate authorities, calendar platforms, communications systems, AI providers, and infrastructure tools. Third-party services are governed by their own terms, privacy notices, availability, and charges. Timeline does not control them and is not responsible for their independent acts or omissions.

The Customer must have authority to connect each provider, protect credentials, configure minimum permissions, and comply with provider rules. Disabling an integration may reduce functionality. References to third-party names do not imply endorsement or partnership.

9. Security, deployment, and backups #

The Operator will apply the security commitments stated in the applicable agreement and will use reasonable measures appropriate to the Service and deployment model. No internet-connected system is completely secure or continuously available.

For a Customer-controlled or self-hosted installation, the Customer is responsible for the host, operating system, network, DNS, TLS, firewall, database, Redis, storage, backups, monitoring, physical security, administrator access, secrets, third-party services, and timely installation of supported updates unless a written managed-service agreement assigns a responsibility to the Operator. A green dashboard or health check does not replace tested backups, restoration exercises, security review, or professional administration.

Users must cooperate reasonably with security and fault investigation through the least intrusive available means. They must not send secrets through ordinary support messages and must follow the Operator's secure support channel.

10. Software, licences, and intellectual property #

The Service, its non-Customer content, branding, product design, documentation, and proprietary components are owned by or licensed to the Operator or relevant rights holder. Subject to payment and the applicable licence, the Customer receives a limited, non-exclusive, non-transferable right to use the enabled software and modules for the agreed term and scope.

Except where a licence or non-waivable law permits it, Users must not copy proprietary components, remove notices, sell or sublicense access, circumvent module or instance limits, or reverse engineer the Service. Open-source and third-party components remain subject to their own licences. Customer branding and imported assets remain the Customer's responsibility; exact third-party logos, text, images, or designs may be used only where the Customer has the necessary rights.

11. Fees, taxes, renewals, and orders #

Fees, currencies, taxes, billing periods, usage limits, renewals, and cancellation terms are stated in the order or other signed agreement. The Service does not impose a charge that was not disclosed through the applicable purchasing process. Unless law or the order states otherwise, fees for a current billing period are non-refundable after supply, except where a failure to supply, lack of conformity, withdrawal right, or other mandatory remedy applies.

A Customer must keep billing and contact information current. The Operator may suspend paid features for overdue undisputed amounts after reasonable notice and an opportunity to cure, except where immediate action is lawful and reasonably necessary.

12. Availability, maintenance, updates, and changes #

The Operator may maintain, secure, repair, update, or modify the Service. Planned maintenance and material adverse changes will be communicated as stated in the applicable agreement or, where no method is specified, through a reasonable in-product or direct notice. The Operator will not use these Terms to remove mandatory rights or retrospectively change an already accrued payment or remedy.

For consumers entitled to digital-content or digital-service conformity rights, the Operator or contracting trader remains responsible for supply, conformity, required updates, and remedies to the extent required by applicable law. Nothing in these Terms converts recurring or material outages into acceptable performance where mandatory law or a service-level agreement says otherwise.

Preview, beta, experimental, community, and third-party-dependent features may change or be withdrawn. Their limitations must be identified clearly before reliance where they materially differ from what a User may reasonably expect.

13. Suspension and termination #

The Operator may restrict or suspend access where reasonably necessary to address a security threat, unlawful use, material breach, licence expiry, overdue undisputed payment, legal requirement, or risk to other users or systems. Except for urgent security, fraud, or legal situations, the Operator will provide reasonable notice and an opportunity to cure where appropriate.

The Customer may stop using the Service and may terminate as provided in its order and mandatory law. On termination, access and licences end. Data export, return, retention, deletion, backup expiry, and transition assistance follow the applicable agreement, configured retention, and legal obligations. The Customer should export required content before access ends. The Operator will not withhold a consumer's legally retrievable content or remedies where applicable law prohibits doing so.

Terms that by their nature should survive—including payment obligations already due, confidentiality, intellectual property, liability limits, dispute terms, and lawful retention—continue after termination.

14. Privacy and data protection #

These Terms are not a privacy notice or data-processing agreement. The Operator and Customer may act as controller, joint controller, processor, or independent controller for different activities and deployments. Their roles, instructions, subprocessors, international transfers, security measures, retention, and data-subject assistance must be documented where data-protection law requires it.

The Customer must provide its Users, guests, clients, employees, and public-form visitors with an accurate privacy notice identifying the controller, contact details, purposes, legal bases, recipients, retention, transfers, and rights. Users may exercise privacy rights through the controller identified in the relevant privacy notice. Account, security, audit, licensing, support, and operational records may be retained where necessary for security, contract performance, legal compliance, or legitimate claims, subject to applicable law.

15. Confidentiality #

Each party must protect the other's non-public business, technical, security, and personal information with reasonable care and use it only for the Service and the applicable agreement. Confidentiality does not cover information lawfully public, already known without duty, independently developed, or lawfully received from another source. A legally compelled disclosure is permitted; advance notice will be given where lawful.

16. Warranties and mandatory rights #

The Operator warrants only what is stated in the applicable agreement and what cannot lawfully be excluded. Business Customers are responsible for deciding whether the Service, deployment, configuration, outputs, and integrations meet their requirements. Documentation and advisory output do not guarantee a particular legal, commercial, security, vehicle, booking, or operational result.

Nothing in these Terms excludes or limits a consumer's rights to clear pre-contract information, supply, conformity, required updates, repair or correction, price reduction, termination, refund, content retrieval, data protection, or any other mandatory remedy. Any disclaimer applies only to the extent permitted by law.

17. Liability #

Nothing in these Terms limits liability that cannot lawfully be limited, including liability for fraud, fraudulent misrepresentation, or death or personal injury caused by negligence where applicable.

For a Business Customer, and to the extent permitted by law, neither party is liable for indirect or consequential loss or for lost profit, revenue, anticipated savings, goodwill, or business opportunity. The Operator's aggregate contractual liability for the event and related events is limited to the fees paid or payable for the affected Service during the twelve months before the event, unless the signed agreement states a different fair allocation. These business limitations do not apply to the Customer's payment obligations, infringement or misuse of the other party's intellectual property, breach of confidentiality, or liability that law does not permit the parties to limit.

For consumers, liability is not limited below the remedies and compensation available under mandatory law. Each party must take reasonable steps to reduce avoidable loss.

18. Business-customer responsibility for third-party claims #

A Business Customer will defend and indemnify the Operator against a third-party claim to the extent caused by the Customer's unlawful Customer Content, unauthorized instructions, infringement, or material breach of the acceptable-use rules, but only where the Operator gives prompt notice, permits reasonable control of the defence, and cooperates. This clause does not apply to the extent a claim was caused by the Operator, and it does not apply to consumers.

19. Changes to these Terms #

The current version and effective date appear above. The Operator may update these Terms prospectively for legal, security, operational, or product reasons. Material changes will receive reasonable advance notice through the agreed channel. Where mandatory law gives a User or Customer a right to reject a material change or terminate without charge, that right remains available. Continued use after the effective date has contractual effect only where applicable law and the parties' agreement permit it.

The downloadable text copy is provided so the Terms can be stored and reproduced. The canonical version is the published Terms record in this Timeline installation at the time the relevant agreement or accepted update took effect.

20. Governing law and disputes #

The configured governing law shown above applies, subject to the signed agreement and mandatory rules. A consumer retains the protection of mandatory law and courts that cannot validly be displaced in the consumer's country of residence.

Before starting formal proceedings, contact the Operator using the details above and allow a reasonable opportunity to investigate and resolve the issue. Nothing in these Terms prevents urgent court relief, a complaint to a competent regulator, use of an available consumer dispute-resolution process, or exercise of a non-waivable right.

21. General provisions #

Neither party is liable for delay caused by events beyond its reasonable control, provided it takes reasonable steps to reduce the impact; this does not excuse payment already due or mandatory digital-service remedies. Neither party may assign the agreement in a way that materially reduces the other party's rights without any consent required by law or the signed agreement. If a provision is unenforceable, it will be limited only as necessary and the rest remains effective. A failure to enforce once is not a waiver. Headings aid reading and do not change meaning.

22. Contact #

Questions, complaints, termination notices, rights requests, and legal notices should be sent to the Operator using the identity and contact details shown above. Security incidents should use the Operator's designated secure reporting channel rather than ordinary public forms.