Privacy Policy

Privacy contact

For privacy questions or requests, contact clippsi.com@gmail.com.

What happens when you visit?

Your browser requests the page, images and videos from our hosting platform, Cloudflare. Delivering and protecting the website involves technical information such as your IP address, browser information, requested URL and request time. The hosting platform may process this information for operation, security and abuse prevention.

Optional, first-party website analytics starts only after you choose to allow it. We do not use advertising pixels, third-party video embeds or sell visitor information. The private owner dashboard uses one-time email codes and a secure session cookie; it is not a customer account system.

Interactive previews and cookies

Text, watermark and style choices entered into the on-page preview are used only in the current browser page. Our preview code does not send these values to a server or save them in cookies or local storage. They reset when the page is reloaded. Demo media is served from this website.

We save clippsi.privacy.v2 in local storage for up to 180 days to remember your analytics choice. Earlier essential-only choices remain a rejection of analytics. This preference contains no visitor ID. You can use Cookie settings in the footer to reject analytics or forget your saved choice. Closing settings without saving does not change it. If storage is blocked, your choice lasts only for the current page.

With analytics consent, clippsi.analytics.visitor stores a random browser ID for up to 30 days. clippsi.analytics.session stores a random visit ID, the browser ID, a broad source label and device-size category; it expires after 30 minutes without recorded activity. Withdrawal removes these analytics identifiers and stops new events. Expired values are replaced or removed when our site next runs; browser controls can remove them earlier. Essential security cookies support owner sign-in and private downloads. The owner challenge expires after 10 minutes, the owner session after 12 hours, and a download grant after 15 minutes. Downloading checks your activation code without consuming a desktop activation. The server keeps only hashes of these temporary credentials; it checks that access remains active. These cookies are separate from optional analytics.

Optional website analytics

On the basis of your consent, we record the page path (home, privacy or terms), a timestamp, random browser and visit IDs, a broad traffic source such as YouTube or direct, a desktop/tablet/mobile viewport category, page views, beta-button clicks, demo interactions and an estimate of time with the tab visible. The source is reduced in your browser to a fixed category; full referring URLs, query strings, advertising IDs, your name, email address and preview content are not sent as analytics data. Browser IDs are pseudonymous and are not proof of a unique person.

Events are stored in Cloudflare D1 and summarized in an owner-only dashboard. They are excluded from reports after 90 days and deleted during cleanup on subsequent event submissions or owner reports. To protect the endpoint, a hash of IP address, site and current hour is kept with an attempt counter for up to two hours and deleted during subsequent cleanup; raw IP addresses are not saved in these analytics tables. Hosting providers may maintain separate security records.

Withdrawing consent stops future collection but does not undo earlier lawful processing. Contact our privacy email for a data request; because the IDs are random, we may need your browser's analytics ID to locate its records. Beta-request totals are counted from the separate invitation list and are not linked to analytics IDs. There is no visitor-level email tracking, session replay or heatmap recording.

If you contact us

If you email us, we receive your email address, any name you provide and your message, including attachments you choose to send. We use this information to respond to your request and keep necessary correspondence. Providing these details is voluntary, but we need a way to reply.

For general enquiries, the legal basis is our legitimate interest in responding to people who contact us and protecting the service. Where you request steps toward a contract, that request may provide the relevant contractual basis. We do not use an enquiry as consent to marketing.

Please do not send passwords, API keys, payment details or unnecessary personal information.

Requesting beta access

The beta form stores your email address, request time and consent version in Cloudflare D1. With your consent, we use these details to review your request and contact you about beta access and setup. This consent does not include newsletters or general promotional emails. Submitting a request does not guarantee an invitation and does not create a purchase or subscription.

You can withdraw by emailing clippsi.com@gmail.com. Withdrawal does not affect earlier lawful processing. We remove requests after withdrawal or when they are no longer needed for the invitation process; unused requests expire after 12 months and are deleted during database cleanup. For activated testers, the retention date may be extended to cover the beta end date plus 30 days for access support.

Beta requests are stored separately from the previous launch-notification list. Existing launch-only subscribers are not enrolled in the beta or given broader email consent. The same short-lived anti-abuse counters described below protect both forms.

In the private beta workspace, we also record whether a request is waiting, has been marked as invited, or has received feedback, with the corresponding dates. These manual records help us manage your beta request and are kept with the request under the same expiry and withdrawal rules. They are not email-open or installation tracking.

Desktop beta activation

When you activate a beta invitation, the app sends your personal code, a random installation identifier, a device public key, app version and platform to our activation service through HTTPS. This verifies the time-limited access you requested and prevents the same code from activating different installations. It is separate from optional website analytics. We do not use a hardware fingerprint or send your footage, transcripts, source links or project files.

The access record stores a hash of the code, a hash of the installation identifier, its device public key and signed-lease sequence, issue and expiry dates, access state, first activation and latest successful verification time, linked to your beta request. We do not retain the raw activation code on the server. Access records are removed with their beta request. Orphaned device-binding records are removed during the next daily cleanup. The same short-lived hashed-IP anti-abuse counters described below protect activation requests. Infrastructure providers receive connection information needed to serve HTTPS.

Your computer encrypts its activation credential and signed access allowance using operating-system protection. Its private device key stays in the operating-system keystore. An online check is required each time the app starts and every 15 minutes while it is open. After successful verification, the open session can continue offline for up to 7 days and never beyond the beta end date. The owner can extend or disable access; a disabled offline installation notices at its next successful check or when its current allowance ends. Projects and completed videos remain on your computer after expiry. Contact us to request an extension, reset an installation, withdraw or ask about activation records.

