SKIDWARE
Terms of ServicePrivacy PolicyBack to forum ↗

Privacy Policy

Effective November 9, 2026

This policy describes how Skidware community administration handles personal information in the Skidware forum. It covers the forum, its registration and login pages, and initial owner setup. Contact bromine34@proton.me with privacy questions or requests.

1. Information the forum uses

  • Account information: your email address, username, account identifier, creation time, role, forum-access status, invitation reference when applicable, and suspension status. Buyer accounts use the same account system and can manage purchases without forum membership. We normalize email addresses for sign-in and store a salted password hash rather than a plain-text password.
  • Contributions: discussion titles, categories, posts, replies, shoutbox messages, author identifiers, timestamps, and thread moderation settings.
  • Member profiles: your permanent forum UID, optional bio and status, uploaded avatar and banner, and a list of your recent forum contributions. Profile posts store comment text, the author, the profile it appears on, and the time posted. We store which account liked each post to count likes and let you remove yours. Signed-in members can view active profiles, their posts, and like counts. You can replace or remove your images from the profile editor.
  • Invitations and administration: invitation labels, creator and redemption references, expiry and revocation status, and administrative audit entries identifying an action, its administrator, its target, and its time. Invitation secrets are stored as hashes.
  • Sessions and security: hashed session tokens, account references, creation and expiry times, and rate-limit records. Rate-limit keys include hashed connecting IP addresses and hashed sign-in email addresses, or account identifiers, depending on the action.
  • Optional Discord sign-in: when this option is available and you choose it, your Discord user identifier and username, and a verified email address for Discord registration. Connecting Discord to an existing account keeps that account's existing forum email. We also use temporary authorization state to finish the sign-in securely.
  • Human verification: Cloudflare Turnstile processes browser, device and network information to distinguish visitors from automated abuse. The forum sends the verification token and, when available, your connecting IP address to Cloudflare for validation. The forum does not store verification tokens.
  • Purchases: R6 purchase approval is recorded on your account and changes are logged for administrators. If you start Stripe checkout when it is available, the forum sends your member UID, selected product, plan and order identifier to Stripe. It records the checkout, subscription, invoice, plan and fulfillment identifiers needed to deliver the purchased license and apply the first renewal discount. It verifies signed payment events before issuing a license.
  • Licenses: the license service associates your forum account identifier with linked license hashes, masked labels, status, activation and expiry information. Staff can create, link, extend or revoke licenses and these actions are audited. When staff link an existing key, the forum hashes it before contacting the license service. Keys generated from paid purchases are stored encrypted by the license service and can be revealed by their signed-in owner through My licenses. Keys created manually by staff have 15-minute recovery when retrying the same creation request.
  • Messages to us: information you choose to include in support, privacy, or moderation correspondence.

Security hashes are pseudonymous identifiers, not anonymous data. The forum receives your IP address to apply limits. Hosting infrastructure may also process IP addresses, request metadata, and security logs.

2. Why information is used

We use this information to create and authenticate accounts, check invitations and membership, publish contributions to members, maintain discussions, prevent abuse, investigate reports, moderate access, and respond to requests.

Where applicable data-protection law requires a legal basis, the relevant purposes include providing the forum service you request, our legitimate interests in maintaining and securing the community, and meeting legal obligations where those arise.

3. Who can see information

Other signed-in members can see your username and the content you publish, along with associated timestamps and role information where shown. Your email and password hash are not included in the member-facing forum responses. The owner and admins can view membership and invitation records in the admin panel. Moderation permissions depend on the staff member's role.

The administration has access to the underlying data needed to operate the service. Hosting providers process information to deliver, store, and secure the forum. We may also need to disclose information to address a valid legal requirement or investigate abuse, subject to applicable law. Invite-only access cannot prevent another member from copying or sharing what they can read.

4. Cookies and session validity

The forum uses an authentication cookie named __Host-skid_session on its HTTPS website. It holds a random session token; the database stores its hash. The cookie is restricted to the host, is marked Secure and HttpOnly, and uses SameSite=Lax. It is used to recognize a signed-in member, rather than for advertising.

A forum session is valid for up to seven days. Signing out clears the current cookie and deletes that session record. Suspending an account invalidates its forum sessions. Expiration prevents further authentication but does not automatically delete the expired database row. Blocking or clearing the cookie prevents continued signed-in use.

The forum application does not currently include advertising, third-party analytics, or marketing cookies. Hosting and security services may use their own technical cookies or request logs; their processing is not limited to the forum cookie described here.

If you choose Discord sign-in when it is available, a separate temporary authentication cookie binds the authorization attempt to your browser. Its validity is limited to five minutes. The corresponding authorization records have the same short validity and may remain until a later cleanup request removes them.

5. Hosting and owner verification

The forum runs on OpenAI Sites and Cloudflare infrastructure, including Cloudflare database storage and object storage for profile images. These providers may process traffic and technical information under their own applicable terms and policies. See OpenAI's Privacy Policy and Cloudflare's Privacy Policy. This policy makes no promise that all processing takes place in a particular country.

Initial owner setup uses ChatGPT sign-in information, including the owner's account identifier and email, to verify site ownership. Ordinary forum registration and login use the forum's own accounts, with email/password or optional Discord authentication when enabled. The forum code does not send posts or passwords to an AI model, and the forum has no feature for selling account information or targeting advertising.

Choosing Discord sends you to Discord to authorize basic account identification and email access. We use a short-lived token to obtain that profile, then discard it; the forum does not retain Discord access or refresh tokens. We do not request permission to read messages or join servers. Discord handles its own sign-in page under Discord's Privacy Policy. Your Discord password is never entered into the forum.

Login and registration use Cloudflare Turnstile, which loads a verification script from Cloudflare. Cloudflare decides whether an interaction is needed. Its processing is described in the Cloudflare Privacy Policy linked above. A failed or expired check requires a new verification before the forum accepts the authentication request.

When checkout is available, Stripe collects your payment and billing details on its checkout page and processes them under Stripe's Privacy Policy. The forum does not receive your full payment card details.

6. Retention and removal

Accounts, contributions, invitation records, connected Discord identifiers, and audit entries currently remain in the database unless removed through moderation or administration. The application does not automatically delete them after a fixed retention period. Session validity is separate from record retention. Expired rate-limit and temporary Discord authorization records are removed in bounded batches during later requests, so removal is not necessarily immediate.

There is no self-service account-deletion tool. Email us to request removal or ask about information we hold. We review related records, security needs, and applicable legal requirements. Provider logs or backups may have separate retention and removal processes; deleting a forum record is not a promise of immediate removal from every provider system.

7. Your choices and requests

Depending on the law that applies to you, you may have rights to access, correct, receive a copy of, or request deletion of personal information, restrict or object to processing, or complain to an appropriate data-protection authority. We handle requests manually and may reasonably verify your identity before disclosing or changing account information.

Contact bromine34@proton.me, include your forum username and the nature of the request, and do not send your password or active invitation code. We handle requests in line with applicable law.

8. Scope and updates

Links to downloads, radar tools, and other websites lead to services with their own data practices and notices. This forum policy does not describe all processing by those services. We may update this policy to reflect changes in the forum, with material changes brought to members' attention where practical. A policy update alone does not authorize unrelated uses of information previously collected.

Skidware Forumbromine34@proton.me
Terms of ServicePrivacy Policy