The deal, in plain words.

• The agreement
• The service
• Accounts and keys
• Your apps and your users
• Acceptable use
• AI agents
• Your content
• Our side
• Fees
• Data protection
• Ending
• No warranty
• Liability
• Indemnity
• Changes
• Law and disputes
• The rest

1. The agreement

These terms are between you and S.Z. CODE AXOL LTD, 27 Despoinas Nikou Pattichi, Flat/Office 2, 3071 Limassol, Cyprus, company number HE 461075 ("DevReply", "we"). "You" is the person or organisation that creates a DevReply account or team, or puts a DevReply key in an app. If you accept for an organisation, you confirm you may bind it.

By signing in to the dashboard, creating an app or using the SDKs or API, you accept these terms, our privacy policy and the data processing agreement (DPA). DevReply is for businesses and developers, not consumers.

2. The service

DevReply is an in-app chat between your app's users and your team: native SDKs (iOS, Android, web, React Native, Flutter), a dashboard to answer from, an API, an MCP server for AI agents, and emails and push notifications to your users about replies (the "Service").

DevReply is in early access. We add and change features often. We keep released SDK versions working (see the changelogs), and we tell you ahead of any change that would break something you rely on. We may stop a feature, with notice where we can.

3. Accounts and keys

• Keep your sign-in safe. You're responsible for what happens under your account and your team, including what teammates and agents you invite do.
• Public keys (pk_) are meant to ship in apps. Secret keys (sk_) are not: keep them on your servers, never in an app, a client bundle, a log or a repository. If one leaks, delete it in the dashboard and tell us.
• Team owners decide who has access and how AI agents may reply. Remove people who shouldn't have access any more.
• Tell us straight away at [email protected] if you think your account or keys were misused.

4. Your apps and your users

You decide to put DevReply in your apps, so you're responsible for doing that lawfully. In particular:

• Tell your users. Your app's privacy policy and store listings (Apple's App Privacy, Google Play's Data safety) must cover what DevReply collects for you. Privacy details for your app lists it.
• Have a legal basis for the data you send us about your users, such as custom attributes. Don't send passwords, payment card numbers, government IDs or health data as attributes.
• Handle their requests. When a user asks for their data or to be deleted, use the tools we give you (the dashboard, DevReply.deleteUser(), the API). When your users delete their accounts in your app, delete them in DevReply too.
• Children. If your app is directed at children, you're responsible for any consent the law requires (such as COPPA or parental consent under GDPR) before they use the chat.
• Follow the stores' rules (App Store, Google Play) for your app, including around notifications and account deletion.
• Your releases are yours. You choose which SDK version goes into your app, test it before you release, and decide when to update. We're not responsible for your app's builds, store reviews, releases or outages. The SDKs are built to fail quietly: if DevReply can't be reached, the chat shows an error or stays hidden, and the rest of your app keeps working.
• Answer your users. DevReply carries the conversation; what you and your agents say in it is yours.

5. Acceptable use

Don't use DevReply to:

• send spam, unsolicited marketing, or messages your users didn't ask for;
• send or store anything illegal, infringing, harassing, hateful or sexually exploitative, or malware;
• collect data from people in ways they weren't told about, or track them across apps;
• get around rate limits, keys or security, probe or overload the Service, or access other teams' data;
• resell or white-label the Service, or build a competing service from it, without our written permission;
• pretend to be someone else, or mislead your users about who they're talking to.

The SDKs are open source under the MIT license; that license, not these terms, governs their code. These rules cover the hosted Service.

6. AI agents

You can connect AI agents to your team through the MCP server. You choose what they may do (read, or read and write) and, per app, whether they may reply to users (off, drafts for your team to approve, or send). What an agent does with your access counts as done by you. Replies from agents go out under your team's AI persona. Text written by your app's users can contain anything, so treat it as data, not as instructions to your agent.

7. Your content

