Privacy Policy

1. Information We Collect

1.1 Contact Form Submissions

When you submit our Contact form, we collect the following information:

• Name — to identify you and personalize our response.
• Email Address — to respond to your inquiry.
• Company Name (optional) — to understand your organizational context.
• Service Interest — to route your inquiry appropriately.
• Project Details / Message — to understand your requirements.

This data is stored securely using Supabase, a hosted PostgreSQL service with row-level security and encryption at rest.

1.2 License and Account Data

When you purchase a Wurk.Flow Pro or Team license through our license portal at flow.wurk.haus, we collect your email address and, when you activate the desktop application, a cryptographic hardware identifier (HWID) generated locally on your machine. This HWID is used solely to bind your license to a specific device and is never used for tracking or profiling.

The web studio uses the same account, but no hardware identifier. Signing in at app.wurk.haus sends your email address and password to our authentication provider (Supabase Auth) and stores the resulting session token in your browser. That session token is what identifies you to our subscription check; the web studio neither generates nor sends an HWID.

1.3 Wurk.Flow Desktop Application — Outbound Calls

The desktop application does not collect usage analytics, behavioral tracking, or advertising data, and we do not sell your information. Project files, database credentials, query results, and workspace configurations are stored exclusively on your local hardware and are never transmitted to us. Packaged builds do send anonymized crash and error reports, which we describe in the outbound calls below.

The desktop application does make a small number of outbound network calls, which we list explicitly:

• License validation: periodic check against our Supabase project to verify a paid license is active. The Free tier does not make this call.
• Update checks: only when you click "Check for Updates" in the About dialog. The app never checks for updates in the background or on launch.
• Crash & error reports: packaged builds send anonymized crash and error reports (via Sentry) so we can diagnose defects. License keys, hardware identifiers, and known AI-key formats are scrubbed before transmission, and reports contain error messages and stack traces — not your project files or query results. Sent only when an error occurs.
• Optional features only: AI provider calls (only if you enable AI and configure a provider), Co-Op relay messages (only if you start a collaboration session), and direct database connections (only to databases you configure).
• Feedback submissions: only when you fill in and submit the in-app feedback form. See Section 1.5.

Anything not in the list above is not transmitted. If you require fully offline operation, simply don't click Check for Updates, decline AI providers, avoid Co-Op sessions, and don't submit feedback — the core schema, SQL, lineage, and DDL workflows function without any network access.

1.4 Wurk.Flow Web Studio (app.wurk.haus)

The web studio is the browser edition of Wurk.Flow. There is no application server: our servers deliver the application's files, and every modeling engine — the canvas, DDL generation, the in-browser DuckDB sandbox — runs inside your browser. We do not receive your project data.

Where your work is stored. The web studio keeps an autosaved copy of your current project in your browser's IndexedDB storage, plus one previous-generation backup slot, as a restore-your-last-session safety net. That copy is local to your browser on your own device and is never uploaded to us. The durable path is the same as on desktop: you download and re-open a .dsm project file. Clearing your browser's site data removes this copy — we have no copy of it to remove.

Other values the web studio keeps in your browser, none of which are transmitted to us: your sign-in session token, a cached record of your subscription tier, your AI provider settings and API key if you choose to save one, a MotherDuck access token if you connect to MotherDuck, a random identifier used only to group repeat feedback submissions from the same browser, and interface preferences such as your theme.

Beyond loading its own files from app.wurk.haus, the web studio makes these outbound network calls and no others:

• Sign-in and subscription check: to our Supabase project, and only while you are signed in — the sign-in itself, automatic session refreshes, and a subscription check at start-up, when you sign in or out, and roughly every six hours while the tab is open. The check sends your session token and receives your tier and renewal date; it does not send anything from your project. If you are not signed in, no such call is made.
• AI provider calls: only if you configure an AI provider and invoke an AI action. Requests go directly from your browser to that provider using your own key — they do not pass through Wurk.Haus servers. See Section 4.
• MotherDuck: only if you connect to MotherDuck with your own access token. Your token, the SQL you run, and the results travel directly between your browser and MotherDuck. See Section 5.
• Feedback submissions: only when you fill in and submit the in-app feedback form. See Section 1.5.

Just as importantly, the web studio does not:

• send crash or error reports — the crash reporter (Sentry) is disabled in the browser edition; errors are shown to you on screen instead;
• check for updates — there is no version to check; the studio always loads the current deployment;
• use the Co-Op relay — real-time collaboration is a desktop-only feature, and the relay host is not reachable from the browser edition;
• run usage analytics, behavioral tracking, or advertising.

These limits are enforced by your browser, not only by our code. The web studio is served with a Content-Security-Policy that restricts the hosts the page may connect to — our Supabase project, the AI provider endpoints listed in Section 4, MotherDuck, and localhost for a locally run AI model. Connections to any other host are blocked by the browser.

