Privacy Policy

1. Introduction

This Privacy Policy explains how DataChant Consulting LLC, an Illinois limited liability company doing business as BI Pixie ("we," "us," or "our"), collects, uses, stores, and protects information in connection with the BI Pixie platform and related services.

BI Pixie is a telemetry and engagement intelligence platform for Microsoft Power BI. It helps organizations understand how their Power BI reports are used by adding invisible native Power BI elements (such as measures and table visuals) to reports. No custom code or scripts are injected into your reports.

This policy applies to:

• The BI Pixie website (bipixie.com)
• The BI Pixie customer portal (app.bipixie.com)
• The BI Pixie service across all deployment models
• All BI Pixie offers available through the Microsoft Marketplace, including the Managed App, Power Platform, Cloud, and Power BI template app offers

BI Pixie is available in three deployment models. The data we can access and our role in data processing differs significantly between them. Please read Section 2 to understand which model applies to you.

If you have questions about this policy, contact us at support@bipixie.com.

2. Deployment Models

Understanding your deployment model is essential to understanding how your data is handled.

2.1 Managed App (Azure)

Available on the Microsoft Marketplace.

You deploy BI Pixie within your own Azure subscription. All data remains in your Azure environment. We have zero access to your data. We do not act as a data controller or data processor for any data collected through your Managed App deployment.

This standalone deployment (also marketed as "Self-Hosted") is different from the Cloud "Bring Your Own Storage (BYOS)" option in Section 2.3. With BYOS you connect BI Pixie Cloud to your own storage and grant us scoped access (read, search, and optional delete) so the self-service features work over your data; here, in the standalone Managed App, there is no such connection and we have no access.

Your organization is solely responsible for the data collected and for compliance with applicable data protection laws. Your own privacy policies govern the data. Our role is limited to providing the software and documentation.

Sections 3 through 9 of this policy do not apply to Managed App deployments. Please refer to Section 10 for details specific to the Managed App model.

2.2 Power Platform

Available on the Microsoft Marketplace.

You deploy BI Pixie within your Microsoft Power Platform environment. All data remains in your Power Platform environment. We have zero access to your data. We do not act as a data controller or data processor for any data collected through your Power Platform deployment.

This model is functionally identical to the Managed App from a privacy perspective. Your organization is solely responsible for the data collected and for compliance with applicable data protection laws.

Sections 3 through 9 of this policy do not apply to Power Platform deployments. Please refer to Section 10 for details specific to the Power Platform model.

2.3 Cloud

Available directly at bipixie.com and on the Microsoft Marketplace (coming soon).

We host the BI Pixie infrastructure on Microsoft Azure on your behalf. In this model:

• We are a data processor for end-user telemetry data. You (the customer) decide what data to collect. We process and store it on your behalf.
• We are a data controller for customer administrator account data, which we need to provide the service.

Each customer's data is stored in a dedicated, isolated storage container secured with Azure Active Directory role-based access control (RBAC). No other customer can access your data.

Telemetry storage location. Cloud offers three places your telemetry can be stored. Our processor role above is the same in each; what differs is where the data rests:

• BI Pixie storage (default). The dedicated, RBAC-isolated container described above. We automatically place it in the BI Pixie region closest to your Power BI tenant's home region (Cloud) or your Fabric capacity's region (Fabric workload); you do not pick the region.
• OneLake delivery. Instead of retaining your telemetry, we deliver it to your own Microsoft Fabric OneLake (your lakehouse). Your data rests in your Fabric tenant; BI Pixie does not store it in our cloud. Optionally, you can grant BI Pixie scoped, revocable read access so you can use the self-service Data Management tools and Event Viewer over your own data. This access is opt-in; without it, we never read your data.
• Bring Your Own Storage (BYOS) (Enterprise). You host your own telemetry web trigger and the events land directly in your own Azure storage account. Your telemetry never enters BI Pixie infrastructure, and BI Pixie does not store it. Optionally, you can grant scoped, revocable read access so the same self-service Data Management tools and Event Viewer work over your store. This access is opt-in; without it, we never read your data.

