Terms

Terms of Service

Terms for Tierora’s website, waiting list and B2B service, including workflow responsibilities, customer data, subscriptions, integrations and service limitations.

Draft updated

Draft for review, not an active customer agreement. The proposed commercial provisions require confirmation. The service terms apply only when incorporated into an agreement accepted by stackwiz labs OÜ and the customer; joining the waiting list does not accept a paid subscription.

1. Parties and definitions

Tierora is a product owned and operated by stackwiz labs OÜ, Estonian registry code 17454751, registered at Uus tn 2-11, Ervita 73002 Järva county, Estonia. “Tierora”, “we”, “us” and “our” mean stackwiz labs OÜ as the provider of Tierora. “Customer” means the business or other organisation that enters an agreement for the service. “Authorised User” means a person the Customer permits to use its workspace.

  • “Service” means the Tierora application, APIs and related hosted functionality expressly made available under the applicable agreement.
  • “Order” means an accepted order form, subscription confirmation or other written commercial agreement that identifies the Customer, service scope, fees and subscription period.
  • “Customer Data” includes information, configurations and credentials submitted by or for the Customer, plus customer-specific workflow, approval, delivery and audit records generated through its use of the Service.
  • “DPA” means the Data Processing Agreement covering Tierora’s processing of personal data on the Customer’s behalf. “Third-Party Service” means an external product, system or provider connected or used by the Customer.

2. Scope, acceptance and order of precedence

These terms are intended for business use. A person accepting them for an organisation represents that they have authority to bind that organisation. Individual users must act within the authority their organisation grants them.

A service agreement begins when an authorised Customer and Tierora accept an Order or another agreement that incorporates these terms. Merely browsing this website, submitting an enquiry or choosing a waiting-list plan does not create a paid service agreement.

Mandatory law takes precedence. Binding data-transfer clauses prevail for the transfers they govern; the DPA prevails on personal-data processing; an Order or signed amendment prevails where it expressly varies these terms. These terms otherwise govern the Service. Marketing examples and roadmap statements do not amend an agreement.

The Privacy Notice explains personal-data handling. It does not replace a DPA or make use of the Service conditional on consenting to unrelated marketing or optional website analytics. Cookie choices are managed separately through Cookie preferences; accepting these terms does not give analytics or newsletter consent.

3. Website, enquiries and waiting list

You may use the website to evaluate Tierora, contact us or request future access. Provide accurate information, use an email address you control and do not impersonate another person or submit confidential information you are not authorised to share.

The waiting list is free and records non-binding interest. It does not reserve capacity, guarantee an invitation, establish a launch date, lock in pricing or create an account. If access becomes available, we will explain the applicable offer and terms before you decide whether to join.

Newsletter subscription is separate from an enquiry or waiting-list request. You may withdraw those communication preferences as described in the Privacy Notice. Product screenshots, simulations and workflow examples are illustrative and do not establish that a particular integration or automation is currently available.

4. What Tierora provides

Tierora is designed to coordinate business changes using service context, configurable workflows, approvals, communications, external tools and operational records. The capabilities actually supplied are those identified in the Order and applicable service documentation at the time of onboarding.

The standard Free, Starter, Scale and Business plans are intended to use infrastructure operated and shared by Tierora. Enterprise may include a separately provisioned namespace or runtime where agreed. A namespace does not, by itself, mean a separate database, physical infrastructure or exclusive hosting region; those commitments must be stated in the Order.

Tierora is responsible for operating the agreed Service. The Customer remains responsible for its applications, infrastructure, business decisions and connected systems. Unless expressly included, Tierora does not supply the Customer’s build runners, third-party licences or an outsourced change-approval function.

5. Organisation administration and access

The Customer appoints administrators, authorises users and maintains accurate ownership, membership and contact information. It must review access, remove people who no longer need it, protect credentials and notify Tierora promptly of suspected unauthorised use.

Where customer-managed single sign-on is supported and enabled, the Customer operates its identity provider and controls the identities and claims it supplies. Tierora remains responsible for its agreed authentication and access-handling functions. An external identity provider’s availability and licensing are outside Tierora’s control.

Administrators may configure workflows, recipients, integrations and access that affect other users. The Customer is responsible for lawful instructions and notices to those users. These responsibilities do not release Tierora from its own security or contractual obligations.

