Refund policy

Refunds, credits, cancellations, and disputes.

A detailed commercial policy for TrendRise digital access, subscriptions, credits, generated outputs, failed jobs, cancellations, Stripe disputes, chargebacks, Partner commission impact, and mandatory consumer rights.

Policy purpose

This Refund Policy explains how TrendRise handles subscription cancellations, credit usage, digital service delivery, failed jobs, refund requests, payment disputes, chargebacks, and related billing questions. It is designed to work together with the Terms of Use, Privacy Policy, Cookie Policy, Partner Terms, and any signed order form.

  • This is a lawyer-review-ready operating draft and must be reviewed by counsel before final public launch.
  • If a signed agreement or order form gives a customer different refund terms, that signed agreement controls for that customer.
  • If mandatory law gives you a refund, cancellation, withdrawal, or consumer remedy that cannot be waived, that mandatory law controls.
  • Billing questions should be sent to billing@trendrise.io before filing a payment dispute when possible.

Short version

TrendRise sells digital access, subscriptions, credits, and online services. The default position is that payments are not refundable once paid access begins, the workspace receives the plan, or credits are spent, except where law requires a refund or TrendRise approves an exception.

  • Cancelling stops future renewal; it does not automatically refund the current billing period.
  • Credits spent on source checks, reports, generated outputs, exports, artifacts, or other paid workflow actions are treated as consumed digital service activity.
  • If a credit-consuming job fails before useful service is delivered, the usual remedy is credit restoration, retry, or usage adjustment, not automatic cash refund.
  • TrendRise may deny refund requests where records show that the customer agreed to the policy, received access, and used credits or paid features.

What this policy covers

This policy applies to purchases and billing events connected to TrendRise, including public website purchases, in-app billing, Stripe Checkout, subscriptions, plan upgrades, renewals, credits, usage-based features, source searches, generated outputs, exports, artifact preparation, Partner-related billing events, and support-approved adjustments.

  • It covers monthly and annual subscriptions unless a separate agreement says otherwise.
  • It covers credits included in a plan, credits granted manually, credits restored by support, and credits purchased separately if that option is offered.
  • It covers digital services delivered through the application, not external products you sell through Shopify, Etsy, Amazon, KDP, Gumroad, Stripe, or other channels.
  • It does not replace platform-specific refund rules for products you sell outside TrendRise.

No physical delivery

TrendRise is delivered digitally. There is no physical shipment, delivery carrier, or mailed product needed for TrendRise to provide service. Digital service can be delivered through account access, workspace availability, plan activation, credit grants, source searches, generated outputs, exports, artifact records, saved reports, and other in-app actions.

  • A customer does not need to download a file for service to begin.
  • A customer does not need to use every feature in a paid plan for access to have been provided.
  • A customer does not need to like, publish, sell, or profit from an output for digital service to have been delivered.

When service begins

Service begins when any meaningful paid access or paid workflow activity starts. This can happen immediately after Checkout, subscription activation, credit grant, workspace plan upgrade, source-search start, credit-consuming job start, generated-output delivery, export preparation, artifact creation, or paid feature access.

  • TrendRise may record service start through login records, plan state, Stripe Checkout metadata, invoice records, credit ledger entries, job records, generated outputs, source-search records, export manifests, artifact versions, support records, and policy version metadata.
  • A paid plan can begin even if the customer later decides not to use all features.
  • A credit-consuming action can begin when the user confirms the action, when credits are deducted, when the provider call starts, or when the system begins processing.
  • The final Checkout wording for EU/UK consumers should be reviewed by counsel to confirm any immediate-performance consent required by local law.

Credits are consumed digital service

Credits are TrendRise's internal usage meter. Once credits are spent on a confirmed action, that part of the service has generally been consumed and is not eligible for a cash refund unless law requires otherwise or TrendRise approves an exception.

  • Credits are not cash, stored value, gift cards, electronic money, cryptocurrency, prepaid balance, or transferable property.
  • Credits may be consumed by reports, product briefs, validation plans, pricing reports, source checks, drafts, UGC scripts, outreach drafts, export packages, artifact preparation, AI/model calls, source-provider calls, and similar paid actions.
  • Credit usage can be used as service-delivery evidence for refund, support, fraud, and chargeback review.
  • Unused credits may expire, reset, be capped, or become unavailable based on the plan terms.