For both OneLake delivery and BYOS, BI Pixie never deletes or alters data in your store by default. For OneLake delivery, the access is read-only; you manage any deletion yourself in your own lakehouse. For BYOS, you can additionally opt into a revocable read + delete tier so you can use our Data Management tools to delete data yourself: for example, to remove files containing sensitive data, or to erase a specific end user's data to comply with a GDPR request. You stay in control of the deletion; BI Pixie only supplies the tools. Our processing of Cloud telemetry, across all three storage locations, is governed by our Data Processing Agreement.

Sections 3 through 9 of this policy describe data handling for Cloud deployments.

2.4 Power BI Template Apps

BI Pixie also provides Power BI template apps (Enterprise, Starter) available on the Microsoft Marketplace. These apps are installed into your Power BI environment and connect to the telemetry data already stored in your deployment. The template apps themselves do not collect additional data. They provide dashboards and reports for analyzing data that was already captured by one of the deployment models above. The privacy provisions of your deployment model apply.

3. Information We Collect (Cloud)

We collect information in the following categories.

3.1 Customer Administrator Data

When you sign in to the BI Pixie portal, the following information is collected through Microsoft Azure Active Directory (Entra ID) authentication:

3.2 End-User Telemetry Data

When a Power BI report is instrumented with BI Pixie, interactions by report viewers (end users) generate telemetry events. You control what data is collected through your project configuration. The following tables describe all data fields.

Important: This section describes data collection for the Cloud deployment. In the Managed App and Power Platform deployments, the same telemetry data may be collected, but it is collected and stored entirely by your organization within your own environment, not by us. We have no access to that data. See Section 10 for details.

Always Collected

These fields are collected whenever a report is instrumented. They describe the interaction context without identifying the individual user.

Collected Only When You Enable Them (Off by Default)

These fields involve potentially sensitive or personal data. They are all disabled by default. Enabling them requires explicit action in the portal, and high-sensitivity features require an additional consent acknowledgment.

3.3 Report and Semantic Model Definitions

To instrument your Power BI reports, BI Pixie accesses the structural definitions of your reports and semantic models through the Microsoft Fabric API. This includes the layout of pages and visuals, measure definitions, and metadata such as report names, page names, and workspace information.

How we use this data:

• We download report and semantic model definitions, add the tracking elements (measures and visuals), and upload the modified definitions back to your Power BI workspace.
• Temporary copies are deleted immediately after processing. We do not retain copies of your report or semantic model definitions.

Inventory metadata:

• After instrumentation, we store lightweight inventory metadata in your dedicated storage container. This includes report names, page names, visual counts, workspace names, and bookmark counts.
• This inventory data is used to power the analytics dashboards in the BI Pixie template app and portal.
• Inventory metadata does not include any of the actual data displayed in your reports.

What we do not access when adding, updating, or removing tracking elements:

• We do not access the actual data displayed in your reports (e.g., sales figures, customer records, financial data).
• We do not read or extract data from your datasets, tables, or data sources.
• To add, update, or remove tracking elements, we use only the structural definition (the "blueprint" of how your report is built), never the data it displays.

The structural-only access described in this section covers everything BI Pixie does when it adds, updates, or removes tracking elements. In two optional features, the AI benchmark and the AI Readiness usage signal, BI Pixie does run read-only queries against a semantic model in your tenant. Section 3.6 describes exactly what BI Pixie reads in each of those features and where the results are stored.

3.4 Portal Browser Data

The BI Pixie portal stores minimal data in your browser:

• Session storage: Authentication tokens from Microsoft Entra ID. These are automatically cleared when you close the browser tab.
• Local storage: A small number of boolean preference flags (e.g., whether you have visited before, UI display preferences). These flags contain no personal information.

We do not use cookies for tracking. We do not use third-party analytics, advertising trackers, or social media pixels on our portal.

3.5 Data We Do Not Collect

