Privacy policy.

This Privacy Policy explains how the operator of clipquickly.com handles information when you browse the site, buy a license, download or run ClipQuickly, email us, or otherwise use the product. It covers the public website, checkout, order records, and the software running on your machine. It does not cover third-party providers you connect with your own keys. Those providers have their own notices.

Depending on how you use ClipQuickly, we collect:

• the email address used for checkout, receipts, order recovery, or support;
• order notes you type, such as a name on a receipt if the payment form asks for one;
• support messages, diagnostics, and files you choose to send us;
• refund and dispute details needed to verify a request.

We do not need your API keys to operate the public site. Do not paste live keys into a form unless we ask for a redacted log.

Stripe keeps the payment record and receipt. In private storage, we keep the Checkout Session and payment references, payment state, amount and currency, product metadata, timestamps, and the email linked to the purchase. We use these records to match signed payment events, recover orders, prevent duplicate fulfillment, and investigate errors, refunds, or chargebacks.

Card and wallet details are entered through our payment processor, such as Stripe or another provider named at checkout. ClipQuickly does not store full payment-card numbers or card security codes in its own database.

The product is designed so that provider keys, drafts, scene data, local footage, and exported MP4 files stay on the computer or browser profile you use. Browser local storage on this site may also hold a license stub, onboarding flags, and draft fields if you use the web studio. That data is stored by your browser on your device. We do not receive it unless you send it to us or a later connected feature that you opt into transmits it.

When ClipQuickly calls a provider with your key, that provider receives the prompts, scripts, search terms, or other inputs needed for the call. That processing is under the provider's terms, not this policy. We do not operate those models.

The site receives technical request data such as IP address, user-agent, device and referrer information through its hosting and content-delivery environment. We use this for security, rate limiting, abuse prevention, diagnostics, and aggregate product measurement. Security keys and any anonymous analytics identifiers we store are stored as hashes or other non-reversible tokens where practical.

We use a short-lived, signed, HttpOnly cookie for download access and may use similar storage for basic site function. We do not use your purchase email to run advertising networks. Application logs are designed to avoid raw access tokens, payment secrets, provider API keys, and full payment details. Operational records may include request outcomes, signed webhook status, security events, and administrative audit records.

We use information to:

• create checkout sessions, confirm payment, and grant the purchased license;
• match and reconcile signed payment events and prevent duplicate or fraudulent fulfillment;
• deliver download access, recover orders, and support payment receipts;
• diagnose render failures and handle refund or chargeback requests;
• secure the site, prevent spam, fraud, abuse, and attacks;
• maintain, measure, and improve the product; and
• meet legal, accounting, tax, security, and dispute-handling obligations.

We use vendors only for the roles they are hired to perform. Typical roles are:

• hosting, request delivery, platform logs, and optional web analytics;
• payment processing and payment confirmation;
• payment receipts and support replies;
• error or uptime monitoring on the public site.

Those providers process information under their own terms and privacy notices. We share only what is needed for their role, legal compliance, security, and dispute handling. The exact vendor names can change. The checkout page and receipt identify the payment processor used for your order.

Your purchase email, payment references, support mail, drafts, keys, and exported videos are not published by us. Demo videos on the marketing site are our examples, not your files. We do not sell personal information. We do not share it for cross-context behavioral advertising.

We keep information only as long as reasonably necessary to issue and honor licenses, keep transaction integrity, handle refunds and disputes, secure the service, and meet legal or accounting obligations. License and payment records are typically kept for the life of the license plus the period tax and consumer-law rules require.

Support attachments are kept for the diagnostic period, then deleted unless a dispute, security incident, or legal duty requires a longer hold. Data in your browser or desktop install is under your control. Clearing site data or uninstalling the app removes our copies only of what was stored on that device, not the server-side order record.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection concerning your personal data, and to complain to a data-protection authority. These rights may be limited where information must be kept for legal, security, transaction-integrity, tax, or dispute-handling reasons. We may need to verify the email that owns the order before we act.

Email support@clipquickly.com. Use this address for legal, privacy, and refund requests. It is not live chat.

ClipQuickly is not directed at children. We do not knowingly collect personal information from anyone under 16, or under 13 where that is the applicable threshold. If you believe we have information about a child, email us and we will delete it unless the law requires a short hold.

We use access controls, private storage, hashed or tokenized secrets where practical, transport encryption, rate limits, and audit records to protect information. No online service can guarantee absolute security. You are responsible for the security of your own computer, keys, and inbox.

We may update this policy when the product, providers, or legal requirements change. The date shown on this page identifies the current version. Material changes apply going forward. If a change needs consent under applicable law, we will ask for it before relying on the new use.