Credit restoration versus cash refund

TrendRise distinguishes between restoring credits and refunding money. If a credit-consuming action fails, the appropriate remedy is usually a retry, credit restoration, usage adjustment, or support correction rather than a refund to the original payment method.

  • Credit restoration may be appropriate when credits were deducted but the job failed before useful service was delivered.
  • Credit restoration may be partial if part of the service was delivered or provider costs were incurred.
  • Credit restoration is not admission that cash is owed.
  • Restored credits remain subject to plan limits, account status, expiration, and acceptable use rules.

Examples of consumed credit activity

The following are examples of activity that normally counts as delivered digital service once started or completed.

  • Trend Radar or Research Center source checks that return source evidence, skipped-source context, warnings, or no-results data.
  • Product Studio reports such as recommendation, market fit, pricing, go-to-market, validation plan, or comparison runs.
  • Product Builder jobs such as outline, content draft, marketing copy, spreadsheet schema, UGC scripts, asset plan, export package, or artifact preparation.
  • Launchpad, Creator Finder, Deal Room, Analytics, or Partner-related generated summaries, scripts, outreach drafts, attribution records, and reports.
  • Saved outputs, private artifact versions, export manifests, source-search logs, and support-visible usage records.

Subscription cancellations

You may cancel a subscription through the billing portal, account settings, or support channel when available. Cancellation stops future renewal unless your plan, Checkout flow, order form, or applicable law states otherwise.

  • Monthly and annual subscriptions are generally not prorated after paid access begins.
  • Cancelling does not automatically refund the current billing period.
  • Cancelling may stop future credit grants, future renewal charges, and future paid feature access.
  • Deleting an account, closing a browser tab, not logging in, abandoning a workspace, or asking a third party to stop using the account does not automatically cancel billing.

Renewals

Subscriptions may renew automatically. You are responsible for cancelling before the renewal date if you do not want another billing period. A renewal charge is generally not refundable once the renewed paid period begins, except where required by law or approved as an exception.

  • TrendRise may send reminders where required by law or configured in the product, but lack of product usage after renewal does not automatically create a refund right.
  • If payment fails, TrendRise may retry payment, downgrade access, pause features, stop credit grants, or suspend the workspace.
  • If a renewal appears mistaken, contact billing@trendrise.io promptly with the account email, invoice reference, and reason for the request.

Plan upgrades and downgrades

Plan changes may affect pricing, renewal dates, credits, feature access, workspace limits, exports, team seats, Partner features, and billing state. The Checkout page, billing portal, order form, or in-app billing page should describe the immediate payment or future billing effect.

  • Upgrade charges are generally not refundable once upgraded access or credits are provided.
  • Downgrades generally affect future periods, not past periods already started.
  • If a plan change creates a billing error, TrendRise may correct the invoice, issue a credit, restore credits, or approve a refund where appropriate.

Free trials and promotions

TrendRise may offer free trials, beta access, discounts, coupons, early-access plans, promotional credits, or manual account grants. These offers may have special limits, expiration dates, feature restrictions, or conversion rules.

  • Promotional credits generally have no cash value and are not refundable.
  • If a free trial converts to a paid plan, the customer is responsible for cancelling before conversion if they do not want to be charged.
  • TrendRise may end or modify promotions prospectively unless a written agreement says otherwise.

Refund exceptions TrendRise may approve

TrendRise may approve a refund, partial refund, invoice correction, credit restoration, or account credit when it determines an exception is appropriate. These exceptions are discretionary unless required by law.

  • A duplicate charge that is not explained by separate subscriptions, invoices, workspaces, plan changes, or intentional purchases.
  • A confirmed billing error by TrendRise or its payment provider.
  • An unauthorized charge reported promptly with enough information to investigate.
  • A material service failure where paid access was not provided and a credit remedy is not adequate.
  • A legal right that requires a refund, cancellation remedy, withdrawal remedy, faulty-digital-service remedy, or similar customer remedy.

Duplicate charges

