Terms of Service

01Agreement & who we are

These Terms of Service ("Terms") govern your use of the veizik.com website and the Veizik software ("Runtime") — a local AI video runtime, built on a native inference engine, that runs 30B-class open video models on a GPU you own (together, the "Service"). "Veizik", "we", and "us" refer to the operator identified below.

• Operator / brand: Veizik
• Registered business name: LinkPick
• Business registration jurisdiction: Republic of Korea
• Business registration number: 148-14-02554
• Representative: Bak Malgeum (박맑음)
• Billing provider: Polar, acting as Merchant of Record (see Section 7)
• Business / support contact: support@veizik.com, billing@veizik.com

Where the Service is available. The Service is currently not offered to residents of the European Union, the European Economic Area, or the United Kingdom. Accounts, keys and subscriptions are not sold into those territories at this stage of the launch, and checkout may be declined on that basis. This is a commercial availability decision, not a statement about your rights: if you are an existing customer in those territories, your statutory rights are unaffected and support@veizik.com will help you.

Payments are processed by Polar as Merchant of Record, but LinkPick, operating the Veizik brand, remains the operator of the Service and your counterparty under these Terms — using a Merchant of Record for billing does not transfer operational responsibility for the Service away from us.

By creating an account, activating an API key, installing the Runtime, or purchasing a subscription, you agree to these Terms. If you use the Service on behalf of an organization, you represent that you are authorized to bind that organization.

02The Service

Veizik is a local runtime, not a cloud rendering service. Rendering happens on your own hardware. The Service consists of:

