Terms of Service

These Terms of Service (the "Terms") govern access to and use of the Creator Assistant services, including our websites, setup pages, dashboards, APIs, webhook endpoints, Discord bot (slash commands, verification flows, Liened Downloads, collaborator sharing), Unity runtime integration, and any related software, features, and content that link to these Terms (collectively, the "Service"). The Service is operated by Creator Assistant ("we", "us", or "our").

By accessing, installing, connecting, configuring, or using the Service, you agree to these Terms. If you do not agree, you must not use the Service.

These Terms apply to all users of the Service, including:

• creators, sellers, studios, moderators, and community operators who install or configure the Service (including Liened Downloads, collaborator sharing, and Unity integration)
• Discord server owners, administrators, and staff members who manage settings, roles, verification flows, and protected downloads
• collaborators who share their Jinxxy store or API key with another creator's Server
• end users who connect accounts, submit verification information (including license keys), or receive entitlements, Discord roles, or access to Liened Download archives
• developers or operators who access our APIs, setup pages, or webhook endpoints

Additional terms, policies, feature specific rules, or order terms may apply to certain features. If there is a conflict, the more specific terms control for that feature.

For these Terms:

• "Admin" means a person authorized to configure the Service for a Creator or a Discord server.
• "Connected Provider" means a third party platform or service connected to the Service: Discord, Gumroad, or Jinxxy.
• "Connected Provider Data" means data received from or sent to a Connected Provider, including account identifiers, product references, order or sale references, webhook events, profile metadata, license information, role information, or entitlement related data.
• "Content" means text, images, metadata, settings, product mappings, links, messages, files, and other materials submitted to or made available through the Service.
• "Creator" means a person or entity using the Service to manage product verification, role assignment, entitlements, or community access.
• "Discord Data" means Discord user IDs, guild or server IDs, role IDs, channel IDs, profile information, and related metadata used by the Service.
• "Entitlement" means a verification outcome, product recognition, license recognition, purchase recognition, access right, or role grant produced by or through the Service.
• "Event Logs" means operational, audit, security, sync, and troubleshooting records generated in connection with the Service.
• "Provider Credentials" means access tokens, refresh tokens, API keys, webhook secrets, or similar credentials used to connect a Connected Provider.
• "Purchase Data" means order data, sale records, line items, product IDs, provider order IDs, provider customer identifiers, payment state, refund state, dispute state, purchase timestamps, and related fields.
• "Server" means a Discord server or guild.
• "Liened Downloads" means the feature that routes qualifying attachments from source channels into role-gated archive channels. Archived files remain in Discord (archive channel); the Service does not store file contents externally. The feature supports backfill and autofix of existing messages.
• "Download Route" means a Creator-configured mapping from a source channel to an archive channel, including required roles, role logic (all or any), and allowed file extensions.
• "Download Artifact" means a record of a file archived for Liened Downloads, including source and archive message references and file metadata.
• "Collaborator" means a creator who shares their Jinxxy store or API key with another creator's server for verification, via an invite flow.
• "Collaborator Invite" means a single-use token (with limited validity) used to invite a Collaborator to share their Jinxxy credentials with a Creator's tenant.
• "Manual License" means a Creator-generated license key validated by the Service; keys are stored only as cryptographic hashes, never in plaintext.
• "License Claim" means a canonical record that associates a license (by provider and license key hash) with a Subject. The Service enforces uniqueness and reuse constraints; transfer or re-claim may require admin mediation, cooldown, or explicit release per Creator policy.
• "Provider Customer" means a remembered purchaser record used for matching and auto-discovery of supported products; may include hashed identifiers and display hints.
• "Purchase Fact" means canonical purchase data derived from provider webhooks or API responses.
• "Tenant" means a Creator organization or workspace linked to one or more Servers.
• "Subject" means the Service's internal canonical identity for a user, which may be linked to one or more external accounts.
• "Binding" means a link between a Subject and an external account (e.g., ownership, verification, or manual override).
• "Unity Installation" means a device or client that has integrated with the Service for runtime assertion (license validation) in Unity applications.
• "User" means any person or entity who accesses or uses the Service.
• "Verification Data" means data used to complete a verification flow, including linked accounts, provider identifiers, license keys or hashes, product references, OAuth state data, verification session records, and related metadata.

