LegalEffective April 3, 2026.

Privacy Policy

This policy explains how Deplio handles account information, workspace data, billing state, and analytics data inside this deployment.

01
Scope of this policy

This policy applies to the Deplio application, the public marketing pages, authenticated workspaces, project onboarding flows, billing pages, and support contact channels operated for this product.

  • It covers data collected directly through the app and related support channels.
  • It does not replace any privacy notice required on the websites you track with Deplio or Umami.
02
Information we collect

We collect the information needed to authenticate users, operate workspaces, provision projects, and provide billing and support.

  • Account data such as full name, email address, avatar, and authentication provider identifiers.
  • Workspace data such as workspace names, memberships, invitations, roles, active workspace state, and project ownership.
  • Project configuration such as domains, timezone, onboarding status, public share settings, audience presets, and tracker options.
  • Billing data such as selected plan, subscription state, Polar customer or subscription identifiers, usage totals, invoices, and checkout metadata.
  • Support data such as the information you voluntarily send when contacting support by email or Telegram.
03
Analytics and event data

When you enable tracking for a project, analytics data is collected through your connected Umami deployment and surfaced inside Deplio reports.

  • This may include pageviews, sessions, referrers, UTM parameters, device and browser information, custom events, and related report aggregates.
  • Deplio stores the mappings and settings required to connect a workspace or project to the corresponding Umami resources.
  • The tracked websites remain responsible for providing any notices, consent flows, or other disclosures required by applicable law.
04
How we use information

We use data to authenticate users, manage access, deliver analytics features, operate subscriptions, prevent abuse, diagnose incidents, and respond to support requests.

  • To create and manage workspaces, projects, invitations, roles, and public sharing.
  • To connect reports and onboarding flows to the configured Umami instance.
  • To operate plan limits, usage monitoring, checkout, billing access, and subscription lifecycle events.
  • To secure the product, investigate misuse, and maintain service reliability.
05
Service providers and infrastructure

We use third-party services to provide core parts of the product. Those services process data only to the extent needed to operate the product or complete a transaction.

  • Supabase Auth handles sign-in sessions and supported identity providers.
  • Polar handles checkout, subscription billing, and invoice-related workflows.
  • Your configured Umami deployment processes analytics collection and reporting data.
  • Hosting, database, monitoring, and infrastructure providers may process operational logs and system data as part of normal service delivery.
Payment card details are processed by the payment providers used by Polar and are not stored directly by Deplio.
06
Retention, deletion, and security

We keep data for as long as it is needed to operate the product, comply with contractual or legal obligations, resolve disputes, and maintain security records.

  • Workspace owners and admins may remove projects, revoke invitations, change members, or reset analytics data where the product allows it.
  • Retention of analytics data may depend on plan level, Umami configuration, and infrastructure choices made by the deployment operator.
  • We use reasonable technical and organizational measures to protect the product, but no system can guarantee perfect security.
07
Your choices and contact

You can usually review or update account and workspace information from inside the app. You may also contact the deployment operator or Deplio support to ask about deletion, retention, billing questions, or rollout concerns.

  • Workspace-specific requests should normally be routed through the workspace owner or deployment operator first.
  • Support requests can be sent by email or Telegram using the contact details listed below.
Questions about privacy or rollout?
If you need help understanding how workspace data, analytics data, or billing data moves through the product, contact support.

Effective April 3, 2026.