Privacy policy

Who this covers

This policy describes how Scrimly handles information when you browse communities, sign in with Discord, host a server or take part in a scrim. Community hosts also control what they post and how they run their events.

Information we use

• Discord identity: your Discord ID, display name and avatar. We use your server memberships and management permissions to verify community access and hosting rights.
• Account access: login sessions and encrypted Discord access and refresh tokens, used to keep your connection working. Scrimly does not receive your Discord password.
• Community content: server branding, image uploads and image links, maps, zones, sessions, team names, placements, con requests, messages and host access records.
• Hosting subscriptions: Stripe customer and subscription identifiers, plan, payment status and billing period. Stripe collects payment details in its checkout; Scrimly does not store full card numbers.
• Technical information: service logs, request information and rate-limit records used for operation, troubleshooting and abuse prevention. Our hosting providers may process network information such as IP addresses.

Why we process it

We use this information to authenticate users, verify Discord access, display and synchronize maps, deliver chat and host tools, manage subscriptions, prevent abuse and resolve service problems. We do not sell personal information or use it for targeted advertising.

What others can see

Community pages and map previews can be viewed publicly. Your display name, avatar, team name, drop position and protection state may appear to visitors. Session chat is visible to people with access to that chat. Owners and authorized hosts can see the information needed to manage their community, including requests and rosters. Avoid posting sensitive information in public names, images or messages.

Service providers

Scrimly uses Discord for identity and community checks, Supabase for application data and uploaded files, Vercel for hosting and delivery, and Stripe for hosting payments when enabled. These providers process information under their own applicable terms and policies. Opening an externally hosted image may also send a request to that image's host.

Cookies and local storage

We use a necessary login cookie and temporary authorization state to secure sign-in. Your browser may store motion preferences and temporary recovery information for application updates. These are functional features, not advertising trackers. Signing out removes your current login session; it does not delete your account or community content.

Retention and deletion

Community content remains while the community uses Scrimly, including ended-session history. Owners can delete their server in Host desk → Settings. This removes its application records, revokes guest-host access and queues uploaded images for removal. File cleanup is retried if a storage provider is unavailable. Deleting a server does not delete your Discord account or shared Scrimly identity.

Backups, security logs and billing records may remain for their operational retention periods or where required by law. Stripe may retain its transaction records independently. We do not promise immediate removal from backups or third-party systems.

Your choices

You can sign out, revoke Scrimly's authorization in Discord, and ask the operator about access, corrections or deletion of your information. Available rights depend on where you live. Requests may require identity verification; we will consider other people's rights and legal retention duties.

Age and changes

Scrimly is not intended for children under 13 or anyone below the minimum age required by Discord in their country. If you believe a child has supplied information, contact the operator. We may update this policy as the service changes and will update the date above.

Operator and contact

Scrimly is operated by NovaTweaks. For support, privacy requests or billing questions, email scrimlydev@gmail.com.