6. Workflow instructions and operational decisions

By enabling a workflow or submitting an authorised instruction, the Customer authorises Tierora to perform the supported actions defined by that configuration. Depending on the enabled features, these may request decisions, distribute information, create or update tickets, trigger external jobs and record results.

  • The Customer must review workflows, service dependencies, recipients, approval requirements, field mappings, scheduling rules and integration permissions before operational use.
  • Dependency and risk outputs depend on available context. A missing or outdated service relationship can leave an affected team or system out of the result. Simulation and validation do not prove that a production change is safe.
  • Approval, quorum, notice-period and deadline rules are customer configuration. Emergency paths may omit gates where the Customer permits that; describing a change as urgent does not automatically authorise it under the Customer’s policies.
  • Retries, skips, overrides, cancellation and parallel execution can affect external systems. Pausing or cancelling a Tierora run may not reverse a message, ticket or release already accepted by another system.
  • The Customer must maintain suitable recovery procedures and verify outcomes in the relevant systems. A completed workflow or successful API response is not a guarantee that every downstream business outcome has been achieved.

Tierora must perform the agreed orchestration functions with reasonable care and skill. These allocations of responsibility do not excuse a failure by Tierora to carry out an agreed function.

7. Third-party services and communications

The Customer chooses and authorises connections to its identity, ticketing, CI/CD, communication, observability and other systems. It is responsible for the necessary rights, subscriptions, API access and appropriate permissions.

Enabling a connection authorises the data transfers and actions reasonably necessary for its configured purpose. The Customer must check distribution lists and channel access before sending sensitive information. Tierora cannot recall copies already delivered to an external recipient.

Providers can change APIs, permissions, prices or availability. Tierora will address compatibility issues within the scope of the agreed Service, but does not control a third party’s operation or guarantee its delivery times, data accuracy or uninterrupted access. Tierora remains responsible for its own integration code and instructions to the extent agreed.

Third-party terms apply to the Customer’s use of those services. A provider logo or example does not imply endorsement, partnership or inclusion of that provider’s subscription in Tierora’s fees.

8. Customer Data and permitted processing

The Customer retains its rights in Customer Data. It grants Tierora the limited rights needed to host, copy, transmit and otherwise process that data to supply, secure and support the Service, follow authorised instructions and meet legal obligations.

The Customer is responsible for having the rights and lawful basis to provide its data and instructions. It must avoid including unnecessary personal data or secrets in free-text descriptions, notifications and evidence. Credentials should be supplied only through the designated connection or secret-handling mechanism.

Tierora will not sell Customer Data, use workspace contents for advertising or use them to train general-purpose AI models without a separate express agreement. Customer-specific outputs and records remain Customer Data; Tierora retains its rights in the underlying software, templates and generic record formats.

Special-category personal data, payment-card data and other regulated datasets requiring additional safeguards are outside the standard intended use unless expressly agreed in writing. This restriction does not limit Tierora’s duties if such information is disclosed to it.

9. Data protection and security

Before processing personal data for the Customer, the parties must put an appropriate DPA in place. It must identify the processing, security measures, subprocessor arrangements, assistance obligations, breach procedure, international transfers and return or deletion terms.

Tierora will apply the security measures agreed for the Service and restrict access to Customer Data to authorised purposes. We will notify the Customer without undue delay after becoming aware of a personal data breach affecting data processed on its behalf and cooperate as required by the DPA.

The Customer must assess whether the agreed deployment is suitable for its data and regulatory obligations. Neither the website nor these terms alone establishes a data-residency guarantee, a regulated outsourcing arrangement, certification or a completed security assessment. Additional requirements must be agreed before the relevant use begins.

10. Confidentiality

Each party will protect non-public information received from the other that is marked confidential or should reasonably be understood as confidential. Customer Data, credentials, non-public security information and commercial negotiations are included.

A receiving party may use confidential information only to perform or exercise rights under the agreement and may disclose it only to people or providers who need it and are bound by suitable confidentiality duties. It must use reasonable care, at least equivalent to the care it applies to its own comparable information.