• We do not access or read the actual data displayed in your Power BI reports (e.g., sales figures, customer records) when adding, updating, or removing tracking elements. For those operations we read only the structural definitions described in Section 3.3.
• We do not query, extract, or store data from your underlying datasets or data sources, except in the two read-only features described in Section 3.6. In the AI benchmark, which runs only when you start it, BI Pixie queries the one semantic model you select and stores the computed answers in your own isolated storage, where the computed answers serve one purpose: scoring your benchmark. For the AI Readiness usage signal, BI Pixie reads usage counts from the BI Pixie dashboard semantic model, never from your business semantic models.
• We do not use an AI provider of our own, because BI Pixie holds no AI provider account. BI Pixie calls an AI provider only after an administrator on your account connects one, and only for the semantic models you select. Section 3.7 describes what BI Pixie sends in that case and what it never sends.
• We do not collect payment card information directly. Payment processing is handled by Stripe, our payment provider, and card details are never sent to or stored on BI Pixie servers.
• We do not sell, rent, or trade any data to third parties.
• We do not use end-user telemetry data for advertising or marketing purposes.

3.6 The AI Benchmark and the AI Readiness Usage Signal

In two features, the AI benchmark and the AI Readiness usage signal, BI Pixie runs read-only queries against a semantic model in your Power BI tenant. These are the two exceptions referenced in Sections 3.3 and 3.5. This section describes what BI Pixie reads in each feature, what is stored, and where.

The AI benchmark. With the AI benchmark, you measure how accurately an AI (Microsoft Copilot in Power BI, a Fabric data agent, or a generic AI agent) answers questions about one of your semantic models. A benchmark runs only when you start it; BI Pixie never runs one on its own. To score the AI's answers, BI Pixie must know the correct answers, so it computes them from the one semantic model you select, using read-only DAX queries sent to the Microsoft Power BI API under your own signed-in permissions. BI Pixie does not keep the access token used for these queries.

The correct answers BI Pixie computes for a benchmark are values from your business data (for example, a total or a top-ranked name). BI Pixie stores them, together with the benchmark questions and the tested AI's answers, as a scored benchmark result in your dedicated storage container in your assigned region, or in your own OneLake lakehouse when your account uses OneLake delivery (Section 2.3). BI Pixie processes benchmark questions and answers only in your assigned region or in your own Fabric tenant. Between your browser and your assigned region, BI Pixie relays benchmark requests and results without reading the questions or the answers, and it keeps no copy of them outside your dedicated storage container or your own OneLake lakehouse. Section 8.4 describes how long benchmark results are kept.

The AI Readiness usage signal. BI Pixie can rank AI Readiness findings and recommendations by how people actually use your reports. To read that usage signal, BI Pixie runs a small, fixed set of read-only DAX queries against the BI Pixie dashboard semantic model in your tenant, which BI Pixie builds from the telemetry described in Section 3.2. These queries return usage counts, such as how often a table, column, or measure appears in what people select in your tracked reports. They return no values from your business data. BI Pixie sends these queries only to the BI Pixie dashboard semantic model, never to the semantic model being assessed and never to any other business semantic model.

3.7 AI Providers You Connect

Two BI Pixie features can ask a large language model to write text or to compare answers. AI Readiness does so when it drafts descriptions, AI Instructions, or display folder names for a semantic model you select, and when it confirms whether two similarly named fields are really duplicates. The AI benchmark does so when it reads the business domains out of your AI Instructions, when it phrases the benchmark questions, and when it reviews the answers a tested AI gave. BI Pixie operates no AI provider of its own and holds no AI provider account on your behalf. An administrator on your BI Pixie account chooses a provider and supplies the credential for it, and until an administrator does that, BI Pixie sends nothing to any AI provider. The AI Readiness assessment itself, including the score, the dimension breakdown, and the findings, is computed without any AI provider.

Which providers you can choose. BI Pixie offers four options and you choose which one to connect. Two of them are companies other than Microsoft: OpenAI and Anthropic, each connected with an API key issued to you on your own account with that company. The other two stay inside Microsoft: Azure AI Foundry, which runs in your own Azure subscription, and the BI Pixie data agent, which runs on your own Microsoft Fabric capacity. When you connect Azure AI Foundry or the BI Pixie data agent, nothing described in this section reaches a company outside Microsoft.

