Privacy Policy

1. Introduction

Welcome to DataCrunch Pro and DataCrunch Inspector. This Privacy Policy explains how F4 Labs AS ("we," "us," or "our") collects, uses, and protects your information when you use our website and services.

2. Information We Collect

Account Information

When you sign up for DataCrunch Pro via Google OAuth, we collect your name, email address, and profile picture.

DataCrunch Inspector

Inspector is our Windows desktop storefront checker. When you create an Inspector account we collect your email address and send one-time sign-in codes via Mailgun. If you opt in, we may send occasional product tips to that email. You can unsubscribe at any time (link in tip emails, or contact us). Stripe processes Inspector Pro subscriptions; we store Stripe customer/subscription IDs and status, not card numbers. The app may send crash/error reports (app version, OS, error message/stack) to our license server to help us fix bugs. Scan results, crawl data, and exported reports stay on your computer unless you choose to share them.

Connected Data

We access data from your connected Google services (Google Ads, Google Analytics 4, Google Search Console, Merchant Center), Meta, Omnium/Kodmyran, and Shopify where you connect them. We store normalized metrics, product/catalog rows, order summaries, automation/audit logs, and integration status needed to provide the service. We also store long-lived OAuth/API tokens required to keep integrations working; these are encrypted at rest in production.

Retired Features

Until October 2026, DataCrunch Pro offered an in-app AI analyst chat and a Microsoft Teams bot. Both have been removed and no longer collect new data. Conversations and Teams connection records created before then remain stored under our retention schedule (see section 6), are included in account data exports, and are deleted with your account or project. Earlier chat messages may be used as background context when we generate an advertising campaign brief for the same user and project.

Claude and Other AI Assistants (Connector)

You can connect DataCrunch Pro to an AI assistant such as Claude, made by Anthropic, using our connector (a remote server based on the Model Context Protocol, or MCP, an open standard for linking AI assistants to apps). When you connect, you sign in to DataCrunch Pro and choose which projects the assistant may use. Your role on each project still limits what it can see and change.

• What we send: only the result of each request the assistant makes on your behalf, for example a sales summary or a product list for one of the projects you chose. Customer names, email addresses, phone numbers and street addresses are removed from these results. Stored passwords, API keys and integration tokens are never sent.
• What we do not receive: we do not receive or store your conversations with the assistant.
• What we store: the connection itself (which app you connected, which projects you allowed, and when it was last used), with access keys stored only in hashed form; and a log entry for each request, holding your user and project, the name of the tool used, the time, whether it worked, and up to 600 characters of the request's settings (for example a date range or a product ID). We use this log for security, troubleshooting and to show what happened in the project's activity log.
• How long: access keys expire after one hour and are renewed automatically for up to 90 days. You can disconnect at any time under Settings → Claude / MCP access, which stops access at once. Request logs are kept as system logs under section 6.
• The assistant's provider: data we send to the assistant is then handled by its provider (for Claude, Anthropic) under that provider's own terms and privacy policy. You choose to connect and can disconnect at any time.

Merchant and Customer Data

For merchant workspaces, the merchant is normally the controller for store/customer data and F4 Labs AS acts as processor. This may include order identifiers, order totals, product/SKU data, shipping country/region, customer email/name where supplied by the commerce system, and live storefront events collected through the DataCrunch collect script. Customer names and emails are stored encrypted and shown in the Customers view only to the project owner and project admins; they are not uploaded to Google or Meta advertising lists unless a separate, documented consent path is enabled.

Advertising Audiences (Customer Match and Custom Audiences)

Where a merchant explicitly enables it for one of their projects, DataCrunch Pro can build hashed customer lists and make them available for advertising audiences on Google (Customer Match) and Meta (Custom Audiences and Lookalike Audiences). This is off by default for every project and must be switched on by the project owner or a project administrator, who confirms at that point that the merchant has a lawful basis under the GDPR for the purpose and that the merchant's own privacy notice covers it. For these lists the merchant is the controller and the advertising platform acts under its own terms; F4 Labs AS acts as processor for the merchant.