Information is not confidential to the extent the recipient can show it was lawfully known without restriction, independently developed, lawfully obtained from another source, or publicly available without a breach. Legally compelled disclosure is permitted, limited to what is required and with advance notice where lawful.

Confidentiality continues after the agreement ends for as long as the information remains confidential. Personal-data protection and agreed deletion obligations apply independently.

11. Software, website content and feedback

Tierora and its licensors retain the rights in the Service, software, website, designs, documentation and reusable templates. Subject to the agreement, the Customer receives a limited right for its authorised users to use the Service for its business purposes during the agreed term.

You may read and share links to public website content, but may not misrepresent Tierora, remove ownership notices or redistribute substantial content as your own. Third-party marks and open-source components remain subject to their owners’ rights and applicable licences.

Feedback is optional. If you provide product suggestions, Tierora may use them to improve its offerings without payment, provided it does not disclose your confidential information or acquire rights to your Customer Data. We will not use your name or logo as a customer endorsement without permission.

12. Plans, capacity and retention

The Order identifies the selected plan, enabled functionality, service and seat limits, change allowance, workflow capacity, record retention and any agreed support or deployment options. Public pricing is an invitation to discuss or select an offer; the accepted Order records the binding commercial details.

Free carries no subscription fee within its agreed scope. Starter, Scale and Business use the agreed fixed subscription price; Enterprise is priced by contract. Taxes and separately purchased third-party services are additional unless the Order says otherwise.

Limits must be used honestly. The Customer must not create duplicate workspaces or identities to circumvent capacity restrictions. Exceeding an allowance does not, by itself, authorise an undisclosed charge: additional paid capacity or a plan change requires the Customer’s agreement.

Record retention is not a backup or archival guarantee. The Customer should export records it needs beyond the agreed window and assess its own legal retention duties. A downgrade that reduces capacity or retention requires an agreed transition; it must not silently erase records outside the agreed deletion process.

13. Payment, renewal and cancellation

No payment is collected for joining the waiting list. For a paid subscription, the Order specifies currency, price, billing frequency and payment method. Unless the Order states otherwise, monthly subscriptions are charged in advance and renew monthly until cancelled before the next renewal.

The Customer can give cancellation notice through an available account control or by emailing support@tierora.com from an authorised billing contact. Cancellation takes effect at the end of the paid period. Annual commitments, invoice due dates and any agreed minimum term must be stated in the Order; they are not inferred from a monthly price display.

Fees for a period already begun are not refundable solely because the Customer stops using the Service, except where the agreement or mandatory law provides a refund. If Tierora terminates without Customer breach, or the Customer terminates for Tierora’s uncured material breach, unused prepaid fees will be refunded proportionately.

Tierora will give at least 30 days’ written notice of a renewal price increase, which will apply no earlier than the next renewal following that notice. The Customer may decline by cancelling. Agreed fixed-term prices will not increase mid-term unless the Order expressly permits it.

Raise billing disputes promptly with enough detail for investigation. The parties will work in good faith to resolve them. Tierora will not suspend solely for a genuinely disputed amount while the Customer cooperates and pays undisputed amounts.

14. Free plans, trials and early access

Free service and any trial or early-access release remain subject to the applicable access and acceptable-use terms. A Free plan is not a paid subscription and does not automatically convert into one.

Early-access functionality may change, be incomplete or be withdrawn. The invitation or evaluation agreement must identify its permitted use, duration and limitations. Use synthetic or non-production data unless Tierora expressly agrees to the proposed operational use and applicable data-protection arrangements.

Unless expressly agreed, early access has no production availability commitment. A test, prototype or roadmap preview must not be relied on as the sole control for a business-critical change. Confidentiality and data-protection obligations still apply to information received during an evaluation.

15. Availability, support and maintenance

Tierora will use reasonable care and skill to operate the agreed Service. Support hours, response targets, availability commitments, recovery objectives and service credits apply only where included in the Order or an agreed service-level agreement.

The Service may be affected by maintenance, security work, network conditions or third-party dependencies. We will give reasonable advance notice of planned material disruption where practicable and communicate significant incidents affecting the agreed Service.

We may make improvements and security changes, but will not materially reduce the agreed core functionality during a paid committed term without providing an appropriate contractual remedy. Features shown on a roadmap are not delivery commitments unless expressly included in the Order.