What BI Pixie sends when it drafts text. For a semantic model you select, BI Pixie sends your provider the parts of the semantic model definition the drafting task needs: table, column, and measure names, data types and format strings, existing descriptions, the DAX expression of a measure, display folder names, and the semantic model's own AI Instructions. Where the reports built over that semantic model have Pixies, BI Pixie also sends a block of observed vocabulary, which is the report, page, and visual titles people open and the values people filter to most often. Those filter values are values from your business data, and BI Pixie sends them so that the text it drafts uses the words your own people use rather than words it guessed.

What BI Pixie sends when you run an AI benchmark. To phrase the benchmark questions, BI Pixie sends your provider the field names each question is about and the slice it asks for, which can include a filter value such as a product category or a region. The correct answer is never sent at that stage, so the answer key cannot leak into the test. After the tested AI has answered, and only then, BI Pixie can send your provider the question, the answer that was recorded, and the correct value or values BI Pixie computed from your semantic model, so that your provider can give a second opinion on whether the two match. Those correct values are values from your business data, such as a total or a short ranked list of names. When no provider is connected, BI Pixie skips the second opinion and scores the benchmark by comparison alone. One benchmark option goes further: when you choose to test a generic AI agent, your connected provider is the AI being tested, so it also receives the description of your semantic model that BI Pixie gives any tested AI, and it writes the query that answers each question. That description carries names, descriptions, synonyms, and your AI Instructions, and it carries no values from your business data.

What BI Pixie never sends to an AI provider. BI Pixie sends no telemetry event records and no end-user identifiers. It does not send the contents of your tables, and the only values from your business data that reach a provider are the ones this section names. Fields you have excluded in the AI data schema contribute no values and no descriptions at any stage; the only thing BI Pixie sends about an excluded field is its name, and only where your existing AI Instructions already mention it, so that your provider can remove that reference. When BI Pixie drafts text, it withholds more: no values at all from a semantic model that defines row-level security, because those values are restricted per user while a drafted AI Instructions block is read by everyone who uses the semantic model, and no values from a column whose name indicates an identifier or personal data.

Whose account this processing happens under. The provider account is yours, the credential is yours, and your provider bills the usage to you. What your provider does with a request, including whether it retains the request or uses it to train, is governed by your own agreement with that provider rather than by this policy. BI Pixie stores your credential encrypted with a key held in the BI Pixie Azure Key Vault, never returns it in any response, and never writes it to a log. You can change or remove the connected provider at any time on the Account page of the BI Pixie portal, and removing it stops every call described in this section.

4. Privacy by Default

Privacy is a core design principle of BI Pixie, not an afterthought.

• Sensitive features are off by default. User identity tracking, filter value collection, feedback collection, and survey features are all disabled unless you explicitly enable them.
• Anonymous by default. When user identity tracking is off, we use a one-way cryptographic hash to provide unique user counts without storing any personally identifiable information.
• IP anonymization available. You can configure IP address hashing so that IP addresses are cryptographically hashed before storage, making them non-reversible.
• Consent-gated. When you enable a high-sensitivity feature in the portal, a consent dialog requires you to acknowledge that the feature collects sensitive data and confirm it complies with your organization's data privacy policy.
• Fully reversible. You can remove all BI Pixie instrumentation from your reports at any time using "Remove Pixies," restoring them to their original, unmodified state.
• You are in control. We do not override, alter, or access your tracking configuration. You decide what data is collected.

5. How We Use Your Information

5.1 Customer Administrator Data

We use administrator data to:

• Authenticate and identify your account
• Deliver and maintain the BI Pixie service
• Process subscriptions and manage billing
• Provide customer support
• Send service-critical notifications (e.g., outages, security, billing changes)
• Maintain audit logs for security and compliance

We may use anonymized, aggregate account statistics (e.g., how many customers use a specific feature) for product improvement. These statistics cannot identify any individual or organization.

5.2 End-User Telemetry Data

We act as a data processor for end-user telemetry data:

• We route telemetry events to your dedicated storage container.
• We store the data for your analysis in Power BI.
• We do not analyze, mine, or use individual end-user telemetry data for any purpose of our own.
• We do not train artificial intelligence or machine learning models on customer telemetry data.
• We do not use telemetry data for advertising, profiling, or behavioral targeting.

5.3 After Account Closure

When your account is closed and your data is deleted, anonymized aggregate metrics (such as total event counts and feature adoption rates across all customers) may be retained for product improvement purposes. These metrics cannot be traced back to any individual customer, end user, or organization.

6. Data Storage, Security, and Residency

6.1 Infrastructure

All Cloud data is hosted on Microsoft Azure infrastructure with the following security measures:

• Network isolation: Internal services are protected by private endpoints and storage firewalls with default-deny rules.
• Encryption in transit: All communications use HTTPS with TLS 1.2 or higher.
• Encryption at rest: Azure Storage Service Encryption (AES-256) is enabled on all storage.
• Secret management: API keys and credentials are stored in Azure Key Vault with soft-delete protection.
• No stored credentials: We use Azure Managed Identity for service-to-service authentication, eliminating stored connection strings and passwords.

6.2 Data Isolation

Each customer receives a dedicated Azure Storage container. Access is controlled by Azure Active Directory role-based access control (RBAC) scoped to the individual container.

• No cross-customer access is possible. This is enforced by the Azure identity platform, not by application logic.
• Your Azure AD identity is granted read access to your container, allowing you to connect directly from Power BI using your own credentials.

6.3 Data Residency

• We automatically assign your data plane region as the BI Pixie region closest to your Power BI home region (Cloud) or your Fabric capacity region (Fabric workload); you do not pick it.
• All telemetry data is stored exclusively in that assigned region.
• Data does not cross regional boundaries.
• The assigned region is fixed for the lifetime of your account.

Deliver events to your own OneLake (Microsoft Fabric)

If you use BI Pixie inside Microsoft Fabric, a workspace administrator may turn on Data residency so that new telemetry events are delivered to your own OneLake lakehouse in your Fabric tenant, instead of being retained in our cloud. When this option is enabled:

• Your end-user telemetry is stored in your own OneLake, under your own governance and access control. You can revoke our write access at any time.
• To deliver events reliably, we briefly hold each event in a short-lived delivery buffer in your selected Azure region until it is written to your lakehouse, then remove it. If delivery is interrupted, you choose whether undelivered events are deleted or kept in the buffer until delivery recovers. The buffer is subject to the same backup-recoverability window described in Section 8.
• We keep a row-level, pseudonymized usage-metering record (no event contents) to enforce your subscription limits and for billing.

7. Data Sharing and Third Parties

• We do not sell or rent customer data or end-user telemetry data to anyone.
• We share it only with the sub-processors listed below, and with an AI provider you connect yourself under Section 3.7.
• We do not use third-party analytics or advertising services in our portal.

Sub-Processors

OpenAI and Anthropic are listed because BI Pixie sends them content that belongs to you, and anyone reviewing this policy should see them named. Their relationship to you differs from the relationship Microsoft Azure and Stripe have with you: you decide whether to connect OpenAI or Anthropic at all, you hold the account with that company, you supply the credential, and your own agreement with that company governs what it does with the request. BI Pixie makes no call to either company until an administrator on your account connects it, and removing that connection stops every such call.

Two further AI provider options are not listed in the table, because neither one sends your content to a company outside Microsoft. Azure AI Foundry runs in your own Azure subscription, and the BI Pixie data agent runs on your own Microsoft Fabric capacity.

We may disclose information if required by law, regulation, or valid legal process (such as a subpoena or court order). We will notify you of such requests to the extent permitted by law.

In the event of a merger, acquisition, or sale of assets, your data would transfer under the same privacy commitments described in this policy. We will notify affected customers in advance of any such transfer.

8. Data Retention

8.1 End-User Telemetry Data

Telemetry data is retained while your subscription is active, subject to the retention limits below. When your subscription is cancelled or expires, data is retained for a short grace period (see our Terms of Service) and then permanently deleted, regardless of the retention tier.

