Privacy notice
Version 1.0 · last updated 30 July 2026
Who is responsible?
Deuver is responsible for Everscope account, billing, security and support data. For customer-provided Power BI, Fabric and governance metadata, Everscope generally acts as processor on the customer’s documented instructions.
Registered address: Steenplaetsstraat 6, Unit 4.14, 2288 AA Rijswijk, Netherlands. KVK: 92707009.
What data does Everscope process?
Everscope processes Microsoft account information, Power BI/Fabric metadata, scan results, aggregated usage statistics, read-only workspace role assignments, and user-provided governance and workflow information. This can include owner, principal or validator names, KPI definitions, strategic objectives, team names, deadlines, decisions, notes, data classifications, SLA information, and links to external tickets. Everscope does not read or store underlying semantic-model rows and never removes Power BI objects automatically.
The optional Free Power BI Project Check processes a selected project folder or ZIP containing customer-provided TMDL and PBIR metadata. A selected folder is packaged locally in the browser, and any local data cache is excluded before upload. Metadata can contain model definitions, query definitions and connection information, so customers should treat it as potentially confidential. The prepared upload and extracted files are deleted immediately after processing succeeds or fails. Everscope retains only the structured, account-scoped scan result for the configured retention period.
Launch control can also store support contacts, readiness attestations, pilot feedback, incident messages, subscription entitlements and billing-provider references. Everscope does not store payment card data. Provider references are excluded from normal exports.
Before Microsoft is connected, Everscope stores the account email, password hash, name, organisation, selected plan, sign-in timestamps and communication preferences. Plain-text passwords are never stored. The account email is marked as matched only when the same email is returned by the connected Microsoft identity.
Governance email preferences are stored per recipient and per organisation. Everscope also records the message type, unique event key, delivery status and destination screen so scheduled worker retries cannot send the same notification twice. Email content is derived from tenant-scoped metadata findings, assignments, changes and time-limited exceptions.
The contact form sends the submitted name, business email, organisation, selected topic and message to Everscope through Resend. Contact messages are not stored in the Everscope application database and are used only to answer the enquiry, unless separate marketing consent is obtained.
Purposes
Data is used only for authentication, technical analysis, history, governance workflow, security, and service support.
Optional product updates and governance guidance are sent only when the account holder actively selects the separate marketing checkbox. The choice and time are recorded as consent evidence and can be withdrawn in Account settings. Service and security messages remain separate from marketing.
Billing information
Stripe processes payment methods, billing addresses, tax identifiers, invoices and payment status as an independent payment provider. Everscope stores only the Stripe customer and subscription references, plan, trial date, billing status and current access period needed to provide the subscription. Everscope never stores full card details.
Microsoft tokens
The MSAL token cache is encrypted at rest with AES-256-GCM. Tokens and secrets are not included in application logs.
Cookies
Everscope uses first-party session cookies for account and Microsoft sign-in security. It also uses a session-limited, first-party visitor identifier to count visits and understand which Everscope pages and product steps are used. Product events contain a page path or a fixed event category, never page content, uploaded metadata, Microsoft tokens or business data. The visitor identifier expires when the browser session ends.
Everscope does not currently use third-party analytics, advertising cookies or cross-site tracking. If those technologies are introduced, Everscope will request the required consent before activating them and will provide a way to change that choice.
Activity Events
User identities from Microsoft Activity Events are used only temporarily in memory to count unique users. Only aggregated counts per asset are stored.
Retention
Reconstructable completed scan history and its compact metadata changes are retained for at least 24 months while the service remains active. Failed scan data and transient operational records follow the configured retention period, which is 90 days by default. Account deletion removes tenant-scoped scan history subject to backup and legal-retention obligations.
Export and deletion
In Settings, a user can export stored data or permanently delete the connection and its associated data. A user can also create tenant-scoped, read-only API keys for governance integrations. Only key hashes are stored; keys can expire and be revoked. API responses do not contain underlying semantic-model rows or KPI business values. Tenant archives include launch evidence, feedback, incident history and operational alerts; billing-provider identifiers are redacted.
Everscope owner exports for marketing contain only email addresses that have both explicit marketing consent and a matched email status.
Subprocessors and region
Production uses Fly.io for application hosting in Amsterdam, Supabase for PostgreSQL in an EU region, Microsoft for identity and Power BI/Fabric APIs, and Stripe for payments and invoices. Those providers process only the information required for their role and may use their own approved international-transfer safeguards where applicable.
See the current Subprocessor list and Data Processing Agreement.
Contact
Privacy questions and data-subject requests can be sent to privacy@everscope.app. Security reports can be sent to security@everscope.app.