Temply
Legal
This policy explains what Temply processes across the Temply Discord bot, the Temply website and dashboard, and the Temply Support bot, why that data is processed, and how it is used to operate the service.
This privacy policy applies to Temply as a whole, including the main Discord bot used for temporary voice channels, the Temply website and dashboard, the premium and billing pages, status and shard pages, and the Temply Support bot used in the support server for tickets, verification, moderation, and premium role handling.
Temply primarily processes operational Discord and account data needed to run the service. This can include Discord user IDs, guild IDs, channel IDs, role IDs, message IDs, temporary room state, ownership and access settings, saved defaults, trust or reject lists, moderation case data, ticket records, ticket transcript metadata, premium subscription state, and billing-related references.
When the dashboard is used, Temply may also process Discord OAuth account information such as your Discord user ID, username, avatar, and the guilds available to your account where Temply is present and where you have sufficient permissions.
Temply uses this data to provide temporary voice channels, room owner controls, dashboard-based configuration, premium branding options, server-specific logs, server statistics boards, support tickets, verification, moderation actions, premium role syncing, service monitoring, and account access to the dashboard.
Temply does not use service data to build advertising profiles. Data is processed to operate the product, secure the service, troubleshoot issues, manage premium access, and provide server administrators with the features they intentionally enable.
The Temply website may process technical information such as IP address, browser metadata, access timestamps, and authentication session data in order to serve pages, maintain sessions, protect routes, and allow users to sign in with Discord.
The dashboard uses Discord OAuth to identify the signed-in user and determine which guilds are available for management. Session and access data may be stored temporarily so users do not need to log in again on every restart or refresh.
If premium services are used, Temply may process subscription identifiers, customer and subscription references, plan tier information, guild assignments for premium access, and payment history needed to provision, maintain, downgrade, or remove premium features. Temply does not store raw card details itself; payment handling is performed by the payment provider.
The Temply Support bot may process support ticket records, verification state, moderation cases, warnings, automod actions, join and leave logs, and premium role sync information. If a support server enables ticket transcripts, Temply may generate transcript attachments and store transcript metadata such as the ticket ID, archive message reference, transcript size, and generation timestamp.
Many Temply features are optional and controlled by server administrators. If logging is enabled, Temply may post event information to channels chosen by the server. If statistics boards are enabled, Temply may maintain and update server-only statistics messages. If ticket archives are enabled in the support bot, transcript attachments may be sent to the configured archive channel.
Temply does not rely on permanent transcript file storage on the host machine for support tickets. Transcript generation may still involve in-memory processing and archive delivery where that feature is enabled.
Temply uses PostgreSQL for persistent application data and Redis for caching, runtime coordination, and other short-lived operational state. Temply may also rely on hosting providers, payment providers, Discord, and related infrastructure services that process technical data required to deliver the service securely and reliably.
Some data remains stored while Temply is active in a server or while a website account session or premium subscription remains active. Temporary runtime data in Redis may expire automatically. Persistent configuration, moderation, billing, and support records may remain for operational, support, abuse-prevention, or accounting reasons unless removed as part of product changes, cleanup, or a handled request.
Temply is not intended to collect more information than is reasonably needed to operate its Discord bots, website, dashboard, support tooling, and premium services. Temply does not sell personal data and is not built as an advertising network or profiling platform.
If you have questions about privacy, stored configuration, premium data, support records, or moderation information connected to Temply, use the official Temply support server or support contact route made available by the project.