Events in BI Pixie's vendor-managed storage that exceed your retention period are automatically and permanently deleted on a daily basis. If your telemetry rests in your own tenant under OneLake delivery or Bring Your Own Storage (Section 3), BI Pixie applies no scheduled deletion to it unless you enable that service yourself; you control the lifecycle of that data. You may also configure a shorter retention period or request earlier deletion at any time by contacting support@bipixie.com.

8.2 Customer Administrator Data

Account information is retained while your account is active. Upon account closure, we delete your account data and keep only the limited records described in Section 9.3.

8.3 Audit Logs

Audit logs that record administrative actions (such as account changes and data deletions) are retained for compliance purposes even after account closure.

8.4 AI Benchmark Results

Scored benchmark results, including the correct answers BI Pixie computed from your semantic model (Section 3.6), are stored in the same dedicated storage container as your telemetry, or in your own OneLake lakehouse when your account uses OneLake delivery. The retention tiers in Section 8.1 do not apply to benchmark results: a stored result in your dedicated storage container is kept until you delete it in the BI Pixie portal or in the BI Pixie workload in Microsoft Fabric, and closing your account deletes that container (Section 9.1). If you turn on OneLake delivery, BI Pixie moves the results already held in that container into your own OneLake lakehouse and deletes its copies, so that your data rests where you asked. Benchmark results resting in your own OneLake lakehouse remain under your own governance, and you control their lifecycle.

9. Data Deletion

9.1 Account Closure

When your account is closed, we permanently delete your entire dedicated storage container and all telemetry data within it. This action is irreversible.

9.2 Individual User Data Removal

You may delete individual end users' telemetry data through the self-service data management tools in the BI Pixie portal. Each end user's data is stored in a dedicated subfolder within your container, enabling targeted deletion without affecting other users' data. You may also contact support@bipixie.com for assistance.

When you delete end-user or report data, the data is removed from your active storage. We may retain a temporary backup copy for up to 90 days to protect against accidental deletion and ensure data integrity, after which it is permanently destroyed. Backup copies are not accessible to you or any other customer.

9.3 What Remains After Deletion

After your account is deleted:

• Your dedicated storage container is permanently destroyed, together with all end-user telemetry, configurations, inventory records, and benchmark results inside it. This deletion is irreversible.
• Backup copies from earlier self-service deletions expire on their own schedule. Section 9.2 describes the temporary backup copies we keep when you delete end-user or report data. Each backup copy is permanently destroyed 90 days after it was created, counted from the self-service deletion that created it rather than from account closure, so a backup copy can remain for up to 90 days after your account is deleted. Backup copies are not accessible to you or any other customer.
• A minimal account record is retained. We keep a record that your account existed and was deleted, including your organization's tenant identifier. We use that record to block a deleted account from being re-registered as a new customer and to let the account administrator re-subscribe later. We also keep the final usage totals for billing reconciliation. For accounts on the Free plan, we keep a record of the semantic models that were already assessed under the free allowance, so that deleting the account does not reset the allowance.
• Anonymized aggregate metrics may be retained for product improvement (e.g., total event counts across all customers, feature adoption rates). These metrics cannot be traced to any individual customer, end user, or organization.
• Audit log entries are retained for compliance and security purposes.

10. Managed App and Power Platform Provisions

This section applies to customers using the Managed App (Azure) or Power Platform deployment models.

10.1 Managed App (Azure)

• BI Pixie is deployed entirely within your Azure subscription.
• All data collected by your deployment remains in your Azure environment.
• We have zero access to your data. We cannot view, retrieve, or process any telemetry or configuration data in your environment.
• We do not act as a data controller or data processor for your deployment.
• Your organization is solely responsible for compliance with applicable data protection laws.
• Your own privacy policies govern the data collected by your deployment.
• Our role is limited to providing the software license, updates, and documentation.

10.2 Power Platform