If you believe you were charged twice, contact billing@trendrise.io with the account email, charge dates, amounts, invoice references, and any Stripe receipt or card statement details that do not expose full card numbers.

  • Some charges that look similar may be separate subscriptions, separate workspaces, plan upgrades, annual versus monthly changes, retry attempts, or other valid billing events.
  • If TrendRise confirms a true duplicate charge, it may refund or correct the duplicate amount.
  • If a payment dispute claims duplicate billing, TrendRise may submit evidence showing the difference between the disputed charge and any prior charge.

Unauthorized charges

If you believe a charge was unauthorized, contact billing@trendrise.io promptly so TrendRise can investigate. TrendRise may ask for account verification and may temporarily restrict access, credits, Partner activity, or billing changes during review.

  • Do not send full card numbers, passwords, bank details, recovery codes, private keys, or sensitive personal data in support messages.
  • TrendRise may review account access, Checkout metadata, login history, workspace activity, payment-provider records, IP/device/browser context where available, and support history.
  • If a charge appears fraudulent or account access appears compromised, TrendRise may suspend access and recommend password, email, or payment-method security steps.

Service failures and outages

TrendRise may experience bugs, provider outages, model failures, source-provider limits, incomplete data, downtime, delayed jobs, or failed exports. Not every issue creates a refund right.

  • If a credit-consuming job fails before useful service is delivered, TrendRise may retry the job or restore credits.
  • If a paid workspace cannot access core paid features for a material period because of a TrendRise-controlled failure, TrendRise may consider a credit, extension, or refund exception.
  • Outages caused by third-party providers, source changes, customer configuration, internet issues, browser issues, payment-provider restrictions, or unsupported beta features may not qualify for cash refunds.
  • Support requests should include the affected route, workspace, job, timestamp, error message, and expected outcome where available.

No refund situations

Subject to applicable law, TrendRise generally will not refund charges where access was provided, credits were granted, credits were spent, generated outputs were created, exports were prepared, source checks were run, or paid features were used.

  • Change of mind after service begins.
  • Not using the product after purchase or renewal.
  • Unused credits that expire, reset, or become unavailable under the plan.
  • Dissatisfaction with market results, source results, creator response, product performance, ad performance, sales, traffic, or generated recommendations.
  • Failure to cancel before renewal when renewal terms were disclosed.
  • Account suspension or termination caused by non-payment, fraud, abuse, policy violation, security risk, or prohibited use.
  • External platform issues involving Shopify, Etsy, Amazon, KDP, Gumroad, Stripe, ad platforms, email tools, creator channels, or other systems outside TrendRise control.

No guarantee of business outcome

TrendRise does not sell guaranteed product-market fit, guaranteed revenue, guaranteed creator response, guaranteed traffic, guaranteed ad performance, guaranteed trend continuation, guaranteed compliance, or guaranteed profit. Refunds are not owed because a product idea, report, source signal, export, or launch plan did not produce the business result you hoped for.

  • TrendRise outputs are decision support and workflow assistance.
  • You are responsible for validation, final claims, product quality, pricing, storefronts, customer support, and launch execution.
  • A low-performing launch, poor sales result, or rejected product idea does not mean TrendRise failed to deliver the digital service.

AI and generated output dissatisfaction

AI-assisted outputs and generated materials may need editing, checking, rewriting, legal review, design work, or business judgment. Dissatisfaction with style, tone, accuracy, completeness, originality, or commercial usefulness does not automatically create a refund right once the output was generated or credits were consumed.

  • If an output is unusable because of a system failure, duplicated empty response, or technical generation error, TrendRise may restore credits or rerun the job.
  • If an output is merely not the customer's preferred direction, the expected remedy is editing, regeneration where available, or using saved-output workflows according to the plan.
  • You must review outputs before using them publicly or commercially.

EU, UK, and consumer rights

Some customers may have statutory cancellation, withdrawal, faulty-digital-content, digital-service, or consumer-remedy rights. TrendRise will not limit mandatory rights that cannot be waived by contract.

  • Digital services and digital content can be subject to specific withdrawal, immediate-performance, and remedy rules depending on customer status, country, purchase flow, and local law.
  • For EU/UK consumers, checkout wording may need express consent to immediate performance and acknowledgement of how withdrawal rights are affected by digital service or digital content delivery.
  • If you are buying as a business, your rights may differ from consumer rights.
  • If mandatory law gives you a right that conflicts with this policy, the mandatory law controls for that right.

