Privacy Policy

1. The Zero-Knowledge Standard

Codeflips ("we", "our", or "the Service") was founded on an absolute commitment to privacy. As software developers, we routinely handle sensitive configuration files, proprietary business logic, database schemas, and API authentication payloads. We believe nobody should have to risk disclosing that data to an unknown server just to format a JSON object or convert a cURL request into fetch syntax.

Unlike conventional web converters that upload your data to remote application servers for processing, Codeflips operates on a Zero-Knowledge, client-side paradigm. Our server delivers static HTML, CSS, WebAssembly, and JavaScript files to your browser once. From that moment forward, every operation occurs completely on your local device.

2. Information We Do NOT Collect

To be unequivocally clear about what does NOT happen on Codeflips:

• We do NOT collect or store your source code: Your input code, pasted configurations, and generated outputs are never transmitted over the internet to our servers.
• We do NOT log credentials or secrets: Any API keys, Bearer tokens, environment variables, or connection strings contained within your code remain strictly in your browser memory.
• We do NOT require user account creation: There are no user accounts, passwords, email logins, or profiles stored in any Codeflips database.
• We do NOT employ session replay software: We do not record your screen, mouse clicks, keypresses, or form inputs via tools like Hotjar, FullStory, or LogRocket.
• We do NOT sell, rent, or monetize your data: Because we never collect your data in the first place, it is impossible for us to sell or share it with data brokers, advertisers, or AI training sets.

3. Technical Execution Model

Codeflips is built as a static application using Astro. All data transformers and parser libraries—including PapaParse (CSV), js-yaml (YAML), fast-xml-parser (XML), curlconverter (cURL), and javascript-obfuscator—are compiled and bundled for direct client execution.

4. Infrastructure & Hosting Telemetry

Like all websites on the World Wide Web, when your browser requests static assets (such as /index.html or stylesheet bundles) from our edge CDN hosting provider (e.g. Cloudflare or Vercel), standard HTTP transmission headers are communicated for routing and security purposes:

• IP address (used transiently by edge DDoS firewalls for rate limiting and bot mitigation)
• Browser user-agent string and operating system architecture
• HTTP referrer and requested URL path
• Timestamp and HTTP response status code (e.g. 200 OK, 404 Not Found)

These standard transport logs contain zero payload content, are retained only for security and DDoS defense, and are never correlated with what you paste into our converters.

5. Cookies & Local Storage

Codeflips deliberately avoids third-party advertising cookies, cross-site trackers, or marketing beacons.

The only client-side storage mechanism utilized on our site is standard browser localStorage for saving your preferred interface theme:

This key never leaves your local browser and contains no personally identifiable identifiers. You can clear your browser storage at any time without impacting tool functionality.

6. Third-Party Services & CDNs

To maintain high typography standards and fast global distribution, we rely on minimal trusted third-party providers:

• Google Fonts (Geist & Geist Mono): Typeface styles are loaded from Google's privacy-compliant font delivery CDN. Google Fonts does not set cookies or require authentication.
• GitHub: We link to GitHub for community issue reporting and open-source contributions. When clicking external links to GitHub, your visit is governed by GitHub’s privacy policy.

7. Security & User Responsibilities

While Codeflips guarantees zero transmission of your data from our web application, as an engineering best practice we always advise following defense-in-depth security:

• Never leave sensitive production API credentials open on shared workstations or untrusted computers.
• Be mindful of browser extensions installed on your machine (some third-party extensions may have broad permissions to read clipboard or DOM elements on all visited pages).
• When testing public cURL snippets, substitute production Bearer tokens with placeholder values (e.g. YOUR_API_KEY).

8. Global Rights (GDPR & CCPA/CPRA Compliance)

Under regulations such as the General Data Protection Regulation (GDPR) in the European Union and the California Consumer Privacy Act (CCPA/CPRA) in the United States, users hold fundamental rights including:

• The Right to Know / Access: Since we do not maintain a database of user records or collect personal profiles, we hold no personal dossiers on you.
• The Right to Erasure / Deletion: Any data you process exists only in your browser RAM and is completely erased simply by closing your browser tab or clearing your browser cache.
• The Right to Non-Discrimination: Every feature of Codeflips is 100% free, equal, and unrestricted for all visitors worldwide without exceptions.
• Do Not Sell My Personal Information: We do not sell, exchange, or commercialize user personal information.

9. Children's Privacy Protection

Codeflips does not knowingly collect, request, or solicit any personal information from children under the age of 13 (or under 16 in certain jurisdictions). If you believe a minor has somehow submitted personal data through our feedback channels, please notify us immediately so we can promptly delete it.

10. Changes to This Privacy Policy

We may occasionally revise this Privacy Policy to reflect enhancements to our tool suite or regulatory changes. Any updates will be published on this page with an updated "Last updated" timestamp at the top. We will never alter our core architectural commitment to client-side data privacy.

11. Contacting Privacy Engineering

If you have any questions, security concerns, or technical inquiries regarding our client-side architecture or this Privacy Policy, please reach out to our privacy engineering team: