Legal

Terms of Service and Privacy Policy for Revival Network and the HCFR server.

Terms of Service

Effective 3 September 2026.

Agreement

Revival Network operates this website, the store, and related services. HCFR is the Minecraft server on that network. Using the site, the store, or HCFR means you accept these terms and the server rules.

Accounts

You can sign in with email and password, Discord, or Google. Creating a website account requires linking a Minecraft account that has already joined the network. Do not share accounts. Purchases go to the Minecraft username entered at checkout.

We may limit or remove accounts for rule breaks, fraud, or abuse of the website or API.

Conduct

Play and chat follow the rules. Staff can mute, ban, or blacklist under the published punishments policy. Bug reports go through tickets, not public chat. Do not attack, scrape, or overload the site or API.

Store

The store sells digital ranks, credits, and command unlocks. Checkout asks for a Minecraft username that has already joined the network. You can buy for yourself or for someone else without signing in.

Items are fulfilled after payment. Refunds are handled case by case through support tickets. Chargebacks may revoke entitlements.

Subscriptions are billed by Stripe until you cancel them.

Availability

The website, store, and HCFR are provided as-is. We do not promise uninterrupted access, and we can change or stop features without notice.

Changes and contact

We can update these terms on this page. The effective date at the top is the current version. Use a support ticket for billing or other disputes.


Privacy Policy

Effective 3 September 2026.

This policy describes what Revival Network stores for the website, store, and related services, and how HCFR game data is used on this site. It matches how the services work today.

What we store

Account. Email address, a password hash if you use password sign-in, display name (from your linked Minecraft username), role, email verification status, and lockout counters after failed logins. We do not keep a mailing or billing address on your account.

Sign-in connections. If you use Discord, we store your Discord user id and email. If you use Google, we store your Google account id and email. We do not keep Discord usernames or Google display names.

Minecraft. The UUID and username linked to your website account.

Tickets. Category, subject, status, assignment, and message text. Ticket records do not include IP addresses. Anything you type in a ticket is stored as you wrote it.

Store. Minecraft username and UUID for the order, line items, amounts, and Stripe checkout, payment, and subscription ids. We do not store card numbers. Stripe handles payment details and may collect a billing address for tax.

Sessions. A signed-in session on our servers, tied to cookies in your browser. See Cookies below.

Staff and operations. Audit entries for actions such as registration and role changes. Role changes may record IP address and browser user agent. In-game entitlement claims may record the claim IP. Staff-uploaded blog images are stored and served publicly.

Game data. Player profiles, stats, factions, events, and punishments come from the HCFR game API. Staff with punishment permissions can see network IP addresses that public pages strip. Those are connection IPs from the game, not mailing addresses.

What we do not do

  • We do not run website analytics products (no Google Analytics, Plausible, or similar).
  • There is no self-service account deletion or data-export button. Ask by ticket.
  • We do not keep a mailing or billing address on your Revival Network account.

How we use it

We use this data to sign you in, link Minecraft, run the store, deliver purchases, handle tickets, moderate HCFR, and keep the site secure. Email is used to verify your address and reset your password. We do not keep a history of those emails in the database.

Who else sees it

  • Stripe — checkout, payments, and subscriptions. If you are signed in, we can prefill the email Stripe already has for you.
  • Discord and Google — only if you choose that sign-in. They authenticate you; we keep the id and email described above.
  • Email delivery — verification and password-reset messages are sent through our mail provider.
  • File storage — blog images uploaded by staff.
  • HCFR game API — player lookup, stats, punishments, and live server data shown on the site.
  • Staff — people with the right permissions can read tickets (including internal notes), orders and fulfillment, audit entries, and, for some roles, game punishment IPs.

The homepage Discord widget is Discord's embed. Discord may set its own cookies there. That is not a cookie we set.

Cookies

We set a small number of first-party cookies. The session cookie is HttpOnly. A copy of the CSRF token may also be kept in sessionStorage so the site can submit forms.

CookiePurposeHow long
SessionKeeps you signed inUp to 7 days; refreshed while you use the site
CSRFProtects form submissions7 days
OnboardingFinishes Minecraft signup24 hours

We also use your IP briefly to rate-limit requests. Those counters are temporary.

How long we keep it

Sessions last up to 7 days and drop after about 12 hours of inactivity. Website accounts, Minecraft links, tickets, and orders stay until we remove them. Short-lived signup and password-reset tokens expire on their own (hours to a day). Game API responses may be cached for seconds.

Children

You must be old enough to use Minecraft and create an account. We do not knowingly collect personal information from children under 13. If you think we have, open a ticket and we will remove it.

Your requests

You can review and update much of your account under Account(email, password, connections, Minecraft link). For access, correction, or deletion of data we hold, open a support ticket. We do not have an automated export or delete flow today.

Changes

We can update this policy on this page. The effective date at the top is the current version.