Counsel should finalize EU/UK consumer wording before full launch, especially around immediate digital performance, subscriptions, renewals, and credit-consuming actions.

Business, agency, and client use

If you buy TrendRise for a company, agency, client, creator business, or other organization, refund requests may require confirmation from the workspace owner, billing administrator, or authorized buyer.

  • TrendRise may rely on billing records, workspace ownership, verified admin access, domain ownership, or written authorization when reviewing requests.
  • Internal disputes between founders, employees, contractors, agencies, clients, or Partners do not automatically create refund rights.
  • If an agency buys TrendRise for client work, the agency remains responsible for its client contract, deliverables, approvals, and billing relationship.

Partner and commission impact

Refunds and disputes can affect TrendRise Partner attribution and commission. Customer billing events may create commission holds, reversals, dispute freezes, payout delays, or negative adjustments under the Partner Terms.

  • Refunds can reverse related Partner commission.
  • Disputes can freeze pending or payable Partner commission until resolved.
  • Lost disputes can reverse unpaid commission or create future negative adjustments if a Partner was already paid.
  • Refunds issued to a customer do not require TrendRise to pay or preserve commission to a Partner for the refunded transaction.

Taxes and payment fees

Refund amounts may be affected by taxes, currency conversion, payment-provider rules, card-network rules, bank fees, exchange rates, partial refunds, disputes, chargeback fees, and local law.

  • Some taxes may be non-refundable or handled separately depending on the payment provider and jurisdiction.
  • Currency conversion changes may cause refunded amounts to differ from the amount shown on a statement.
  • TrendRise generally refunds to the original payment method where a cash refund is approved and possible.

How to request a refund or credit review

Send billing questions, refund requests, duplicate-charge concerns, unauthorized-charge concerns, renewal questions, and credit-restoration requests to billing@trendrise.io.

  • Include the account email, workspace name, invoice id or Checkout reference if available, charge date, amount, and a clear description of the issue.
  • For credit issues, include the route, action name, timestamp, job or output reference if available, and what went wrong.
  • For cancellation issues, include when you attempted to cancel and what happened.
  • For duplicate charges, include enough transaction information to distinguish the charges without sending full card numbers.

Review process

TrendRise may review refund requests against product, billing, payment-provider, credit, support, and account records. TrendRise may ask for more information before deciding.

  • Relevant records may include Terms acceptance, refund-policy disclosure, Checkout metadata, invoice records, subscription status, plan state, account email, workspace id, login records, credit grants, credit deductions, job records, generated outputs, source-search records, exports, artifacts, support messages, and prior refund decisions.
  • TrendRise may approve, deny, partially approve, restore credits, retry a job, issue an account credit, correct an invoice, or request further verification.
  • TrendRise may decline to review incomplete requests that do not identify the account or charge.
  • TrendRise may prioritize security, fraud, unauthorized-charge, and duplicate-charge reports.

Timing

Refund and credit reviews take time. TrendRise may need to inspect Stripe records, credit ledgers, support records, workspace activity, provider logs, and job outputs before deciding.

  • Approved refunds may take additional time to appear depending on the payment provider, bank, card issuer, currency, and country.
  • Credit restoration, when approved, may appear faster than a cash refund but remains subject to account status and plan rules.
  • If a payment dispute has already been filed, TrendRise may need to handle the issue through Stripe or the payment provider rather than through a normal support refund.

Chargebacks and payment disputes

If you file a bank dispute or chargeback, TrendRise may respond through Stripe or the applicable payment provider. The card issuer, network, or payment provider may decide the outcome, and TrendRise cannot guarantee dispute results.

  • TrendRise may submit a copy of the Terms, Refund Policy, cancellation policy, product description, policy disclosure, Checkout metadata, receipt, invoice, service date, service documentation, access logs, customer email, customer communications, credit ledger records, generated outputs, source checks, exports, artifact records, cancellation history, refund history, and refund-refusal explanation.
  • TrendRise may explain that the customer agreed to the policy, received access, and spent credits or used paid features.
  • If TrendRise already issued a partial refund, it may submit refund evidence to avoid over-refund.
  • Dispute activity can affect account access, fraud review, future purchases, and Partner commission state.

