This Privacy Policy describes the data the Striq VPN service ("Striq", "Service", "we", "us") processes to deliver your connection, why it is processed, and how long it is kept. This document applies to the Telegram bot @StriqVpnBot, the website striq.cc, and the SafeTun mobile application. Striq is a network privacy service: the guiding principle is to process the minimum necessary to run the Service and to keep no record of what you do while connected.
1. Subscription data
Each subscription is identified by randomly generated values — a subscription UUID and a short token used in your import link. These identify the subscription, not you as a person.
We store the plan you purchased and its start and expiry dates so the Service can grant the correct level of access and terminate it at the right time.
If you interact with the Service through the Telegram bot, we process your Telegram numeric user ID and, if available, your Telegram username, display name, and language preference. These are used solely to deliver your key, respond to your messages, and send service notices such as upcoming expiry reminders.
If you use the SafeTun mobile application, the same subscription credentials apply. The app does not collect additional personal data beyond what is needed to establish the VPN connection.
An email address is not required and is only stored if you voluntarily provide one for delivery of subscription details.
2. Connection provisioning data
To connect you, the Service issues and stores the personal keys and credentials your apps use, the list of servers your subscription is allowed to reach, your plan's data allowance, and, where a device limit applies, the number of devices permitted.
When a device limit is enforced, each connecting app may report a hardware identifier. It is used only to count distinct devices against your limit and is not linked to any browsing activity.
3. Aggregate traffic counters
The Service keeps a running total of the volume of data your subscription has transferred — bytes sent and received — updated periodically. This total exists solely to enforce your plan's data allowance and is reset according to the billing cycle.
It is a cumulative number, not a history. It does not record which sites or services the traffic went to, or what it contained.
4. Short-lived connection metadata
For session management, abuse prevention, and troubleshooting, the Service may retain a small amount of recent operational metadata: the most recent IP address a device connected from, the time it last connected, and which server region it used.
These values are overwritten as new connections are made and are kept only for a short rolling window. They are not compiled into a log, profile, or browsing history.
5. Server metrics
The Service records per-server figures such as load, bandwidth, and health for capacity balancing and fault detection. These describe infrastructure, not individual subscriptions, and are not linked to your identity.
6. Payment data
When you purchase a plan, we store: the plan purchased, the payment amount and currency, the payment status, and a reference identifier returned by the payment processor.
Card numbers, bank credentials, and other sensitive payment information are entered directly with the payment processor and are held exclusively by that processor. Such data never reaches Striq systems.
The specific payment processor may change at any time depending on availability and operational requirements. Regardless of the processor used, Striq does not receive or store your actual payment instrument details.
7. What the Service does not collect
The Service does not log the websites or services you connect to, your DNS queries, your search history, or the contents of your traffic.
There is no deep packet inspection and no activity profiling.
Data is never sold, rented, or shared for advertising purposes by any party.
8. Legal basis for processing
All data processing described in this Policy is performed on the basis of the contractual necessity to deliver the Service you paid for: issuing keys, granting access to the right servers, enforcing plan limits (data allowance, device limit, subscription term), maintaining network availability, and processing payment.
9. Who data is shared with
Hosting and transit providers operate the servers that carry your VPN connection. They handle traffic in transit under confidentiality obligations and do not have access to your subscription identity.
The payment processor receives the details needed to process your payment and, where applicable, to process a refund. The specific payment processor may vary over time.
The Telegram platform carries bot messages if you use the Telegram bot.
Apple, as the operator of the App Store, may collect its own data in connection with the SafeTun application in accordance with Apple's privacy policies. We do not control Apple's data practices.
The limited data described above may be disclosed if compelled by a valid legal order issued by a court of competent jurisdiction. Because no activity logs exist, any such disclosure would be limited to subscription metadata and recent-connection metadata as described in this Policy.
10. Retention
Subscription records are kept while the subscription is active and for a limited period afterwards for renewals, support, and accounting purposes.
Aggregate traffic counters are reset each billing period.
Recent-connection metadata (last IP, last-seen time, last region) is kept only for a short rolling window and is then overwritten.
Payment records are retained for the period necessary for accounting, dispute resolution, and compliance with applicable financial record-keeping obligations.
Server metrics are retained in aggregate for capacity planning.
11. Security
Connections are encrypted in transit by default. Access to the systems that issue keys is restricted to authorized personnel. Keys can be rotated or revoked if a subscription is compromised or abused.
While we implement commercially reasonable security measures, no system is impenetrable. We cannot guarantee absolute security of data in storage or transit.
12. Your rights and controls
You can stop using the Service at any time and request deletion of your subscription record by contacting support@striq.cc.
You can reset your connection keys at any time through the bot interface.
A minimal payment and accounting record may be retained after deletion where required for legal or financial compliance, limited to what is strictly necessary.
13. International data processing
Servers are located in multiple countries. Choosing a server region means your traffic exits the network in that region. Provisioning data may be processed on infrastructure in more than one country.
By using the Service, you consent to the transfer of your data to servers in any country where our infrastructure operates.
14. Children
The Service is not directed at persons under the age of 18 or the applicable minimum age for consent to data processing in their jurisdiction. We do not knowingly collect data from minors. If we become aware that we have inadvertently collected data from a minor, we will take steps to delete it promptly.
15. Changes to this Policy
This Policy may change as the Service evolves. The current version is always the one published on this page, with the date indicated above. Your continued use of the Service after any change constitutes acceptance of the updated Policy.
16. Contact
For any questions or requests regarding this Privacy Policy or your data, contact us at: support@striq.cc. This is the sole official communication channel.