Terms of Service

These Terms of Service (the Terms) are an agreement between two parties. The first party is the customer that accepts them (Customer or you). The second party is Mikheit AB (PayloadRelay, we, or us). Mikheit AB is a Swedish limited liability company with organisation number 559548-6225, registered address Köpmangatan 63, 972 34 LULEÅ, and registered office in Luleå.

PayloadRelay offers the Service only for business use and professional use. PayloadRelay does not offer the Service to a consumer, or for a mainly private purpose. When you create an account, accept an invitation, or use the Service, you confirm three facts:

• You are at least 18 years old.
• You act in the course of a trade, a business, a craft, or a profession.
• You have the authority to bind the organisation that you represent.

If you do not meet these requirements, or if you do not agree to these Terms, do not use the Service.

PayloadRelay is an event-relay service. It receives a webhook event, an HTTP event, a form event, an API event, or an email event. It then delivers that event to the configured destinations. A destination can be an HTTP webhook, email, Slack, Discord, Google Sheets, Microsoft Teams, PagerDuty, or Telegram. The features can include validation, authentication, filtering, transformation, templates, retry policies, failover, response forwarding, and activity monitoring that holds metadata only.

Email ingestion usually converts an inbound message into structured JSON. If you select the body-as-payload mode, PayloadRelay uses the configured JSON, XML, or plain-text body instead.

Before a paid subscription starts, an authorised administrator of the organization can review the plan, the billing interval, the recurring price, the tax treatment, and each displayed resource impact. That administrator can also go back and correct the selection. A paid subscription starts only after Stripe confirms a successful payment and PayloadRelay activates the plan. The parties conclude a contract in English. You can save or reproduce these Terms and the incorporated legal documents from their permanent version links.

You must give accurate account information, and you must protect the account credentials. If you suspect unauthorised access, you must tell us immediately. You are responsible for the activity that occurs through your account. You are also responsible for the correct roles and the correct access in your organization.

A new organization from the standard signup flow starts with a 14-day Team trial, and that trial needs no payment card. A user who joins by invitation joins the inviting organization on its existing plan, and that user gets no separate trial. If a trial ends without a paid subscription, the organization moves to Sandbox. “Personal workspace” is a product label for a professional organization that has one user. That label does not permit consumer use or private use.

The members of an organization share the configured resources, the activity metadata, and the plan quotas. The owner role, the admin role, the user role, and the viewer role control what each member can do. An owner or an admin can invite a member. An authorised user of an organization can read the configuration of that organization and its activity information.

PayloadRelay prices and charges the paid plans in United States dollars (USD). A displayed price excludes sales tax, VAT, and a similar charge, unless the price states otherwise. Stripe calculates the applicable tax from the billing information that you give.

• A subscription renews automatically for the selected monthly term or annual term until you cancel it.
• You authorise PayloadRelay and Stripe to charge the recurring fees, the taxes, and a confirmed prorated upgrade to the selected payment method.
• A change to a higher tier, and a change from monthly to annual, takes effect after you confirm the displayed proration and Stripe confirms the payment.
• A downgrade, and a change from annual to monthly, takes effect at the next renewal. PayloadRelay can then disable the resources above the new limits.
• A cancellation stops the next renewal. The paid features stay available through the current paid term. The organization then moves to Sandbox.
• The fees are non-refundable by default, and this includes unused time. A refund occurs only when the law requires it, or when PayloadRelay expressly approves it.

An ordinary past-due subscription usually gets a payment-recovery period of seven days. If the subscription stays unpaid after that period, the organization becomes read-only and PayloadRelay blocks the relay ingestion. If Stripe reports a terminal status such as unpaid, cancelled, or incomplete-expired, the access can end sooner and the organization can move to Sandbox. The Billing page holds the cancellation controls and the recovery controls. The billing portal of Stripe holds the payment-method controls, the tax controls, and the invoice controls.

The limits that PayloadRelay shows for the selected plan apply to the Service. The plans are Sandbox, Team trial, Solo, Team, Scale, and custom. A limit can apply to the accepted events, the active endpoints, the enabled destinations, the members of the organization, the payload size, the retries, the retry policies, and other features of the plan. The applicable order or a separate agreement governs the limits of a custom plan.

• One accepted webhook event or email event counts one time against the monthly quota. Destination fan-out and delivery retries use no more accepted-event quota.
• The calendar-month usage usually resets at 00:00 UTC on the first day of each month. A move to Sandbox can start a new Sandbox usage period immediately.
• The payload size limit is 256 KB on Sandbox and Solo, 512 KB on the Team trial and Team, and 1 MB on Scale. A custom agreement can state a different limit.
• PayloadRelay rejects an event above the accepted-event quota until the next reset or a qualifying upgrade. When a new plan takes effect, PayloadRelay can disable the resources above the limits of that plan.