• the Runtime you install locally (e.g. via curl -fsSL https://veizik.com/install.sh | sh, which requires git and Python 3.10+);
• the website (signup, key management, checkout, documentation); and
• the entitlement service — the server that issues and verifies license entitlements and session leases for the Runtime.

Supported environments at the time of these Terms: Linux x86_64 with an NVIDIA 24 GB-class GPU (Internal Verified — measured internally on RTX 3090), Windows WSL2 with NVIDIA (Experimental), and macOS Apple Silicon (Waitlist — not yet released). We do not claim support for all GPUs or platforms.

03Accounts & API keys

• You sign up with an email address; an API key is displayed once at signup. You are responsible for storing it securely. You bind it to the Runtime with veizik login <KEY>.
• Your API key and account are personal to you, unless your plan explicitly states otherwise. See Section 6 on sharing.
• You are responsible for activity under your key. If you believe your key is compromised, contact support@veizik.com to rotate it.
• You must provide accurate account information and be legally capable of entering this agreement in your jurisdiction.

04License & entitlement

Your paid subscription grants you an entitlement: a limited, non-exclusive, non-transferable, revocable right to run the Runtime with your tier's features for the duration of your subscription term. The entitlement is issued and enforced by the entitlement service; it is a license, not a sale of software.

The software's distribution license is published at github.com/veizikhq/veizik — LICENSE. A detailed End User License Agreement (EULA) will be bundled with the software at v1.0 after legal review; until then, that distribution license plus these Terms govern — these Terms control for the website, accounts, and billing.

When your subscription ends, your entitlement lapses to the free tier's scope. Section 12 describes the offline grace behavior if the Service itself is interrupted or discontinued.

05Tiers & commercial use

What you may do with outputs depends on your tier at the time of rendering:

• Every tier, including the free one, may be used for personal or commercial purposes within the scope that tier permits — and subject to the licence and usage restrictions of each third-party model, model weight, dataset or other third-party component you use with the Software. Veizik grants no rights in third-party models or content beyond the rights granted by their respective licensors. Wan 2.2 is Apache-2.0 and may be used commercially; FLUX.1-dev is non-commercial by its own licence and running it here does not change that. See model licences.
• One key licenses one computer. Every tier, paid or free, permits the Software to be registered and run on a single PC at a time. Additional computers require additional keys (volume discounts apply from five). Hardware replacement is supported by up to three self-service device transfers per twelve-month period.
• Tiers differ by capability range, not by usage. A tier determines which model families the Software will run, the maximum resolution and frame count, and which execution features are enabled. There is no per-render or usage-based charge: the Software runs on your own hardware and electricity.
• Paid tiers permit commercial use of outputs you render during an active licence, subject to Section 5a, Section 9 and Section 10 (including third-party model licenses). Commercial output rights apply on every tier and carry no revenue test; what varies by tier is deployment scope — see Section 5a. Creator is $29/month or $249/year; annual pricing is discounted against paying monthly, not a fixed multiple of it. Studio is offered by inquiry only — it is not available through self-serve checkout at this time. Billing has not opened yet — reserving with a free key collects no payment; these terms apply from your first charge.
• OEM/Enterprise offers are contracts by inquiry; their terms are set in the applicable order form and may include redistribution rights that these Terms otherwise withhold.
• TimeMachine (checkpoint-branch rendering) is not yet included in the public download; it has been validated internally and is planned to ship as a Preview build asset. When released it will be a beta feature on eligible tiers and may change or be interrupted without notice.
• No tier applies a visible watermark to your output, the free tier included. Removing or weakening the machine-readable AI provenance mark — present on every tier, paid tiers included — is separately prohibited and may put you in breach of AI transparency law where you operate. See AI transparency.
• Model licences are separate from your tier. A paid tier licenses the Runtime commercially; it grants nothing in the models you load. FLUX.1-dev is non-commercial and the Hunyuan family's licence does not apply in the EU, the UK or South Korea. See model licences.
• Some models are not available in every territory. The Runtime never ships model weights. Where a model publisher's licence excludes your territory, the Runtime will not download or load that model's weights there, and we do not publish its benchmark figures or sample outputs on pages addressed to those territories. The architecture support stays in the software; only the weights and their execution are territory-limited. This is a restriction imposed by the model's publisher, not by us, and we cannot waive it. If you hold a separate licence from that publisher, contact us and we will enable the model for your account.

05aCommercial use, deployment scope, and what we do not measure

You may use Veizik for personal or commercial purposes on every tier, including the free one, within the scope that tier permits. We do not ask an individual what they earn, and no tier requires a revenue statement or certification except where stated below for organisations.

Two different grants, and they are not the same

• Commercial output. You may sell, publish and be paid for what you render. This applies on every tier. It is limited only by the model licences below, never by your revenue.
• Infrastructure use. Running Veizik itself as shared or central inference, across a render fleet, as a hosted or API service, or embedded in or redistributed as part of another product, is a Business, Enterprise or OEM arrangement — at any revenue, on any tier. Selling your renders is not the same thing as running our engine as your infrastructure.

Model rights come from their publishers, not from us

Veizik grants no rights in third-party models or content beyond the rights granted by their respective licensors. Each model, weight and dataset carries its own licence and it travels with the weights whatever tier you are on. Wan 2.2 is Apache-2.0 and can carry commercial work; FLUX.1-dev is restricted to non-commercial use by its publisher's terms, and buying a paid tier here does not create a commercial right its licensor did not give. Territory restrictions are recorded per model artefact and licence revision, not per family — see model licences, which is the page to check before paid work.

Which licence an organisation needs

A Studio licence becomes a Business licence when any of these is true, whichever comes first: consolidated annual revenue reaches $1,000,000; the Software is operated as a shared inference or render server; it runs across a render fleet; it is deployed as a central API service; or GPU use exceeds the licensed count. An OEM agreement is required, regardless of revenue or tier, to offer Veizik capability to third parties as a service, to embed it in a product, or to redistribute the runtime.

Capacity, and what happens when you exceed it

We do not stop a render to make a licensing point. Exceeding your licensed capacity does not interrupt work in progress; it is reconciled afterwards on defined terms:

• Grace. Short-lived peaks above licensed capacity are permitted and are not billed.
• Sustained overage. Capacity held above the licensed count beyond the grace threshold stated in your order form is recorded as overage.
• True-up, at a rate agreed in advance. Recorded overage is reconciled on the next billing cycle at the per-GPU rate in your order form. We do not invoice a figure of our own choosing after the fact — if a rate is not stated in your order form, no overage is payable.
• You can see the same numbers we do. Licensed capacity, observed peak capacity and recorded overage are shown in your administrator dashboard, and the administrator is notified when overage begins accruing.

What the licence service receives, and for how long

Never your prompts, your input images, your generated video, or your filenames. The telemetry has no field for them: there is nowhere for a prompt or a media payload to go.

• What is received. A licence identifier; a pseudonymous device and GPU identifier; GPU count and class; runtime version; which capabilities are in use; concurrency; a timestamp.
• Purpose limitation. Used only for licence verification, issuing entitlements, capacity measurement, and detecting fraud or abuse. Not for analytics about your work, and not sold.
• Pseudonymous identifiers. Device and GPU identifiers are transmitted as keyed hashes (HMAC), so the licence service can tell one machine from another without holding the original hardware identifier.
• Retention. Raw licensing events are kept for 90 days. Aggregated capacity and billing records are kept as long as tax and accounting law requires, and no longer.

This is a term of the agreement, not a policy page, which means we cannot narrow it quietly. If we ever needed to receive something not on that list, it would take a change to these Terms and the notice period that comes with one.

05bAI transparency, provenance & watermarks

Veizik Runtime is a generative AI product. It uses generative AI models to produce images and video from your prompts and reference inputs. We state this before purchase because Korean AI Framework Act Art. 31(1) requires it, and because you should know what you are buying.

There are two different marks. Do not confuse them.

• Provenance marking — always on, every tier, cannot be disabled. Every image and video the Runtime writes carries a machine-readable provenance mark (C2PA Content Credentials, plus an in-pixel provenance signal) recording that the content was generated by an AI system and by which engine and model family. This mark is required of us by law (EU AI Act Art. 50(2); Korean AI Framework Act Art. 31(2)) and is present on free and paid tiers alike. It is not a branding mark, it does not appear on screen, and it does not restrict your commercial rights. You may verify any output with any C2PA-conformant verifier, or with the verifier we publish at veizik.com/verify.
• Visible watermark — none, on any tier. No tier of this Software draws a Veizik mark onto your picture, and that includes the free one. Nothing here is sold to you by making the free output worse to look at. The provenance marking described above is a separate thing that lives in the file's metadata, applies everywhere, and does not appear on screen.

Korean law applies to us wherever you are. Korean AI Framework Act Art. 31(3) requires that synthetic audio, images or video that are hard to tell from reality be disclosed in a way the user can clearly recognise, and Art. 4(1) extends the Act to conduct outside Korea that affects the Korean market or Korean users. That standard is stricter than the EU's, and LinkPick is a Korean business — so we hold to it on every output, in every territory, regardless of where a given sale happens.

What you may not do. You may not remove, strip, obscure, weaken, or circumvent the provenance marking, and you may not modify the Runtime, its output files, or any downstream processing for that purpose. Doing so may place you in breach of the AI transparency laws that apply where you operate, and is a material breach of these Terms.

Your own disclosure duty. If you publish AI-generated or manipulated image, audio or video content that resembles real persons, objects, places, entities or events and could falsely appear authentic (a "deep fake"), EU AI Act Art. 50(4) places the duty to disclose that on you as the deployer, not on Veizik. Where the content forms part of an evidently artistic, creative, satirical or fictional work, that disclosure may be made in a manner that does not hamper the display or enjoyment of the work. Equivalent duties may apply under Korean AI Framework Act Art. 31(3) and other national law. We provide the machine-readable mark; the visible disclosure to your audience is yours.

06Seats, devices & sharing

• A subscription is a personal seat: one person, not one PC. We do not charge per computer. What a plan limits is (a) how many computers may be registered to the seat and (b) how many may run at the same time.
• Every tier, free and paid: one key registers and runs on one computer. A second computer needs a second key. Up to three self-service device transfers per twelve months cover hardware replacement. Current limits are always shown on the pricing page and at checkout.
• Replacing hardware is normal. You can release a registered computer yourself (self-service via the API or your account) up to 3 times per year — e.g. a new PC, a reformat, or a GPU swap. Registration is bound to a machine fingerprint, not to the GPU alone, so changing a GPU does not by itself break your license. For genuine hardware failures beyond the yearly limit, contact support@veizik.com.
• Concurrent execution is enforced by short-lived render leases with heartbeats. If your internet connection drops, the Runtime keeps working offline for up to 30 days before it needs to check in again — a studio that loses its uplink mid-project does not lose the project. Seat and concurrency limits still require that check-in, so the offline window extends your ability to work, not the number of machines you may work on.
• Account and key sharing is prohibited. You may not share, publish, sell, rent, or lend your API key or account, or pool one subscription across multiple people.
• Creator includes community support. Pro adds the priority support channel. Studio Node adds one-business-day support. Advanced/dedicated technical support is an OEM/Enterprise contract item.
• We may throttle, suspend, or revoke entitlements that show clear signs of sharing or automated key abuse. Where practical, we will contact you first.

07Billing, cancellation & refunds

• Paid subscriptions are sold through Polar, acting as Merchant of Record, via hosted checkout. Prices are in USD; applicable taxes are calculated and handled by Polar.
• Subscriptions renew automatically each billing period until cancelled.
• Cancellation: you may cancel at any time in the customer portal — sign in with the email you paid with. The same portal is where you update a card. Your entitlement remains active until the end of the current paid billing period, after which it lapses. No partial-period credit is given for cancellation.
• Refunds are processed through Polar and governed by our Refund Policy (Policy v1). In summary: within 7 days of your first subscription, if the free sample fails to run in a stated supported environment (Internal Verified or Experimental) and you submit a diagnostic report, you receive a full refund. Renewal payments are non-refundable except where required by law.
• Use the same email for checkout and your API key so your payment can be matched to your account.

08aPerpetual fallback licence

Pay for twelve months and one version of the Software is yours to keep, permanently, whether or not you keep paying us — and whether or not we are still here. This is the only honest answer we have to the fair question about subscription software: what happens to the work you make a living from if you stop paying, or if we stop existing. It should not be "it stops opening".

• How it is earned. Twelve consecutive paid months on a paid tier. Monthly and annual billing both count — an annual payment buys twelve months at once, twelve monthly payments buy them one at a time, and both arrive at the same place.
• Which versions you keep: every one released while you were paying. Not the version from a year ago — the one you were actually running on your last paid day, and everything before it. What vests is a date, and any build published on or before it is yours. We chose this deliberately over the more common rule, under which you fall back to the build from twelve months earlier and lose the one you had been working in; that is the clause people find out about later and rightly resent. The date is fixed once, when you earn it, and a later correction to our release dates cannot move it.
• What it lets you do. Everything your tier allowed on that version, including commercial use if your tier had it, for as long as you like, on the machines your tier allowed. It does not include updates, new versions, or support, and we will not be fixing that version.
• Cancelling does not take it away. That is the whole point. If you paid twelve months and left, you earned it and you keep it.
• A chargeback does take it away, and it is the only thing that does — a month that was charged back was not a paid month. A refund breaks the run towards the licence but does not reach one you have already earned.
• It has to work without us. A promise that depends on our servers still answering is not insurance against us, it is a decoration. The perpetual licence is delivered as a signed file your copy verifies on its own, with no expiry and no check-in.

What we owe you if we stop. A promise that quietly depends on us being alive is not insurance against us. So:

• It survives us ending this, not just you. The licence continues through any expiry or termination — including our own decision to discontinue the Software, which is precisely the case the promise exists for. The only thing that ends it is your own uncured material breach. We say this explicitly because the best-known version of this clause in the industry does not: it is drafted to survive customer-initiated cancellation and, read literally, not the vendor's own withdrawal of the product.
• The terms freeze with the software. If we change these Terms and you are relying on a perpetual fallback licence, you may keep using it under the terms that applied when you earned it. Otherwise "perpetual" would mean only that we cannot take the file away, while remaining free to rewrite what it permits.
• The build that needs no licence server already exists. It is not something we promise to make later. A version of the Software that performs no licence check at all is produced alongside each release, its SHA-256 is published here, and the artefact itself is held in escrow for release if we cease operating this service. We do not publish the build while we are trading, for the obvious reason; we publish its fingerprint, so that whatever is released can be checked against what we committed to.
  This is deliberately not the usual wording, because the usual wording has a documented failure. Large vendors have shipped activation-free rescue builds when they switched their servers off — and those rescue downloads were themselves withdrawn a few years later, so the escape hatch protected only the people who happened to grab it in time. A rescue that has to be built and hosted at the moment of shutdown depends on us being there to build and host it, which is precisely the assumption this section exists to remove.
• We keep the builds your licence covers downloadable. A licence naming a version is worth nothing if the version cannot be obtained, so every release stays available for download for as long as we operate this service — we do not delete old builds to tidy up. We would still advise keeping your own copy of the build you rely on, alongside your licence file: the vendors whose rescue downloads were quietly withdrawn a few years after a shutdown were not acting in bad faith, they simply stopped hosting.
• Your licence file is yours to hold. The perpetual certificate is written to your own machine and can be exported and kept wherever you like. You never have to ask us for it, and there is no counter and no transfer limit on it. The failure mode we are avoiding is the one where a customer's entitlement survives on paper while the only way to actually install it runs through a server that is no longer answering.

The honest limits of this promise. Three things it cannot insure against, said plainly rather than discovered later. Anything that calls our servers stops working — the rendering does not, but account, delivery and verification features do. Our code-signing and notarisation certificates expire, and after that macOS and Windows may refuse to launch the build regardless of what any licence says; that is a kill switch we do not fully control. Operating systems move on, and an old build eventually stops running for reasons no licence can address. A promise with stated limits is the kind worth believing.

Not yet issued, and we would rather say so than let you find out. Nothing can earn this before billing opens, so no one is waiting on it. It also has a real precondition: the Software must be able to verify a licence that never expires and refuse to apply it to a build newer than the one it names. Until it does both, issuing these files would grant every future version rather than the one earned — and because the file is designed to keep working without us, that mistake could not be taken back. Months are being counted from the first payment; the file is issued once the check exists.

09Prohibited conduct

Scope. Veizik does not provide face swapping, audio-driven lip-sync or mouth reanimation, or voice cloning. These are absent from every build, not merely disallowed.

You may not, and may not assist or permit anyone to:

• reverse engineer, decompile, disassemble, or extract the Runtime's engine internals, except to the extent a law expressly permits it notwithstanding this restriction;
• share, publish, resell, or sublicense API keys or entitlements, or circumvent device limits, AI provenance marks, tier restrictions, or the entitlement service;
• remove, strip, obscure, weaken, or circumvent the machine-readable AI provenance marking on any output, or modify the Runtime or its outputs for that purpose;
• use the Service to generate unlawful content — including content that infringes intellectual-property or publicity rights, child sexual abuse material, or content unlawful in your jurisdiction or the Republic of Korea;
• use the Service — alone or as one stage alongside third-party tools — to produce face swaps, deepfakes, audio-driven lip-sync, or voice clones of a real, identifiable person, with or without that person's consent;
• use the Service to create deceptive impersonations of real people without authorization, or content intended for fraud or harassment;
• interfere with, probe, or disrupt the website or entitlement service, or misrepresent telemetry sent to it.

We may suspend or terminate accounts for material violations. Because rendering is local, we do not review your content (Section 11); enforcement is based on entitlement abuse signals and reports.

10Your content & outputs

• Your inputs (images, video, prompts) and outputs are yours. We claim no ownership of them, and — because they never leave your machine (Section 11) — we never receive them.
• As between you and us, you may use outputs within your tier's scope (Section 5). You are responsible for your outputs, including compliance with the licenses of the third-party open models you run and with rights of any people or works depicted in your inputs.
• AI-generated output may be similar to output generated for others and may be subject to jurisdiction-specific rules on authorship; we make no representation about the copyright status of outputs.

11Privacy & data

• Your media stays local. Input images, video, prompts, and rendered results remain on your machine. The Runtime never uploads them.
• The Runtime communicates with our servers only for license entitlement and session leases: key ID, device ID, and tier. No media is transmitted.
• The website collects anonymous funnel events only (an anonymous ID and event names). We do not run advertising and do not sell data.
• Details are in the Privacy Policy, which is part of these Terms.

12Preview status, changes & discontinuation

• The Service is in Technical Preview. Features (including TimeMachine beta), supported environments, and pricing for not-yet-live tiers may change. Published performance numbers are internal benchmarks with no third-party verification yet.
• Known limits we disclose today: the engine applies quantization only where it holds up against the fp16 reference and disables it where it does not, and no external reproduction data exists yet.
• Offline grace — 30 days. The Runtime executes locally and does not hard-stop the moment our servers are unreachable. An entitlement stays valid for 30 days without contacting us, so an interruption on our side, or on your connection, does not block work you have already paid for. We give the number rather than saying "a reasonable period", because a reasonable period is exactly what people end up arguing about.
• If we permanently discontinue the Service, we will give reasonable advance notice by email and on the website, and stop charging renewals.

13Disclaimers & limitation of liability

To the maximum extent permitted by law, the Service is provided "as is" and "as available", without warranties of merchantability, fitness for a particular purpose, or non-infringement. Performance on your specific hardware may differ from our internal benchmarks. We do not warrant that the Runtime will be error-free or uninterrupted, that any model will run on unlisted hardware, or that beta features will remain available.

To the maximum extent permitted by law, we are not liable for indirect, incidental, special, consequential, or punitive damages, or for loss of profits, data, or renders. Our aggregate liability arising out of the Service is limited to the amounts you paid us in the 12 months preceding the claim (or, if you paid nothing, USD $50). Nothing in these Terms limits liability that cannot be limited under applicable law, including under the consumer-protection laws of the Republic of Korea.

14Governing law

These Terms are governed by the laws of the Republic of Korea, without regard to conflict-of-law rules. Disputes arising from these Terms or the Service are subject to the jurisdiction of the competent courts of the Republic of Korea, provided that mandatory consumer-protection provisions of your country of residence remain unaffected where they apply.

15Changes to these Terms & contact

• We may update these Terms as the Service evolves. Material changes will be announced on the website (and by email for paid subscribers) with the new effective date; continued use after the effective date constitutes acceptance.
• If you do not agree to a change, stop using the Service and cancel your subscription; Section 7 governs the remainder of your paid period.
• Questions: support@veizik.com · github.com/veizikhq/veizik