Minimal Logging Policy — What FreeGuard Collects and What It Does Not

FreeGuard operates a minimal logging policy. We collect connection timestamps and anonymized error codes needed to maintain service reliability. We do not collect browsing history, DNS queries, traffic content, or IP-to-activity associations.

What FreeGuard Collects and Why: Full Transparency

FreeGuard collects connection timestamps, bandwidth usage totals, and anonymized error codes. This data is necessary for server capacity planning, abuse prevention, and debugging connection issues.

We believe honesty is better than marketing claims. Here is exactly what FreeGuard collects:

What IS collected:

• Connection timestamps: When you connect and disconnect from VPN servers. Used for capacity planning and fair usage enforcement. Stored for 30 days, then deleted.

• Aggregate bandwidth usage: Total data transferred per session (not per-site or per-request). Used to manage server capacity and enforce fair use on free tier accounts.

• Anonymized error codes: When connections fail, we log error types (not content) to identify and fix infrastructure issues. These are not linked to user identity.

• Account information: Email address, subscription status, and payment metadata needed for account management. What is NOT collected:

• Browsing history or websites visited

• DNS query logs

• Traffic content or payload data

• Source IP addresses linked to activity logs

• Connection-level metadata that could identify specific user activity

Why Honest Minimal Logging Is Better Than False No-Logs Claims

Many VPN providers claiming zero-logs have been caught collecting data. A transparent minimal logging policy with clear boundaries is more trustworthy than unverifiable marketing promises.

The VPN industry has a credibility problem with logging claims. Multiple providers advertising zero-logs policies have been exposed collecting user data — sometimes revealed through data breaches, sometimes through law enforcement cooperation that contradicted their stated policies.

The reality is that operating a reliable VPN service requires some data collection. Connection timestamps are needed to manage server load. Bandwidth totals are needed for capacity planning. Error logs are needed to fix outages.

Rather than claiming we log nothing (which would either be false or indicate we cannot maintain reliable service), we choose transparency. We tell you exactly what we collect, why we collect it, how long we keep it, and what we will never collect.

This approach is aligned with GDPR principles of data minimization and purpose limitation. We collect only what is necessary for the specified purpose, keep it only as long as needed, and provide clear documentation of our practices.

How Our Logging Policy Compares to Industry Standards

FreeGuard collects less data than most VPN providers while being more transparent about what is collected, aligning with GDPR data minimization principles.

To put our policy in context, here is how different logging approaches compare:

Full logging (ISPs, some free VPNs): Records browsing history, DNS queries, IP addresses, timestamps, and sometimes traffic content. This data can be sold, shared with governments, or breached.

Session logging (many paid VPNs): Records connection timestamps, bandwidth, and server selection. This is similar to FreeGuard’s approach but many providers also log source IP addresses.

FreeGuard’s minimal logging: Connection timestamps and aggregate bandwidth without source IP association. Error codes are anonymized. No browsing data of any kind.

Claimed zero-logging: Providers state nothing is collected. While theoretically possible using RAM-only servers and no monitoring, this claim is difficult to verify and has been disproven for multiple providers.

We recommend evaluating any VPN’s logging policy based on specificity (do they say exactly what is collected?), retention periods (how long is data kept?), and third-party audits (has an independent party verified the claims?).

How to Get Started

1. Step 1: Read our full privacy policy at /privacy for complete details on data collection and retention
2. Step 2: Enable FreeGuard VPN and connect — minimal logging applies automatically with no configuration needed
3. Step 3: Review your account’s data in Settings → Privacy to see exactly what information is associated with your account

Frequently Asked Questions

What specific data does FreeGuard VPN collect about my connection activity when I use the service and what are the key considerations and potential limitations that I should be aware of before proceeding?

We collect connection timestamps (when you connect/disconnect), aggregate bandwidth totals per session, and anonymized error codes. We do not collect browsing history, DNS queries, or traffic content.

How is FreeGuard’s minimal logging policy different from VPN providers that claim to have a strict no-logs policy and what are the most important things I should know about this?

We are transparent about collecting connection timestamps and bandwidth totals needed for operations. Many no-logs providers have been caught collecting more data than disclosed. We prefer honesty over marketing claims.

Can FreeGuard see which websites I visit or what content I access while connected to the VPN service and what are the most important things I should know about this?

No. We do not log DNS queries, browsing history, or traffic content. Our servers process your encrypted traffic in real-time but do not record destinations or content.

How long does FreeGuard retain the connection data that it collects, and can I request its deletion and what are the most important things I should know about this?

Connection timestamps and bandwidth data are retained for 30 days, then automatically deleted. You can request immediate deletion of your data through Settings → Privacy or by contacting support.

If law enforcement requests my data from FreeGuard, what information would you actually be able to provide and what are the most important things I should know about this?

We could only provide connection timestamps and bandwidth totals for the past 30 days. We cannot provide browsing history, DNS logs, or traffic content because we do not collect that data.

Does FreeGuard’s minimal logging policy apply equally to both free tier and premium subscription users and what are the key considerations and potential limitations that I should be aware of before proceeding?

Yes. The same minimal logging policy applies to all users. Free tier accounts have bandwidth tracking for fair use limits, but the types of data collected are identical.

Why does FreeGuard need to collect connection timestamps at all if it values user privacy so highly to ensure my personal data and browsing activity remain fully private?

Connection timestamps help us manage server capacity, detect abuse patterns (like DDoS-through-VPN), and debug connection issues. Without this data, we could not maintain reliable service.

Has FreeGuard’s logging policy been verified by an independent third-party security audit or assessment to ensure comprehensive protection of my personal information and online activity from potential threats?

We are committed to transparency and pursue regular infrastructure reviews. Details of completed and planned audits are published on our trust page at /trust.