1. Introduction
This Privacy Policy describes how dataprep.dev ("we," "our," or "the Service") handles information when you access or use our browser-based data processing tools. By using the Service, you acknowledge the practices described in this policy.
dataprep.dev is fundamentally different from traditional cloud-based SaaS platforms. Our tools run entirely within your web browser using WebAssembly (Wasm) and client-side JavaScript. This architecture has significant implications for your privacy, which we outline below.
2. How We Process Your Data
2.1 Zero-Upload Architecture
When you open a CSV, Excel, or JSON file in any dataprep.dev tool, the file is read and processed exclusively within your browser's memory space using technologies such as DuckDB-Wasm and the File API. Your raw data files are never uploaded to any server operated by us. We do not operate databases that store, index, or have access to your original datasets.
2.2 Browser-Side Processing
All transformations — including filtering, deduplication, schema mapping, and statistical analysis — execute locally on your device. Output files (cleaned CSVs, reports, etc.) are generated in your browser session and downloaded directly to your device. No intermediate data is transmitted to external endpoints as part of the core processing pipeline.
3. Information We May Collect
While our core data processing tools do not transmit your file contents, certain ancillary information may be generated as a natural consequence of operating a web application on modern hosting infrastructure:
- Server Access Logs: Our hosting providers (such as Vercel or Cloudflare) may automatically record standard HTTP request metadata, including IP addresses, timestamps, requested URLs, and browser user-agent strings. These logs are generated by infrastructure providers and are not controlled by dataprep.dev.
- Analytics: We may use lightweight, privacy-conscious analytics to understand aggregate usage patterns (e.g., page views, tool popularity). Such analytics, if implemented, are designed to avoid tracking individual users across sessions and do not capture any file content or processing data.
- Error Reporting: Client-side errors (e.g., uncaught JavaScript exceptions) may be logged to improve stability. These reports contain technical diagnostic data and do not include your file contents or personally identifiable information.
4. Cookies
As of the date of this policy, dataprep.dev does not set or rely on tracking cookies, advertising cookies, or cross-site identifiers. We may use essential session-level storage (such as localStorage or sessionStorage) to remember UI preferences (e.g., theme settings) — this data remains on your device and is never transmitted to our servers.
If our cookie practices change in the future (for example, to support authentication or preference synchronization), we will update this section and, where required, present a cookie consent mechanism before any non-essential cookies are placed.
5. Third-Party Services
dataprep.dev relies on certain third-party infrastructure to deliver the Service:
- Hosting & CDN: Vercel Inc. and/or Cloudflare serve our static assets and may process HTTP requests as described in Section 3.
- Open-Source Libraries: Client-side libraries (DuckDB-Wasm, Papa Parse, SheetJS, etc.) execute entirely in your browser and do not establish external network connections for data processing.
We do not sell, rent, or share your information with third parties for advertising or marketing purposes.
6. GDPR & CCPA Principles
dataprep.dev is designed with GDPR and CCPA principles in mind. Due to our zero-upload architecture, we are not a "data controller" or "data processor" with respect to the contents of your files, because we do not have access to them.
For the limited categories of information described in Section 3 (e.g., access logs), where applicable data protection laws apply:
- You may have the right to request access to, correction of, or deletion of any personal data we hold.
- You may have the right to opt out of any analytics data collection.
- We do not engage in automated decision-making or profiling based on your usage of the Service.
Please note that compliance with data protection regulations is ultimately a shared responsibility. When processing datasets that contain personal data of third parties (e.g., customer records), you remain responsible for ensuring that your own processing activities comply with applicable laws.
7. Data Retention
Because we do not receive or store your file data, there is no server-side retention period for your datasets. Any infrastructure-level access logs generated by our hosting providers are subject to those providers' own retention policies, which typically range from a few hours to 30 days.
8. Children's Privacy
The Service is not directed at children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children.
9. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. The "Last updated" date at the top of this page indicates when the most recent revision was made. Continued use of the Service after changes are posted constitutes acceptance of the revised policy.
10. Contact Us
If you have questions or concerns about this Privacy Policy or our data practices, please contact us at:
- Email: [[email protected]]