1. Overview

HiveMoments subscriptions and purchases may be billed through HiveMoments checkout flows or through a third-party billing provider or merchant of record, depending on the transaction. Your bank or card statement may show HiveMoments, the billing provider, or another billing descriptor disclosed at checkout.

This Refund Policy explains how HiveMoments reviews refund requests. It does not limit any rights you may have under applicable law, and any mandatory consumer protections that apply to your purchase will continue to apply.

• Some purchases may be recurring subscriptions, while others may be one-time charges, depending on the product or offer presented at checkout.
• Checkout, tax, payment processing, and billing support may involve a third-party billing provider or merchant of record for the transaction.
• Payments are processed securely via Stripe.

2. Subscription Billing

If you start a paid subscription, you authorize recurring charges at the interval shown at checkout until the subscription is canceled. It is your responsibility to review the renewal terms shown at purchase and to cancel before the next renewal date if you do not want to be charged again.

Unless otherwise stated at checkout or required by law, canceling a subscription stops future renewals but does not automatically refund the current billing period after the charge has already been processed.

• Renewal timing, billing frequency, and price are shown during checkout or in the applicable billing flow.
• If a plan changes, the new billing terms apply only as described at checkout, in your account, or in the billing notice associated with the change.
• One-time purchases are charged once unless a recurring billing relationship is clearly disclosed before checkout is completed.

3. Refund Eligibility

Refund requests are reviewed case by case. HiveMoments does not promise automatic refunds in every situation, but it will consider refund requests in a fair and commercially reasonable manner based on the facts of the transaction and any legal rights that apply.

Whether a refund is approved may depend on factors such as when the request is made, whether the charge appears to be duplicate or unauthorized, whether there was a technical failure that materially prevented use of the purchased service, whether the request relates to an accidental renewal reported promptly, and what applicable law requires.

• Duplicate charges or clearly incorrect billing may qualify for refund review.
• A serious technical service failure that prevented reasonable access to the purchased service, and that HiveMoments could not correct within a reasonable time, may support a refund request.
• A subscription renewal reported promptly after billing, particularly where there was little or no use after renewal, may be considered for discretionary refund review.
• Where applicable law gives you a right to cancel or receive a refund, HiveMoments and the billing provider or merchant of record involved in the transaction will review the request accordingly.
• Event purchases are generally non-refundable once the event has been created or used.
• Subscription fees are non-refundable except where required by law or explicitly stated.

4. Non-Refundable Cases

Unless required by law or approved in HiveMoments’ discretion, some charges are generally not refundable. The examples below are intended to explain common situations and are not meant to override any non-waivable rights you may have.

• Partial billing periods after cancellation where the service remained available during that period.
• Requests based only on a change of mind after the purchased service was made available and materially used.
• Charges associated with misuse, abuse, fraud, charge evasion, or accounts or events that violated HiveMoments policies.
• Charges raised outside a reasonable review window where no legal right to refund applies.

5. How to Request a Refund

To request a refund, contact HiveMoments at billing@buildwithtfs.com and provide enough information for the purchase to be identified and reviewed. For general legal questions about this policy, you can also reach legal@buildwithtfs.com. If the transaction was processed through a third-party billing provider or merchant of record, that provider may also provide billing support or request additional information as part of the review process.

• Include the email address used at checkout, the transaction reference or receipt number, the date of the charge, the amount charged, and the reason for your request.
• If relevant, include screenshots or a concise explanation of the technical issue, duplicate billing, or renewal concern you want reviewed.
• Refund reviews may require reasonable verification to confirm the identity of the purchaser and the basis of the request.

6. Chargebacks

If you believe a charge is incorrect, please contact HiveMoments at billing@buildwithtfs.com first when possible before initiating a chargeback. Many billing issues, including duplicate charges, renewal confusion, or technical purchase problems, can often be resolved more quickly through direct review.

This request does not limit your rights to contact your card issuer or bank. However, if a chargeback is opened, HiveMoments or the billing provider handling the transaction may need to limit access to the affected purchase while the dispute is being reviewed.

• Contacting support first can often avoid unnecessary dispute fees, delays, or account interruption where the issue can be resolved directly.

7. Contact Information

For billing questions or refund requests, contact billing@buildwithtfs.com. For general legal questions about this policy, you can also reach legal@buildwithtfs.com. You may also write to Tradeforce Systems, LLC, Attn: Privacy, 1621 Central Ave #8904, Cheyenne, WY 82001. If your purchase was processed through a third-party billing provider or merchant of record, you may also be directed to that provider’s billing support or transaction emails associated with the purchase.

• Providing complete purchase details will help HiveMoments review billing requests more quickly and accurately.