You are responsible for your events, your configurations, your recipients, your destinations, your instructions, your legal notices, your permissions, and your use of the Service. You must hold all the rights and all the lawful grounds that you need. These let you give Customer Data to PayloadRelay, and they let you instruct the delivery of that data to each configured destination.

You must not use the Service to do any of the following:

• Violate the law, a third-party right, a contractual restriction, or a data-protection obligation.
• Send malware, harmful code, unlawful content, spam, or a deceptive communication.
• Probe, bypass, disable, or interfere with the security, the rate limits, the tenant isolation, or the availability.
• Access the account or the data of another customer without authorisation.
• Resell the Service to a third party, or give the Service to a third party, unless an order or a separate agreement permits it.
• Use the Service in a way that creates an unreasonable technical risk, legal risk, or security risk.

Between the parties, Customer keeps its rights in the data that it submits to the Service or transmits through the Service (Customer Data). Customer gives PayloadRelay a limited right to process Customer Data. PayloadRelay can use that right only to supply, secure, and support the Service, to obey the lawful obligations that relate to the Service, and to carry out the documented instructions of Customer.

The Data Processing Addendum applies when PayloadRelay processes personal data for Customer. The Privacy Notice explains how PayloadRelay acts as the controller of the account data, the billing data, the security data, the website data, and the business-contact data. Customer acknowledges the Privacy Notice as a notice. Customer does not accept it as a contract. Use of the Service is not consent to the processing.

PayloadRelay does not store a customer relay request body or a customer message body in its databases, activity logs, object storage, application logs, traces, metrics, files, caches, or backups. A body stays only in process memory, and in the trusted MTA queues and the RabbitMQ queues for delivery, retry, and dead letters. It stays there only while PayloadRelay delivers the event. If the delivery fails permanently, the message stays in a dead-letter queue for a maximum of 7 days. This period lets the parties diagnose the failure, and it lets Customer instruct a new delivery. The broker then discards the message.

PayloadRelay can keep operational metadata in the 30-day Activity trail. That metadata includes SMTP envelope sender addresses, originating IP addresses, HTTP methods, identifiers, timestamps, and delivery outcomes. A stored endpoint template and a stored destination configuration are not received relay-event bodies.

Delivery is asynchronous and at least one time. An acceptance response means that PayloadRelay accepted the event for processing. It does not mean that every destination completed the delivery. Retries, failover, a network failure, and an ambiguous remote response can each cause a duplicate delivery. Stable event keys and an idempotent receiver prevent the effect of a duplicate. If PayloadRelay reports a temporary ingestion failure, the sender must send the original event again.

PayloadRelay uses reasonable technical safeguards and organisational safeguards. These include access controls, tenant isolation, transport protection, and protection of the sensitive configuration at rest. No system is completely secure or continuously available. PayloadRelay supplies the Service without a guarantee of uptime or response time, unless a separate written service-level agreement applies. The Service can be unavailable during maintenance or a deployment. It can also be unavailable because of a third-party failure, or an event outside our reasonable control.

The Service depends on third parties and integrates with them. These include Stripe, identity providers, infrastructure providers, email delivery services, and the destinations that Customer configures. A destination that Customer directs receives data on the instruction of Customer. The relationship between Customer and that provider governs the destination. PayloadRelay is not responsible for the availability, the security, or the retention of a third party, or for its acts after a delivery. A change at a third party can force us to modify an integration or to stop it.

We can limit the access or suspend it when this is reasonably necessary. The reasons are a security threat, unlawful or abusive use, a material breach, non-payment, a third-party or infrastructure requirement, and a risk to the Service or to others. We will give notice when this is reasonably practicable. A serious or urgent circumstance can need immediate action. We will limit the scope and the duration where this is reasonably possible.

Either party can terminate a free account. To do this, that party stops the use of the Service and completes the available account-deletion process. Section 4 governs the cancellation of a paid subscription. PayloadRelay can terminate these Terms for a material breach that the other party does not cure, after reasonable notice. PayloadRelay can terminate these Terms immediately for a serious security violation, a fraud, an abuse, or a legal violation.

You can schedule the deletion of your account in Settings. PayloadRelay disables the access immediately. An emailed single-use link usually permits recovery for 30 days before the permanent deletion.

