Policy
Privacy
How Great North Gaming handles your RaidCreator account, saved work, community activity, and billing information.
Last updated: October 8, 2026. Great North Gaming is responsible for RaidCreator's handling of personal information. Privacy questions and requests: admin@greatnorthgaming.com.
Great North Gaming
Data map
Information RaidCreator may process
The information we process depends on the features you use. This policy describes what we collect, why we use it, who receives it, and the choices available to you.
Account and authentication
- Supabase Auth manages account sessions, email/password sign-in, Google sign-in, and authentication cookies.
- Google sign-in can provide basic OAuth profile metadata such as name, email, avatar, or picture depending on the account and provider settings.
- RaidCreator uses this information to authenticate users, show account controls, protect private Library pages, and connect creator profile display data.
Builder and Library content
- Private packs can include pack names, pack types, manifests, layout JSON, type configuration, NPC configuration, vendor configuration, version data, folders, and preview thumbnails.
- Layout JSON can include creator-authored prefab placement, anchor placement, rotations, positions, pack settings, and export-related metadata.
- Preview thumbnails and community prefab thumbnails can be stored through server-managed storage paths.
Community activity
- Creator profiles can include handle, display name, bio, avatar URL, banner URL, website URL, creator XP, levels, and badges.
- Published prefab listings can include names, descriptions, tags, facets, snapshots, thumbnails, status, stars, saves, adds, views, and reports.
- Private shares, imported prefabs, creator follows, notification records, notification preferences, and moderation reports are stored to support community workflows.
Pro Deploy and paired servers
- Pairing stores your chosen server name, runtime-reported server identity and version, connection duration, connection status, and scoped credential hashes. RaidCreator does not request your FTP, SFTP, or RCON passwords.
- The server reports installed-pack metadata and observed Rust administrator names, Steam IDs, and online status. We store selected test admins so you can run authorized pack tools. Selecting an admin does not grant them Rust administrator privileges.
- Deployment and tool records include the initiating creator, pack identity, checksums, status, timestamps, and result messages. Private deployment artifacts contain the exported pack files and sign artwork needed to install that pack.
- Inviting another creator shares connection details, the observed and saved admin roster, installed-pack metadata, and recent operation records with accepted server admins. Runtime credentials and downloadable deployment artifacts are not exposed through shared access.
- Completed or failed deployment artifacts older than 30 days are pruned when their initiating creator next submits a job. Unconfirmed artifacts are retained for recovery, and operation metadata remains. Disconnecting revokes access; it does not immediately delete activity records or uninstall packs on your server.
Subscriptions and payment information
- Stripe collects payment details through its checkout and billing portal, processes subscription payments, and handles payment authentication. RaidCreator does not store your full card number or card security code.
- We store billing identifiers and records needed to connect your RaidCreator account to its Stripe customer and subscription, including plan, payment and subscription status, billing periods, cancellation state, invoice references, and billing event records.
- We use verified billing records to grant or end paid Pro access, show subscription information and invoices, handle support, and reconcile payments. A contact email saved in Stripe or Link may differ from your RaidCreator sign-in email; paid access is linked to your RaidCreator account.
- If you use Stripe Link, Stripe may remember contact and payment information across checkout sessions according to its own privacy notice and your Link settings. Signing out of RaidCreator does not necessarily sign you out of Link.
Device, cookies, and local storage
- The app uses cookies for Supabase sessions and a community viewer id cookie for anonymous view dedupe.
- Local storage can hold theme preference, dev/offline testing data, builder draft fallback data, clipboard state, viewport preferences, and view-dedupe markers.
- Server logs and provider infrastructure can process technical request data needed to operate, secure, and debug the service.
- Payment providers may use their own cookies or browser storage for checkout, authentication, and fraud prevention. You can manage browser storage, but blocking necessary cookies may prevent sign-in or checkout, and clearing local draft data may remove an unsaved fallback copy.
Sharing and service providers
- Great North Gaming operates RaidCreator. We share information with service providers where needed to run the service: Supabase for authentication, database and storage; Google when you choose Google sign-in; Stripe for payments; and infrastructure providers for hosting and delivery.
- Your public profile and published content are visible to other users and visitors according to the features you use. Private shares disclose shared content to the recipients you choose. Other users can retain copies they have already imported or exported.
- Support correspondence and information you send us may be used to investigate your request, verify account ownership, and resolve account, billing, or privacy issues. Please do not send passwords or full card details.
- We may disclose information when legally required, to address fraud or security threats, or to protect lawful rights. If ownership of the service changes, information may transfer as part of that transaction, subject to applicable privacy obligations and notice requirements.
- Providers may process information outside your province or country, where it can be subject to local laws and lawful access requests. We do not promise storage in a particular country. Contact us for questions about provider processing or international transfers.
How the information is used
Information supports the features you use and the operation of the service.
- Pair servers, deliver approved pack files, run authorized test tools, manage shared server access, and reconcile deployment results.
- Provide the builder, Library, Community, account, notification, and export workflows.
- Authenticate users, protect private content, and show profile-backed account controls.
- Generate, store, retain, replace, or delete thumbnails through supported save and publish flows.
- Track public community interactions such as views, stars, saves, imports, follows, reports, and updates.
- Troubleshoot errors, prevent abuse, apply moderation decisions, and improve product reliability.
- Process subscriptions, determine Pro access, maintain billing records, respond to support and privacy requests, and meet legal obligations. We obtain consent where required and use information only for the disclosed purposes or other purposes permitted by law.
User choices
Manage your content and preferences, or contact us to exercise your privacy rights.
- You can disconnect a paired server, remove invited admins from a server you own, or leave shared server access through Account Servers. These controls remain available on Free.
- You can choose what to publish publicly; private Library packs are separate from public Community prefab listings.
- You can edit creator profile fields from account/community surfaces where those controls are available.
- You can change notification preferences from account notification settings.
- You can remove or hide public listings through supported creator or admin moderation flows.
- For access, correction, account deletion, consent withdrawal, or a privacy complaint, contact the person responsible for RaidCreator privacy at admin@greatnorthgaming.com. We may need to verify your identity and will respond within the time required by applicable law, explaining any lawful restriction on your request.
- You may withdraw consent to optional processing, subject to legal or contractual restrictions. Some information is necessary to provide an account or subscription, so withdrawal may affect those services. You can also raise unresolved concerns with the privacy regulator responsible for your location.
- Cancel a paid subscription separately through Account Billing before requesting account deletion, or ask support to help with both. Removing public content or deleting an account cannot recall copies already retained by other users.
Security, retention, children, and providers
We limit retention to service needs and lawful purposes. No online service can guarantee complete security.
We use authentication, server-side authorization, and provider security controls to protect account and private Library information. Keep your sign-in method secure. If a security incident affects personal information, we will investigate and provide any notices required by law.
We retain account and saved content to provide the features you use. Pro expiration alone does not delete your work. Retention also depends on payment and accounting obligations, security investigations, disputes, and legal requirements. Deletion requests may leave records we must lawfully retain and copies awaiting removal through provider backup processes; we will explain applicable limits when handling your request.
RaidCreator is not directed at children. Users must have legal capacity to agree to the Terms or use the service with a responsible parent or guardian's permission and supervision. Contact us if you believe a child has provided personal information without the consent required by applicable law. We will review and take appropriate action.
We will update this page when our practices change and provide appropriate notice of material changes. If a new use requires consent, we will seek it before that use. The provider policies below explain their own practices.