VidSparks | Cookie Policy | v1.0 | Effective 21 July 2026
| Field | Value |
| Operator | LOGIC OCTAVE LTD |
| Company number | 15587296 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | VidSparks |
| Website | https://vidsparks.com |
| Contact email | info@vidsparks.com |
| Support / complaints | info@vidsparks.com; Monday to Friday, 09:00-17:00 UK time, excluding public holidays |
| Governing law | England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Important: Strictly necessary technologies support secure login, checkout, consent choices and reliable delivery. Analytics, performance and marketing technologies are not activated until the applicable consent is obtained. You can change non-essential preferences without losing access to core account functions. |
1. Introduction and scope
1.1 This Cookie Policy explains how LOGIC OCTAVE LTD, trading as VidSparks, uses cookies, local storage, session identifiers, pixels and comparable technologies on https://vidsparks.com and within the Account interface. It should be read with the Privacy Policy.
1.2 The Policy distinguishes technologies needed to provide a requested and secure online service from optional technologies used for measurement or marketing. The specific technologies present can change as providers and features change; the consent interface controls optional use at the time of the visit.
2. What cookies and similar technologies are
2.1 A cookie is a small text record placed on a browser or device. Local and session storage keep comparable data inside the browser. Pixels and software development tools may send an event to a service provider when a page loads, a consent choice is made or an authorised feature is used.
2.2 First-party technologies are set for the VidSparks domain. Third-party technologies are supplied by another provider, such as a payment, analytics or embedded-service provider. A technology may last only for the browser session or for a stated period, subject to browser settings and earlier deletion.
3. Why we use cookies
3.1 We use essential technologies to maintain sessions, prevent cross-site request forgery, remember a consent choice, route traffic, protect checkout state, detect abuse and keep the Account signed in where the user requests that function. Disabling these items may make login, payment or generation unavailable.
3.2 With consent, we may measure pages, errors, feature usage and campaign performance, or remember non-essential preferences. Optional data helps us understand whether users can find Token Pack information, complete checkout and use generation tools, but it is not required for the core contractual service.
4. Cookie categories
| Category | Purpose | Consent required | Effect if disabled |
| Strictly necessary | Authentication, security, checkout state, load balancing, fraud prevention and consent storage | No, where legally exempt because essential to the requested service | Login, payment, security controls or preference storage may fail |
| Functional / preferences | Remember non-essential interface choices such as language, layout or recent tool settings | Yes, where the choice is not strictly necessary | Preferences reset and some convenience features may be unavailable |
| Analytics / performance | Measure visits, feature use, errors and aggregated service performance | Yes | Core Service remains available; measurement is reduced |
| Marketing | Measure campaigns, limit advertising frequency and support relevant promotion | Yes | Core Service remains available; advertising is less tailored or measurable |
4.1 A single provider can support more than one category. Classification depends on the actual purpose of a particular technology, not the provider name. We do not treat a technology as essential merely because it is useful to our business or simplifies analytics.
5. Lawful basis and consent
5.1 Non-essential cookies and similar technologies are activated only after the user makes the relevant choice through the consent interface, where prior consent is required. Consent is specific by category, can be refused without detriment to the core Service and can be withdrawn as easily as it was given.
5.2 Strictly necessary technologies may operate without consent where they are essential to deliver a service explicitly requested by the user, such as secure authentication, checkout or fraud protection. We still provide information about them and limit their use to the necessary purpose.
5.3 The related processing of personal data follows the lawful bases explained in the Privacy Policy. Refusing optional cookies does not prevent transaction records, security logs or other data from being processed where another lawful basis applies.
6. Cookie inventory and representative technology
| Cookie / technology | Type | Purpose | Duration | Provider |
| Session identifier | Strictly necessary; first-party cookie | Maintains authenticated Account and secure navigation | Session or up to 24 hours | VidSparks |
| Security / CSRF token | Strictly necessary; first-party cookie or storage | Protects forms and account actions against forged requests | Session | VidSparks |
| Consent preference record | Strictly necessary; first-party cookie or storage | Stores consent categories so the choice is applied on later visits | Up to 12 months | VidSparks or consent-management provider |
| Checkout state token | Strictly necessary; first-party or PSP technology | Links the Account to a secure payment session and prevents duplicate submission | Session or up to 24 hours | VidSparks / payment provider |
| Fraud and device signal | Strictly necessary; provider technology | Detects suspicious payment, login or automated abuse | Session to 13 months, depending on provider | Payment or security provider |
| Interface preference record | Functional; first-party storage | Remembers optional language, layout or recent settings | Up to 6 months | VidSparks |
| Analytics client identifier | Analytics; cookie or local storage | Counts visits and feature events after consent | Up to 13 months | Analytics provider |
| Performance event | Analytics; pixel or server-linked event | Measures errors, latency and completion of key steps after consent | Event data retained under the Privacy Policy | VidSparks / analytics provider |
| Campaign attribution tag | Marketing; cookie or URL-linked storage | Attributes a visit or purchase to a consented campaign | Up to 90 days | Marketing provider |
6.1 The inventory describes the function and expected duration even where the technical key is generated dynamically. The live consent interface and browser developer tools provide the most current deployment details. Optional provider technology is not loaded before the relevant consent where prior consent is required.
7. Third-party cookies and embedded services
7.1 A PSP may set technologies required to authenticate a payment, prevent fraud, maintain checkout state or comply with card-network obligations. Those technologies can be essential to the requested payment and may be governed partly by the PSP notice shown in its checkout environment.
7.2 An embedded video, support widget, model preview or social feature may contact its provider when loaded. Where the feature is not essential, we seek the relevant consent before activation or provide a click-to-load mechanism. A third party is responsible for its independent processing under its own notice.
8. Managing preferences
8.1 You can accept, reject or customise optional categories through the consent banner or preference control. A later change applies prospectively. Technologies already stored can also be deleted through browser settings, although deletion of the consent record may cause the banner to appear again.
8.2 Browsers allow users to block all cookies, block third-party cookies, clear storage or limit tracking. Blocking essential items may prevent secure login, Token purchase or generation. Instructions vary by browser and device, so use the current help materials supplied by the relevant provider.
9. Retention and inventory control
9.1 Session technologies expire when the session ends or shortly afterwards. Persistent technologies use the duration shown in the inventory unless deleted earlier, renewed after a fresh interaction, or changed through a consent choice. Related server-side data is retained according to the Privacy Policy rather than indefinitely through the browser key.
9.2 We compare deployed technologies against this Policy when adding or changing checkout, analytics, advertising, support or embedded features. A technology that changes purpose is reclassified and, where required, is held back until the appropriate consent is obtained.
10. Do-Not-Track and browser privacy signals
10.1 Some browsers transmit Do-Not-Track or other privacy signals. There is no single universal interpretation for every signal, but we apply the consent choices presented through the Service and will honour a legally recognised opt-out signal where applicable to the processing concerned.
10.2 A browser signal does not disable strictly necessary security, authentication or checkout technology. It may restrict optional analytics or advertising where the signal is technically recognised and legally relevant. Users can always make a direct choice through the preference control.
11. Children and age
11.1 The Service is intended for users aged 18 or over and is not designed for children. We do not knowingly use optional tracking to profile children. If we identify an underage Account or inappropriate collection, we may disable the Account and remove data that is not required for legal or security reasons.
11.2 A parent or guardian who believes a child has interacted with the Service should contact the privacy address. We may request enough information to locate the relevant device, Account or communication while avoiding unnecessary collection of additional child data.
12. International data flows
12.1 A cookie or comparable technology may transmit identifiers, device data or events to a provider outside the United Kingdom. Where that is a restricted transfer, we use an applicable adequacy arrangement, approved contractual safeguard or another lawful mechanism described in the Privacy Policy.
12.2 Optional international transfers do not occur through an optional category before the required consent. Essential payment or security providers may process data internationally where needed to perform the requested service and where an appropriate transfer mechanism and security controls are in place.
13. Changes
13.1 We may update this Policy when technologies, providers, legal requirements or purposes change. The version and effective date identify the current publication. A material change to optional tracking is reflected in the consent interface so users can make an informed choice.
13.2 An update does not convert an optional technology into an essential one merely by description. Classification follows the actual function and applicable law. Where a new purpose requires consent, the technology remains inactive until the choice is obtained.
14. Contact
14.1 Questions about cookies, consent or browser storage may be sent to info@vidsparks.com or to 20 Wenlock Road, London, England, N1 7GU. Include the browser, device, approximate time and screenshot where relevant, but do not send passwords, full card information or authentication codes.
14.2 Privacy rights concerning data produced by cookies are handled under the Privacy Policy. A request to change consent can usually be completed directly through the preference control without identity verification, while a request for linked Account data may require proportionate verification.
14.3 This Policy is governed by the laws of England and Wales. Mandatory privacy, electronic-communications and consumer protections applicable in the user’s location remain unaffected, including rights to withdraw consent and complain to a competent supervisory authority.
Checklist. Operational Maintenance Checklist
| Control point | Required action |
| Before adding a provider | Identify every browser technology, purpose, duration, recipient, transfer route and whether prior consent is required. |
| Before release | Test that optional tags remain blocked before consent and that reject and withdraw choices work without impairing core Account functions. |
| After a feature change | Compare live cookies and storage keys against the inventory and update the consent interface and Policy where function or duration changed. |
| At least quarterly | Review consent logs, provider configuration, retention, transfer safeguards and any unclassified technology detected in production. |
| After a complaint or incident | Reproduce the user path, preserve relevant evidence, correct misclassification promptly and assess whether notification or wider remediation is required. |
This checklist describes the governance standard applied to the live implementation. It is not a user obligation and does not limit the rights or choices stated above.
VidSparks | Cookie Policy | v1.0 | Effective 21 July 2026. Published on the website; subject to update; the current published version governs.