Developer Terms
Last updated November 7, 2026
The short version
- These terms are for anyone who builds on Glofly: API keys and bots, webhooks, bridges, and linked game servers.
- Ask only for what you need, use it only for what people expect, and say so in your own privacy policy.
- Never sell Glofly people's information, use it for ads or tracking, or use their messages to train AI.
- Keep your keys and secrets secret. What happens with them is on you.
- It's free, there's no guarantee it stays the same, and we can switch off anything that breaks these terms.
These terms are an agreement between you and Glofly, run by Chip Mullins in Lexington, Kentucky, USA ("Glofly", "we", "us"). They add to the Terms of Service and the Privacy Policy, which still apply to you and to everything you build. You agree to them when you make an API key, a webhook or a game-server link, or otherwise use Glofly's developer features ("the API"). If you build for a company or group, you agree for them too and confirm you're allowed to.
What these terms cover
- Not Sign in with Glofly: signing in with a Glofly account is only for Glofly's own apps (like Gloslate and Tablespin) and isn't offered to other developers.
- Constellation integrations: API keys and the bots they act as, slash commands and buttons, incoming and outgoing webhooks, and bridges that read or post messages in nebulas a constellation's owner picked.
- Linked game servers: game servers (for example FiveM, RedM or Minecraft) that check a player's Glofly link, including the Glofly Whitelist resource.
Your keys and secrets
- API keys, webhook addresses and signing secrets are passwords. Keep them on your server, never in a public repo, a game resource others can read, or a web page.
- You're responsible for everything done with your keys, bots and servers, including by anyone you let use them.
- If one leaks, reset it straight away (the constellation's Integrations page) and tell us at support@glofly.app if people's information may have been exposed.
People's information
Everything you get from Glofly about a person (their name, username, photo, Glofly ID, email address, roles, game links, presence and messages) is "Glofly data". With Glofly data you must:
- Tell people. Say plainly (for example in your bot's description, your server's rules or your own privacy policy) what you get from Glofly, why, how long you keep it and how people can have it deleted.
- Ask for the least you need and use it only to provide the feature people chose your bot or server for. Ask only for the scopes and nebulas it really uses.
- Respect "no". People can unlink a game server or leave a constellation, and constellation owners can remove your key at any time. When that happens, stop using what you no longer have permission for and delete it within 30 days unless the law requires you to keep it. Do the same when someone asks you to, or when your bot or server shuts down.
- Keep it safe with reasonable security, and tell affected people (and us) without undue delay if it's exposed.
You must not:
- sell, rent or trade Glofly data, or give it to data brokers, ad networks or anyone else, except service providers who handle it only for you and under the same rules;
- use Glofly data for advertising, to build profiles of people, or to track them across other apps and sites;
- use messages or other content from Glofly to train, fine-tune or evaluate AI or machine-learning models;
- combine Glofly data with other information to work out who someone is when they haven't told you, or to find, follow or harass anyone;
- send people email they didn't ask for: use their email address only for your service's own account messages unless they separately agree to more;
- build anything aimed at children under 13, or try to sign in or link family accounts (Glofly refuses them).
Messages and bridges
- A key with permission to read messages can only read the nebulas the constellation's owner picked, and Glofly tells everyone in those nebulas that their messages are shared with your bot. Use those messages only to provide that bridge or feature.
- Don't keep copies of messages longer than the bridge needs, and remove or update them when Glofly tells you a message was edited or deleted, where your service makes that possible.
- Never read, store or forward direct messages or group chats. The API doesn't offer them; don't try to get them another way.
Bots, webhooks and game servers
- A bot must say what it is and what it does, and do only what the constellation's owner set it up for. No spam, mass mentions or unasked-for messages.
- Game servers: use a player's link only to let them in, give them their roles and show their Glofly name in game. Tell players on your server what the link does.
- Constellation owners are responsible for the integrations they add, and for following these terms and the Terms of Service in their constellation.
Using the API fairly
- Stay within the rate limits, and don't try to get around them, Lockdown, bans, timeouts, family-account rules or any other limit or security measure.
- Don't scrape Glofly, collect information about people who haven't used your bot or server, or use the API to copy Glofly or build a competing messenger from its data.
- Don't make anything that pretends to be Glofly or the Glofly team, asks for people's Glofly passwords, or hides what it is from the people using it.
- Found a security problem? Email support@glofly.app and give us a fair chance to fix it before you tell anyone. Never test against accounts or constellations that aren't yours.
The Glofly name
You can say your bot or server works with Glofly. Don't use the Glofly name, firefly logo or anything like them in your bot's or server's name or logo, or in a way that suggests we made, checked or endorse it. Anything marked "Made by Glofly" is only ours.
Our part
- The API is free. We may set or change limits, and add, change or remove parts of it. We'll try to give notice of changes that break working bots and servers, but can't always.
- We may ask what your bot or server does with Glofly data, and you'll answer honestly.
- We can suspend or switch off any key, bot, webhook or game-server link, or your access to the API, at any time, for example if it breaks these terms, puts people at risk or harms Glofly. Where it's safe and sensible we'll tell you why.
- We don't review bots, integrations or game servers before people use them and aren't responsible for them. Your relationship with the people who use them is yours.
Disclaimers and liability
The API is provided "as is" and "as available", with no promise that it will be uninterrupted, error-free or stay the same, and the disclaimers and limits on liability in the Terms of Service apply. To the extent the law allows, you'll defend and cover Glofly against claims, losses and costs that come from your app, bot, server or integration, how you handle Glofly data, or your breaking these terms.
Ending things
You can stop using the API and delete your keys and webhooks at any time. If you stop, or we switch you off, delete the Glofly data you hold as described above. The sections on people's information, messages, disclaimers and liability continue after that.
Changes to these terms
We may update these terms. We'll change the date above, and for important changes we'll tell you by email or in Glofly before they take effect, and may ask you to agree again before you change an app. If you keep using the API after that, the new terms apply. The law and courts in the Terms of Service apply to these terms too.
Contact
Questions about these terms or the API: support@glofly.app.