Temply
Legal
This policy explains what Temply processes across the main bot, website and dashboard, support systems, Premium billing, and service operations, and why that information is needed.
This policy applies to Temply as a whole, including the main temporary voice bot, the public website, the dashboard, Premium checkout and billing flows, public status pages, and the Temply support bot used for tickets, moderation, verification, and Premium role syncing.
Temply processes operational Discord and account data needed to provide the service. This can include user IDs, guild IDs, channel IDs, role IDs, message IDs, room state, room ownership state, room defaults, trusted and rejected access data, moderation records, ticket records, transcript metadata, Premium entitlement state, and billing-related references.
When the dashboard is used, Temply may process Discord OAuth 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. Session data may also be stored temporarily so protected pages can work properly.
Temply uses service data to create and manage temporary rooms, enforce room-owner controls, run dashboard editing, maintain Premium entitlement and branding state, repair managed room state, operate support tickets and transcripts, run moderation and automod features, and keep service diagnostics and status tooling working.
The website may process technical request information such as IP address, browser metadata, access timestamps, route usage, and authentication state in order to serve pages, protect sessions, process dashboard actions, confirm checkout returns, and troubleshoot service issues.
If Premium is used, Temply may process plan tier, billing type, entitlement state, Stripe references, guild attachments, and payment-related identifiers needed to activate, maintain, downgrade, remove, or audit Premium access. Temply does not store raw bank card details itself; payment handling is performed by the payment provider.
The support bot may process support ticket records, moderation records, verification state, automod outcomes, join and leave logs, and Premium role sync information. If transcripts are generated, Temply may store transcript metadata such as the ticket ID, transcript URL or archive reference, generation size, and related timestamps.
Many Temply features are optional and administrator-controlled. If a server enables logging or statistics, Temply may store and process the configuration for those outputs and update the relevant channels or messages inside that server.
Temply uses PostgreSQL for persistent application data and Redis for caching, coordination, and short-lived runtime state. Temply also depends on Discord, hosting providers, payment providers, and related infrastructure services which may process technical data needed to deliver the service.
Some information remains stored while Temply is active in a guild, while a support or moderation record still needs to exist, or while a Premium entitlement remains relevant for service operation or accounting. Short-lived cache data may expire automatically. Persistent records may remain for operational, abuse-prevention, or support reasons unless removed through product changes or cleanup.
Temply is not built as an advertising network or data-broker service. It is designed to process the information needed to operate Discord bots, the dashboard, support tooling, Premium systems, and related service infrastructure.
If you have privacy questions about stored server configuration, Premium entitlement data, ticket records, moderation data, or service-side account handling, use the official Temply support route made available by the project.