Network operations staffed around the clock
Skyroute
EN · EnglishEN
Talk to salesRequest access
POLICIES / DRAFT

Privacy Notice

This notice describes data paths visible in the local build. It requires a production review of the hosting region, processors, retention schedule and rights workflow before real customer data is processed.

Updated Draft for business and legal review
Draft notice

This dated draft records current product behavior. It must be reviewed before accepting live traffic or payments.

01

Data handled

Account details, authentication records, sender and caller identity records, message and call events, wallet transactions, contact inquiries and support tickets may be stored to operate the service. Message content and recipient numbers are sensitive operational data.

02

Why it is handled

The platform uses this data to authenticate users, route traffic, calculate usage and ratings, reconcile funds, investigate failures, prevent abuse and answer requests. Roles and tenant checks restrict access to account data.

03

Sharing and infrastructure

Traffic may be sent to the configured carrier or SIP provider needed for delivery. Payment and email services require separate production configuration. The local build uses simulated providers and a loopback test inbox; it does not establish a production processor list.

04

Optional website analytics

If an administrator configures a Google Analytics 4 measurement ID, the public website offers an analytics choice. Google Analytics is not loaded until a visitor accepts. The choice is stored in that browser and can be changed with the Privacy choices control; declining or withdrawing consent prevents it from loading on later pages. Google may receive site-use data and set analytics cookies after acceptance.

05

Retention and requests

Events, logs and financial records currently remain in the local database. A production retention and deletion schedule has not been approved. Use the contact form to request access, correction or deletion review; the local build does not promise automated erasure.

06

Security and changes

Credentials are intended to be kept secret, access is role-gated, and audit records exist for sensitive actions. No system is guaranteed to be risk-free. Material policy or infrastructure changes should be reflected in an updated notice.