Privacy Policy

1. Introduction

This Privacy Policy describes how BuiltByTerra collects, uses, and stores information when you use Coinly. We are committed to handling your data responsibly and transparently.

2. Data We Collect

We collect only the data necessary to operate Coinly:

• Guild (Server) ID, to store per-server configuration, wallets, and the server pot.
• User IDs, to associate wallet balances, bank balances, daily streaks, and cooldowns with your Discord account on a per-server basis.
• Balances and economy state, wallet balance, bank balance, daily streak, and command cooldown timestamps for each server you use Coinly in.
• Transaction records, a log of economy events where coins move between members or by your own choice, /daily, /work, payments, bets, robberies, heists, shop purchases and sales, including amounts, timestamps, and the user IDs involved. It is kept only so a balance that looks wrong can be explained, and is deleted after 90 days. Passive earnings from chatting or sitting in voice are not recorded here at all.
• Shop purchases and inventory, which server-configured shop items you've bought, the price paid, and any Discord role linked to that item, kept so your purchase and role grant survive even if an admin later edits or removes the item.
• Voice channel presence, whether you are in a voice channel and how many members are present, checked periodically to award voice activity coins. Audio is never accessed or recorded.
• Message activity, the fact that you sent a message, used to award passive coins on a cooldown. What you wrote is not read and not stored, and the earning itself is not recorded either, all that is kept is the cooldown timestamp that stops the next message earning again too soon.
• Counting game messages, if a server admin has set up the counting game, Coinly reads the text of messages posted in that one channel, purely to check whether it is the next number. The text is never stored. What is kept is the number the server has reached, its record, how many wrong numbers the run has left before it resets, and the user id of whoever posted the last number, so the same person cannot count twice in a row. No other channel is read.
• Error diagnostics, if something fails, a short technical record of the error, which may include the server and user id involved, is written to an internal log and automatically deleted after 30 days.
• Operational analytics, the id and name of each server Coinly is in, that server's member count, and the dates Coinly was added to or removed from it, plus hourly totals of how many times each command was used. Command totals are counts only: they record that a command ran forty times in an hour, never who ran it, what they typed, or which server they ran it in.

Coinly requests Discord's Message Content intent for one feature only: the counting game, which cannot work without reading the number someone posted. Content is read in a single place in the code, only for messages in a server's configured counting channel, only to decide whether the text is the next number, and it is never stored. Every other feature ignores message text entirely, passive coins are awarded on the fact that a message was sent, never on anything it contained. Voice audio is never accessed or recorded; Coinly sees only who is connected to a voice channel and how many people are there. All economy data is strictly per-server, balances are not shared or merged across servers.

3. How We Use Data

Collected data is used solely to:

• Operate the per-server economy: wallets, banks, streaks, and cooldowns.
• Award passive earnings for chat and voice activity.
• Run games and resolve their outcomes (coinflip, challenge, rob, heist).
• Process shop purchases and sales, granting item-linked Discord roles on purchase and removing them again when the item is sold back.
• Maintain the server pot and heist participation records.
• Run the counting game in the one channel an admin sets aside for it, if the server enables it.
• Generate server and global leaderboards.
• Diagnose faults: error records are used only to find and fix bugs, and are never used to build a profile of anyone.

We do not sell, share, or disclose your data to third parties for marketing or advertising purposes.

4. Data Storage and Security

Data is stored in a PostgreSQL database with encrypted connections (SSL/TLS). We take reasonable technical measures to protect stored data from unauthorized access. However, no system is completely secure, and we cannot guarantee absolute security.

Operational analytics are kept in a database separate from Coinly's feature data, and that database contains no user identifiers of any kind, no user ids, no message content, and no per-member activity. It is readable only by the developer, through a private dashboard that requires both a randomly generated access token and a time-based one-time code from an authenticator app. That dashboard connects using a read-only credential, is excluded from search engines, and returns an ordinary "page not found" to anyone who is not signed in. These analytics are never sold, shared, or used for advertising.

5. Data Retention

Your economy data, wallets, banks, streaks, cooldowns, and the server pot, is retained while Coinly remains in your server. Transaction records are the exception: they are deleted after 90 days regardless, because their only purpose is explaining a balance that looks wrong recently. If Coinly is removed, all of that server's data is automatically and permanently deleted 7 days after removal. Re-adding Coinly within those 7 days cancels the scheduled deletion and restores your data. You may also request immediate deletion at any time (see Section 8).

This applies to operational analytics with no exception. When Coinlyis removed from a server, that server's analytics record, its id, name, member count, and install and removal dates, is permanently deleted on the same 7-day schedule as everything else, from the analytics database as well as the application's own. Re-adding Coinlywithin those 7 days cancels the deletion. Nothing about a server that removed Coinly is retained beyond that window.

6. Third-Party Services

Coinly operates within the Discord platform and is subject to Discord's Privacy Policy. We do not integrate with other third-party data processors beyond the database provider used to store operational data.

7. Children's Privacy

Coinly is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided data, please contact us so we can remove it.

8. Your Rights and Data Requests

You may request access to, correction of, or deletion of your data at any time. For server administrators, this includes all data associated with your guild ID.

To submit a data request, join our Discord community and open a support ticket with your Discord server ID or user ID.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Continued use of Coinly after changes constitutes your acceptance of the revised policy.

10. Contact

For questions, concerns, or data requests, join our Discord community.