1.5 In-App Feedback

Both editions include an optional feedback form, opened from the command palette. It is transmitted only when you fill it in and submit it. The submission contains the feedback type, title, and message you write, the contact email address you choose to provide, any file you attach, and a reporter identifier used to group repeat reports: in the desktop application this is the same locally generated hardware identifier used for licensing, and in the web studio it is a random identifier generated in and stored by your browser — not a hardware fingerprint. Submissions are stored in our Supabase project and attachments in Supabase Storage. We attach nothing from your project ourselves; only what you type or choose to upload is sent.

1.6 Server Logs

Like most web services, our servers may automatically log standard HTTP request data including IP addresses, browser type, referring pages, and timestamps. Under laws such as the GDPR an IP address can constitute personal data; we use these logs only for security monitoring and troubleshooting, retain them briefly, and do not use them to build profiles.

2. How We Use Your Information

We use the information we collect exclusively for the following purposes:

• To respond to your contact form inquiries and schedule consulting sessions.
• To process and fulfill software license purchases and activations, and to confirm that a signed-in web studio account holds an active subscription.
• To provide customer support and communicate about your license or services.
• To read and act on feedback you submit through the in-app feedback form.
• To maintain and secure our website infrastructure.

We do not sell, rent, or share your personal information with third parties for marketing purposes.

3. Third-Party Services

We rely on a limited number of third-party services to operate:

4. AI Integrations (BYOAI)

Wurk.Flow supports optional AI integrations through a "Bring Your Own AI" (BYOAI) model. AI is off until you configure it. Supported providers as of this writing:

• Desktop application: OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Groq, Mistral, and Ollama (local).
• Web studio: OpenAI, Anthropic, Azure OpenAI, Groq, Mistral, and Ollama (local). AWS Bedrock is not offered in the browser, because its request signing cannot be performed from a web page.

When you choose to use these integrations:

• Your API keys and credentials stay on your own device and are never transmitted to Wurk.Haus servers. The desktop application holds them in the operating system's encrypted storage; the web studio holds them in your browser — in local storage if you leave "Remember in this browser" enabled, otherwise only for the session — and "Forget Stored Key" erases every copy.
• Requests go directly from your device to the provider you configure. They do not pass through Wurk.Haus servers, and we never see your prompts, your key, or the provider's responses.
• Prompts carry schema metadata — table and column names, types, keys, and descriptions — and the text you write. They do not carry your query results or table contents.
• Because you supply your own key, your use of a provider is governed by your own agreement with that provider, and the data you send is handled under that provider's privacy policy rather than this one.
• You may use a fully local AI provider (e.g., Ollama) to ensure no data leaves your network.

5. Database Connections

The desktop application allows you to connect to external databases (PostgreSQL, Snowflake, BigQuery, SQL Server, and others) for schema introspection and data architecture. All database credentials are stored locally on your device. Wurk.Haus has no access to your database credentials, schemas, or data at any time.

The web studio does not include those live database drivers. In the browser you can query the in-browser DuckDB sandbox and open a local .duckdb file — both of which are read and executed entirely on your own device and are never uploaded to us — or connect to MotherDuck with your own access token, in which case your queries and results travel directly between your browser and MotherDuck (Section 3).

6. Cookies

The Wurk.Haus website does not use tracking cookies, advertising pixels, or third-party analytics tools. We may use essential cookies strictly necessary for website functionality (such as session management on the license portal).

The web studio keeps your sign-in session in your browser's local storage rather than in a cookie, alongside the other browser-local values listed in Section 1.4. These are functional storage, not tracking: they are readable only by app.wurk.haus, they are not sent to us, and clearing the site's data removes them.

7. Data Retention

Contact form submissions are retained for as long as necessary to fulfill your inquiry and maintain our business records. License data is retained for the duration of your license relationship with us. You may request deletion of your data at any time by contacting us.

8. Data Security

We implement industry-standard security measures including HTTPS encryption for all web traffic, encrypted database storage via Supabase, atomic file writes on the desktop client (interruption-safe saves), and limiting the desktop client's outbound calls to the small list documented in Section 1.3. The web studio is additionally served with a Content-Security-Policy that restricts the hosts the page may contact to the list in Section 1.4 — a limit your browser enforces independently of our code. However, no method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

9. Your Rights

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you.
• Request correction of inaccurate or incomplete data.
• Request deletion of your personal data.
• Object to or restrict the processing of your data.
• Withdraw consent at any time where processing is based on consent.

To exercise any of these rights, please contact us using the information below.

10. Children's Privacy

Our Services are not directed to individuals under the age of 16. We do not knowingly collect personal information from children. If you believe we have inadvertently collected such data, please contact us immediately and we will delete it.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date. Your continued use of our Services after any changes constitutes acceptance of the updated policy.

12. Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us: