Join our Discord communityJoin our Discord communityJoin our Discord communityJoin our Discord communityJoin our Discord communityJoin our Discord community
BuiltByTerra
← Back to Giftly
Giftly

Privacy Policy

Giftly — by BuiltByTerra

Last updated: July 20, 2026

1. Introduction

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

2. Data We Collect

We collect only the data necessary to operate Giftly:

  • Guild (Server) IDto store per-server configuration such as the giveaway manager role and the giveaway ping role.
  • Giveaway definitionsthe prize text, optional description, winner count, required role ID, end time, and the channel and message IDs of the giveaway post — everything needed to run and resolve a giveaway.
  • User IDs of hosts, entrants, and winnersthe ID of the member who started each giveaway, the IDs of members who clicked Enter, and the IDs of drawn winners (so rerolls never re-pick an existing winner).
  • Timestampswhen giveaways were created and ended, and when entries were made.
  • Error diagnosticsif 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.

Giftly never reads messages — it has no access to message content, and entries happen exclusively through button clicks on the giveaway post itself. Giftly no longer uses the Server Members intent for any feature.

3. How We Use Data

Collected data is used solely to:

  • Run giveaways: track entries, enforce role requirements, and draw winners when time runs out.
  • Resume reliably: end times are stored so giveaways survive bot restarts.
  • Guarantee fair rerolls: winner records prevent the same member winning twice in one giveaway.
  • Enforce per-server limits (maximum simultaneous active giveaways).
  • Assign or remove the configured giveaway ping role when a member requests it via the Giveaway Role button — no additional data is stored for this.
  • 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.

5. Data Retention

Your giveaway data — configurations, giveaways, entries, and winner records — is retained while Giftly remains in your server. If Giftly is removed, all of that server's data is automatically and permanently deleted 7 days after removal. Re-adding Giftly within those 7 days cancels the scheduled deletion and restores your data. You may also request immediate deletion at any time (see Section 8).

6. Third-Party Services

Giftly 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

Giftly 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 Giftly after changes constitutes your acceptance of the revised policy.

10. Contact

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