LineLayer Privacy Policy

Scope

This policy primarily describes the LineLayer Android app (package com.enkidev.linelayer). Where a statement is specific to the LineLayer Learn website instead of the Android app, it's marked clearly, and the "LineLayer Learn website privacy" section further down covers the website on its own.

What LineLayer does not do

• LineLayer does not operate user accounts, logins, or cloud sync — there's nothing to create an account for.
• LineLayer does not read your device's system call log; it only keeps a record of the calls it screens itself.
• LineLayer does not copy your contacts into its own storage. It looks up a number against your contacts, or a name for display, at the moment it's needed, and does not retain that lookup.
• LineLayer is not a global caller-ID or spam-verification service. Reported-activity checks compare an incoming number against public report data — they don't identify who a number belongs to, and a report isn't proof of anything. LineLayer's core filtering works from rules you define, not from identifying strangers.

What LineLayer accesses

Contacts. LineLayer can request access to your contacts (Android's Contacts permission) so it can recognize numbers you've already saved. This permission is optional and requested at runtime: LineLayer works without it, just without the "block numbers not in your contacts" rule active, and you can grant or revoke it any time from your device's Settings.

Call screening. To apply your rules before a call rings, LineLayer uses Android's built-in call-screening system. You turn this on once, from your device's settings, by making LineLayer your call-screening app. Android's call-screening role does not receive every private or hidden call, so LineLayer's rules apply to calls Android makes eligible for screening, not a guarantee of intercepting every restricted or unknown call — see "Private and hidden calls" below.

Reported activity (on-device). LineLayer can check whether an incoming number has FTC-reported activity, using a snapshot dataset bundled with the app and refreshed through app updates — this check runs entirely on your device, without a live network lookup. It's separate from your contacts and does not upload your contacts, allow list, block list, call history, or settings. Smart Protection, a LineLayer Pro feature, can use this same on-device check to automatically handle calls with strong reported-activity matches. A report is context, not proof — caller ID can be spoofed, coverage varies, and the FTC does not verify who made a call. See the LineLayer FAQ for more on Smart Protection.

Purchases (LineLayer Pro). If you subscribe to LineLayer Pro, the purchase is handled entirely by Google Play's billing system. LineLayer never receives or stores your payment-card or bank details — that information is handled directly by Google, under Google's own Privacy Policy. LineLayer's code communicates only with Google's Play Billing library to start a purchase and confirm it completed; it does not log or store the purchase token itself, or any other purchase or transaction detail. The app only keeps a single true/false flag on your device recording whether your Pro subscription is currently active, used to unlock Pro features like Smart Protection. There's no EnkiDev backend server that independently verifies or re-checks this.

What's stored on your device

Everything LineLayer stores lives in the app's own private storage on your device, using Android's standard per-app storage sandbox — nothing described here is stored anywhere else. This includes: your allow list and block list (phone numbers only, no names); a record of incoming calls the app has screened (the number, when it happened, and which rule applied); your protection settings (which rules are turned on, your selected home country for country-based rules, your app language, temporary "Expected Call Mode" state, and similar preferences); and the single flag recording whether your LineLayer Pro subscription is currently active. None of it is copied anywhere else on your device, and none of it is transmitted off your device except as described in "Data transmission and sharing" below.

How LineLayer uses this information

LineLayer uses each type of data only for the feature it supports: your contacts, to recognize numbers you've already saved and apply your "not in contacts" rule; call information, to decide whether an eligible incoming call is allowed through and to show you why in your call history; reported-activity data, to show public report context for a number and, for LineLayer Pro subscribers, to let Smart Protection automatically handle strong matches; and your subscription status, to unlock the LineLayer Pro features you've paid for. LineLayer does not use this data for advertising, profiling, or any purpose beyond the feature it belongs to.

Data transmission and sharing

LineLayer does not transmit your contacts, LineLayer call history, allow list, block list, or protection settings to an EnkiDev server. EnkiDev does not operate a backend that receives this data, and none of it is sent to Google Play Billing either.

Separately, LineLayer Pro purchases are processed by Google Play. When you subscribe, Google Play — not LineLayer — collects the payment information needed to complete the purchase, under Google's own Privacy Policy (see "Third-party services" below). LineLayer's code only talks to Google's Play Billing library to start a purchase and confirm your subscription status; it never receives your payment-card or bank details, and it does not send your contacts, call history, or any other app data as part of that process.

Reported-activity checks, including Smart Protection, run against a snapshot bundled with the app and never involve a network request, so nothing is sent anywhere for those checks either.

Analytics, advertising, and telemetry

LineLayer does not include analytics, advertising, or crash-reporting software of any kind. LineLayer's own code does not access the Advertising ID, Android ID, IMEI, IMSI, or send usage statistics or diagnostic data to EnkiDev. Google Play Billing, described below, is Google's own platform code and may separately process purchase, account, or device information as part of operating the Play Store and Play Billing — that processing happens under Google's own Privacy Policy, independent of anything LineLayer's code does or can see.

Data security

LineLayer's local data — your allow list, block list, call history, and settings — is stored using Android's standard private app storage, which the operating system keeps isolated from other apps on your device without special permissions. Contacts access uses Android's runtime permission system: it's off until you grant it, and you can revoke it at any time from your device's Settings. LineLayer does not publish or expose these local databases to other apps. Because none of this data is transmitted off your device, there is no separate "data in transit" question for it; the LineLayer Pro purchase flow is handled by Google Play's own secure billing infrastructure.

Backup, deletion, and uninstalling

You can remove any number from your allow or block list at any time, and clear part or all of your call history from within the app. Android's automatic cloud backup is turned off for LineLayer, so this local data isn't included in device backups. Clearing LineLayer's storage from Settings, or uninstalling the app, permanently deletes everything described above on your device — it's the only copy LineLayer keeps, so there's nothing left anywhere else under EnkiDev's control. LineLayer does not have user accounts, so there is no LineLayer cloud account to delete. If you've subscribed to LineLayer Pro, Google Play separately retains your purchase and transaction records under Google's own policies, independent of anything stored locally by LineLayer — you can review or manage that through your Google Play account.

Private and hidden calls

Android's call-screening system — the mechanism LineLayer uses to apply your rules — does not pass every incoming call to screening apps. Calls presented as private, restricted, unknown, or from a payphone are not guaranteed to reach LineLayer before they ring, regardless of your settings. LineLayer's rules apply to the calls Android makes eligible for screening; this is a platform limitation, not something any call-screening app can override.

Reported activity data in the app and website

The LineLayer Android app's on-device reported-activity checks and Smart Protection use only a bundled snapshot of the FTC's Do Not Call reports — currently FTC data alone, not FCC data. LineLayer Learn's Reported Numbers lookup on this website is separate and draws on a broader public dataset — currently both the FTC's Do Not Call reports and the FCC's Consumer Complaints data. Neither dataset is collected from LineLayer app users; both come entirely from these public U.S. government sources, and neither is a crowdsourced reputation database built from anyone's calls or contacts. LineLayer and LineLayer Learn are not affiliated with, sponsored by, or endorsed by the FTC or the FCC.

A reported number or complaint is an unverified consumer report, not a finding. Neither agency verifies who made a call, and caller ID can be spoofed. LineLayer Learn republishes this data as-is and does not verify individual reports. Smart Protection, a LineLayer Pro feature, can use LineLayer's on-device FTC snapshot to automatically handle calls with strong matches, in addition to your own rules — presence in the data isn't proof that a number's owner did anything wrong. The on-page lookup and the downloadable CSV on the Reported Numbers page both cover FTC and FCC activity, with each source kept in its own column or entry — never summed into one total.

Third-party services

Google Play Billing is the only external service LineLayer uses — through the Google Play Billing library, solely to process LineLayer Pro subscription purchases and check their status. Google's handling of information related to your Google Play account and purchases is governed by Google's own Privacy Policy . The app also includes Google's libphonenumber library for local phone-number parsing; that library runs entirely on-device and does not perform network requests or send data anywhere. LineLayer does not integrate any advertising network, analytics provider, crash-reporting provider, or other third-party SDK, and has no EnkiDev backend of its own.

LineLayer Learn website privacy

This section covers the LineLayer Learn website (linelayerapp.com) specifically, separate from the Android app described above. LineLayer Learn's website code does not add analytics, tracking scripts, or cookies. The Reported Numbers lookup runs in your browser against static data files; the website does not submit the full phone number you enter to an application API. Some pages include a small amount of client-side JavaScript for interface behavior — such as a scroll-based guide on the homepage and a dismissible mobile install prompt — none of which collects, stores, or transmits any personal data. Google Play links from this website may include campaign/source parameters for attribution; the website's code does not append a user-specific identifier to those parameters, though they remain visible in the outbound URL. The Google Play Store you install LineLayer from operates under Google's own Privacy Policy, and Android system components may perform their own platform-level functions independent of any individual app's permissions.

Changes to this policy

This policy describes the currently published version of the LineLayer app, based on its actual implementation. If a future version changes what the app accesses or how it handles your data, this page will be updated to match.

Contact

Questions about this policy or how LineLayer handles your data? Contact [email protected].