Seerveil Privacy Policy

Seerveil (“the Extension”) is a browser extension and associated proxy exit operated as part of the Seerror suite by Jay Tiwari in Bengaluru, India. This policy applies to the Extension and the Singapore proxy it connects to — not the full Seerror website, which is covered in our site Privacy Policy. By installing or using Seerveil, you agree to this document.

Summary at a glance

Who we are

Seerveil is built and operated by Jay Tiwari, an individual founder based in Bengaluru, India. The product is part of the Seerror suite, a founder-funded project. There is no parent company, no investors, no co-owners.

For the purposes of this policy:

• “Seerveil,” “we,” “us,” “our” → the extension and the proxy server it connects to.
• “You,” “your” → the person using the extension.
• “Server” → the Singapore VPS (currently Contabo) that routes encrypted traffic.

Data we do collect

Honestly? Almost nothing. Here is the complete list:

That's it. Three things. All stored locally in your browser. Nothing leaves your device as personally identifiable information to us.

Data we do not collect

This list is longer than the previous one. That is intentional.

• No name, email, phone number, or any account. Seerveil has no signup. There is no user database.
• No IP address logs. We do not record which IP you came from, or which IP the server assigned to you.
• No browsing history. We do not log which websites you visit through the tunnel.
• No DNS query logs. Your DNS goes through DNS-over-HTTPS (Cloudflare by default) — we never see it.
• No bandwidth metering per user. Server-level totals only, never per user.
• No device fingerprint. No user-agent harvest for tracking.
• No analytics. No Google Analytics, Plausible, Mixpanel, Sentry, etc.
• No crash reports phoning home.
• No marketing pixels.
• No A/B testing.
• No “anonymous” usage statistics.

How the extension works

Because vague policies hide bad practices, here's exactly what happens when you engage:

• The extension generates a session key locally in your browser. The key never leaves your device.
• Chrome's built-in proxy API is told: "route all traffic through the Singapore SOCKS5 proxy at sg-01.seerveil.example:1080."
• Your browser opens an encrypted connection to that server.
• WebRTC is sealed (disable_non_proxied_udp) to reduce common leaks.
• DNS lookups are forced through DNS-over-HTTPS to your chosen resolver (default: Cloudflare).
• Your popup may show the new public IP — fetched from api.ipify.org unless disabled.
• Settings persist in chrome.storage.local. They are not synced to Google or Seerror.

When you disengage: proxy settings are cleared and local connection state resets.

What the proxy server sees

Like every VPN, the proxy is a middleman. By nature of TLS and routing, the server can technically observe:

• Your source IP — during the connection, in RAM only.
• The destination hostname — via DNS or TLS SNI. Page content stays encrypted.
• Connection timing and bytes.
• Source and destination ports.

What we do to minimize this:

• RAM-only operation. The Dante SOCKS5 daemon is configured with log: error only. Successful connections are not logged. Failed connections log only an error code, no IP.
• No persistent disk writes. The server's disk holds the OS and binary, not user data. A reboot wipes any volatile state.
• No remote log shipping. We do not run Splunk, Datadog, or any centralized log collector.
• Aggregate bandwidth only. We monitor total monthly TB (to avoid Contabo overage), never per-user.
• Singapore jurisdiction. The server is outside Indian legal reach for CERT-In provider logging rules as described in our India section.

What your ISP and network see

When Seerveil is engaged, your ISP sees:

• An encrypted connection to one IP in Singapore.
• How much data flows and when the tunnel is up.

They cannot see which sites you visit inside the tunnel, your plaintext searches, or your DoH queries to the resolver you chose. They can tell you are using encrypted tunneling to a hosting provider.

Third parties

The complete list of third parties Seerveil interacts with includes:

• Contabo GmbH — hosts the physical server. They see hosting metadata; not your TLS payloads.
• Cloudflare (default DoH) — receives DNS queries when DoH is enabled. See Cloudflare's resolver privacy policy. You can switch resolver in settings.
• ipify.org — optional request from your popup for public IP display.

We have no advertising partners, data brokers, or analytics vendors for Seerveil.

Cookies and storage

The extension uses Chrome's chrome.storage.local API. This is local-only storage on your device, never synced.

The Seerveil website (seerror.com pages) uses zero cookies, zero local storage, zero session storage for this policy's static pages. There is no consent banner on this document because there is nothing to consent to here.

Children

Seerveil is not directed at children under 13 (or 18, depending on jurisdiction). We do not knowingly collect personal data; there is no account to delete.

Government and legal requests

If a court or agency demands user data, we will respond honestly:

• No user accounts — no name, email, or KYC to hand over.
• No subscriber logs as described in this policy.
• Hardware/hosting metadata may be held by Contabo under their policies.

If we ever receive a request to add user-identifying capabilities (logging, backdoors), our published response will be: no, and here is the request. We commit to a public transparency post.

India and CERT-In

India's CERT-In Directions (April 2022) require VPN providers operating within Indian jurisdiction to retain five years of subscriber identification and connection logs.

Seerveil deliberately avoids this requirement through the following design choices:

• The proxy server is located in Singapore, not India.
• The operating jurisdiction for infrastructure decisions is outside Indian regulatory reach for that logging mandate.
• We collect no subscriber data, so there is no KYC to retain even if compelled.
• We will publish a transparency report annually starting May 2027.

This is the same architectural strategy used by major providers that withdrew physical servers from India in 2022 rather than implement subscriber logging.

Your rights (DPDP Act 2023)

Because we do not hold personal data on servers for accounts, most rights are moot in practice — settings live on your device; uninstall erases extension storage.

For GDPR users, the same logic applies: we do not maintain an account database for Seerveil users.

Changes to this policy

If we change this policy, the new version replaces this page, and prior versions may be archived (e.g. under seerror.com/seerveil-privacy/history/v1.html). We commit to:

• Notifying in the extension popup for at least 14 days before material changes.
• Keeping prior versions accessible.
• Never silently weakening protections.

If a change would reduce privacy (e.g. add logging), we commit to 30 days' notice and a clear uninstall path before it applies.

Contact

Privacy questions, complaints, or government inquiries:

• Email: seerrorworks@gmail.com
• X: @seerrorX
• Discord: Community
• Grievance officer: Jay Tiwari — same email; postal address in Bengaluru available on legitimate request.

Seerveil — Part of the Seerveil product page · Seerror · Site privacy