Privacy Policy

Legal

Privacy Policy

Last updated: August 30, 2026

viewparquet is operated by Kaladev Digital Private Limited. This policy describes how we handle information when you use our website and in-browser Parquet viewer.

Local file processing stays on-device

Parquet, GeoParquet, CSV, and JSON files you open are processed locally in your browser using DuckDB-WASM. We do not upload your datasets to our servers for viewing or SQL execution. You can verify this in your browser's developer tools Network tab: file reads come from disk, a remote URL, or object storage, not from viewparquet servers.

Remote sources (S3 and URLs)

When you open a dataset from HTTPS or S3 (including private buckets), your browser connects directly to that host. When the host supports HTTP range requests, DuckDB-WASM can fetch portions of a Parquet object; actual transfer depends on the query, file layout, codecs, and host. viewparquet does not proxy or cache your files on our servers.

Access keys and session tokens you enter for private buckets are used only inside your browser to sign requests. They are not persisted on our servers. Query-free public URLs may be saved locally as recents. URLs containing query parameters, including presigned URLs, are kept only for the current browser tab; reopening a private source prompts you to enter credentials again.

Optional AI assistant

AI features are optional and BYOK-only. To use chat or SQL helper AI, you add your own OpenRouter key or a supported direct provider key in Settings → AI. viewparquet does not proxy AI prompts through its servers.

In BYOK mode, chat and SQL-helper requests are sent directly from your browser to the provider you configure, typically OpenRouter. viewparquet does not proxy BYOK requests through our servers and does not receive or server-log your API key, prompts, schema, generated SQL, responses, or result previews. Your browser may retain chat history and accepted SQL locally; your provider handles requests under its own policies.

Your messages and prompts are always sent when you invoke AI. Settings → AI controls the schema, profile fields, and samples preloaded into a request. Chat tools and saved AI context may also provide structural metadata or SQL. Requests may include:

  • Your messages and SQL prompts
  • Column names and types from the open file
  • Dataset metadata (file name, row count, column count, file size)
  • Bounded query-result values when that toggle is enabled
  • Value-bearing profile facts or SQL-helper samples only when you enable those settings

Chat and SQL helper can use different sharing settings. Use the presets (Minimal, Balanced, Full context) or fine-tune each toggle, and review tool and saved-context behavior before use. Do not include secrets or personal data you are not permitted to share with your chosen model provider.

You may optionally add direct provider keys (for example Anthropic) in advanced settings. Keys are kept in session storage for the current tab by default. You can explicitly opt in to remembering them in local storage on the device. They are sent only to the provider you select.

No cookies, no cookie banner

We use privacy-friendly analytics to understand aggregate product usage and performance, such as page views and whether key viewer actions succeed or fail. We do not use analytics cookies, advertising trackers, or cross-site profiling for this purpose. A fixed task-origin category may be held in session storage for the current tab so we can connect a public-page CTA with aggregate viewer outcomes; arbitrary values are rejected. We do not use cookies for this attribution.

Information we may collect

  • Product analytics (cookieless): we use Vercel Analytics and Speed Insights to collect aggregated page views, referral sources, performance timings, and coarse workflow events: which safe CTA category was used, whether the viewer loaded, whether a file opened, and whether a SQL query or export succeeded or failed. We may include non-identifying categories such as local, saved, sample, or remote source; Parquet, CSV, JSON, or another supported format; the selected export format; and an allowlisted public-page task category. On public marketing pages, URL telemetry may retain only bounded, slug-shaped values for utm_source, utm_medium, and utm_campaign. Viewer, support, internal, utility, and unknown-route query strings and all URL fragments are removed before telemetry is sent.
  • What analytics never includes: filenames, remote URLs, viewer URL query strings, bucket paths, credentials, file contents, cell values, SQL text, raw error messages, AI prompts, exported contents, and non-allowlisted campaign parameters are never included in our analytics events.
  • Error monitoring (essential): we use Sentry to capture crash and error reports so we can keep the app working. Sentry is configured with default PII disabled and event scrubbing intended to exclude file contents, AI prompts, and obvious personal identifiers.
  • Support messages: when you contact us through the in-app messenger, Featurebase processes your message and conversation metadata so we can reply. Personal support asks for a reply email; email is optional for bug reports. The address is included in your private message, not used to sign you in or added to analytics. Opening an email draft does not send it. Do not include sensitive datasets or secrets in support messages.
  • Local storage: preferences (such as theme and AI settings), chat session history, and opened local or sample file contents that may be saved automatically in IndexedDB for Recent files until you remove them or clear site data. BYOK keys use session storage by default and use local storage only when you enable “Remember keys on this device.” These are functional settings, not trackers. BYOK API keys never leave your browser except when sent to the AI provider you configure.

Third-party services

The app may load open-source runtime assets (for example DuckDB-WASM) from our CDN. When you use BYOK AI features, your browser communicates with your chosen model provider according to their policies. See OpenRouter's Privacy Policy. Vercel Analytics processes data according to Vercel's Privacy & Compliance policy, Sentry according to Sentry's Privacy Policy, and Featurebase according to Featurebase's Privacy Policy.

Contact

Questions about this policy? Visit our Support page or reach us through the channels listed there.