Legal
Cookie Policy
This policy lists every cookie the Velora website sets, what each one does, and how long it lasts. It is short because there is very little to describe.
Effective September 14, 2026
The short version
Velora’s website sets one cookie, and only after you sign in. It keeps you signed in. There is no analytics, no advertising, no tracking pixel, no session recording, and no third-party script of any kind on this site. Nothing here follows you to another website, and nothing builds a profile of you.
Because the only cookie is strictly necessary to deliver a service you asked for, no consent banner is required and none is shown. If that ever changes, this page changes first and you will be asked before anything non-essential is set.
The cookie we set
| Name | Purpose | Lifetime | Category |
|---|---|---|---|
velora-auth | Keeps you signed in and lets your session refresh securely. Set by our authentication provider, Supabase, on this domain. Without it you would be signed out on every page. | Until you sign out, or the session expires | Strictly necessary |
Signed out, this site sets no cookies at all. You can browse the entire public site — the home page, pricing, documentation, changelog, downloads, and this policy — without one being written.
What we deliberately do not use
This list is specific on purpose, so you can check it against what your browser actually reports:
- No analytics. No Google Analytics, Plausible, Fathom, PostHog, Mixpanel, Segment, or any equivalent. We do not measure your visit.
- No advertising or social pixels. No Meta pixel, no LinkedIn Insight tag, no conversion tracking, no retargeting.
- No session recording or heatmaps. Nothing records your mouse, your scrolling, or your keystrokes.
- No third-party embeds. No embedded videos, maps, chat widgets, comment systems, or social buttons. There are no iframes on this site.
- No external fonts or CDNs. Typefaces are served from this domain, so requesting a page does not tell any other company that you did.
Browser storage
Aside from the cookie above, authentication uses your browser’s local storage to hold session details between page loads. That data stays in your browser, is not transmitted to us as a cookie, and is cleared when you sign out. Your theme and similar display choices, where the site offers them, are stored the same way.
Payments
Paid subscriptions are processed by Stripe. When you begin checkout you are taken to Stripe’s own pages, where Stripe sets cookies on Stripe’s domain under Stripe’s policies — including ones used for fraud prevention. Velora cannot read those cookies, and Stripe does not set any on this domain. Stripe’s privacy policy governs that part of the transaction.
Managing cookies
Every browser can block or delete cookies, and you may do so for this site. Blocking the authentication cookie will prevent you from signing in or staying signed in, because it is what a signed-in session is made of; everything else on the site will continue to work. Signing out removes it.
The desktop application
The Velora desktop app is not a website and does not use cookies for its own features. It stores your session credentials in your operating system’s keychain or credential vault, and its data in a local database on your machine. Where an agent you direct opens a web page, that browsing happens in an isolated browser under your instruction and is described in the Privacy Policy.
Changes
We will update this page before introducing any cookie or similar technology that is not strictly necessary, and will ask for consent where the law requires it. The effective date above records the current version.
Who to contact
- Service
- Velora
- Operated by
- Utsav Das, trading as Velora. Velora is an independent sole proprietorship, not an incorporated company.
- Contact
- support@runvelora.app
- Postal address
- 4601 Marshall Hall Lane, Fairfax, VA 22033
- Governing law
- Virginia, United States
Privacy requests, legal notices, and billing questions can be sent to the address above. Support questions are usually answered faster through the support page.