Privacy Policy

Veluko is a pre-launch product for agencies, studios, and freelancers. It is built so teams can share a review link, collect feedback on the right version, record an approval, and keep extra work from becoming unpaid revisions — without asking the client to create an account.

Until a registered company name and address are published here, the operator of this website is the person or team publishing Veluko. A legal entity, registered address, and a dedicated privacy email will be added before paid accounts are offered.

This policy applies to veluko.com (or the domain where this site is hosted) and to the demo and review pages on that domain. It applies to visitors, waitlist subscribers, and anyone who opens the in-browser demo or a demo review link.

It does not apply to third-party sites we link to, or to tools you already use for client work (Figma, Slack, email, and similar). Those services have their own policies.

Today we collect personal data only when you choose to join the waitlist or leave optional waitlist feedback. The in-browser demo does not send project, file, comment, or approval data to our servers.

We do not run advertising pixels, third-party analytics suites, or social tracking on this site. Fonts are self-hosted with the application, so your browser does not fetch them from Google or another font CDN at runtime.

If you join the waitlist, we store the information you submit so we can email launch and early-access updates and understand who Veluko should serve first.

• Work email (required).
• What best describes you — for example freelancer, web agency, marketing agency, branding studio, video studio, development agency, UX/UI studio, or other (required).
• How many active clients you currently work with — 1–5, 6–15, 16–30, or 31+ (optional).
• A short note about the biggest problem in your current client review or approval process (optional; you can skip this step).

If you arrived from a campaign link, we may also store UTM parameters from the URL (source, medium, campaign, content, term) and the referring website, when the browser provides it. That helps us see which channels bring people to the waitlist. We keep this in session storage in your browser until you submit the form, then save it with your waitlist row.

The waitlist form includes a hidden honeypot field to reduce spam. If that field is filled, we ignore the submission and do not store it.

Waitlist records are stored in a private database table hosted by Supabase, accessed only with a server-side service key. Public visitors cannot read other people’s waitlist rows. Duplicate emails are not inserted again; we treat a second signup as “already joined.”

If an optional notification webhook is configured by the operator, a copy of the signup or feedback payload may also be sent to the operator’s internal automation (for example a private Slack, email, or workflow tool) so new signups are not missed. That payload can include email, persona, client-band, optional pain-point text, UTM fields, and referrer.

The product demo at /demo (and related workspace pages) is an interactive preview of Veluko. It runs in your browser. Workspace data — sample projects, deliverables, review rounds, comments, approvals, change requests, plan switching, and anything you add while exploring — is saved in local storage under a key used only on your device (veluko-demo-workspace).

That demo state is not uploaded to Veluko servers. We cannot see your demo projects, reset them remotely, or recover them if you clear your browser. If you reset the demo from the product, or clear site data, the sample workspace is rebuilt locally.

The demo is seeded with fictional studio and client examples (such as sample review tokens). You can also type your own names, emails, files, and comments while you explore. Treat the demo as a sandbox: do not paste real client secrets, production credentials, or confidential files. Anything you type stays in that browser profile unless you copy it elsewhere yourself.

There are no real user accounts in the demo. Plan names shown in the demo (for example Freelancer or Studio) only change what the local preview displays. They are not a purchase and they are not billed.

Veluko’s intended client flow is a protected review link: the studio sets an unlock email, the client opens the link, types that email, reviews the files for that version, leaves comments, and can approve or request changes — without creating a Veluko account.

In this demo, that check happens only in the browser. The email you type is compared with the unlock address stored in local demo data. If it matches, the page remembers the unlock in session storage for that review token until you close the tab (or until session storage is cleared). The typed email is not sent to our servers and is not added to the waitlist.

When a hosted product launches, review unlock, comments, and approvals will be stored on our systems under a new privacy policy. Until then, demo review pages are a local simulation.

We do not set advertising or analytics cookies. We use a small amount of browser storage that is similar in effect to strictly necessary or functional storage:

• Session storage for waitlist attribution (UTM and referrer) until you submit or close the tab.
• Local storage for the demo workspace so your exploration can persist if you refresh.
• Session storage for demo review unlock so you are not asked for the email on every click in the same tab.

You can block or clear this storage in your browser. The marketing site and waitlist still work without the demo storage. Clearing storage will reset the demo and signed-in-looking review unlock in that browser.

We use waitlist data to:

• Send launch, early-access, and related product emails to the address you gave us.
• Prioritize who to invite first and which workflows to build, using persona, client volume, and optional feedback.
• See which campaigns or referring sites brought people to the waitlist.
• Prevent duplicate signups and reduce spam.
• Respond if you contact us about your data or about early access.

We do not sell personal data. We do not use waitlist emails for unrelated third-party advertising.

If you are in the European Economic Area, the United Kingdom, or another region with similar rules, we process waitlist data on these bases:

• Consent — you submit the waitlist form (and optional feedback) so we can email you and learn who the product should serve.
• Legitimate interests — keeping the form free of spam, understanding channel attribution at a coarse level, and operating the site securely.

Demo workspace and review-unlock data processed only on your device is under your control. We are not the recipient of that data.

We share waitlist data only with processors that help us run this pre-launch site:

• Supabase — hosts the waitlist database. Access is restricted to the operator via a server key; anonymous visitors cannot query the table.
• Optional internal webhook destination — only if the operator has configured one, to notify the team of new signups or feedback.
• Email delivery — when we send launch or early-access messages, your address is processed by the email channel we use for that purpose. That channel will be named here when transactional or broadcast email is connected.

We may also disclose information if required by law, or if needed to protect the site, our users, or the operator from fraud or abuse.

Hosting of the website itself (for example the application host and CDN) will process technical request data such as IP address and user agent in server logs, as most websites do, for security and reliability. We do not use those logs to build marketing profiles.

Waitlist records are kept until you ask us to delete them, until we shut down the waitlist, or until they are no longer needed for launch communication — whichever comes first. Optional feedback is stored with the same waitlist row.

Browser demo data remains until you clear it, reset the demo, or your browser expires the storage. Session unlock and attribution storage typically last until the tab or browser session ends.

When a paid product launches, retention for customer accounts, hosted files, comments, and approvals will be described in an updated policy before those features store data on our servers.

Depending on where you live, you may have the right to access, correct, delete, or export the waitlist data we hold about you, to object to or restrict certain processing, and to withdraw consent for waitlist emails.

To make a request, join or use the waitlist form with the same work email and clearly say that you are making a privacy request (access, correction, or deletion). If you already joined, use that same email so we can find your row. We will add a dedicated contact address on this page before public launch.

You can also stop launch emails using the unsubscribe method included in those messages once email sending is active. You can clear demo data yourself in the browser.

If you are in the EEA or UK, you may also complain to your local data protection authority. In Lithuania that is the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija).

Supabase and any webhook or email provider may process data in the EU, the United Kingdom, the United States, or another country where they operate. Where a transfer needs safeguards under EU or UK law, we will rely on the provider’s published transfer mechanism (such as Standard Contractual Clauses) and name the region here once production infrastructure is fixed.

Veluko is aimed at professionals running client work. We do not knowingly collect personal data from children under 16. If you believe a child has submitted a waitlist email, contact us using the process in section 12 and we will delete it.

Waitlist inserts go through a server action to a locked-down database table. The public site cannot list waitlist emails. Demo project data never leaves your browser in this version, which also means we cannot encrypt or back it up for you.

No method of transmission or storage is perfectly secure. Do not use the demo to hold real confidential client material.

We will update this page when the product starts storing customer files, comments, approvals, or account data on our servers, when we add analytics or email providers, or when the law requires it. The “Last updated” date at the top will change. Material changes for waitlist subscribers will be reflected here before those new processing activities begin.

For privacy questions or requests about waitlist data, use the early-access form on the Veluko homepage with a short note that you are contacting us about privacy. A direct email address will replace this process before anyone is asked to create a paid account.