Terms of Service

These Terms of Service (“Terms”) govern your access to and use of Ray, a notification and messaging API and dashboard (the “Service”), operated by L’Atelier Gege LLC, a limited liability company registered in Mongolia (“Ray”, “we”, “us”). By creating an account or using the Service, you agree to these Terms. If you use the Service on behalf of an organization, you confirm you are authorized to accept these Terms for it, and “you” includes that organization.

1. Accounts and workspaces

You sign in to Ray with your GitHub account. Your work in Ray lives in workspaces; you can belong to more than one, and each workspace member has a role (owner, admin, or member). You must provide accurate account information and be able to form a binding contract to use the Service.

You are responsible for all activity in your workspaces, including activity using your API keys. Keep your GitHub account and API keys secure, give access only to people you trust, and revoke any key you believe has been exposed. Tell us promptly if you suspect unauthorized access.

2. Acceptable use

You agree not to use the Service to:

• send unsolicited bulk messages (spam) or violate anti-spam or telemarketing laws;
• transmit unlawful, infringing, or harmful content;
• send messages to recipients without a lawful basis or required consent;
• probe, overload, or circumvent the Service’s limits, security, or authentication.

You are responsible for the content you send and for obtaining any consent required from your recipients.

3. Your data

You own the data you put into the Service — templates, recipient details, message content, and similar material (“Customer Data”). You grant us a limited license to host, process, and transmit Customer Data only as needed to provide, secure, and support the Service for you. Our Privacy Policy describes how we handle personal data, including how long message data is kept.

4. Delivery providers and credentials

Ray delivers messages through providers you connect using your own accounts and credentials — for example Amazon SES, Firebase Cloud Messaging, Twilio or sendsms.mn SMS, Slack or Discord webhooks, a Telegram bot, or your own webhook endpoints. Those providers are engaged by you, not by us. You are responsible for keeping those accounts in good standing, for complying with each provider’s terms and policies, and for any charges they bill you. We store the credentials you give us encrypted and use them only to deliver your messages. We are not responsible for a provider’s own outages, rejections, or account actions.

5. Plans, fees, and automatic renewal

Plans include a monthly notification allowance and other limits described at /pricing. Subscriptions apply per workspace. Fees are exclusive of taxes unless stated otherwise.

Card subscriptions renew automatically. When you subscribe by card, you are charged the plan price shown at checkout in advance, and the subscription renews and charges you again at the start of each billing period until you cancel. You can cancel at any time from your workspace’s billing settings; cancellation takes effect at the end of the current paid period and you will not be charged again. Card payments are sold and processed by Polar, our merchant of record, and are also subject to Polar’s buyer terms. If we change the price of a plan, we will tell you before the new price applies to your renewal.

QPay payments do not renew automatically. They are billed in MNT for one period at a time, and you are only charged when you pay the invoice for the next period.

6. Cancellation

You may cancel a card subscription at any time from your workspace’s billing settings, or stop QPay billing by not paying for the next period. Cancellation stops future renewals; your plan remains active through the end of the current paid period, after which the workspace reverts to the Free plan. See our Refund Policy.

7. Archiving and deleting a workspace

A workspace owner can archive a workspace from its Settings page. While a workspace is archived:

• its API keys stop working immediately;
• members lose access to it in the dashboard, except that the owner can still open its Settings to restore or delete it;
• pending invitations to it can no longer be accepted;
• scheduled sends that come due while it is archived are cancelled, and are not sent later even if you restore it;
• nothing is deleted, but the normal data retention schedule keeps running, so older data can still age out; and
• delivery status updates and tracked-link redirects for messages sent before archiving continue to be processed.

Restoring the workspace turns everything back on, including its API keys. Archiving does not pause or extend your billing period: paid time keeps running while the workspace is archived.

Once a workspace is archived, its owner can permanently delete it by retyping the workspace’s URL name (slug) to confirm. Deletion removes the workspace’s data from the Service — including templates, channels and stored provider credentials, API keys, delivery logs and sends, in-app feed items, suppressions, webhooks, members and invitations, usage counters, the audit log, and the subscription record. Deletion is irreversible, and we cannot restore a deleted workspace. Because the dashboard and API are closed while a workspace is archived, retrieve any data you want to keep before you archive it. Billing and payment records are kept after deletion as described in our Privacy Policy.

You cannot archive or delete a workspace while it has a card subscription that is set to renew. Cancel the subscription first; you can then archive or delete right away. Archiving or deleting a workspace does not refund or prorate the unused part of a paid period.

8. Service availability and changes to the Service

We aim to keep the Service available but do not guarantee uninterrupted operation. We may modify, suspend, or discontinue features. If we discontinue a feature you actively rely on, we will try to give you reasonable notice.

9. Suspension and termination

We may suspend or terminate access to the Service, a workspace, or an API key for violation of these Terms, non-payment, or activity that risks harm to the Service, its users, or third parties. Where practical, we will tell you why and give you a chance to fix the problem first.

You may stop using the Service at any time by cancelling any paid subscription and deleting your workspaces as described in section 7. To close your user account itself, email us at [email protected]; we will confirm the request and explain what happens to any workspaces you own.

When access ends, your right to use the Service ends too. If we terminate a workspace, we may delete its data after termination, so retrieve anything you need beforehand where you can. Fees already owed, and sections that by their nature should survive termination — including sections 10, 11, and 13 — continue to apply.

10. Indemnity

You will defend and indemnify Ray against third-party claims, and related losses and reasonable costs, arising from the content you send through the Service, your recipients’ claims, your use of your delivery providers, or your violation of these Terms or applicable law.

11. Disclaimers and limitation of liability

The Service is provided “as is” without warranties of any kind. To the maximum extent permitted by law, Ray is not liable for indirect, incidental, or consequential damages, and our total liability is limited to the amounts you paid for the Service in the twelve months preceding the claim.

12. Changes to these Terms

We may update these Terms. We will give reasonable advance notice of material changes through the Service or by email, and update the date at the top of this page. If you keep using the Service after a change takes effect, the updated Terms apply; if you do not agree, stop using the Service and cancel any subscription.

13. Governing law

These Terms are governed by the laws of Mongolia, without regard to conflict of laws principles. Disputes will be resolved in the courts of Ulaanbaatar, Mongolia.

14. Contact

Questions about these Terms can be sent to [email protected].