Zibfo Shield Privacy Policy
Last updated: 5 August 2026
1. Overview
This privacy policy applies to the Zibfo Shield Android application (“Zibfo Shield”, “the app”) and the filtering service behind it, developed and operated by Parishod. It explains what data we collect, why, how long we keep it, who else can see it, and how you can delete it.
The short version: Zibfo Shield records the site names your device looks up, because that is how filtering works and how the app shows you what it blocked. It never sees the pages themselves, your messages, photos, passwords or app data. Query records are deleted automatically after 30 days, and you can delete your account and everything associated with it at any time.
2. How the app works, and why it needs a VPN permission
Zibfo Shield asks Android for permission to set up a VPN connection. This is required because it is the only way an Android app can filter what the whole device requests rather than a single browser. Android displays a key icon in your status bar for as long as it is active.
Zibfo Shield is not a proxy or an anonymity VPN. It does not hide your IP address, change your apparent location, unblock geo-restricted services, or route your web page contents through our servers. The only traffic it handles is your device’s domain name lookups.
When your device looks up the address behind a site name, the app sends that lookup over an encrypted connection (DNS-over-TLS) to our filtering servers. Those servers compare the name against the categories and rules you have enabled and refuse to answer for anything that matches, so the connection to a blocked site is never made.
3. What we collect
Account information
Zibfo Shield requires an account, created by signing in with Google. From that sign-in we receive and store your email address, your display name, and a Google account identifier. We use these solely to identify your account, keep your settings attached to it, and contact you about the service.
Domain name lookups (your browsing history, in part)
When filtering is on, the site names your device requests — for example example.com — are sent to our filtering servers and recorded, together with a timestamp, an identifier for your device, and whether the name was allowed or blocked. Under Google Play’s data disclosure categories this counts as web browsing history, and we declare it as such.
We record it for one reason: so the app can show you your own activity — how many requests were made, how many were blocked, and which sites were blocked most often. We do not sell it, share it, use it for advertising, or build profiles from it.
Note what this does not include: the pages themselves, anything you typed or submitted, the contents of encrypted connections, your messages, photos, passwords or app data. A name lookup tells us that your device asked where a site is, not what happened next.
Device and diagnostic information
- Device identifiers. An identifier for each device registered to your account, plus the device name you choose, so settings can be applied to the right device.
- Crash reports and diagnostics. If the app crashes or misbehaves, Google Firebase Crashlytics sends us a crash report containing device model, Android version, and a stack trace, so we can fix it.
- Usage analytics. Google Firebase Analytics records aggregate, in-app events — which screens are opened, which features are used — so we can see what is worth improving. This may include Android’s advertising identifier. We do not use it for advertising, and we do not run ads.
4. What we never collect
- The contents of web pages, messages, emails, photos, files or app data.
- Your passwords, payment details, or the contents of encrypted connections.
- Your contacts, call logs, SMS, microphone or camera.
- Your precise location. We do not request location permission.
5. Who else sees your data
We do not sell your data, and we do not share it with advertisers or data brokers. Your data is processed by:
| Provider | What it handles |
|---|---|
| Google (Firebase Authentication, Firestore, Cloud Messaging, Crashlytics, Analytics) | Sign-in, account and settings storage, push notifications, crash reports, usage analytics |
| Parishod filtering servers | Your domain name lookups, filtering rules, and the activity records shown in the app. Operated by us, not a third party. |
We may disclose data if we are legally required to — for example in response to a valid legal order. We will not do so voluntarily.
6. How long we keep it
- Domain name lookup records: automatically deleted 30 days after they are recorded.
- Account information, devices, and filter rules: kept for as long as your account exists. Deleted when you delete your account.
- Crash reports and analytics: retained according to Google Firebase’s own retention settings, and not linked to your browsing activity.
Deleting your account revokes your device's filtering credentials immediately, so no further lookups are recorded. Existing lookup records are then removed by the same automatic 30-day expiry, so none remain within 30 days of your request.
7. Deleting your data
You can delete your account and everything associated with it — account details, devices, filter rules, and your lookup history — at any time. See Delete your Zibfo Shield account for the steps. You do not need the app installed to do it.
You can also stop new data being recorded at any time without deleting your account, by turning protection off in the app or revoking the VPN permission in Android settings. Nothing is sent to our servers while filtering is off.
8. Your rights
Depending on where you live, you may have rights to access, correct, export, or erase your personal data, to object to or restrict its processing, and to complain to a data protection authority. To exercise any of these, email dk.zibfoshield@deekshith.in. We will respond within 30 days.
9. Security
Lookups travel between your device and our filtering servers over an encrypted DNS-over-TLS connection, authenticated with a token unique to your device. Account data is transmitted over HTTPS. Your PIN is stored on your device as a salted hash and is never transmitted to us. No system is perfectly secure, but we do not retain data we do not need, which is the most effective protection we can offer.
10. Children’s privacy
Zibfo Shield is intended for adults filtering their own devices. It is not directed at children, and we do not knowingly collect data from anyone under 18. If you believe a child has created an account, email us and we will delete it.
11. Changes to this policy
If we change what we collect, why, or how long we keep it, this policy will be updated before the change takes effect, and we will tell you in a clear and conspicuous way — for example an in-app notice — rather than quietly amending this page. The date at the top always reflects the current version.
12. Contact
Questions about this policy or about Zibfo Shield: dk.zibfoshield@deekshith.in.