Privacy Policy

Your files stay on your 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. DuckDB-WASM streams byte ranges from the object; 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. Recent remote sources may be saved locally without secrets; 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, does not receive your API key, and does not log prompts, schema, generated SQL, responses, or result previews by default.

Depending on your Settings → AI data-sharing choices, 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)
• Sample cell values, only when you enable that toggle or when the chat query tool fetches rows

Chat and SQL helper can use different sharing settings. Use the presets (Minimal, Balanced, Full context) or fine-tune each toggle. 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. Those keys are also stored locally in your browser and sent only to the provider you select.

No cookies, no cookie banner

We use privacy-friendly analytics to understand aggregate product usage, such as page views and feature interactions. We do not use analytics cookies, advertising trackers, or cross-site profiling for this purpose. Because nothing is stored on your device for tracking, there is no cookie banner to click through.

Information we may collect

• Product analytics (cookieless): we use Simple Analytics and Vercel Analytics to collect aggregated page views, referral sources, and feature usage. Both are cookieless and do not build user-level profiles or track you across sites. Neither receives your file contents or AI prompts.
• Error monitoring (essential): we use Sentry to capture crash and error reports so we can keep the app working. This is part of the core service and does not include your file contents, AI prompts, or automatic personal identifiers such as your IP address.
• Support messages: when you contact us through the in-app messenger, Featurebase processes your message and conversation metadata so we can reply. Do not include sensitive datasets or secrets in support messages.
• Local storage: preferences (such as theme, AI settings, and BYOK API keys), chat session history, and optionally saved file references in IndexedDB on your device only. 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. Simple Analytics processes data according to Simple Analytics' Privacy Policy, Vercel Analytics 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.