Dispute evidence package

TrendRise should keep dispute evidence concise, structured, and tied to the dispute reason. Internal records should be organized so support can produce a clear evidence packet without exposing unnecessary customer data.

  • Policy evidence: Terms version, Refund Policy version, cancellation policy, policy disclosure, and Checkout acceptance context.
  • Payment evidence: Stripe customer id, Checkout session id, PaymentIntent or invoice id, receipt, charge date, amount, plan, and renewal state.
  • Service evidence: access dates, login events, workspace plan state, credit grants, credit deductions, job records, generated outputs, source searches, exports, artifacts, and service dates.
  • Communication evidence: support messages, cancellation requests, refund decisions, refund explanations, and any customer acknowledgement.
  • Risk evidence: IP/device/browser context where lawfully available, account verification, prior non-fraud transactions where relevant, and fraud-review notes.

Disputes after refunds

A customer may still dispute a payment after a partial refund or agreed adjustment. If that happens, TrendRise may respond with refund evidence, refund amount, refund date, remaining amount, and the reason the remaining amount was not refunded.

  • TrendRise may submit evidence to avoid an over-refund.
  • If the disputed amount includes an already-refunded portion, TrendRise may provide payment-provider records showing the prior credit.
  • Partial refunds do not waive TrendRise's right to defend the remaining amount.

Fraud, abuse, and repeated disputes

TrendRise may deny refunds, restrict access, refuse future purchases, close accounts, freeze Partner attribution, or require additional verification where refund requests, disputes, payment failures, signup patterns, credit usage, or Partner activity indicate abuse, fraud, self-referral, policy evasion, or misuse.

  • Examples include using credits heavily and then requesting a refund, repeated renewal disputes after continued access, duplicate accounts to evade limits, self-referral schemes, coupon abuse, false unauthorized-charge claims, and attempts to receive both service and refund.
  • TrendRise may preserve relevant records for fraud prevention, payment defense, security, tax, legal, and compliance purposes.
  • TrendRise may cooperate with payment providers, card networks, platforms, banks, law enforcement, or regulators where legally appropriate.

Account suspension and termination

If an account is suspended or terminated for violating the Terms, non-payment, fraud, abuse, security risk, or prohibited activity, TrendRise generally does not refund amounts for the period in which service was available or credits were consumed, except where required by law.

  • Suspension may prevent further use of remaining credits.
  • Termination does not erase amounts already owed.
  • TrendRise may retain billing, credit, support, security, fraud-prevention, dispute, tax, and legal records after termination.

External product refunds

This policy applies to TrendRise charges, not refunds owed by you to your own customers. If you use TrendRise to plan, build, analyze, or launch a product sold elsewhere, you remain responsible for your product refund policy and customer support obligations.

  • TrendRise is not responsible for refunds, chargebacks, support, taxes, shipping, delivery, platform disputes, or customer claims for products you sell outside TrendRise.
  • TrendRise recommendations about refund copy, FAQ copy, launch assets, or support workflows are drafts that you must review and adapt.
  • If you sell through Stripe, Shopify, Etsy, Amazon, KDP, Gumroad, or another platform, that platform's rules may apply to your customer transactions.

Policy version and updates

TrendRise may update this Refund Policy as the product, credits, billing model, payment providers, legal obligations, Partner program, and support workflows change. The policy version shown or linked at purchase may be relevant for refund and dispute review.

  • TrendRise may record the active policy version in Checkout metadata, invoice metadata, credit ledger metadata, or support records.
  • Material changes should apply prospectively where required by law.
  • Continued use after a policy update may mean you accept the updated policy, subject to applicable law.

Contact

Refund, billing, credit, invoice, duplicate-charge, unauthorized-charge, and dispute questions should be routed to the billing inbox.

  • Billing and refund requests: billing@trendrise.io.
  • Legal notices: legal@trendrise.io.
  • Privacy requests related to billing records: privacy@trendrise.io.
  • Security concerns about account compromise or unauthorized use: security@trendrise.io.