Only irreversibly hashed identifiers leave DataCrunch Pro. Email addresses and phone numbers are normalized and hashed with SHA-256 before transmission; names and country are hashed or sent as a country code according to each platform's specification. We never transmit plaintext email addresses or phone numbers, street addresses, order history, order values, or our internal order-joining keys. Hashing is one-way, and the platforms use the hashes only to match against their own existing users.

Customers can object at any time. On request we add a customer to a per-project suppression list which excludes them from every future list for that project and survives any later resynchronisation from the merchant's commerce system; the merchant is also responsible for removing them from lists already uploaded to a platform. List membership on the platform side is time-limited: up to 540 days on Google and up to 180 days on Meta, after which membership expires unless refreshed. Every export is recorded in an audit log holding counts, the segment, the platform, and the operator — never the members themselves. To exercise this right, contact the merchant you purchased from, or contact us using the details in section 8 and we will route the request to the relevant merchant.

Payment Information

All payments are processed securely by Stripe. Charges will appear on your bank statement as "F4 Labs AS" or "DataCrunch Pro". We do not store your credit card details on our servers. We store only the Stripe Customer ID and Subscription status.

Cookies and Tracking Technologies

We use cookies and similar tracking technologies to enhance your experience on our website, analyze usage patterns, and improve our services. This includes:

• Essential Cookies: Required for basic website functionality and security.
• Analytics Cookies: Help us understand how visitors use our website to improve user experience.
• Marketing Cookies: Used to track visitors across websites to display relevant advertisements.

You can control cookie preferences through your browser settings. However, disabling certain cookies may affect website functionality.

3. How We Use Your Information

We use your information to:

• Provide, maintain, and improve our services.
• Process transactions and manage your subscription.
• Send you technical notices, updates, and support messages.
• Send optional product tips for Inspector if you opted in.
• Generate AI-driven insights for your e-commerce optimization.

4. Data Sharing and Disclosure

We do not sell your personal data. We may share information with:

Service Providers

We use third-party vendors to perform services on our behalf, including Render for hosting/database/Redis, Stripe for payments, Mailgun for email, OpenAI for AI analysis, Sentry for error monitoring, Google/Meta/Shopify/Omnium APIs for connected integrations, and analytics/marketing providers where enabled.

Advertising Platforms

Where a merchant has enabled advertising audiences for a project (see section 2), hashed customer identifiers are shared with Google Ireland Limited and/or Meta Platforms Ireland Limited for the purpose of matching against those platforms' existing users. Each platform processes that data under its own customer-list terms, under which the merchant is the controller. No other customer data is shared with advertising platforms for this purpose.

AI Assistants You Connect

When you connect an AI assistant such as Claude (see section 2), we send it the results of the requests it makes for you, as described there. This happens only at your direction and only for the projects you chose.

Legal Compliance

If required by law or to protect our rights.

5. Data Security

We implement industry-standard security measures to protect your data. Communications are encrypted via SSL/TLS. Production requires encrypted long-lived integration tokens, CSRF protection for authenticated browser writes, OAuth state validation, security headers, rate limiting, and private Render database/Redis networking.

6. Retention and Deletion

Live storefront events are retained for a short operational window. Analytics metrics, order data, reports, earlier AI analyst conversations, system logs (including connector request logs), and ads audit data are retained for service, accounting, audit, and support purposes according to our operational retention schedule. Account deletion anonymizes or removes account-user data, revokes stored tokens where possible, disconnects any AI assistant connections, and deletes user-linked AI conversations. Merchant project offboarding deletes or anonymizes project-scoped orders, product/catalog data, metrics, live events, analyst conversations, ads snapshots, and integration credentials. Backups may persist for a limited period before automatic expiry.

7. Your Rights

You have the right to access, correct, or delete your personal information. To request data deletion, please contact us at hello@f4.no and we will process your request. You can also revoke our access to your Google accounts at any time via your Google Account security settings.

8. Contact Us

If you have any questions about this Privacy Policy, please contact us at hello@f4.no.