This policy explains how IBKO Pixels processes information when you use Barq VPN (formerly BaraqVPN). Barq VPN does not require you to create an account to use its core features.
1. Information we may process
Device and app information
This may include device type, operating system and version, app version, language, country or approximate location derived from an IP address, mobile network, installation identifiers and technical settings.
VPN connection information
To establish, maintain and secure a VPN connection, the app and its infrastructure may process an IP address, connection timestamps, selected server or region, connection status, bandwidth or performance measurements and technical error information. IBKO Pixels does not use the content of network traffic to create advertising profiles.
Accounts and guest access
If you choose account sign-in, our authentication providers, Supabase and Firebase Authentication as configured by the app, process your email address, account identifier and available profile information such as your name and profile image. Guest access can also create an anonymous service identifier. Account identifiers may be shared with RevenueCat to associate Premium access with your account.
iOS analytics and advertising tracking
In iOS versions 1.0.5 build 6 through 1.0.7, and the earlier 1.0.8 build 10, Firebase Analytics and Meta App Events collection is disabled. Those versions do not send app-use events to those analytics services. Advertising identifier collection is disabled. This does not remove the account, subscription, VPN connection or user-requested breach-check processing described in this policy.
Starting with iOS 1.0.8 build 11, Meta App Events is available only after a separate, optional opt-in. It is off by default, including for users who previously agreed to analytics in an older version. Meta receives app-open and predefined screen-view events for app usage and advertising measurement. The SDK may process IP address, app-scoped identifiers, device and SDK metadata. We do not supply VPN connection events, selected servers, browsing history, DNS queries, tunnel content, account email or purchase events to Meta on iOS. Automatic event logging, IDFA collection and advertiser tracking are disabled. Firebase Analytics remains disabled on iOS. You may decline analytics or withdraw consent in Settings to stop future app event submissions; this does not delete events already received by Meta. Meta describes its processing in its Privacy Policy.
From iOS 1.0.8 build 13, the optional Meta integration is further limited to app-open and standard app activation/install measurement events for our own campaign measurement. The app no longer sends screen-view events. This choice remains off by default and can be withdrawn in Settings under “App launch and campaign measurement”. A launch or activation event is not itself a count of new App Store downloads. Advertising identifier collection, automatic purchase logging and advertiser tracking remain disabled.
Earlier iOS builds and Android versions may offer optional Firebase Analytics and Meta App Events measurement after consent. Where this option is present, you can continue without analytics. These events may include app opens, screen views, connection outcomes, selected server or protocol and subscription activity. We do not include scanned email addresses, browsing history, DNS queries or VPN tunnel payloads in analytics event parameters.
Advertising in free accounts
Starting with iOS 1.0.7, free accounts may receive non-personalized banner and interstitial ads through Google AdMob, after applicable consent. Premium accounts do not request or display ads. Google may process IP addresses (including approximate location), app-scoped device identifiers, advertising interactions, crash logs and performance diagnostics for ad delivery, measurement and fraud prevention. Non-personalized ads do not mean that no data is processed. We do not send VPN browsing history, DNS queries, tunnel payloads or account email to AdMob. We do not request IDFA access, and publisher first-party ID is disabled before SDK initialization. You can manage applicable advertising consent in the app's Settings. Google's processing is described in How Google uses information from sites or apps that use its services.
Subscriptions and optional breach scans
Apple and RevenueCat process purchase records, transaction and app-user identifiers, and subscription status to provide purchases, restore purchases and manage Premium access. When you explicitly start an email breach scan, the address you enter is sent to XposedOrNot and LeakCheck to return the scan result. This is separate from VPN traffic processing.
Diagnostics
Crash logs, performance data and technical diagnostics may be processed to maintain reliability, investigate errors and protect the service.
2. Why we process information
- Provide and maintain the VPN connection.
- Protect the app and infrastructure from misuse and security threats.
- Maintain accounts and diagnose technical problems. Optional app-use and advertising measurement applies only after consent in versions that offer it; see the version-specific iOS explanation above.
- Provide Premium subscriptions, purchase restoration and user-requested breach scans.
- Comply with legal obligations and enforce our terms.
3. Legal bases
Where the GDPR applies, processing may be based on performance of the service you request, our legitimate interests in security and product operation, consent for optional analytics and advertising where required, and compliance with legal obligations.
4. Service providers
Our providers include VPN hosting and infrastructure providers, Apple and RevenueCat for subscriptions, Supabase and Firebase Authentication for accounts, Google Firebase Analytics and Meta App Events only in versions that offer consent-based app analytics, Google AdMob for advertising in free accounts in supported versions, and XposedOrNot and LeakCheck for user-requested breach scans. They process information under their own terms or on our instructions, depending on their role. Some providers may process information outside the European Economic Area using legally recognised safeguards.
5. Retention and security
Information is retained only for as long as needed for the purposes described, including security, troubleshooting, optional app analytics, subscription management and legal obligations. Retention periods vary by data type and provider. We use reasonable technical and organisational measures, but no service can guarantee absolute security.
6. Your choices and rights
In older iOS versions described above, analytics event collection is disabled. From iOS 1.0.8 build 11, you can choose “Continue without analytics” or disable optional usage analytics in Settings. Previous analytics consent is not reused for this iOS feature. You can request account deletion through the app where available, or contact us for help, deletion requests or withdrawal of previously granted consent. You can also contact us to exercise applicable privacy rights, including access, correction, deletion, restriction, objection and portability. You may complain to the Dutch Data Protection Authority or your local supervisory authority.
7. Children
BaraqVPN is not directed to children under 13. We do not knowingly request account information from children. If you believe a child has provided personal information, contact us.
8. Changes and contact
We may update this policy when the app, providers or legal requirements change. The current version will remain available on this page. Questions and privacy requests can be sent to contact@ibkopixel.nl.