Privacy Policy for Secure PC Keyboard | Cibru

Privacy Policy - Secure PC Keyboard # Privacy Policy Effective date: October 20, 2026 · Version 4.0 > **Privacy summary:** Keyboard, pointer and game-controller input are processed on your Android device and sent to the computer you choose. Clipboard text can also pass between that computer and your phone. This is not an entirely on-device service. CIBRU's billing and referral backend does not receive your typing or clipboard content. The free tier uses Google Mobile Ads; optional paid purchases use online verification, and optional referral rewards use Supabase, Google Play Install Referrer and Play Integrity as described below. ## 1. Who operates the app Secure PC Keyboard is operated by CIBRU (sole proprietorship owned and operated by Krishna moni Borah). Privacy and deletion requests: support@cibru.in. **Postal Address:** Kakojan, Jorhat, Assam - 785107, India. ## 2. Data the app processes - **Input and type-bar content:** Text, key combinations, pointer actions, controller inputs and supported device-motion readings are used to create input for your selected PC. The type-bar preview and undo/redo history are held in memory rather than a persistent typing-history database, and are cleared when the main keyboard screen stops or you clear the type bar. Custom key labels, shortcuts, presets, recent emoji and settings can be retained in local app storage until removed or app storage is cleared. The PC and the applications receiving input may retain what you send. - **Clipboard:** **Clipboard Sync with PC is enabled by default.** With an authenticated companion connection, changes to plain-text Android clipboard content can be sent to the PC while the app is in the foreground; the companion can send plain text back to Android's clipboard. Copy, cut and paste actions can also use this connection. Turn the setting off under *Keyboard Preferences → PC Clipboard Sync* to stop automatic clipboard synchronization. Explicit emoji entry can still send your selected characters through the PC clipboard for pasting as chosen input. Receipt of PC clipboard text does not itself execute a paste command or insert it into the type bar. Automatic checks skip some suspected credentials, but are not a guarantee that all sensitive text will be recognized. The app clears its own labelled clipboard entries at relevant lifecycle boundaries; Android, the PC, clipboard history or another application may retain copies. - **Voice shortcut:** The microphone/voice key sends **Windows+H** to the selected PC to open Windows dictation. This app does not request Android microphone permission, record phone audio or run a speech-recognition SDK. Dictation uses the PC's microphone, Windows settings and any speech services enabled there; those providers' privacy terms apply. - **Connection information:** Bluetooth names and device addresses, local PC host/IP and port, pairing/authentication PINs, decoded QR connection details and trusted PC certificate fingerprints are processed to connect to and authenticate the selected computer. After companion authentication, the phone sends its device-model name to the PC for connection identification. These PC connection details are not submitted to the referral or billing backend. - **Camera:** Optional QR setup uses the camera and the bundled ZXing scanner to decode the PC companion's QR code on the phone. The app does not save or upload the camera images. The decoded host, port, PIN and certificate details are used for setup. - **Purchases:** Google Play handles payment details using your Play Store account. No separate CIBRU login or email registration is required. Play Billing supplies product IDs, purchase tokens, order information and purchase status when you purchase, restore, or the app automatically checks existing purchases at startup or resume. Unless purchase syncing is paused, completed purchases can be sent for online verification. A pending payment is displayed locally and is not submitted by the app for entitlement verification or used to unlock Premium. Verification and purchase-data deletion send the app/package ID, product ID, **purchase token**, action, request ID and Play Integrity token over HTTPS to our configured service. The Supabase-hosted service uses Google's Play Developer API and Integrity API to check eligibility, status, expiry and authenticity. Server purchase records can contain the purchase token itself, product, order number, state, expiry and verification time; they are not limited to hashes. Related queued billing jobs and replay/rate-limit records support ongoing verification and fraud prevention. No payment-card number is provided to CIBRU. - **Advertising and consent:** The free tier can request Google Mobile Ads (AdMob) when configured and Google's consent checks permit it. Google's Mobile Ads data disclosure describes processing of advertising identifiers, app-set and other applicable device/account identifiers, IP address, app/ad interactions and performance diagnostics for advertising, measurement and fraud prevention. IP addresses can be used to estimate a general location without Android location permission. Google and participating partners may also use permitted data for personalization. Google's User Messaging Platform checks consent status and presents a message when required; review **Ad privacy choices** when that option is offered. Verified Premium suppresses in-app ad requests and display, but consent checks or SDK initialization can still occur; it is not a promise that all Google processing stops. Billing and Integrity processing remain separate. - **Referral rewards (optional opt-in):** Rewards are disabled by default. An explicit enable/consent action on the rewards screen establishes or resumes an anonymous Supabase authentication session without an email sign-in. Registration sends the app identifier, **Android's app/device-scoped identifier** (`Settings.Secure.ANDROID_ID`), Install Referrer attribution (including the referrer string/referral code and installation/click timestamps), request ID and Play Integrity token over HTTPS. The Android identifier is transmitted to the service before it derives a keyed, app-scoped device hash for the installation ledger; it is not anonymized on the phone before transmission. The referral identifier is not an IMEI, hardware MAC address or advertising ID. The service also processes the anonymous user/profile identifier, session credentials, referral code, installation outcome, referral events/counts, reward expiry and sync/security timestamps. These records verify installations, attribute rewards, provide access and prevent duplicate claims. “Anonymous” means no separate email sign-in, not that these records cannot identify the same profile or installation. Typing, clipboard text, PC PINs and PC input traffic are not sent to this service. - **Sharing a referral:** Choosing *Share Invite Link* sends the invitation text and public referral link to the app or service you select in Android's share chooser. That service processes the shared content under its own terms; our app does not read your contacts to send invitations. ## 3. Purposes and recipients We process relevant data to deliver PC input and clipboard features, retain your settings, verify paid or referral access, show permitted ads, prevent abuse, handle support and comply with law. Recipients include: - the PC and companion you connect to, and the PC applications or operating-system services receiving your input; - Google Play for billing, restoration, Install Referrer and Play Integrity checks; - Google Mobile Ads, User Messaging Platform and participating ad partners for ad and consent processing; - our configured Supabase-hosted purchase verification service when you choose paid features, and referral/authentication service when you opt into rewards; and - CIBRU support when you email us or request assistance or deletion. Online service providers also receive connection metadata such as your IP address. We do not sell your keyboard or clipboard content or submit it as an ad-targeting payload. For Google's processing and controls, see How Google uses information from sites or apps that use its services and Google's Privacy Policy. Cloud providers may process relevant data outside your country under their service arrangements and applicable data-protection requirements. ## 4. Transfers and local protection Bluetooth HID reports go to the paired computer using Android's Bluetooth stack and pairing protections. The USB mode uses a companion connection through an ADB/USB bridge; the local-network mode uses the configured private/LAN address. Companion connections use TLS 1.3, a trusted certificate fingerprint and PIN-based challenge-response authentication. Bluetooth HID is not the same transport as this TLS connection. Verify first-pairing certificate prompts against your PC and protect your PIN. A foreground connection service can keep a connection open after the keyboard screen closes; use the app's disconnect control when you want to end the connection. Local app data is protected by Android app isolation. Pairing PINs, saved Bluetooth connection records, trusted certificate fingerprints, purchase entitlement records and referral/session records use Android Keystore-backed encrypted preferences. Ordinary settings, PC host/IP and port, custom shortcuts/presets and non-entitling consent or sync-pause markers are not all separately encrypted. If secure storage is unavailable, paid verification fails closed; freshly verified referral/session state may be held only in memory and lost when the process ends. An old unverified local access flag is not proof of entitlement. Do not treat every locally stored item as an encrypted vault. The manifest disables Android app backup and configured backup/device-transfer rules exclude sensitive purchase and referral preferences. Device-manufacturer transfer behavior and any copies you export are separate. No storage or transmission method is completely secure. ## 5. Retention, deletion and paused sync **Local data:** Saved preferences, connection details and local entitlement/session records remain until reset, removed, cleared by an app action or deleted through Android app storage controls. **Clear cache** removes temporary cache files, not saved preferences, purchase/referral records or sync-pause choices. Clearing storage or uninstalling removes app-private local data but does not erase the PC's input, clipboard history, companion configuration, Google records or backend records. See Data Deletion Instructions. **Purchase verification:** Records support active subscriptions and reconciliation. Confirming *Delete purchase verification data* in the Premium screen, where available, persistently pauses automatic purchase syncing on that installation and removes local paid access, then requests deletion of the locally known records. A failed or partial request is not proof of deletion; retry if available or contact support. Local identifiers needed to retry may remain after failure. Reopening the app or Premium screen or attempting a new purchase does not resume that pause. **Restore Purchases** explicitly resumes syncing and can recreate eligible verification records after successful verification. A reinstall or storage reset removes local pause choices, so take account of other installations that may still sync. Completed server purchase deletion removes the relevant purchase records and associated queued billing jobs. A one-way SHA-256 purchase-token marker is kept to suppress stale/background recreation and abuse, becoming eligible for cleanup 90 days after the later of deletion or subscription expiry. A fresh permitted restoration can remove that marker earlier when it recreates the purchase record. Replay-protection request records become eligible for cleanup after one day. Expired or revoked purchase records become eligible after the configured retention period (90 days after expiry by default); billing jobs marked dead become eligible after 30 days by default. Cleanup occurs when maintenance runs, not at a guaranteed hour. These are our backend records; Google's transaction records follow Google's policies. Deletion does not cancel payments or issue a refund. Cancel separately in Google Play subscriptions. See purchase deletion instructions for older or unavailable records and support requests. **Referral rewards:** Profiles and attribution records are kept to provide the program until deletion is completed. Confirmed Unsync/Turn Off Sync persistently disables referral sync and removes local reward status/access on that installation. It retains the anonymous session, registered-profile identifier and installation-attribution bookkeeping, including cached referrer details and install/click timestamps, for continuity and deletion requests. It does not delete server data or pause reward expiry. Only an explicit enable/resume choice restarts syncing; merely reopening the rewards screen does not. Clearing storage or reinstalling can lose the anonymous session and does not restore rewards. Request referral deletion through *Keyboard Preferences → Legal & Privacy → Data Deletion*, an in-app deletion action where offered, or support@cibru.in. The settings link opens instructions; viewing it or sending email is not an immediate deletion or a change to sync settings. After verified completion, this app's referral profile, its installation records and linked referral events are removed, including remaining rewards. A one-way device hash is retained for 90 days to prevent repeat reward claims and is then eligible for cleanup. A shared Supabase authentication identity and other apps' records are not automatically removed; ask support to review a wider request. See referral deletion instructions. ## 6. Permissions and bundled services - **Bluetooth/Nearby devices** (legacy Bluetooth permissions on older Android, Connect/Advertise on newer Android, and HID support): pair and act as a PC input device. - **Internet, network state and change network state:** companion sessions, connected-device foreground work, ads/consent, billing and optional online verification/referral features. These are not a request to upload all phone data. - **Camera:** optional QR scanning; **vibration:** optional haptic feedback. - **Notifications and foreground/connected-device service:** connection status and keeping Bluetooth or USB/LAN sessions active. The bundled SDKs also declare **wake-lock** support for their work. - **Google Play Billing and Install Referrer service access:** purchases/restoration and referral attribution. - **Advertising ID and Android ad-services permissions:** the Google Mobile Ads dependency declares `AD_ID`, `ACCESS_ADSERVICES_AD_ID`, `ACCESS_ADSERVICES_ATTRIBUTION` and `ACCESS_ADSERVICES_TOPICS`; availability and use depend on Android, Google services and your privacy choices. - **App-private receiver permission:** AndroidX adds a signature-protected permission for internal broadcasts; it does not grant access to your personal files. The app does not request Android microphone, contacts, location, calendar or shared storage/media permissions. This does not prevent Google's ad service from inferring a general location from the IP address as described above. Libraries include Google Play Billing, Mobile Ads, User Messaging Platform, Play Integrity, Install Referrer, ZXing for QR scanning, AndroidX encrypted preferences and OkHttp for network communication. Supabase is accessed through HTTPS APIs. A library being bundled does not by itself mean that an optional referral or purchase request has been made; the feature choices and sync-pause controls above govern those requests. ## 7. Your choices You can turn off **Clipboard Sync with PC**, disconnect a PC, deny optional camera or notification permission, avoid paid/referral features, clear local app storage and review **Ad privacy choices** in Keyboard Preferences when Google requires that option. Advertising options and availability vary by region and consent status. A valid paid subscription or referral reward suppresses in-app ads while access remains verified. Referral participation is separate from purchases and ads. Opening or closing its screen does not enable it. Explicit enabling saves your choice and starts registration/syncing; confirmed Unsync stops future local referral syncing and access until you explicitly resume. It does not cancel an independently valid paid subscription. For purchase cancellation, trial and refund details, see Subscriptions & Refunds. ## 8. Children The app is a general-audience utility and is not directed to children under 13 or the applicable minimum age in their country. If you believe a child has provided personal information to CIBRU, contact us so we can investigate and delete it where required. ## 9. Privacy requests and support Email support@cibru.in to request access, correction or deletion or raise a concern. Depending on applicable law, you may have rights to object to or restrict processing, receive a copy, withdraw consent or complain to a data-protection authority. We may need to verify authority and identify the relevant records. Withdrawing referral consent stops future sync; it does not erase data already collected. You can request deletion without reinstalling or purchasing the app. Support processes the email address, message and supporting information you choose to provide to handle your request. Correspondence is retained as needed to resolve the matter, document its outcome and meet applicable legal obligations. You can request deletion subject to those obligations. Do not send passwords, card details, PC PINs, session credentials or raw purchase tokens. A Google Play order number or referral code can help locate records but is not proof of ownership by itself. ## 10. Changes and contact We may update this policy when the app or legal requirements change. We post the revised date here and provide additional notice when required. Questions: support@cibru.in.

Privacy Policy. Respect for your autonomy.

Have questions about your personal data?