Earlier launch-email requests

The previous launch form stored your email address, request time and the version of your consent in a database provided through OpenAI Sites and Cloudflare D1. We use these details to send one CLIPPSI launch notification. No payment or reservation is created.

Submitting the form with the consent box selected gives consent for this one email. You can withdraw by emailing clippsi.com@gmail.com. Withdrawal does not affect earlier lawful processing. We remove requests after the launch notification or withdrawal. Unused requests expire after 12 months and are deleted during database cleanup.

To limit automated submissions, we keep a short-lived hash derived from your IP address and the current hour, with an attempt counter. This does not contain your email address or the raw IP address. The counter expires after two hours and is cleared during subsequent submissions. This security processing serves our legitimate interest in protecting the form. Our database has no publicly accessible list of subscribers.

Service providers and international processing

The website runs on Cloudflare Workers. Optional analytics, beta requests and the earlier launch list are stored in Cloudflare D1. Private installers and server key material are held in Cloudflare R2. Resend delivers owner sign-in and transactional emails; contact correspondence is handled through Gmail. Older desktop builds temporarily relay activation requests through the previous OpenAI Sites address to the same CLIPPSI service. The previous hosting copy is retained during migration for compatibility and recovery. These providers and their infrastructure providers may process information in countries outside your own. Their applicable privacy terms explain their processing, international transfers and safeguards.

• Cloudflare Privacy Policy
• Resend Privacy Policy
• OpenAI privacy information for the EEA, UK and Switzerland
• Google Privacy Policy

We do not copy preview text or desktop video projects to these services through this website.

How long information is kept

On-page preview choices remain only while the current page is open. The separate cookie-notice choice is retained as described above. For email correspondence, we keep information while it is needed to resolve the enquiry and for necessary follow-up, legal obligations or the establishment or defence of claims; it should be removed when those purposes no longer apply. Hosting and email providers manage their own operational records under their policies. We do not control or promise a fixed deletion period for their independent service logs.

Your rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal data, and object to processing based on legitimate interests. Contact us using the email above. We may need proportionate information to verify that a request concerns your data.

You may also complain to your local data protection authority. In the Czech Republic, this is the Office for Personal Data Protection (ĂšOOĂš). Where a provider independently controls information, you can also contact that provider directly.

The desktop application

The current CLIPPSI workflow processes videos and transcripts on the user’s computer. Downloading source videos and AI models requires connections to the relevant providers. The website preview cannot read or alter your desktop projects or saved presets. This notice does not replace product-specific privacy information for a future commercial release.

Future changes

Before adding accounts, payments, cloud processing or marketing tools, we will update this policy to describe the actual data use. The date at the top identifies the latest revision.

Performance and beta milestones

With optional analytics enabled, Cloudflare Web Analytics measures loading speed, responsiveness and layout stability on public pages. It does not receive your activation code, email address or editor content from this integration. It is disabled on private dashboards, purchase pages, download pages and URLs containing query parameters. Withdrawing analytics consent reloads the page to stop performance observers.

For beta delivery and support, we record the first authorized download start and first successful activation against your beta request. Repeated downloads do not create new people. These operational milestones are not linked to website browser IDs and follow the retention and deletion of the associated beta request. A started download is not proof of a completed installation.

Website security and backups

Cloudflare Turnstile helps protect beta requests, license transfers and administrator sign-in against automated abuse. It processes technical browser and connection signals for this security check. It is loaded when you use a protected form, not for advertising. Private daily backups of website records and configuration are retained for up to 30 days. Operational error records use service names and status codes rather than activation codes, submitted emails or request bodies.

Moving your license

To move a single installation, provide your current activation code and the email used for your invitation or purchase. We match these to the existing license and send an eight-digit verification code through Resend to that existing address. A secure, HTTP-only browser cookie binds the request to your browser for up to 30 minutes. Verification codes expire after 10 minutes, have a five-attempt limit and are stored as hashes. Completing a transfer replaces the activation code and clears the old device binding. An already open offline session can continue within its existing allowance, up to 7 days.

The replacement code is encrypted on the server and available only to the verified browser for 30 minutes. Expired transfer records are deleted during the next request or daily maintenance. Transfer timestamps tied to the license enforce a 24-hour cooldown and are retained for up to 30 days. They are included in private backups, which also expire after 30 days. Verification codes and temporary transfer results are excluded from backups.

Optional desktop first-export measurement

This is separate from website analytics and is off by default. If you enable it in the desktop license panel before your first successful export, the app sends one success event, its version, platform and an existing signed license verification. We use the license reference to avoid counting the same person repeatedly. A one-way activation fingerprint lets the app request deletion even after the license is moved or expires. No raw activation code is stored with the event. No footage, audio, transcript, source link, filename or file path is accepted. This measurement is pseudonymous, not anonymous, because the license is linked to its beta or purchase record.

On the basis of your consent, the event is retained for up to 90 days, with expired records removed in daily maintenance. It is excluded from daily backups. Turning the setting off stops reporting and requests deletion of an existing event; the app retries if offline. You can also ask for deletion at clippsi.com@gmail.com. Exports completed before consent are not sent retroactively. The owner dashboard labels these opt-in totals separately from activations.