1. Who handles your information
Blockyfy, the independent studio identified in the Service provider section of our Membership terms, controls the membership records described here. Privacy requests can be sent to contact@blockyfy.net.
2. Information we collect
- Checkout and membership data: email address, selected plan, Stripe customer and subscription references, payment status, billing period and cancellation status.
- Discord data: the username entered at checkout, Discord user identifier after verification, server membership, verification status and supporter-role status.
- Minecraft data: the username you provide, the verified profile username and UUID, and verification or authentication status and timestamps when used for an applicable build or test.
- Service and security records: webhook references, verification attempts and timestamps, administrative changes and technical records needed to diagnose errors, prevent abuse and protect the service.
- Messages: information you send when contacting support.
Stripe collects payment-card details on its own checkout pages. Blockyfy does not receive or store your full card number or card security code.
3. How we use information
- Confirm subscription status and deliver the benefits listed for your plan.
- Match a paid membership to the correct Discord account, send one-time verification and manage supporter roles.
- Use a Minecraft username for access authentication when an eligible test build enables that feature.
- Process cancellation, plan corrections, support and refund requests.
- Prevent fraud, investigate abuse, secure the service and maintain audit records.
- Meet accounting, dispute-handling and other legal obligations.
Blockyfy does not sell membership information and does not use it for third-party behavioral advertising.
5. Retention and security
Operational membership data is kept while a membership is active. After Stripe reports that it has ended, identifying subscription-profile data in Blockyfy's Gate is automatically deleted or de-identified within 30 days. Stripe event identifiers used for deduplication are kept for 30 days, and administrative correction history is kept for no more than 180 days. Short-lived verification challenges and sessions expire sooner.
If Discord has not yet accepted removal of a no-longer-entitled supporter role, the Discord user ID may remain only in a restricted revocation record while Blockyfy retries that removal. It is deleted after revocation succeeds when no other active membership or Minecraft binding still uses it.
A minimal subscription-ID tombstone may be retained after erasure to stop delayed or replayed Stripe events from recreating access. It does not retain the checkout email, Stripe customer ID, Discord username or user ID, Minecraft username or UUID, verification token, or administrative correction history. Stripe may retain separate billing, fraud-prevention, accounting or legal records under its own policy and applicable law.
Blockyfy uses access controls, restricted service credentials and one-time verification links to protect membership records. No online service can guarantee absolute security, so suspected misuse should be reported promptly.
6. Your choices and rights
You may ask Blockyfy to provide, correct or delete personal information, or object to or restrict certain uses where applicable. Include the checkout email and enough information to identify the membership, but never send a full card number or password. If a paid membership is still active, Blockyfy must first end it in Stripe so billing does not continue after service data is erased. Blockyfy has an authenticated administrative deletion procedure for this request; the limited anti-replay tombstone described above and records required for billing, fraud prevention or law may still be retained.
You can correct an incorrectly entered Discord or Minecraft username by contacting contact@blockyfy.net. You can manage or cancel billing through the Stripe customer portal.
7. Public website and external links
Blockyfy does not currently place advertising or analytics cookies on the public site. GitHub Pages and Google Fonts may receive ordinary connection information such as IP address and browser details when pages or fonts are requested. Links to Stripe, Discord and social platforms take you to services with their own privacy practices.
8. Younger users
A purchaser must be able to enter into the membership agreement or have a parent or legal guardian make and authorize the purchase. If you believe a child submitted information without appropriate authorization, contact Blockyfy so the request can be reviewed.
9. Updates and contact
If this policy changes materially, Blockyfy will update the effective date and provide reasonable notice where appropriate. Questions and privacy requests can be sent to contact@blockyfy.net.