16. Acceptable use

You and your authorised users must use the website and Service lawfully and within the agreed scope. In particular, you must not:

  • Access another organisation’s information, bypass authentication or permissions, impersonate someone, or use credentials without authority.
  • Introduce malicious code, interfere with availability, evade rate or capacity controls, or conduct intrusive security testing without prior written authorisation.
  • Use workflows, notifications or public forms to send spam, harass people, distribute unlawful content or perform unauthorised actions in a connected system.
  • Submit data or instructions that infringe another person’s rights or violate applicable privacy, employment, export-control or sanctions requirements.
  • Resell access or operate the Service for unrelated third parties unless that use is agreed. Reverse engineering is restricted except where mandatory law or an applicable open-source licence permits it.

Report suspected vulnerabilities privately to support@tierora.com. Do not include exposed secrets or other people’s data in an initial report; we will arrange a suitable way to receive necessary details.

17. Service assurances and operational limits

Tierora will supply the Service substantially in accordance with the agreed scope and with reasonable care and skill. The Customer must report a material nonconformity with enough information for us to investigate. We will work to correct it; persistent material failures can be addressed under the termination provisions.

We do not promise that the Service is error-free, that every external action occurs exactly once, or that a dependency calculation captures relationships absent from the available data. A delivery record or audit export records available evidence; it does not independently prove the truth of every external event.

Tierora helps implement the Customer’s controls but does not certify compliance, provide legal advice or replace the Customer’s authorised decision-makers. Outside express commitments and non-excludable legal protections, no additional warranty of fitness for a particular regulatory or operational outcome is given.

18. Liability and limits

Nothing in the agreement excludes liability for fraud, wilful misconduct, gross negligence, death or personal injury caused by negligence where protected by law, or any liability that cannot lawfully be limited. Nothing restricts an individual’s statutory data-protection rights.

Subject to those exceptions and any different limits in the Order, each party’s total liability arising from the agreement is limited to the greater of USD 1,000 and the fees paid or payable for the affected Service during the 12 months before the event giving rise to the claim. Related events count together and do not create a new limit for each claim.

Within the same legal limits, neither party is liable for indirect or consequential loss, or lost profit, revenue, business opportunity or anticipated savings. Reasonable direct costs of restoring Customer Data following a breach of the agreement are not excluded merely because the loss involves data; they remain subject to the applicable financial cap.

Undisputed payment obligations are not reduced by the liability cap. Confidentiality, data-protection and intellectual-property claims are subject to the cap unless the Order or mandatory law provides otherwise. Enterprise or higher-risk deployments may require different negotiated limits before service begins.

19. Third-party claims

Tierora will defend the Customer against a third-party claim that the unmodified Service, used as authorised, infringes that party’s copyright, patent or trademark, and pay damages or a settlement we approve, subject to the agreement’s liability limits.

This obligation does not cover claims caused by Customer Data, unauthorised modifications, use outside the agreement, or a combination not supplied or required by Tierora where the claim would not otherwise arise. Tierora may obtain continued use rights, modify or replace the affected functionality, or end the affected Service and refund unused prepaid fees if those options are not reasonably available.

The Customer will similarly defend Tierora against third-party claims arising from Customer Data or instructions that infringe rights or are unlawful, to the extent caused by the Customer’s breach and not by Tierora’s own conduct.

The protected party must give prompt notice, reasonable assistance and control of the defence, without losing protection merely for a delay that causes no prejudice. No settlement may admit fault for, or impose non-monetary obligations on, the protected party without its consent.

20. Suspension and protective action

Tierora may restrict affected access where reasonably necessary to address an active security threat, unlawful activity, material misuse or a binding legal requirement. We will limit the action to what is proportionate, explain it where lawful, and restore access when the reason is resolved.

For remediable misuse or overdue undisputed fees, we will normally give written notice and a reasonable opportunity to resolve the issue before suspension. Immediate action may be necessary where delay risks harm to systems, data or other customers.

Suspension is not an instruction to undo actions already sent to external systems. We will cooperate on safe handling of active workflows and access to records where practicable. Suspension alone does not authorise deletion outside the agreed retention and termination process.

21. Ending the agreement

