Refund Policy

01Current status and policy scope

PostingZone currently offers a demonstration and does not accept subscription payments through the configured website. The pricing tiers are proposed. Using the local workspace, creating a sample draft, or visiting a checkout return page does not create a paid subscription or prove that a payment was received.

This is the proposed refund framework for a future paid service. The operator must confirm commercial terms, a working billing contact, processing procedures, and response targets before checkout opens. The policy forms part of the Terms of Service when a valid paid offer incorporates it. Mandatory consumer remedies always take precedence over discretionary restrictions.

02Subscription charges and renewal

A future checkout must disclose the plan, price, currency, taxes, billing interval, renewal terms, and any credit allowance before payment. Monthly or annual payment must not be collected merely because a user explored the demo.

If recurring billing is offered, it will require your payment authorization and continue only under the agreed renewal terms until cancellation. A changed price or material billing condition must be communicated as required before it applies. Payment confirmation should come from verified transaction records, not from the address of a success page.

03Cancelling future renewal

The intended cancellation route is the payment-provider customer portal, with a working support alternative if portal access fails. Cancellation should stop the next renewal and state when paid access ends. It does not automatically mean that an earlier payment has been refunded.

Deleting demo data does not cancel a subscription. Closing a social account or disconnecting a platform is also separate from billing cancellation. Before live sales, PostingZone must provide clear instructions and confirmation so users can tell which action has been completed.

Keep the cancellation confirmation and the date of your request. If a renewal is collected despite a valid cancellation, provide that evidence through the billing channel so the charge can be investigated. Do not submit full card details.

04Proposed refund eligibility

The current proposed request window is 14 days from the initial purchase, subject to applicable consumer rights. It is a voluntary request threshold to be confirmed before launch, not a universal legal withdrawal period or a waiver of later rights.

Refund requests should be assessed against the offer made at checkout, the actual service supplied, and the applicable law. The following cases warrant review even when a discretionary request window has passed.

• An accidental duplicate charge or a billing amount that does not match the agreed offer.
• A renewal taken after a valid cancellation was received under the agreed terms.
• Failure to provide a paid service, or a material service defect that triggers an applicable remedy.
• A valid statutory withdrawal or refund right.
• Another case covered by a specific written commercial commitment.

05Usage, credits, and partial periods

The final offer must explain how used and unused credits, plan changes, annual payments, and any partial billing period affect a discretionary refund. No blanket “all payments are non-refundable” rule is imposed by this draft. The demo’s sample credits have no cash value and are not a purchased entitlement.

Usage must be evaluated fairly. A generation failure, undelivered paid feature, or mistaken debit should not be treated as successfully supplied service without investigation. Any deductions or prorating must be disclosed and lawful. A statutory remedy is not denied merely because some credits were used.

06Consumer withdrawal and faulty-service rights

Some customers may have a legal cooling-off period or other remedies depending on their location and the type of service purchased. Eligibility, deadlines, and permitted deductions depend on the applicable law. This proposed policy does not select another company’s jurisdiction or treat every subscription as the same type of digital product.

Starting service immediately does not create a blanket waiver. Where law requires an express request, acknowledgement, confirmation, or other conditions for immediate performance or loss of a withdrawal right, checkout must satisfy those conditions separately. A preselected option, ordinary browsing, or arrival at a return page is not evidence of valid consent.

Rights concerning faulty, misdescribed, or undelivered services remain available where required. If a legal deadline or remedy is more favorable than a discretionary policy, the applicable legal protection takes precedence.

07How to prepare a refund request

Once a verified billing contact is available, send a request identifying the purchase and explaining the issue. The current contact form does not send messages unless an endpoint is configured; a demo confirmation is not a submitted refund request. The owner must publish an operational route before collecting money.

• The email used for the purchase and, where relevant, the workspace or plan name.
• The invoice, receipt, or transaction reference, with payment credentials removed.
• The purchase or renewal date and the amount and currency charged.
• A short reason for the request, including any relevant cancellation confirmation or service error.
• A safe reply address and the remedy you are requesting.

08Review and decision

Requests should be acknowledged and assessed promptly, with further information requested only where necessary to identify the transaction or investigate the issue. A response target must be confirmed and displayed before sales begin; this draft does not promise an unsupported five-business-day deadline.

The outcome should explain whether the request was approved, the amount involved, the basis for any deduction, and the next step if you disagree. Operational support should not substitute a discretionary policy for a mandatory legal remedy. Keep a copy of your correspondence and any transaction reference.

09Approved refunds and payment timing

The intended approach is to return an approved amount through the original payment provider to the original payment method, where supported. The exact process must be confirmed when the payment integration is enabled. Staff should never request a password or full card details to issue a refund.

Provider processing and bank posting times may differ. An approved decision and a completed refund transaction are separate milestones; confirmation should identify the amount and a reference where available. Any processing estimate must reflect the actual provider and should not be presented as a guaranteed bank settlement time.

10Unexpected charges and disputes

If you see an unfamiliar charge, first check the merchant description and your receipt. Do not assume a third-party charge came from PostingZone because you previously used the demo. If evidence links it to a future PostingZone transaction, contact the operational billing channel and preserve the relevant records.

This policy does not prevent you from using payment-provider dispute procedures or other lawful remedies. If a refund and a payment dispute are both open, disclose that fact so duplicate repayment can be avoided and the provider’s process followed.

11Policy revisions and related information

The date above records this proposed policy revision. A policy change should identify when it applies and must not remove rights attached to an earlier purchase or override mandatory law. The policy must be finalized alongside checkout, billing support, and the Terms of Service.

Read the Privacy Policy for treatment of billing-request information and Security for safe handling of payment references. Contracting identity, governing law, support details, and commercial procedures require owner confirmation.