• BI Pixie is deployed within your Microsoft Power Platform environment.
• All data collected by your deployment remains in your Power Platform environment.
• We have zero access to your data. We cannot view, retrieve, or process any telemetry or configuration data in your environment.
• We do not act as a data controller or data processor for your deployment.
• Your organization is solely responsible for compliance with applicable data protection laws.
• Your own privacy policies govern the data collected by your deployment.
• Our role is limited to providing the software license, updates, and documentation.

10.3 What Applies to All Deployment Models

Regardless of your deployment model, the following sections of this policy apply to all BI Pixie users:

• Section 11: Your Rights and Choices
• Section 12: Children's Privacy
• Section 13: International Data Transfers (for the bipixie.com website and portal only)
• Section 14: Changes to This Policy
• Section 15: Contact Us

11. Your Rights and Choices

11.1 Customer Administrators

• Access: View your account and profile data in the BI Pixie portal at any time.
• Correction: Update your profile information through your Azure AD (Entra ID) account.
• Deletion: Request account closure and full data deletion by contacting support@bipixie.com.
• Data portability: Your telemetry data is stored in standard formats (TSV and JSON) in Azure Storage and is directly accessible via Power BI or Azure Storage Explorer using your own credentials.

11.2 End Users (Report Viewers)

End users whose interactions are tracked may have rights under applicable data protection laws (such as GDPR or CCPA). The BI Pixie customer (the organization that deployed tracking in your Power BI reports) is the data controller for your telemetry data.

If you are an end user and wish to exercise your data rights:

1. Contact your organization: the company or team that manages the Power BI reports you use. They control what data is collected and can fulfill access, correction, and deletion requests.
2. Your organization can use BI Pixie's tools to delete your data, or contact us at support@bipixie.com for assistance.

11.3 GDPR Rights (EU/EEA Individuals)

If you are located in the European Union or European Economic Area, you have the following rights under the General Data Protection Regulation:

• Right to access your personal data
• Right to rectification of inaccurate data
• Right to erasure ("right to be forgotten")
• Right to restriction of processing
• Right to data portability
• Right to object to processing
• Right to lodge a complaint with a supervisory authority

To exercise these rights, contact support@bipixie.com.

11.4 CCPA Rights (California Residents)

If you are a California resident, you have the following rights under the California Consumer Privacy Act:

• Right to know what personal information is collected
• Right to delete personal information
• Right to opt out of the sale of personal information. We do not sell personal information.
• Right to non-discrimination for exercising your privacy rights

To exercise these rights, contact support@bipixie.com.

12. Children's Privacy

BI Pixie is a business-to-business service designed for enterprise Power BI environments. We do not knowingly collect personal information from children under 16. If we discover that we have inadvertently collected information from a child under 16, we will delete it promptly. If you believe a child has provided us with personal information, please contact us at support@bipixie.com.

13. International Data Transfers

DataChant Consulting LLC is based in the United States.

• Cloud telemetry data is stored in the Azure region we automatically assign you, the BI Pixie region closest to your Power BI home region (Cloud) or Fabric capacity region (Fabric workload). If that assigned region is in Europe, your telemetry data remains within the EU/EEA.
• Account management data (customer administrator information and audit logs) may be processed in the United States.
• Requests to an AI provider you connect (Section 3.7) leave from the Azure region assigned to your account. Where OpenAI or Anthropic then processes such a request is determined by that company and by your own agreement with it. BI Pixie sends no such request until an administrator on your account connects a provider.
• For international data transfers, we rely on Microsoft's Data Processing Agreement and Standard Contractual Clauses where applicable.

For Managed App and Power Platform deployments, data does not leave your own infrastructure, and international transfer considerations are governed by your own policies.

14. Changes to This Policy

We may update this policy from time to time to reflect changes in our practices, technology, or legal requirements.

• Material changes will be communicated through the BI Pixie portal and/or by email to account administrators.
• The Last Updated date at the top of this page indicates when the policy was most recently revised.
• Continued use of the service after changes constitutes acceptance of the updated policy.

15. Contact Us

For questions, concerns, or requests related to this Privacy Policy or your data:

We aim to respond to all privacy-related inquiries within 30 days.