Everything you and your users put into DevReply (messages, files, user details, settings, your app's name and icon) stays yours. You give us the right to host, copy, process and show it only as needed to run the Service for you, as the DPA describes. We don't sell it, and we don't use it to train AI models.

If you send us ideas or feedback, we may use them freely.

8. Our side

The Service, the dashboard, the DevReply name and logo, and everything we build around them are ours. Apart from the open-source SDKs, you get a right to use the Service under these terms, not ownership of it. Don't remove our notices or copy the Service.

We run the Service with reasonable care and security (see the privacy policy) and aim to keep it available, but we don't promise a service level. We may do maintenance, and we'll try to announce anything long in advance.

9. Fees

Plans. DevReply has a free plan and paid plans (Pro, Scale), described with their prices and limits at devreply.com/#pricing. Until paid plans go on sale, every account has every feature for free; we'll tell team owners at least 30 days before any limit of the free plan applies to them.

Paying. Prices are in US dollars and exclude VAT and similar taxes, which are added at checkout where they apply (for example, reverse charge for businesses in the EU with a VAT number). Paid plans are billed in advance, monthly or yearly, through our payment provider Stripe, and renew automatically until cancelled. The team's owners manage the plan, cards and invoices in the dashboard.

Cancelling and refunds. You can cancel at any time; the plan stays until the end of the period you paid for, then the team moves to the free plan (nothing is deleted). If you're not happy, ask for a refund within 7 days of a payment and we'll refund that payment. Otherwise payments aren't refunded, except as section 11 says.

Changes and missed payments. We may change prices with at least 30 days' notice; the new price applies from your next period after that. If a payment fails, Stripe retries it for a while; if it still fails, the team moves to the free plan until it's paid.

10. Data protection

For your app users' data, you're the controller and we're your processor; the DPA forms part of these terms. For your own and your teammates' dashboard accounts, we're the controller under our privacy policy.

11. Ending

• You can stop at any time: delete your apps in the dashboard (their users, conversations, messages and files go at once), or email [email protected] to close your account. We then delete the remaining data within 30 days. Ask first if you want a copy.
• We may suspend access right away, or end these terms, if you break them in a serious way (such as section 5), if a key is being abused, or if the law requires it. Where we can, we'll warn you first and give you a chance to fix things. We may also end the Service for everyone with at least 60 days' notice; we then refund the unused part of any prepaid period, and switch the chat off in your apps before the servers go, so your app hides its DevReply button (isAvailable).
• Sections 7, 8, 12 to 15 and 17 continue after the end.

12. No warranty

The Service is provided "as is" and "as available". To the extent the law allows, we disclaim all warranties, express or implied, including fitness for a particular purpose and non-infringement. We don't promise the Service will be uninterrupted or error-free, or that every email or push notification will arrive.

13. Liability

To the extent the law allows:

• Neither of us is liable for indirect or consequential losses, lost profits, revenue or data, or loss of goodwill.
• Our total liability for everything related to the Service in any 12 months is limited to the greater of the fees you paid us in those 12 months and 100 euros.
• None of this limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law doesn't let us limit.

14. Indemnity

If someone makes a claim against us because of your apps, your content, your use of the Service in breach of these terms, or your breach of law (for example towards your users), you'll cover our reasonable costs and losses from it. We'll tell you about the claim promptly and let you control the defence.

15. Changes to these terms

We may update these terms. We change the date at the top, and for changes that matter we email team owners at least 30 days before they apply. If you keep using DevReply after that, the new terms apply; if you don't agree, stop using it before then.

16. Law and disputes

These terms are governed by the laws of the Republic of Cyprus. The courts of Limassol, Cyprus, have jurisdiction, but either of us may seek urgent relief wherever needed. Before going to court, write to us and we'll try to settle it in good faith within 30 days.

17. The rest

• These terms, the privacy policy and the DPA are the whole agreement about the Service. If one part is found invalid, the rest stays.
• Not enforcing a right isn't giving it up.
• You may not transfer these terms without our consent. We may transfer them to a company that takes over the Service, and we'll tell you.
• Neither of us is responsible for delays caused by events beyond reasonable control.
• Notices to us: [email protected]. Notices to you: the email of your team's owners.