Either party may end a subscription as permitted by its Order and the cancellation provisions. Either party may terminate for a material breach if the other fails to remedy it within 30 days of written notice describing the breach, or immediately if a material breach cannot be remedied.

A party may also terminate where continued performance would be unlawful, or in connection with the other party’s insolvency to the extent applicable law permits. Tierora may discontinue a Free or evaluation service with reasonable notice where practicable.

On termination, rights to use the affected Service end, accrued payment obligations remain and any applicable unused-fee refund will be made. The parties must coordinate the handling of outstanding runs, credentials and exports; termination cannot recall an external release or message.

Confidentiality, ownership, accrued rights, liability limits, dispute provisions and required data handling survive for as long as their purpose requires.

22. Export, return and deletion

The Order and DPA must identify available export formats, the post-termination retrieval period, assistance and any agreed charges, deletion timing, and backup expiry. Those arrangements must be settled before operational Customer Data is hosted.

At the Customer’s choice, Tierora will return or delete personal data processed on its behalf when the service ends, as required by the DPA and law. Records retained by a legal requirement will be restricted to that purpose. Backup copies remain protected and expire under the agreed schedule.

The Customer is responsible for saving exports it needs and revoking credentials or connections in its own systems. Copies in its ticketing tools, pipelines, notification channels or downloaded audit packages are outside Tierora’s direct deletion control.

These terms do not reduce any mandatory switching, portability or data-retrieval rights. The applicable service agreement must meet those rights where they apply.

23. Changes to terms and notices

Tierora may propose updated terms and will identify their revision date. Material changes affecting an existing Customer require at least 30 days’ notice and will normally apply at renewal, rather than retrospectively changing an accepted Order.

Changes required by law or necessary to address an urgent security issue may need an earlier effective date, with as much notice as practicable. If a material change must apply during a committed term and materially disadvantages the Customer, the parties will agree a resolution or the Customer may end the affected Service with a proportionate refund of unused prepaid fees, unless mandatory law requires otherwise.

Contract notices must be sent to the contacts identified in the Order. General enquiries may be sent to hello@tierora.com; cancellation and support requests may be sent to support@tierora.com. Changing the Privacy Notice does not itself amend the Customer’s DPA or expand permitted processing.

24. Governing law, disputes and general provisions

These Terms are governed by the laws of Estonia. Disputes are subject to the jurisdiction of the courts determined by applicable law, unless the parties validly agree otherwise in an Order. Mandatory rights, including applicable data-protection and data-transfer rights, remain unaffected.

The parties will first try in good faith to resolve a dispute through their designated contacts. This does not prevent urgent protective relief, a complaint to a regulator or action necessary to preserve a legal deadline.

Neither party is liable for a failure caused by events beyond its reasonable control if it takes reasonable steps to limit the impact and informs the other. This does not excuse accrued payment, confidentiality or mandatory data-protection duties. If a material interruption continues, the parties will agree a reasonable exit from the affected Service.

Neither party may assign the agreement without the other’s consent, not to be unreasonably withheld, except to a successor in a merger, reorganisation or sale of substantially all relevant assets that assumes the obligations and can lawfully perform them.

If a provision is unenforceable, the rest remains effective to the extent lawful. A failure to enforce a right is not a waiver. The accepted Order, these terms and incorporated agreements form the complete service agreement; amendments must be agreed in writing or through an expressly authorised acceptance process. Neither party becomes the other’s agent or partner.

Questions about these Terms can be sent to support@tierora.com. For Tierora product enquiries or to discuss an agreement appropriate to your organisation, contact hello@tierora.com. Postal correspondence should be addressed to stackwiz labs OÜ, Uus tn 2-11, Ervita 73002 Järva county, Estonia.

PRIVACY PREFERENCES

Necessary storage

Always active

After you save, we remember this choice on your device for 180 days. It contains no personal identifier and isn't sent to an analytics service.

Google Analytics

Optional. Helps us measure page visits and successful form requests. Google receives browser/device information and pseudonymous cookie identifiers. We exclude form contents, query strings and confirmation pages. Analytics cookies last up to 180 days.

How Google uses this information ↗

Advertising

Not used

We don't use advertising cookies, Google Signals or personalised advertising.

Reopen these settings anytime using “Cookie preferences” in the footer.