Terms of Service

Acceptance and eligibility

By creating an account or otherwise using Social Relay, you agree to these terms. If you are using the service on behalf of an organization, you are confirming that you have the authority to bind that organization to these terms, and "you" refers to that organization.

You must be able to form a binding contract to use the service, and your use must comply with the terms of the underlying platforms — Instagram, Facebook, and Telegram — as well as any applicable law.

The service

Social Relay connects your Instagram and Facebook accounts to a Telegram forum group. Each conversation on a connected platform becomes its own Telegram topic, and replies posted in that topic are sent back out as direct messages over the platform the conversation started on.

The service depends on Meta's and Telegram's APIs, both of which are outside our control. We do not guarantee uninterrupted availability, and features may change if the underlying platform APIs change, restrict access, or are discontinued.

Acceptable use

You may not use Social Relay for any unlawful purpose, to send spam or unsolicited bulk messages, or in any way that violates Meta's or Telegram's platform terms and policies. You are responsible for the content you send through the service, whether it originates on the connected social platform or in your Telegram group.

We may suspend or terminate access to the service for accounts that we determine, in good faith, are being used to violate this section or to abuse the underlying platform APIs.

Your platform accounts

You may connect only Instagram and Facebook accounts and pages that you are authorized to manage. Connecting an account you do not have authority over is a violation of these terms and likely a violation of the connected platform's own terms.

You are responsible for maintaining the permissions Social Relay needs on the connected platform. If Meta revokes or expires those permissions, message delivery for that account will stop until you reconnect it.

Delivery limitations

Message delivery is best-effort and depends on the availability, rate limits, and behavior of the Meta and Telegram APIs. We retry failed deliveries, but delivery is not guaranteed, and messages may be delayed during platform outages or rate limiting.

Delivery of inbound media and outbound message parts is at-least-once, not exactly-once: in a narrow failure window — for example, if a delivery worker fails after a platform has accepted a message but before that acceptance is recorded — the same message or attachment may be delivered more than once.

Billing

Where billing is enabled for your account, subscriptions are billed in advance on a recurring basis and renew automatically until you cancel. Payment processing is handled entirely by Stripe; we do not store your card details.

You can cancel a subscription at any time from your account's billing portal. Cancelling stops future renewals; it does not automatically entitle you to a refund for the current billing period unless required by applicable law.

Disclaimer and limitation of liability

The Social Relay software is released to the public domain under the CC0-1.0 license and is provided without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement.

To the fullest extent permitted by applicable law, neither the authors of the software nor the operator of a hosted deployment will be liable for any indirect, incidental, special, or consequential damages arising from your use of the service, including delayed, undelivered, or duplicated messages.

Changes to these terms

We may update these terms from time to time, for example to reflect changes in the service or in the platforms it depends on. When we make a material change, we will update the "last updated" date on this page. Continued use of the service after a change takes effect constitutes acceptance of the revised terms.

Contact

Questions about these terms should be directed to the operator of the deployment you are using, through whatever contact channel that operator publishes for support requests.