Privacy Policy
Website and app blocking takes place on the device, but Sello also uses servers and providers for identity, subscriptions, notifications, diagnostics and measurement. This policy describes those data flows in the app, the website and the server.
Summary
- You do not need to create an email-and-password login. We use user, device and RevenueCat identifiers; this does not mean there is no personal data.
- Filtering is local. Blocked attempts stay in local history; a report you voluntarily submit may contain a domain or app.
- The server keeps operational data beyond your seal and license. See the categories below.
- Protection depends on permissions, Android and your seal contract. It is not tamper-proof.
- Google Play processes payments; Sello does not receive your card details.
1. Data and purposes
- Identity and devices: user, device and RevenueCat IDs, country when available, device bindings and temporary pairing codes.
- Protection and service: seal dates and contract version, license status, the three permission states, last contact, sessions and the FCM notification token.
- Subscriptions: product, store, events, amount, currency and purchase, renewal, cancellation and expiration dates received through RevenueCat.
- Acquisition: installation referrer, UTM parameters, click identifiers and click/installation timestamps for attribution.
- Optional submissions: reported domain/app and local verdict, cancellation feedback, an invited partner's email and waitlist email. Support also receives what you send by email.
2. On-device processing
The VPN applies DNS filtering locally and does not act as a remote Sello browsing VPN. Allowed queries are forwarded to the configured DNS resolver; current code uses Cloudflare's 1.1.1.1. Blocked-attempt history stays local. Reporting a website/app is a separate action that sends the selected item to the server. This is not the same as automatically sending your entire browsing history.
3. Permissions
Accessibility observes the active window's package and class to detect gambling apps and protection-removal screens. Current code does not use these events to capture typed text, passwords or screen images. Device Administrator and Accessibility make removal harder during protection; they do not guarantee that removal is impossible. The VPN filters supported connections. Revoked permissions or Android limitations may reduce protection.
4. Server and providers
Sello's backend stores the operational categories above. Google Play and RevenueCat support purchases and subscription validation. Firebase provides Analytics, Crashlytics, Remote Config and FCM; Amplitude receives product events when configured. Events and diagnostics may include identifiers, version, permission states and usage steps, not just anonymous totals. Partner invitations use Resend when that feature is available and configured. Being present in the code does not mean a service is enabled in every installation.
5. Payments and subscriptions
Google Play processes payment. RevenueCat and the backend reconcile identity, license and subscription events; Sello does not receive or store card numbers. Price, eligibility and terms are shown at checkout. Uninstalling or requesting data deletion does not cancel a subscription: manage renewal in Google Play. Canceling renewal and opening a seal are different actions governed by the terms shown in the app.
6. Website, measurement and sharing
The production website uses Google Analytics and retains campaign parameters for the Google Play link. The waitlist sends email and source when you use it. The backend also supports conversion exports to Google Ads, including a click identifier and event, when configured; it would be inaccurate to promise no sharing for advertising measurement.
7. Rights and contact
You may request information about processing and ask for access, correction or deletion through the contact below, under applicable rights. Persistent IDs do not make data anonymous. To locate a record, include the identifier available in Settings; never send passwords or card details. Each request is handled through the contact below; deletion is not automatic.
8. Retention and security
A uniform retention period has not been verified for all categories. Retention periods, reasons for keeping data, deletion procedures and provider responsibilities must be approved before publishing this revision. No system offers absolute security.
e@getsello.app · Data subject rights — ANPD
Sello is intended for adults aged 18 and over.