Privacy policy
Meridian collects the minimum identity and operational data needed to run the service cleanly.
Privacy is approached as an operational discipline: collect less, separate billing from raw payment handling, and keep account identity legible.
Privacy policy
Structured overview
Billing
Stripe-processed
Identity
Account-linked access
Delivery
Private Telegram routing
Requests
support@meridiansig.com
Policy standard
The service should know who has access, why they have it, and which provider handles the sensitive part.
Last updated: April 15, 2026.
Data Meridian collects
Meridian collects account identity data, subscription status, and service-operation metadata required to provision access, support billing, and route private delivery.
Why it is collected
The service uses this data to authenticate members, attach billing to the correct account, support Telegram delivery, and resolve entitlement issues.
Processors and providers
Meridian relies on service providers such as Stripe, hosting infrastructure, analytics and operational tooling, and delivery infrastructure.
Retention and deletion
Data is retained only for as long as needed to operate the service, maintain records, comply with legal obligations, and preserve audit history.
Member rights
Members should be able to challenge, verify, and correct identity data tied to access.
Request access to the personal data Meridian holds about your account.
Request correction where account or billing identity data is inaccurate.
Request deletion where Meridian no longer has a valid operational or legal basis to retain the data.
Request clarification on which processors handle billing, hosting, and delivery-related functions.