Privacy Policy

This Privacy Policy explains how ORQVION (“we”, “us”, “the product”) handles information when you use the desktop application, this marketing website at orqvion.com, checkout, and — for organisations — the self-hosted license and enterprise servers.

ORQVION is a Pakistan-based company. Leadership: Muhammad Faheem Bantva, Founder & Chief Executive Officer. The architectural privacy rules in our product documentation are the same rules this page describes.

This page is a product-accurate policy for customers and visitors. It is not legal advice. Enterprise customers may also have a signed master agreement or data processing addendum, which controls if it conflicts with this page.

1. The core promise

ORQVION will never silently upload your project source code, project files, private prompts, AI conversations, or credentials for permanent storage.

ORQVION Online Beta defaults to online routing (AUTO). When you use cloud providers, inference leaves your device to reach those APIs — typically with BYOK keys in your OS keychain. The license server resolves entitlements; it does not permanently retain prompt or response content for model training or product analytics. Offline paths use ORQVION AI and local GGUF via llama.cpp — not the Ollama application.

Privacy rules that still apply:

• Website analytics scripts are off until you opt in. Nothing in the consent banner is pre-checked.
• Desktop telemetry and crash reporting are off until you turn them on.
• Agent file writes and network tools require approval.
• BYOK and offline GGUF / ORQVION AI are optional; the Ready wizard defaults online — Advanced Local is under Settings.

2. What this policy covers

Surface	What it is	Where data lives by default
Desktop IDE	Tauri app on your Mac, Windows, or Linux machine	Your disk and OS keychain
Online AI (Online Beta default)	Desktop → provider APIs (BYOK) with server entitlements	Ephemeral inference; no permanent ORQVION content store
Offline AI	ORQVION AI bundles + downloaded GGUF (llama.cpp)	Your machine
This website	Marketing, docs, contact, pricing	Website database + mail
Checkout	JazzCash, Easypaisa, bank	Payment provider + license server
Enterprise server	License, SSO, policy, audit ingest	Your PostgreSQL (self-hosted)

We do not operate a “send us the repo so the assistant can work” coding cloud. Online inference is between your desktop and providers you enable; it is not permission to archive your repository on ORQVION servers.

See also: AI & Data Processing Policy and Acceptable Use Policy.

3. Data classification (desktop product)

Classification	Default location	Can leave the device through ORQVION?
Project source code	Your project directory	No (default)
Project files, assets, configs	Your project directory	No (default)
AI conversations and prompts	Local storage	No (default)
Credentials, API keys, tokens	OS keychain	Never via ORQVION
Generated files	Your project directory	No (default)
Git repositories	Your project directory	Not by ORQVION (git remotes you configure are yours)
Project indexes and symbols	Local ORQVION storage	No
User preferences, themes	Local storage	No
Account data (email, name, plan)	License / account server	Yes — required to sell a license
License tokens	Local cache + license server	Minimal entitlement data
Diagnostics	Local, optional upload	Only with explicit consent
Usage metrics	Optional	Anonymized aggregates only, if enabled

4. Information we collect

4.1 Desktop — Online Beta default

When you use ORQVION Desktop on Online Beta:

• Your project files and indexes stay on the machine.
• Online AI sends inference payloads from your desktop to configured providers (BYOK). ORQVION does not permanently store those prompts or completions on our servers.
• We do not receive your repository as a product dataset.

If you sign in or activate a license, the license server stores what it needs to honour the seat: identity (or SSO subject), device binding, plan, expiry, and activation events. That is entitlement data, not your source tree.

4.2 This marketing website

If you only browse, we store what the web server needs to function (typically an essential session cookie if you log into Admin, and a consent cookie if you make a choice).

If you submit Contact, we store: name, work email, optional company, topic, and message, so we can reply. We may email that inquiry to our support address. We do not ask you to upload a repository.

Analytics (Plausible or a custom HTTPS script configured by an operator) load only after you opt in (orqvion_consent=analytics). Essential-only is the primary action. Checkout pages are noindex.

4.3 Payments

Checkout for Pakistan payment methods (JazzCash, Easypaisa, supported bank flows) is handled by those providers and our license-server payments API. We receive payment status, package, amount (typically PKR), and enough metadata to issue or withhold a license. Card or wallet secrets are handled by the provider, not stored as PAN on this website.

Those providers have their own privacy policies. We are not their controller for data they collect on their pages.

4.4 Optional telemetry and diagnostics (desktop)

	Telemetry	Diagnostics
Default	Off	Off
If enabled	Feature counts, session duration, error categories	Stack traces, component state, hardware profile, app version
Never included	Source, file names, prompts, chats, project names, credentials	Source, project files, prompts, credentials
Retention (if sent)	90 days	30 days
Extra	Anonymized; not joined to a marketing profile	You can preview before send

4.5 Online AI, BYOK, and offline paths

Online (AUTO default on Online Beta):

• The desktop sends inference to configured provider APIs from your machine. The license server resolves entitlements and quotas only — it is not a prompt proxy and does not permanently store chat or completion bodies.
• BYOK provider keys stay in your OS keychain / encrypted local store. OpenAI is not a required core provider.
• Usage metering where enabled stores metadata and token counts — not prompt or response bodies.

BYOK (optional):

• If you enable a bring-your-own provider, data sent to that provider is subject to their policy.
• You control scope (selection vs larger context). Optional per-request approval exists where the product surfaces it.
• BYOK calls are logged locally where the product surfaces them. You can disable a provider immediately. Org policy can forbid external / BYOK models.

Offline (ORQVION AI + GGUF) ships in the same desktop build under Settings → Advanced Local (llama.cpp — not the Ollama application). The Ready wizard does not require offline weights to start.

ORQVION is not responsible for how a third-party provider processes the context you chose to send.

4.6 Enterprise / organisation deployments

Your administrator may configure SSO (OIDC, SAML, LDAP), org policy, audit sync, and metering summaries. Audit events are structured JSON about security-relevant actions. Source contents are not the log payload. The enterprise database is yours when you self-host.

5. How we use information

• Provide and secure the website, licenses, and (if you buy) payment completion.
• Reply to sales and support inquiries.
• Honour entitlements, device limits, and updates.
• Improve the product using consented telemetry only.
• Detect abuse, fraud, or license sharing that violates the Terms.
• Comply with Pakistani law and valid legal process.

We do not sell personal data. We do not use your source code to train a public ORQVION foundation model.

6. Legal bases and Pakistani law

Pakistan does not yet apply a GDPR-style statute to every processing activity. We still minimise collection, default to on-device processing, and treat PECA-related duties and any future data-protection statute as requiring fail-secure design.

If you are in a jurisdiction that grants specific privacy rights, contact us and we will honour access, correction, and deletion for account and website data we hold. Local desktop data is already under your control: you can delete conversations, indexes, and the app data directory.

Where Pakistani consumer or electronic-transactions law gives you a stronger right than this policy, that right applies.

7. Sharing

We share personal data only with:

• Payment gateways you use to check out.
• Email delivery for contact-form notifications.
• Your own identity provider, if you use SSO.
• Subprocessors that host this website or the license API you pointed the client at (including a server you run).
• Authorities when required by law.

We do not sell lists. We do not share repositories with model vendors unless you enabled that vendor.

8. Retention and deletion

Data	Retention
Project / chat / indexes on disk	Until you delete them or uninstall (you may keep project files)
Website contact inquiries	Until handled, then as needed for legitimate support/legal records
Account / license records	Until account deletion or expiry, then as required for accounting
Consented telemetry	90 days
Consented diagnostics	30 days
Audit on enterprise server	Whatever your admin configures

Delete conversation / index / agent logs — local, immediate.
Delete account — removes server account data; local files are untouched.
Uninstall — option to remove ORQVION app data; your git project remains yours.

9. Children

ORQVION is a professional developer tool. We do not target children. If you believe we hold account data for a minor, contact us and we will delete it.

10. Security

We use least privilege, fail-secure defaults, signed license tokens (Ed25519), sandboxed agent execution (including optional Docker), signed extensions (WASM runtime), and a rule that secrets must not appear in logs. No method is perfect; see the Security page for product controls.

11. International visitors

The company is based in Pakistan. If you access the site or a hosted license API from abroad, you understand that account and payment metadata may be processed in Pakistan and in regions where our (or your) hosting lives. Desktop project data does not need to leave your country because it does not leave your machine by default.

12. Changes

We will update the date at the top of this page when the policy changes. Material changes to how the desktop default treats source code will be called out clearly — that default is not a dark pattern we intend to flip.

13. Contact

Privacy and data requests: use Contact or email the support address published in the site footer.

For a data processing agreement or on-premise review, ask sales. Bring your counsel; we will not pretend this Markdown replaces a signed DPA.