Clear data practices, written for people.

When you create and manage a DataCrew account, BrandCrew determines how your account and service data is handled. For analytics collected from a customer’s website, that customer decides why the tracker is installed and how the resulting analytics are used. In that context, the customer is responsible for its own privacy notices, consent choices, and instructions to DataCrew.

“You” may mean a DataCrew account holder or, where the context requires, a visitor to a website that uses DataCrew.

Account and authentication

• Name, email address, username, profile image, email-verification status, and account timestamps.
• Authentication provider identifiers and tokens when you choose Google or GitHub sign-in, or credential and verification records when you use email-based access.
• Session token, expiry, IP address, and user agent used to protect DataCrew account sign-ins and active sessions.

Workspace and product configuration

• Website name, primary and allowed domains, timezone, currency, goals, funnels, segments, onboarding progress, and tracker settings.
• Privacy preferences such as cookie or cookieless mode, excluded paths, allowed subdomains, localhost tracking, and whether Do Not Track and Global Privacy Control are honored.
• Saved AI conversations, messages, tool results, model usage, and brand-intelligence profiles when you use those features.

Billing and support

For paid plans, we keep subscription status, product and customer references, price, currency, billing interval, and renewal or cancellation dates. Payment checkout and card handling are provided by Polar; DataCrew does not store full payment-card numbers. If you email us, we receive the message, your email address, and any information you choose to include.

Visits, pages, and acquisition

DataCrew can receive an anonymous visitor ID, session ID, event time, page path, page title, hostname, landing and exit pages, referrer origin and path, referring domain, and first-touch or current campaign information. Campaign parameters are limited to UTM fields and the documented ref, source, and via fields. For common advertising click IDs, the tracker records that an ID was present, not the ID value itself.

Engagement and events

DataCrew can record page views, custom event names and privacy-filtered properties, scroll milestones, section views, outbound-link destinations, safe call-to-action labels, form-submission occurrence, pageview and event counts, approximate engaged time, bounce status, and conversion or funnel progress.

Device and approximate location

The service can process language, timezone, screen and viewport size, browser and version, operating system and version, broad device category, bot classification, and approximate country, region, and city. Network information may be used transiently to derive coarse location and protect ingestion, but the analytics event tables do not retain a raw visitor IP address.

Data a customer sends deliberately

If a customer uses DataCrew’s Identify, Revenue, Bot Traffic, or custom-event APIs, the customer may send its own external user ID, selected traits, transaction ID, amount, currency, provider and payment lifecycle status, bot request details, and permitted custom properties. DataCrew processes that information on the customer’s instructions; customers should not send secrets or unnecessary sensitive information.

Event labels and custom properties pass through format, length, and sensitive-value filters. Strings resembling email addresses, phone numbers, payment-card numbers, authentication tokens, API keys, UUIDs, or long opaque identifiers are excluded from ordinary automatic event properties.

• Authenticate accounts, maintain sessions, and provide requested dashboard features.
• Receive, aggregate, visualize, and explain website analytics, visitor journeys, revenue attribution, goals, funnels, and bot traffic.
• Generate requested AI analysis and brand intelligence, and store the conversation so it remains available in the workspace.
• Manage subscriptions, communicate service or security information, respond to support, and prevent fraud or abuse.
• Diagnose reliability, understand product performance, and comply with law or enforce our terms.

In cookie mode, the tracker uses first-party random visitor identifiers named sd_vid and datacrew_visitor_id. They are scoped to the site, use SameSite=Lax, use Secure on HTTPS, and are set for up to 365 days to recognize returning visits and attribute revenue.

In cookieless mode, the tracker uses a random sd_cvid value in session storage. It is limited to the browser tab session and is removed when that session storage is cleared. DataCrew also uses necessary authentication storage to keep account holders signed in and protect the dashboard.

We may use infrastructure, database, authentication, email, billing, AI, and web-research providers to run the service. Depending on the feature you choose, these may include Google or GitHub for sign-in, Resend for account email, Polar for billing, Google Gemini for AI analysis, and Exa for requested brand research. They process information under their own terms and our operational instructions.

We may also disclose information when required by law, to protect users and the service, in connection with a corporate transaction, or with your direction. Workspace analytics are available to authorized users of that workspace.

Account, workspace, analytics, AI, and billing records generally remain while the relevant account or workspace is active. Some records may remain longer in backups, security logs, billing records, or where legal obligations require it. Deleting a website or account is designed to remove dependent workspace records from the active database, subject to those limited exceptions.

You can request account or personal-data deletion by emailing support@brandcrew.live. We may need to verify the request. Website visitors should usually contact the operator of the website they visited first because that operator controls the analytics workspace.

• Customers can select cookie or cookieless mode, honor DNT and Global Privacy Control, exclude path prefixes, restrict allowed domains, and reset or remove tracking.
• Visitors can use browser controls to clear or block first-party storage and can enable supported privacy signals where the website owner has configured DataCrew to honor them.
• Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data. You may also have the right to complain to a local data-protection authority.

Submit a request to support@brandcrew.live. We will respond as required by applicable law and may ask for information needed to verify your identity or authority.

We use technical and organizational measures intended to protect data, including scoped access, authentication, token hashing for DataCrew APIs, and collection sanitization. No internet service can guarantee absolute security.

DataCrew is not directed to children under 13, and we do not knowingly seek their personal data. We may update this policy as the product or law changes; the date at the top will show the latest revision. Material changes may also be communicated through the service.

Questions, privacy requests, or security concerns can be sent to support@brandcrew.live.