You must be at least 13 years old to use the Service and old enough to legally consent in your jurisdiction. If you are under the age of majority where you live, you may use the Service only with permission from a parent or legal guardian.

You must also satisfy the eligibility rules of each Connected Provider you use. If Discord, Gumroad, or Jinxxy suspends or restricts your account, your ability to use related parts of the Service may be limited or terminated.

The Service is designed to help Creators and communities manage verification, linked accounts, entitlements, Discord role access, protected downloads, and Unity runtime validation. Depending on the feature set enabled by a Creator, the Service may:

• install and operate a Discord bot in one or more Servers via OAuth (bot and applications.commands scopes)
• provide a setup wizard (/creator-admin setup start or restart) and Connect flow for Gumroad OAuth, Jinxxy, and Discord account linking
• expose slash commands: /creator (status, verify, refresh) and /creator-admin (setup, product, downloads, settings, moderation, collab, stats, analytics, spawn-verify)
• let Creators connect Gumroad or Jinxxy and store Provider Credentials in encrypted form
• receive and process provider webhooks (sale, refund, payment, product events) from Gumroad, Jinxxy, and Collaborator Jinxxy webhooks
• perform historical sync or backfill of sales or orders for connected products
• maintain a product catalog with products from Gumroad, Jinxxy, Discord role (cross-server), and manual sources
• create or update subject records, external accounts, bindings, entitlements, and provider customer records
• match purchases to users through account identifiers, hashed email matching, license-key verification (Gumroad/Jinxxy API or manual licenses), or auto-discovery for remembered purchasers
• project, grant, update, suspend, revoke, or remove Entitlements
• assign, sync, or remove Discord roles based on verification results, role rules, or Creator configuration; optionally auto-verify on guild member join
• support cross-server verification (user must have a required role in an approved source Server)
• operate Liened Downloads: route qualifying attachments from source channels into role-gated archive channels; support backfill and autofix; gate access by required roles (all or any)
• support Collaborator sharing: Creators may invite other Creators via single-use invite links; Collaborators may share API key only or full account (API key plus webhook); Collaborator webhooks route to the owner tenant
• issue Unity runtime assertions (JWTs) for license validation in Unity applications (when enabled)
• support manual licenses (Creator-generated keys stored as hashes), suspicious account marking (quarantine, notify, revoke), and moderation actions (unverify)
• generate analytics, operational metrics, audit events, and Event Logs

The exact features available may vary by Creator, Server, provider, and product.

5.1 Discord account and installation authority

To use Discord bot features, you must have a valid Discord account and sufficient authority to install, configure, or manage the bot in the relevant Server.

By installing or configuring the bot, you represent and warrant that:

• you have the authority to act for the applicable Server, Creator, or organization
• you are authorized to manage roles, channels, settings, and integrations in that Server
• you have the right to submit all information and instructions you provide to the Service

5.2 Connected Provider authority

If you connect Gumroad or Jinxxy, you represent and warrant that:

• you are the lawful owner of that provider account or are authorized to connect it on behalf of its owner
• you have permission to grant the Service access to the provider data needed for the selected features
• the Provider Credentials and configuration you supply are accurate and current

5.3 Creator responsibility for community notices

Creators and Admins are responsible for giving their community any notices required by law or platform policy regarding verification flows, linked accounts, role assignment, data handling, moderation decisions, and external services used in their Server.

6.1 Provider connections

The Service integrates with Connected Providers: Discord, Gumroad, and Jinxxy. By connecting a provider, you instruct us to communicate with that provider as needed to:

• authenticate the connection
• store and maintain connection status
• retrieve account or profile information
• retrieve, import, sync, or backfill product, purchase, order, sale, or license data
• receive and process webhooks or similar provider notifications
• verify purchases, licenses, product ownership, account status, or role eligibility
• maintain, refresh, or disconnect the provider connection

6.2 Gumroad and Jinxxy commerce sync

If a Creator connects Gumroad or Jinxxy, the Service may ingest or process information such as:

• provider user IDs and connected account metadata
• product IDs and product mappings
• sale or order identifiers
• order item identifiers
• license identifiers where applicable
• purchase timestamps
• payment, refund, or dispute status
• customer email addresses or normalized or hashed forms of email addresses
• webhook payloads and historical purchase records

The Service may also perform a historical sync or backfill of sales or orders for connected products where that feature is enabled.

6.3 Webhooks and provider events

The Service receives webhooks from Gumroad (per-tenant), Jinxxy (per-tenant), and Collaborator Jinxxy (per owner-tenant and invite). Webhook payloads are verified using HMAC-SHA256 signatures where a secret is configured; Gumroad may fall back to API verification when no secret is set. Provider events are stored with metadata such as provider, event type, raw payload, signature validation state, tenant or creator association, processing status, error state, and timestamps. Events are deduplicated and processed into Purchase Facts and Entitlements.

6.4 Revocation and refund truth source

Webhooks are the primary channel for revocation and refund updates. The Service treats provider webhooks (sale, refund, dispute events) as the source of truth for Entitlement and role changes. Provider API status checks are used only when necessary (e.g., dispute or refund claims, missing webhooks, or reconciliation). Such lookups are cached and rate limited to avoid excessive provider API usage.

6.5 No control over third party providers

Connected Providers are independent third parties. We do not control their APIs, uptime, product identifiers, event quality, webhook delivery, rate limits, account restrictions, or data accuracy. Providers may change or discontinue features at any time. We are not responsible for losses caused by third party provider actions, omissions, delays, outages, policy changes, or API changes.

7.1 Verification methods

The Service supports verification methods including: Gumroad OAuth (account linking; one linked account may verify all products), Jinxxy account linking or API-key verification, Discord role based verification (cross-server; user must have a required role in an approved source Server), and manual license keys (Creator-generated keys entered by the user; validated against hashed records). Verification may be triggered by: provider webhooks (sale, refund, purchase events), user actions (/creator verify, /creator refresh, Connect flows), or guild member join (when auto-verify on join is enabled). OAuth flows use PKCE and short-lived session tokens.

7.2 Linked identities and subject records

To operate the Service, we may create records that associate one or more external accounts with a single internal subject, profile, or verification record. This may include Discord accounts, provider accounts, email based matching, or Creator configured license records.

7.3 Entitlement projection

The Service transforms verification or purchase information into Entitlements. An Entitlement may represent a verified product, a verified purchase, a verified license, a Discord role grant, access to Liened Download archives, or a Unity runtime assertion.

7.4 Role assignment and removal

If enabled by a Creator, the Service may assign, sync, maintain, or remove Discord roles based on active Entitlements, provider events, configuration changes, revocations, refunds, disputes, security flags, or moderation actions (e.g., unverify). Role rules map products to Discord roles per guild; Creators may configure priority, remove-on-revoke, and cross-server source guild and required role.

7.5 Cross server verification

If enabled by a Creator, the Service may consider a User's role or status in another approved Server as part of a verification or role decision. Cross-server verification is distinct from store-based verification (Gumroad, Jinxxy, manual). The Service issues a signed verification stamp from our backend with a bounded validity window, audience and guild binding rules, and does not treat Discord roles as a long-term source of truth. Creators configure allowed source guilds and required roles.

7.6 Errors and reversals

Verification and Entitlement decisions may change over time. A prior success does not guarantee permanent access. We or the Creator may correct errors, remove access after refunds or disputes, revoke mistaken grants, quarantine suspicious accounts, or update a decision following new provider data.

7.7 License claim and reuse prevention

The Service maintains canonical License Claim records keyed by provider and license key hash, with datastore constraints that prevent or strongly bound reuse. A license may be associated with only one Subject per product and tenant unless Creator policy permits transfer or re-claim (admin mediated, cooldown, or explicit release). Attempts to use the same license key across many accounts or guilds may be classified as suspicious and trigger review, quarantine, or revocation.

7.8 No guarantee of access or timing

We do not guarantee that any verification, sync, backfill, role assignment, or Entitlement update will be instantaneous, continuous, successful, or error free.

To operate the Service, we may process and store information such as:

• Discord account, guild, channel, role, and interaction metadata
• Creator and Admin setup data, tenant policy configuration, and guild links
• Connected Provider account identifiers and profile metadata
• Provider Credentials (OAuth tokens, API keys, webhook secrets), stored in encrypted form
• verification sessions, OAuth state values, PKCE verifier hashes, setup session tokens (short-lived), Collaborator invite tokens (hashed), and temporary state data
• purchase facts, order, sale, refund, dispute, product, and license related records
• normalized or hashed email addresses, provider customer records (hashed identifiers, display hints, confidence), and catalog product links for product resolution
• internal subject, external account, binding, license claim, role rule, guild link, product catalog, purchase fact, provider customer, entitlement, provider connection, download route, download artifact, Unity installation, runtime assertion, collaborator invite, and collaborator connection records
• webhook payloads, webhook event records (with signature status), webhook processing records, and outbox job records (role sync, revocation, notifications)
• audit events, event logs, error logs, security review logs, and fraud or suspicious activity flags
• IP addresses, user agent strings, timestamps, correlation IDs, and related operational metadata
• session cookies, authentication records, and account connection status
• analytics and telemetry events relating to command usage, verification flows, product activity, suspicious activity review, and Service performance

Some data may be stored temporarily in in memory systems, key value stores, caches, or job queues for setup flows, OAuth flows, webhook processing, retry handling, or rate limiting.

9.1 Security measures

We use reasonable technical and organizational measures designed to protect the Service and the data we process. These measures may include: encryption for stored Provider Credentials (OAuth tokens, API keys, webhook secrets); hashing (e.g., SHA-256) for license keys, invite tokens, and email identifiers, with plaintext never stored where hashing is used; display hints (e.g., email prefixes) for UI only where full values are not needed; session protections, PKCE for OAuth, state validation, expiration controls for setup and verification sessions, and access restrictions.

9.2 Abuse controls and rate limiting

We apply abuse controls to protect the Service and Connected Providers. These may include: per-IP and per-account throttles for verification attempts; per-guild throttles for role sync operations; replay protection for verification sessions (nonce, state, TTL); and step-up actions for repeated failures (e.g., captcha, cooldown, or manual review). Rate limiting applies to verification, connect, and collaborator flows. Provider API lookups are cached and rate limited.

9.3 No absolute security guarantee

No system is perfectly secure. You acknowledge that the Service may still be subject to unauthorized access, outages, provider compromise, configuration errors, credential misuse, malicious actors, or unforeseen failures.

9.4 Your obligations

You are responsible for keeping your own accounts, servers, devices, and provider credentials secure. You must promptly rotate or revoke credentials if you suspect compromise.

9.5 Secrets and license data

Do not submit secrets, keys, or sensitive data in public channels. If the Service accepts license keys or similar values, you are responsible for entering them in the intended private flow.

If you are a Creator or Admin, you are solely responsible for:

• deciding whether to use the Service in a Server or product community
• choosing what products, licenses, providers, or roles to connect
• configuring role rules, product mappings, download routes (source channel, archive channel, required roles, role logic, allowed extensions), cross-server source guilds, tenant policy (e.g., verification scope, revocation behavior, suspicious account behavior), and verification policies correctly
• ensuring that your product listings, license terms, refund practices, support practices, and access policies are lawful and clearly communicated
• ensuring that you have a lawful basis and any required notices or consents for personal data you ask the Service to process on your behalf
• ensuring that bot permissions, role hierarchy, and Server settings are configured correctly
• reviewing suspicious activity, duplicates, disputes, false positives, false negatives, and other edge cases as needed
• managing Collaborator invites and connections, and ensuring Collaborators understand what data they share
• using moderation tools (mark suspicious, clear suspicious, unverify) appropriately and in compliance with your community rules

You understand that a misconfiguration by a Creator or Admin can lead to mistaken role grants, missed role grants, revoked access, duplicate verification outcomes, or inconsistent verification results.

If you are an end user verifying a purchase or account, you are responsible for:

• using your own accounts and truthful information
• not impersonating another person or attempting to verify purchases you are not entitled to use
• keeping your provider accounts and license information secure
• understanding that a Creator's own product, refund, moderation, and community rules may separately apply to you

Your transaction for a product may be with the Creator, Gumroad, or Jinxxy, not with us. Except where expressly stated, we are not the merchant of record, seller, reseller, licensor, or payment processor for Creator products.

You may not, and may not assist or permit others to:

• use the Service in violation of law, platform rules, or third party rights
• use the Service to commit fraud, deception, chargeback abuse, license key reuse or sharing in violation of Creator policy, or unauthorized access
• attempt to bypass verification requirements, role rules, account linking controls, Liened Download access controls, or security checks
• upload, transmit, or distribute malware, malicious code, phishing content, or harmful automation
• interfere with or abuse webhooks, APIs, rate limits, retries, job queues, or provider connections
• scrape or harvest personal data through the Service without a lawful basis and authorization
• use the Service to stalk, harass, dox, intimidate, or discriminate against others
• use the Service to make access decisions in a way that violates law or protected rights
• probe, scan, reverse engineer, or test the Service for vulnerabilities without our written authorization, except where non waivable law permits a narrower right
• use the Service in a way that burdens or disrupts our infrastructure or a Connected Provider

We may investigate violations and take appropriate action, including suspension, revocation, or reporting.

13.1 Your Content

You retain ownership of your Content, subject to the rights you grant in these Terms.

13.2 License to us

You grant us a worldwide, non exclusive, royalty free license to host, store, reproduce, adapt, process, transmit, display, and use your Content only as necessary to operate, secure, maintain, improve, troubleshoot, and provide the Service and to comply with law.

13.3 Feedback

If you provide suggestions, feedback, ideas, or recommendations, you grant us the right to use them without restriction or compensation.

13.4 Our rights

The Service, including our software, code, design, names, branding, interfaces, documentation, and related materials, is owned by us or our licensors and is protected by intellectual property laws.

Our Privacy Policy explains how we collect, use, disclose, retain, and otherwise process personal information. The Privacy Policy is incorporated into these Terms by reference.

Privacy Policy: /legal/privacy-policy

If you are a Creator or Admin, you acknowledge that your own privacy notices may also be required for your end users depending on your jurisdiction, your product, and how you configure the Service.

We may collect or generate analytics, telemetry, and Event Logs to operate and improve the Service, monitor feature usage, measure verification performance, detect abuse, diagnose failures, support users, and enforce these Terms.

This may include administrative actions, command usage, setup events, verification started or completed events, verification failures, product activity, suspicious activity signals, and role sync outcomes.

We may limit, suspend, quarantine, revoke, or terminate access to the Service or any portion of it if we reasonably believe that:

• you violated these Terms or applicable law
• your use presents a security, fraud, abuse, or operational risk
• a Connected Provider requires us to do so
• a refund, dispute, revocation, or provider event justifies an Entitlement or role change
• your configuration or conduct exposes us, other users, or a Connected Provider to harm or liability

We may take these actions with or without prior notice where reasonably necessary.

The Service is offered on an evolving basis. We may modify, add, suspend, or remove features at any time. Some features may be identified as alpha, beta, preview, experimental, or early access. Such features may be incomplete, unstable, or changed without notice.

We do not guarantee that the Service or any feature will remain available or compatible with any specific platform, provider API, browser, server setup, or Discord permission model.

17.1 Support

We provide support through documentation, Discord, and email (contact@yucp.club). We do not commit to specific response times or service level agreements unless expressly agreed in a separate written agreement for paid plans. Support is provided on a best-effort basis.

Some parts of the Service may be free, while others may require payment now or in the future. If paid features apply, we will disclose the relevant pricing, billing terms, and feature scope at the point of purchase or in a separate written agreement.

Unless expressly stated otherwise:

• fees are non refundable except as required by law or expressly stated by us
• taxes are your responsibility
• failure to pay may result in downgrade, suspension, or termination of paid features
• paid plans renew automatically at the end of each billing period (monthly or annually, as applicable) unless you cancel before the renewal date
• cancellation takes effect at the end of the current billing period; you retain access until then
• trial periods, if offered, convert to paid subscriptions at the end of the trial unless you cancel
• we may change prices with at least 30 days' notice; continued use after the change constitutes acceptance

Your use of Connected Providers and other third party services is governed by their own terms and policies. This includes Discord, Gumroad, Jinxxy, Unity, analytics providers, cloud providers, hosting providers, and any marketplace or identity service connected to the Service.

We are not responsible for third party services or third party content, including their:

• policies and legal terms
• outages and downtime
• API or platform changes
• payment processing
• product availability
• moderation actions
• account suspensions
• privacy or security practices

References to third party names, brands, or logos are for identification only and do not imply endorsement, partnership, or affiliation unless we expressly state otherwise.

To the maximum extent permitted by law, the Service is provided "as is" and "as available". We disclaim all warranties, whether express, implied, statutory, or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title, quiet enjoyment, and non infringement.

We do not warrant that:

• the Service will be uninterrupted, timely, secure, or error free
• provider data will be accurate, complete, or current
• verification outcomes will always be correct
• role sync or Entitlements will always function as intended
• security measures will prevent every unauthorized act or incident

To the maximum extent permitted by law, we will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, business opportunity, or business interruption, arising out of or relating to the Service, even if we were advised of the possibility of such damages.

To the maximum extent permitted by law, our total liability for all claims arising out of or relating to the Service will not exceed the greater of:

• the amount you paid us for the Service in the three months before the event giving rise to the claim, or
• USD $100

Some jurisdictions do not allow certain limitations. In those jurisdictions, some parts of this section may not apply.

You agree to defend, indemnify, and hold harmless us and our affiliates, licensors, service providers, officers, directors, employees, contractors, and agents from and against any claims, losses, liabilities, damages, judgments, settlements, costs, and expenses, including reasonable legal fees, arising out of or related to:

• your use of the Service
• your Content
• your products, listings, customer interactions, or community rules
• your Server configuration or provider connections
• your violation of these Terms, applicable law, or third party rights

You may stop using the Service at any time.

We may suspend or terminate your access or any part of the Service at any time as described in these Terms. Upon termination, your right to use the Service ends immediately.

Termination does not affect any rights or obligations that by their nature should survive, including sections relating to intellectual property, disclaimers, limitations of liability, indemnification, dispute resolution, and accrued payment obligations.

Following disconnection, suspension, or termination, we may retain certain data for legitimate business and legal purposes, including security, fraud prevention, audit, dispute handling, legal compliance, enforcement, backup integrity, and recordkeeping.

We may also delete or de identify data in accordance with our retention practices and applicable law.

Creators may request an export of their configuration data (role rules, product mappings, download routes, tenant settings) before or shortly after termination, subject to our then-current export capabilities and retention schedule. Contact contact@yucp.club to request an export. We do not guarantee export of audit logs, webhook payloads, or other operational data.

You may not use the Service if prohibited by applicable export control, sanctions, or trade laws. You represent and warrant that you are not located in, organized in, or ordinarily resident in a jurisdiction subject to applicable restrictions that would make your use unlawful.

If you believe that content made available through the Service infringes your copyright, please send a DMCA-compliant notice to our designated agent:

Creator Assistant
Copyright Agent: Yeusepe
Email: yeusepe@yucp.club

Please include: (1) identification of the copyrighted work claimed to have been infringed; (2) identification of the allegedly infringing material and its location; (3) your contact information; (4) a statement that you have a good-faith belief the use is not authorized; (5) a statement under penalty of perjury that the information is accurate and you are authorized to act; and (6) your physical or electronic signature. We may file designated agent information with the U.S. Copyright Office where applicable.

27.1 Governing law

These Terms are governed by the laws of Colombia, with venue in Bogotá, excluding conflict of law rules.

27.2 Venue

Except where applicable law requires otherwise, disputes arising out of or relating to these Terms or the Service will be resolved exclusively in the courts located in Bogotá, Colombia.

27.3 Informal resolution

Before initiating formal legal proceedings, you agree to contact us at contact@yucp.club and attempt to resolve the dispute informally for at least 30 days. We will do the same before bringing a claim against you. This informal resolution process does not apply to claims for injunctive relief or intellectual property infringement.

We may update these Terms from time to time. If we make a material change, we may provide notice through the Service, by email, through a setup page, in a dashboard, or by other reasonable means. The updated Terms will become effective on the stated effective date.

Your continued use of the Service after the effective date of updated Terms means you accept the revised Terms.

• Entire agreement. These Terms and any incorporated policies or feature specific terms are the entire agreement between you and us regarding the Service.
• Severability. If any provision is held unenforceable, the remaining provisions remain in effect.
• Waiver. A failure to enforce any provision is not a waiver.
• Assignment. You may not assign these Terms without our prior written consent. We may assign these Terms in connection with a merger, acquisition, financing, reorganization, or sale of assets.
• No third party beneficiaries. These Terms do not create third party beneficiary rights except where expressly stated.
• Contact. Questions may be sent to contact@yucp.club.