Developer Terms of Service

These terms are for people who build on Palloo: bots, incoming webhooks, slash commands, apps that use Log in with Palloo, and anything else that talks to the Palloo API. They sit on top of our Terms of Service, Privacy Policy and Acceptable Use Policy, which still apply to you and to everything your app does. "We" and "us" mean the operator of Palloo, and "you" means you, the developer, or the organization you build for.

1. Agreeing to these terms

By creating a bot or webhook, requesting a Log in with Palloo app, or otherwise using the API, you agree to these Developer Terms. If you build for an organization, you confirm that you're allowed to accept them on its behalf, and "you" includes that organization.

Each version of these terms has a version identifier and an effective date, shown at the top of this page. When you request a Log in with Palloo app, we ask you to accept these terms and record which version you accepted and when. Creating a bot or webhook doesn't show these terms yet, and we don't record an acceptance for it, but these terms still apply to every bot, webhook and other use of the API.

If these terms and the Terms of Service disagree about your app, these terms win for that question.

2. Words we use

• The API means Palloo's REST API, the gateway, incoming webhooks, interactions, the Log in with Palloo (OpenID Connect) endpoints and the developer documentation at developers.palloo.app.
• Your app means anything you build or run that uses the API, including bots, webhook integrations and Log in with Palloo apps.
• Credentials means anything that lets your app act on Palloo or identify itself: bot tokens, webhook URLs, client IDs, client secrets, private keys and the access and refresh tokens Palloo issues.
• User data means any information about a Palloo user or their content that your app gets through the API, such as user IDs, usernames, profiles, email addresses, messages and files.

3. Bots and apps

• You're responsible for your app. Whatever your app does on Palloo counts as if you did it yourself, including what it posts and how it treats people.
• Be honest about what it is. Give your app an accurate name, description and avatar. Bot accounts must stay clearly marked as bots, and an app must never pretend to be a person, another app or Palloo.
• Ask before you act. Your bot should only join servers whose moderators added it, and only do what those moderators and its users expect from its description. Don't message people who haven't interacted with your app or asked to hear from it.
• Ask only for what you need. Request the smallest set of permissions, intents and scopes that your app needs to work, and explain why when people ask.
• Keep it working safely. Fix security problems promptly, keep the software your app runs on up to date and stop your app if it starts misbehaving.

4. Credentials

• Keep them secret. Treat every credential like a password. Store them in a secret manager or your host's secret settings, never in source code, public repositories, client-side code, screenshots or logs.
• Don't share them. Credentials are for your app only. Don't sell, lend or publish them, and don't let other apps or people use them. If several people work on your app, give access only to those who need it.
• Rotate them. Regenerate a bot token, or ask us to replace a client secret or key, whenever you think it might have leaked, when someone with access leaves your team, and from time to time anyway. For Log in with Palloo apps we recommend private_key_jwt, which means no shared secret ever has to leave your servers.
• Tell us about leaks. If a credential leaks, revoke or rotate it right away and tell us through the Help center if user data might have been exposed.
• We can revoke them. We may revoke or reset any credential at any time to protect Palloo or its users, for example when we find one published online. We'll try to tell you when we reasonably can, but we can't promise a notice every time.

5. Rate limits

The API has rate limits, described in the developer documentation. Respect them: slow down when you get a 429 answer and wait for the time it gives you.

Don't try to get around the limits. That includes spreading requests over several bot accounts, apps, tokens or IP addresses to do what one app couldn't, and creating accounts or apps in bulk. If your app really needs more, ask us through the Help center and explain why.

6. User data

People trust Palloo with their information, and when they use your app they extend that trust to you. So:

