Privacy Policy
Effective Date: March 18, 2026
Last Modified: March 18, 2026
Many privacy policies obscure how companies use your data. Tabularly is different.
Our business model is selling a high-performance, in-browser data tool, not your personal information. Because we use DuckDB-Wasm, your data processing happens only in your browser. We don't see your uploaded data, we don't track your behavior, and we don't use cookies. The only personal information we receive is what you provide during checkout (such as your name and email) or on our contact page.
For more details on how Tabularly operates, see our terms of service.
Definitions
"Personal Data" refers to information that can identify you, such as your name or email address.
"Uploaded Data" refers to any files you load into Tabularly. This data never leaves your device.
"Local-First" refers to our architecture where all data processing occurs on your machine using technologies like WebAssembly, IndexedDB, and localStorage.
1. The "Local-First" Architecture
Tabularly is a local-first application. When you load a file, it stays on your hardware.
- No Cloud Uploads: Your data files are never uploaded to a Tabularly server. We serve the app code to you, but your data never makes the return trip.
- On-Device Storage: We use browser technologies like IndexedDB and localStorage to keep your datasets and SQL queries available between sessions. This data is only stored on your local machine.
- Local Execution: SQL queries and data profiling are executed by your device's CPU via WebAssembly. We can't see your results.
- No Data Egress: Our application is configured to prevent the transmission of your data and queries to any external endpoint.
2. The "Clean Stack" (Third Parties)
We only use third-party services that align with our privacy-first philosophy:
A. Payments (Polar.sh)
All payments are handled by Polar.sh, our Merchant of Record. They process your payment information and handle tax compliance. We receive limited personal data from Polar (including your name, email address, and purchase details) but we never see your credit card number or banking information.
B. Analytics (Cloudflare)
We use Cloudflare Web Analytics. Unlike Google Analytics, it is cookie-less and doesn't track you across the web. It only tells us things like how many people are using the site.
Cloudflare Web Analytics provides us with aggregated, non-identifiable usage metrics. We can't see individual user behavior, IP addresses, or device fingerprints.
3. Compliance: HIPAA, GDPR, and CCPA
A. HIPAA (Healthcare Data)
Tabularly is HIPAA-friendly by design. Because your data never leaves your local machine, using Tabularly doesn't constitute a disclosure of protected health information (PHI). You maintain 100% custody of the data.
Since Tabularly never receives, transmits, or stores PHI, a Business Associate Agreement is generally not required, as we're not a "Business Associate" under Health Insurance Portability and Accountability Act (HIPAA) definitions.
B. GDPR & CCPA
Since we don't use cookies and don't process your uploaded data on a server, we are private-by-design. For uploaded data, you're the Data Controller and Data Processor. Tabularly never receives or processes your uploaded files, so we have no role under GDPR or CCPA with respect to your data.
4. AI Disclaimer
No AI Training: Our tools are powered by DuckDB-Wasm (see our features page) and not an AI model.
5. Data Retention
We retain only the minimal personal information required for purchase records (such as your name and email). This information is stored by our payment provider, Polar.sh, according to their retention policies. We don't store or retain any uploaded data, as it never leaves your device. If you optionally submit personal information on our contact page, we'll retain it so we can respond to your requests. You can request deletion of this personal information at any time.
6. Changes to This Policy
We may update our privacy policy as we improve Tabularly or add new features. Significant changes will be announced on this site, and the effective date will be updated accordingly.
7. Contact Us
Questions? Reach out via our contact page.