SitravaSecure

How it works

The connection path, explained plainly

This page describes the intended connection path and its boundaries. It does not represent a live service state.

Abstract light trails representing an encrypted connection path
Encrypted sectionYour deviceSitrava appSitrava serverEncryption ends herePublic internetOnward routingDestinationOwn termsEncryption covers the device-to-server section only.The destination service applies its own security, logging and terms.

Diagram of the connection path. Your device creates an encrypted connection to a Sitrava server. Encryption applies only on that section. Traffic then continues from the Sitrava server to the destination service over the public internet, where the destination service's own security and terms apply.

Encryption applies between your device and the Sitrava server. It does not remove the security, privacy or legal responsibilities associated with the destination service.

Step by step

  1. Step 1

    Install a supported Sitrava application

    A Sitrava application must be published and supported for your platform before it can be installed. Supported platforms are listed only once an application is released.

  2. Step 2

    Sign in with an active account

    The application requires an active account. Account creation becomes available when the account system and subscription terms are open.

  3. Step 3

    The app connects to an available Sitrava server

    Availability varies by supported app, plan and location. Locations are published only when they are operational.

  4. Step 4

    Traffic between device and server is encrypted

    Traffic on that section is encrypted according to the configuration supported by the released application.

  5. Step 5

    The destination receives traffic after it leaves the server

    From the Sitrava server onward, the destination service applies its own security, logging, terms and legal obligations.

Limitations you should read before subscribing to any VPN

  • A VPN does not make you anonymous to every service. Accounts you sign in to still identify you.
  • A VPN does not protect a device, browser or account that is already compromised.
  • A VPN does not authorise activity prohibited by law, an employer, an educational institution or a service provider.
  • Connection quality varies by network, device, location and destination service.

Questions about scope and boundaries can be sent through the contact page, and data handling is described in the Privacy Policy.

Terms used on this page

Each word below has one fixed meaning across the whole website, including the plans and the policies.

Tunnel
The encrypted section of the path between a supported device and a Sitrava server. Everything outside that section is handled by other parties.
Destination service
The website, application or system you are actually contacting. It applies its own security, logging, terms and legal obligations regardless of how the traffic reached it.
Device allowance
The number of devices that may use one subscription. It is stated on the plan, in the subscription summary and at checkout — never inferred.
Merchant of record
The legal entity that sells the subscription, appears on the payment, issues the receipt and carries the refund obligation. For Sitrava that is Clicked IN FZE LLC.
Hosted payment page
A payment form served by the payment gateway rather than by this website, so card details are entered on the gateway's own page.
Renewal interval
The period a payment covers. The next charge falls at the end of it unless the subscription has been cancelled first.
Operational location
A server location that is running, monitored and approved for public display, published with the date it was last verified.
Service status
The published release stage of the whole service. It governs which parts of this website are visible, and it is changed only when the underlying fact changes.

What people usually want to check next

Scope questions, answered without marketing language.

How the service is being brought online

The connection path above is the intended design. This is the order in which the pieces behind it open.

  1. 01

    Company, legal and commercial foundation

    Completed

    Legal entity established in the United Arab Emirates, registered office confirmed, merchant of record named, and the terms, privacy, acceptable-use, subscription and refund documents drafted and approved for publication.

  2. 02

    Published service definition

    Completed

    The service boundary, the connection path and the limitations of any VPN written in plain language, along with the catalogue structure, device allowances and AED pricing.

  3. 03

    Subscription and payment route

    In progress

    Account-based monthly and annual subscriptions in AED, taken through a hosted payment page so that card details are entered on the payment gateway and never on this website.

  4. 04

    Application release and platform support

    Not started

    Each application is listed only when it is downloadable, versioned, supported and maintained. Until then the Apps page states that nothing is available rather than showing store badges.

  5. 05

    Operational server locations and status reporting

    Not started

    Locations appear individually once they are operational, monitored and approved for public display, each with its own last-verified date. No coverage map is drawn before then.