• Use it only for your app's stated purpose. Collect and use user data only to provide the features your app describes to the people who use it. Don't use it for anything those people wouldn't reasonably expect.
• Get consent. Tell people what your app collects and why before it collects it, in a privacy policy that's easy to find. Get their consent where the law or these terms require it, and don't collect more than you said you would.
• Don't sell it. Never sell, rent or trade user data, and never share it with data brokers, advertising networks or anyone else who would use it for their own purposes. You may use service providers that process it only on your behalf and under confidentiality obligations at least as strong as these terms.
• Don't scrape. Don't collect user data in bulk beyond what your app needs to work, and don't build profiles, archives or search indexes of people, messages or servers that their members didn't ask for.
• Delete it when asked. When someone asks you to delete their data, delete it within 30 days, unless the law requires you to keep it.
• Delete it when they leave. When someone disconnects your app (for example, by revoking it under Settings, Authorized Apps), removes your bot from their server, or deletes their Palloo account, delete the user data you got about them through the API within 30 days, except what the law requires you to keep. Palloo doesn't yet send apps a notice when someone disconnects them or deletes their account, so treat it as them leaving when Palloo stops accepting your tokens for them or answers that their account no longer exists. If your app stores messages, delete each one when your app learns it was deleted, for example from a deletion event your bot receives or when Palloo answers that it no longer exists.
• Respect Palloo's privacy tools. People can export and delete their data on Palloo. Don't work against that: don't keep copies of content that someone deleted on Palloo, and don't make it harder for anyone to leave.
• Keep it secure. Protect user data with reasonable technical and organizational measures: encrypt it in transit, limit who can access it, and keep only what you need for as long as you need it.
• Tell us about breaches. If you learn that user data your app holds was accessed without permission, tell us through the Help center within 72 hours, and tell the affected people and the authorities when the law requires it.
• Follow the law. You're responsible for complying with the privacy and data protection laws that apply to your app and the people who use it.

7. What's not allowed

Your app must follow the Acceptable Use Policy, just like a person on Palloo. In particular, don't build or run an app that:

• Spams. Sends unsolicited messages, mass direct messages, unwanted invites or friend requests, fake engagement, or manipulates the public server directory.
• Harasses. Targets, threatens, raids or abuses people or servers, or helps others do so.
• Watches people. Tracks, monitors or profiles people without their knowledge, including following what someone does across servers, recording their presence or status over time, or identifying people behind their accounts.
• Trains models on Palloo content without consent. Uses messages, files, profiles or other user content to train, fine-tune or evaluate machine learning models, unless every person whose content is used has clearly agreed to that use. A server moderator's consent isn't enough on its own.
• Impersonates Palloo. Pretends to be Palloo, Palloo staff, Palloo Support or a Palloo system message, or suggests that we made, endorse or partner with your app when we don't.
• Gets around safety features. Evades or weakens blocks, bans, timeouts, permissions, privacy settings, content filters, verification, rate limits or any other protection on Palloo, or helps someone return after we've suspended them.
• Shares illegal or harmful content. Creates, shares, requests or helps find child sexual abuse material or anything that sexualizes minors. We have zero tolerance for this: as soon as we learn of it, we remove the app, suspend its developer and report to the authorities. The same goes for any other content or activity that's illegal where you or your users are.
• Attacks Palloo. Spreads malware, phishes for credentials, probes Palloo for security weaknesses without our permission, or tries to get at data or systems it isn't meant to reach. If you find a security problem, tell us privately through the Help center.
• Resells the API. Sells or gives others access to the API or to user data, outside of what your app offers its own users.

8. Content and moderation

Everything your app posts or does must follow the Terms of Service and the Acceptable Use Policy. If people can use your app to post content, give server moderators a way to deal with abuse, and act on reports about your app quickly.

We may review your app, its listing and how it uses the API at any time, including after we've approved it. If your app breaks these terms, the Terms of Service or the Acceptable Use Policy, or puts people or Palloo at risk, we may ask you to change it, limit it, suspend it, or revoke its credentials and access. For the most serious harms, especially anything involving the safety of children, we act immediately and without notice. Server moderators can also remove your bot from their servers at any time.

If you think we got a decision about your app wrong, tell us through the Help center.

9. Log in with Palloo apps

Log in with Palloo lets people sign in to your website with their Palloo account. Because people see your app's name on Palloo's consent screen and trust it with their identity:

