Cookie Policy
This Cookie Policy explains how Clipwright, operated by Dimantika sp. z o.o., uses cookies and similar technologies.
Contents07
What Are Cookies
Cookies are small text files that are stored on your device (computer, tablet, or mobile) when you visit a website. They help websites remember your preferences and improve your browsing experience.
Related technologies include web beacons, pixels and local storage. This policy covers them too, but it does not lump them together under one word: where something is not a cookie, it says so. Local storage in particular differs in the way that matters here: unlike a cookie, the browser does not attach it to requests. The table below says which entry, if any, the page itself sends to us.
Clipwright uses cookies to provide essential functionality, remember your preferences and keep you signed in for our video platform service.
Types of Cookies We Use
We use different types of cookies for various purposes. The table lists each one, and each entry kept in local storage; the sections after it describe each category.
| Name or pattern | Purpose | Set and read by | Lifetime | Renewal |
|---|---|---|---|---|
sb-<project>-auth-token, which may be split into numbered parts | Keeping you signed in | Our own server, on this domain, using our authentication provider’s software | 400 days | Written again with a new 400-day lifetime whenever your session is refreshed |
sb-<project>-auth-token-code-verifier | Completing a confirmation or password-reset link | Our own server, on this domain, using our authentication provider’s software | Set with a 400-day lifetime when you request the link, and deleted when the link is opened in the same browser; otherwise it stays for those 400 days | Not renewed; a session refresh does not extend it |
sidebar_state | Whether the dashboard sidebar is expanded or collapsed | Set by the dashboard in your browser; read by our server | 7 days | Written again with a new 7-day lifetime each time you toggle the sidebar |
theme (local storage, not a cookie) | Your light, dark or system theme | Set and read in your browser only; never sent to us | Until you clear your browser’s site data | Written again when you change the theme |
clipwright:assets:tile-size (local storage, not a cookie) | The tile size you picked in your asset library | Set and read in your browser only; never sent to us | Until you clear your browser’s site data | Written again when you pick a size |
clipwright.editor.width.v2.files and clipwright.editor.width.v2.details (local storage, not a cookie) | The widths you gave the editor’s side panes | Set and read in your browser only; never sent to us | Until you reset the pane to its default width or clear your browser’s site data | Written again when you finish resizing a pane |
clipwright.editor.pending-start.v1.<run> (local storage, not a cookie) | Remembering a render you started from the editor, so a retry is not charged twice and the editor can follow the run it started | Set and read by the editor in your browser; when you retry that render, the editor sends the count it holds back to our server | Until the run’s files are deleted: the editor removes it the next time it reads it after that. A refused start removes it, unless an earlier start of the same draft is still unanswered. Clearing your browser’s site data removes it too | Written again each time you start a render of that draft and when that start is answered |
2.1 Essential Cookies
These cookies are necessary for the dashboard to work, and there is no switch inside Clipwright to turn them off — your browser can still block them, and section 5.1 says what happens then. They enable core functionality such as:
- Authentication: keeping you signed in as you move between pages, and completing the account-confirmation and password-reset links we email you
Your light or dark theme choice is not a cookie: it is stored in your browser’s local storage and never sent to us.
Essential Cookies Used:
- Supabase authentication cookies: set on this domain by our own server, using our authentication provider’s software, to keep you signed in. They are first-party cookies — section 3.2 explains why that distinction matters — and the only cookies required for the dashboard to work.
2.2 Preference Cookies
These cookies remember your choices and preferences to provide a more personalized experience:
- UI Preferences: whether the dashboard sidebar is expanded or collapsed
Preference Cookies Used:
- sidebar_state: whether the dashboard sidebar is expanded or collapsed
2.3 Analytics Cookies
We do not use any. There is no analytics cookie on this site and no Google Analytics. Our public pages load a cookieless visit counter from a web analytics provider; it sets no cookie and stores nothing on your device (see Privacy Policy section 2.4). The dashboard does not load it. We do not follow you across sites and we do not build a profile of your behaviour.
What we do keep is operational: our servers and our payment provider record requests in order to run and secure the Service, and our database holds your account, your credit balance and your run history. That is described in our Privacy Policy, and none of it relies on cookies.
Third-Party Services and Cookies
No third party sets a cookie on this site. The services we work with relate to cookies in one of two ways:
3.1 Payment Processing
- Stripe: to pay, you leave this site for a checkout page hosted by Stripe. Anything Stripe stores in your browser is set on Stripe’s own domain and governed by Stripe’s privacy policy, not by this one. We set nothing on your browser at that step, and we never see your card details.
3.2 Authentication Services
- Supabase: the sign-in cookies described in section 2.1 are set on our domain by our own server, using Supabase’s software. They are first-party cookies; Supabase does not set them in your browser itself.
3.3 Generation Providers
- Our processing providers receive the material you submit for a run; they do not set cookies in your browser.
Note: while you are on the Stripe checkout page you are on Stripe’s site, and what it stores there is governed by Stripe’s privacy policy rather than this one. Section 4 of our Privacy Policy describes the providers we pass data to and what each one receives.
Managing Your Cookie Preferences
You have several options for controlling how cookies are used on your device:
4.1 Browser Settings
Most web browsers allow you to control cookies through their settings. Here's how to manage cookies in popular browsers:
Google Chrome
- 1. Click the three dots menu → Settings
- 2. Go to Privacy and security → Cookies and other site data
- 3. Choose your preferred cookie settings
Mozilla Firefox
- 1. Click the menu button → Settings
- 2. Go to Privacy & Security
- 3. Choose your cookie and tracking settings
Safari
- 1. Safari menu → Preferences
- 2. Go to Privacy tab
- 3. Choose your cookie preferences
Microsoft Edge
- 1. Click the three dots menu → Settings
- 2. Go to Cookies and site permissions
- 3. Manage cookies and site data
4.2 Cookie Consent
We show no cookie consent banner, and the reason is that we have nothing to ask you about: the only cookies this site sets are the ones that keep you signed in and the one that remembers whether the sidebar is open. There is no advertising, analytics or tracking cookie to opt out of. Introducing one would require asking for your consent first.
Impact of Disabling Cookies
While you have the right to disable cookies, doing so may affect your experience on our platform:
5.1 Disabling Essential Cookies
Warning: blocking these cookies stops the dashboard from working — you will not be able to sign in or stay signed in, so you cannot reach your balance, your API keys or your run history. The API, the MCP server and the command-line client are not affected: they authenticate with an API key and use no cookies at all.
5.2 Disabling Preference Cookies
- Sidebar layout choices won't be saved
- Your light or dark theme choice is not affected: it lives in local storage, not in a cookie
- You'll need to reconfigure settings on each visit
Updates to This Cookie Policy
We may update this Cookie Policy from time to time to reflect changes in our practices, new technologies, or legal requirements. When we make significant changes, we will:
- Update the “Last Updated” date at the top of this policy
- Provide clear information about what has changed
We encourage you to review this Cookie Policy periodically to stay informed about our cookie practices.
Contact Information
If you have any questions or concerns about our use of cookies or this Cookie Policy, please contact us:
Email: support@dimantika.com
Contact form: https://dimantika.com/contact
Address: ul. Jana Heweliusza 11/819, 80-890 Gdańsk, Poland
KRS: 0001101232 · NIP: 9571172408 · REGON: 528408146
Entered in the Register of Entrepreneurs of the National Court Register (KRS) on 18 April 2024. Share capital 5,000.00 PLN.
We're committed to transparency about our cookie practices and will respond to your inquiries promptly.
Last Updated: 2026-11-02
This Cookie Policy is effective as of 2026-11-02. By continuing to use our service, you acknowledge that you have read and understood this policy.
If you have any questions about this document, please contact us at support@dimantika.com or through our contact form.