Privacy Policy

1. Scope

This Privacy Policy explains how Veylaro Labs ("Veylaro", "we", "us") handles information in connection with the Veylaro desktop application (the "App") and the veylaroai.com website (the "Site"). It applies to all plans: Free, Pro, Team and Enterprise. Where local law grants you stronger rights (GDPR, CCPA/CPRA, and similar), those rights apply in full.

2. What runs locally (everything that matters)

The defining property of Veylaro is that the AI is on your machine. The following core operations stay local; the optional search-query exception is stated explicitly:

• Model inference. Every token Veylaro generates is computed on your hardware.
• Your code and files. Reading, indexing, editing and searching your projects.
• Prompts and conversations. Coding chat stays local. If you enable web search, the query shown in the activity stream is sent to the search provider.
• Memory. Veylaro's long-term memory of your projects and preferences, stored in the App's local data area and protected by your device account and disk security.
• Private verified learning. If you enable it, passing checks and compact task summaries are stored locally for retrieval on similar work. They are not uploaded or mixed into another user's model.
• Transcripts and logs of AI activity. Session history lives in your local app data folder and is yours to keep or delete.
• Images, documents and other inputs you provide to the App.

You can verify this with a network monitoring tool. Blocking the App's network access leaves local inference and local project work available; optional web search, account verification and update checks will be unavailable.

3. The data we do collect

We collect the smallest set of data required to operate a software business:

• Account data (all plans, including Free). Email address and display name, used for login, plan enforcement, receipts and license recovery. Accounts are stored with Supabase Authentication (hosted in the EU/US); your password is hashed by Supabase and never visible to us.
• Billing data. Handled by our payment processor (see §5). We receive plan, status and country — never your full card number.
• License checks. Paid apps periodically confirm license validity by sending a license token, app version, and a coarse platform identifier (e.g. "macOS/arm64"). No code, prompts, file names, hardware serials or usage content are ever included.
• Crash reports. Diagnostic upload is disabled in the current build and there is no crash-upload endpoint. A future release may add a separate opt-in flow with a new disclosure.
• Support correspondence. Whatever you choose to email us.

4. The data we deliberately do not collect

• No source code, diffs, file contents or file names.
• No full prompts, completions, chat history or AI transcripts. Optional web search transmits only the query displayed in the activity stream.
• No behavioral analytics or telemetry inside the App. There is no event tracking, period.
• No service-side training on user data. Optional private verified learning stays on your machine and can be exported or deleted by you.
• No advertising identifiers, no data sales, no data "sharing" as defined by the CPRA. We have never sold personal information and never will.

5. Payments

Purchases are processed by a PCI-DSS Level 1 payment processor acting as our processor (currently Stripe, Inc.), with checkout in USD or NZD. Your card details go directly to them; we receive only subscription status, plan tier, and billing country. Their privacy policy governs their processing.

6. Model updates & licensing

When you check for updates (or enable automatic updates), the App requests a version manifest and, if you choose, downloads new binaries and model weights. These requests carry the same minimal payload as license checks (§3). Updates are always optional; declining them never disables the model versions you already have.

7. Website

Website analytics collection is currently disabled. An optional Vercel Web Analytics integration is prepared for public-page visits and download-button clicks. If enabled, page URLs are sent without query strings or fragments; account and admin routes are excluded. Download events contain only the platform and a broad referral category such as Google, X, direct, or other. A referral category is stored for the current browser tab, without a visitor identifier. Download clicks do not prove installation or account creation. Analytics never includes project code, chat content, passwords, or email form values.

The Site uses no advertising trackers. We use Supabase for accounts and to store register-interest emails you submit before launch — those are used only to tell you when downloads open, never sold or shared, and deleted on request. We keep standard, short-lived server logs (IP address, user agent, pages requested) for security and capacity planning, retained for a maximum of 30 days.

8. Support

If you contact support, we use your message and email solely to resolve your issue. If a bug requires sharing a code sample, you choose what to send — we will never ask for more than a minimal reproduction, and support materials are deleted within 90 days of ticket closure.

9. Retention

• Account & billing records: for the life of the account plus the period required by tax and accounting law (typically 7 years for invoices).
• License check logs: 90 days, then aggregated and deleted.
• Site logs: 30 days.
• Crash reports: none collected by the current build.
• Everything on your device: yours, forever, under your control. Uninstalling the App removes it, or you can delete the app data folder at any time.

10. Your rights

Depending on where you live, you may have rights of access, rectification, erasure, portability, restriction and objection, and the right to lodge a complaint with a supervisory authority. We honor all of these globally, not just where forced to, and we will respond to any request within 30 days of receiving it through the contact channel published in section 14. Deleting your account removes your personal data from our systems within 30 days, subject to the legal retention items in §9. Because your AI data never reached us, there is nothing further to delete on our side — it is already only on your machine.

11. Security

• All Site and API traffic is encrypted in transit (TLS 1.2+).
• Local memory and transcripts inherit your operating system account and full-disk protection. App-level vault encryption is a separate release gate and is not claimed until shipped.
• Public release is gated on platform code signing, Apple notarization or Windows Authenticode as applicable, and published SHA-256 checksums. Pre-release builds are not represented as signed releases.
• Our small server-side footprint (licensing, billing) follows least-privilege access with audit logging.
• We run a responsible-disclosure program and credit researchers; the reporting channel is published at launch alongside the contact route in section 14.

12. Children

The Site and App are not directed to children under 13 (or the higher minimum age in your jurisdiction), and we do not knowingly collect their data. Since the App collects essentially nothing, the practical exposure is limited to account creation, which requires being of age.

13. Changes to this policy

If we change this policy, we will post the new version here with an updated date, and — for material changes — notify account holders in-app and by email at least 30 days before it takes effect. One commitment is permanent and will never be weakened by any future revision: the App will never transmit your project code, chat history or model responses to us.

14. Contact

Veylaro Labs. A privacy contact channel — including a dedicated route for data-protection requests and for exercising the rights in section 10 — is published here at public launch, before any paid account exists. We would rather leave this blank than list an address that bounces.