• Approval is required. You request an app the way the developer documentation describes, and we review each request before it gets a client ID. We may approve, ask for changes or decline a request, and we may limit the number of apps per developer.
• Keep your app's information accurate. The name, description, homepage, redirect URIs, logo and contact details you give us must be true and kept up to date. Ask us before your app changes what it does or who runs it.
• Have a privacy policy. Your app must link to a privacy policy, at a public URL, that explains what it does with the data it gets from Palloo. If you have terms of service, link to them too.
• Ask only for the scopes you need. Request only the scopes your app actually uses. The scopes reserved for Palloo's own staff tools can never be requested.
• No misleading consent screens. Don't make people believe your app is something it isn't, don't hide what you're asking for, and don't send people to the consent screen without telling them why. Don't frame, imitate or copy Palloo's sign-in or consent pages, and never ask people for their Palloo password.
• Keep sign-ins secure. Follow the developer documentation: do the code exchange on your server, check state, nonce and the ID token, use the exact redirect URIs you registered, and keep refresh tokens as safe as passwords.
• Development apps are for development. An app approved for local development may use localhost redirect URIs. Once registered, Palloo treats it like any other app and doesn't stop real users from signing in through it, so it's up to you: don't use it for real users, and request a separate app for production.

10. Pip and the Palloo brand

Palloo, the Palloo logo and Pip, our mascot, are our marks. You may use the word "Palloo" to say truthfully what your app works with, for example "a bot for Palloo" or "Log in with Palloo", and you may use the Log in with Palloo button the way the documentation shows it. Beyond that:

• Don't use Palloo or Pip in your app's name, logo, domain or account names in a way that suggests it's made or endorsed by us.
• Don't use Pip, the Palloo logo or anything that looks like them, and don't change our marks, without our written permission.
• Don't make your app look like part of Palloo itself.

We may ask you to change how you use our marks, and you agree to do so promptly.

11. Changes to the API

Palloo is in beta, and so is the API. We'll do our best to keep it stable, but we can't guarantee it: endpoints, events, limits and scopes may change, and some may be removed. Where practical, we'll announce breaking changes in the developer changelog ahead of time and give you a reasonable time to adapt. Sometimes we'll need to change things at once, for example to fix a security problem.

We may also set or change limits on how many bots or apps you can create, or on what they can do.

12. Suspension and termination

You can stop using the API at any time by deleting your bots and webhooks or asking us to remove your Log in with Palloo app.

We may suspend or end your access to the API, or any of your apps, if you break these terms, the Terms of Service or the Acceptable Use Policy, if the law requires it, or if we stop offering part of the API. We'll usually try to tell you first and give you a chance to fix the problem, unless doing so would put people or Palloo at risk. Suspending your Palloo account doesn't by itself switch off your apps; we remove them separately when we need to.

When your access ends, stop using the API, delete your credentials and delete the user data you got through it, except what the law requires you to keep. Sections 6, 7, 13 and 14 keep applying after your access ends.

13. Disclaimers

The API is provided "as is" and "as available", like the rest of Palloo during the beta. We can't promise it will always be available, free of bugs or right for your purpose, and we don't promise that your app will keep working the same way.

We're not responsible for your app or for what it does, and the people who use it are your users, not ours. Nothing in these terms makes you our employee, partner or agent.

14. Limitation of liability

To the extent the law allows, we're not liable for any indirect, incidental, special or consequential damages, or for lost profits, revenue or data, that come from your use of the API or your app, even if we were told they might happen. Palloo doesn't charge for the API, so to the extent the law allows, our total liability to you for anything related to these terms is limited to 100 US dollars.

Nothing in these terms limits any rights you have under consumer protection law that can't be waived by agreement, or any liability that the law doesn't allow us to limit.

15. Changes to these terms

We may update these terms as Palloo and its API grow. When we do, we'll publish the new version here with a new version identifier and effective date, and announce important changes in the developer changelog. If you keep using the API after a new version takes effect, you accept it. If you don't agree with a change, stop using the API and remove your apps.

16. Contact

For questions about these terms, to report a problem with an app, or to tell us about a security issue or a data breach, open a request through the Palloo Help center at support.palloo.app. A contact address for legal notices will be listed here before Palloo opens to everyone.