The owner of an organization must transfer the ownership before that owner deletes only their own account. As an alternative, the owner can close the organization. A closure of an organization cancels the active paid subscriptions immediately, and it gives no automatic refund. Recovery returns the organization on Sandbox, and it does not restore the previous subscription. New paid billing stays unavailable while the billing cleanup for the account closure retries.

Limited records can stay for accounting, fraud prevention, deletion integrity, backup rotation, or another legal obligation. The Privacy Notice and the DPA describe these records.

PayloadRelay and its licensors keep all the rights in the Service, the software, the documentation, the branding, and the related materials. These Terms give Customer a limited right to use the Service for its internal business purposes during the term of the agreement. That right is non-exclusive and non-transferable. These Terms grant no other right.

If Customer gives a suggestion or feedback voluntarily, PayloadRelay can use it without a restriction and without a payment. We will not identify Customer as the source without permission.

Each party must protect the non-public information of the other party with reasonable care at least. Each party must use that information only to supply the Service or to receive it. This duty does not cover information that is public without a breach, that is already lawfully known, that the party developed independently, or that the party received lawfully without a restriction. A party can disclose confidential information when the law requires this, and that party must first give notice where the law permits notice. Customer Data is the confidential information of Customer.

Each party warrants that it has the authority to enter into these Terms. Customer warrants that its Customer Data, its instructions, its destinations, and its use obey Section 6. To the maximum extent that the law permits, PayloadRelay otherwise supplies the Service “as is” and “as available.” PayloadRelay disclaims the implied warranties of merchantability, of fitness for a particular purpose, and of non-infringement. PayloadRelay also disclaims a warranty that the delivery will be continuous, that it will have no error, or that every destination will accept it.

To the maximum extent that the law permits, neither party is liable for an indirect, incidental, special, punitive, or consequential loss that arises from these Terms or the Service. Neither party is liable for a loss of profit, revenue, goodwill, anticipated savings, business opportunity, or data that arises from these Terms or the Service. This exclusion applies even when someone told the party that the loss was possible.

The total aggregate liability of each party that arises from these Terms and the Service has a limit. That limit is the greater of USD 100 and the fees paid or payable by Customer to PayloadRelay during the 12 months immediately before the event that gave rise to the claim. The exclusions and the cap do not apply to a payment obligation, a fraud, intentional misconduct, or gross negligence. They also do not apply to a liability that the applicable law does not permit a party to exclude or to limit. They do not restrict the statutory rights of a data subject or the powers of a regulator under data-protection law.

Customer will defend PayloadRelay against a third-party claim, and Customer will indemnify PayloadRelay for the damages and the reasonable costs. This applies to a claim that arises from Customer Data, from an unlawful or unauthorised instruction or destination of Customer, from an infringement that material from Customer caused, or from a material breach of Section 6 by Customer. PayloadRelay must notify Customer immediately, cooperate reasonably at the expense of Customer, and let Customer control the defence and the settlement. A settlement must not admit fault, and it must not put a non-monetary obligation on PayloadRelay, without the consent of PayloadRelay.

We can change the Service as it develops. During the current paid term of a paid plan, we will not materially reduce its core functionality without a reasonable operational, legal, or security reason.

We will give notice of a material change to these Terms at least 30 days before it takes effect. We will give that notice by email or through the Service, and we will state the effective date. If Customer does not agree, Customer can cancel before that date. A change can take effect sooner, with as much notice as is reasonably practicable, when the law requires the change, when the change addresses an urgent security or abuse risk, or when the change is only beneficial. Continued use after the effective date is acceptance in a business relationship.

These Terms and the non-contractual obligations that arise from them are governed by Swedish law. The conflict-of-law rules do not apply. The United Nations Convention on Contracts for the International Sale of Goods does not apply. The courts of Sweden have exclusive jurisdiction. Stockholm District Court (Stockholms tingsrätt) is the court of first instance.

These Terms, the DPA, the applicable plan or order, and each expressly incorporated document are the complete agreement about the Service. Where a signed order or a separate agreement conflicts directly with these Terms, that order or agreement controls. For the processing of personal data for Customer, the DPA controls. A failure to enforce a term is not a waiver. An invalid term will be limited to the minimum that is necessary, and the other terms continue.

Customer cannot assign these Terms without our previous written consent. Customer can assign them with a merger, or with a sale of substantially all the relevant assets. PayloadRelay can assign them with a reorganisation or a business transfer. Neither party is liable for a delay that an event beyond its reasonable control caused. This exception does not apply to a payment obligation.