Terms of Service

This is an agreement between you and Amirhossein Yaghoubnezhad (“we”), an independent developer. By signing in to the dashboard, calling the API, or embedding the widget, you accept these terms. If you are agreeing on behalf of a company, you confirm you may bind it.

Concretely, the product is three parts:

• A widget — a custom element you place on your own pages, which renders inside Shadow DOM and collects a category, a message, and a way to reach the person writing in.
• An API that receives those tickets, stores them, and relays them onward.
• A dashboard where you read threads, reply, change a ticket’s status, manage categories and auto-replies, and grant colleagues access.

The full attribute surface and API reference are in the documentation. Features not described there are not part of the service.

You sign in with Google or with Telegram. A deployment may restrict which accounts are allowed to sign in, so being able to authenticate with a provider does not by itself entitle you to an account here.

A platform belongs to the account that created it. That owner may grant other accounts access to it, and each grant carries its own permissions:

Two powers are never delegable and stay with the owner: deleting the platform itself, and rotating its API key. You are responsible for who you grant access to and for what they then do.

Keep your session secure. Your dashboard session is a bearer token held in your browser; anyone with it can act as you until it expires.

Each platform has an API key. That key identifies the platform, not the person writing in — it is published in the HTML of any page you embed the widget on, and it is meant to be. It is not a secret and must never be treated as one, or reused as a credential anywhere else.

Anyone who copies your key can therefore file tickets against your platform. If that becomes a problem, rotate the key from the dashboard — which immediately breaks every existing embed until you paste the new snippet.

The widget bundle is served with a permissive cross-origin header so it can load on your site, and the public ticket endpoints accept requests from any origin. That is a deliberate design requirement of an embeddable widget, not an oversight.

You agree not to:

• Use the widget to collect payment card numbers, government identifiers, health records or other sensitive categories of data. It is a plain-text message box with no field-level protection, and conversations are relayed to Telegram.
• Embed the widget on a site whose purpose is unlawful, or use it to transmit malware, spam or harassment.
• Use another platform’s API key, or attempt to read tickets belonging to a platform you have not been granted access to.
• Automate ticket creation to load-test, flood or otherwise degrade the service for others.
• Represent the service as your own product, or remove attribution where it is displayed.

Bulk operations in the dashboard act on at most 200 conversations per request. Do not work around that limit programmatically.

Content submitted through your widget is yours. We process it to operate the service on your behalf — the Privacy Policy sets out exactly what that means.

Because your visitors are giving personal data to you, you are responsible for telling them so: your own privacy notice must cover the support widget, and you must have a lawful basis for the messages and contact details it collects. If your users are in the EU, EEA or UK, you are the controller and we act on your instructions.

Deletion is irreversible by design. A deleted conversation, and every platform deletion, destroys the underlying records — there is no recycle bin and no undo. Keep your own export if you need one.

Telegram delivery and Telegram sign-in are provided by Telegram, not by us. Their availability, rate limits and policies are outside our control, and a message can fail to arrive for reasons we cannot fix — most commonly because a user has never opened a chat with the bot, which Telegram requires before any bot may message them.

A ticket is always recorded in the database and visible in the dashboard regardless of whether its Telegram copy succeeded. Do not rely on Telegram delivery as your only notification path.

The service commitment for this deployment, if any, is provided on a best-effort basis without guaranteed uptime. Absent such a commitment, the service is provided on a reasonable-efforts basis with no guaranteed uptime.

We may change or remove features. Where a change would break existing embeds — a removed widget attribute, for instance — we will document it in the documentation.

Pricing, billing cycles, taxes and refunds for this deployment are currently provided free of charge, with future pricing subject to change with notice. No payment processing is implemented in the service itself.

You may stop using the service at any time by removing the widget from your site and deleting your platforms. We may suspend or terminate access for a material breach of these terms, or where continued operation would be unlawful.

On termination, your platforms and their tickets may be deleted. Export anything you need first.

The service is provided “as is” and “as available”, without warranties of any kind, whether express or implied, including merchantability, fitness for a particular purpose and non-infringement. We do not warrant that the service will be uninterrupted, that every Telegram message will be delivered, or that it is free of defects.

Nothing here excludes liability that cannot lawfully be excluded, and statutory consumer rights are unaffected.

To the fullest extent permitted by law, we are not liable for indirect, incidental, special or consequential damages, nor for lost profits, lost revenue, or lost or corrupted data — including data destroyed by a deletion you or one of your admins performed.

The cap on our aggregate liability is $100 USD or the amount you paid in the last 12 months, whichever is greater.

These terms are governed by the laws of the developer’s primary jurisdiction, and disputes are subject to the exclusive jurisdiction of the competent courts in the developer’s jurisdiction, without prejudice to any mandatory protections of your country of residence.

Questions about these terms: info@frix.me.