Billing support

Refund Policy

This policy explains the difference between cancelling a subscription and requesting a refund, how PostPlugin.org reviews support tickets, and how verified generated-output usage can affect a request.

Last updated

CancellationStops a future subscription renewal; it is not a refund request.
Refund ticketCreates an in-app request for review; it does not move money automatically.
Credit guidelineA full refund is generally unavailable when 100 or more output credits are verified for the relevant paid period, unless law requires otherwise.

1. Subscription cancellation is separate from a refund

Cancelling a subscription stops future renewals under the terms shown at checkout and in the Stripe billing portal. Cancellation does not itself reverse a payment or create a PostPlugin.org refund ticket.

If you want us to review a payment for a possible refund, submit a separate refund request from the Contact section of your signed-in account.

2. Output credits and full-refund review

Credits represent generated output from Swizie. The prompt text and supported files you send as input are not counted as billable output credits.

The current 100-output-credit guideline

PostPlugin.org generally does not offer a full refund when records verify that 100 or more output credits were used for the relevant paid period, except where applicable law requires otherwise.

The ticket form does not automatically attach a payment-period usage total or apply this guideline. Credit records are reported by UTC calendar month, which may not match a Stripe renewal date, so relevant usage must be reviewed rather than assumed from the ticket alone.

Using fewer than 100 output credits does not guarantee a full or partial refund. Each request is reviewed using available purchase and usage records, timing, the reported service issue, and any rights that apply to the customer.

3. How to request a review

  1. Sign in to the PostPlugin.org account connected to the subscription.
  2. Open Account, choose Contact, and select Request a refund.
  3. Describe what happened and why you are requesting a refund, then submit the form.
  4. Keep the ticket number shown in the Contact section and return there to view its latest status.

The reason must contain 10 to 1,000 characters. Do not include a full card number, bank details, password, API token, or private server credential. You may have only one active refund ticket at a time; a ticket is active while marked Submitted or In review.

4. Refund ticket states

The Contact section may show these public ticket states:

SubmittedThe request was saved and is waiting for review.
In reviewAn authorized staff account has started reviewing the request.
DeniedThe ticket review ended without a refund approval through that request.
ClosedThe staff workflow was closed. A Closed ticket does not by itself prove that Stripe issued or settled a refund.

5. What submitting a ticket does

A refund request stores the reason you provide with your account email and a snapshot of the plan tier and subscription status available to PostPlugin.org. The public ticket view shows the ticket number, status, and submission date.

Submitting a ticket does not send the reason to Stripe, instruct Stripe to refund a charge, cancel the subscription, or automatically approve a payment reversal. Updating a ticket status is also an in-app support action and does not itself perform a Stripe payment or refund operation.

The ticket does not include full payment-card details or Stripe customer, subscription, charge, payment, or invoice identifiers.

6. Ticket access and retention

The signed-in user sees the ticket number, status, and submission date. Authorized staff accounts can see the reason, account email, and saved plan and subscription-status snapshot needed to review the request.

Submitted and In review tickets remain stored while open. Denied and Closed tickets are normally deleted 24 months after their last update, unless a chargeback, fraud review, legal duty, litigation, or another dispute requires longer retention. See the Privacy Policy for more information.

7. Review, decisions, and timing

Every ticket remains a request for review unless PostPlugin.org expressly communicates a decision. We do not guarantee that a request will be approved, that a full or partial amount will be available, or that a particular remedy will apply.

We do not promise a specific review, decision, processor, or bank settlement time. Any approved payment action may depend on the payment processor and financial institutions involved.

8. Statutory and non-waivable rights

This policy does not exclude or restrict a consumer protection, refund, warranty, chargeback, cancellation, or other right that applicable law does not allow us to exclude or restrict. Where a non-waivable legal right conflicts with the 100-output-credit rule or another part of this policy, that legal right controls.

9. Contact and related policies

For a refund review, use the in-app form so the request is connected to the correct signed-in account. For a question about this policy or trouble accessing the form, contact eftasmare@gmail.com.

Read the Terms of Service refund section for the service terms and the Privacy Policy for information about refund-ticket records.

Request a refundView all policies