LEGAL

Privacy Policy

Effective September 13, 2026

Effective date: September 13, 2026
Application IDs: com.cisr.app and com.cisr.iphone
Cisr privacy contact
Privacy contact: [email protected]

This policy describes the current supported Cisr releases, including TestFlight and internal test builds; older store versions may offer fewer features. This Privacy Policy explains how the Cisr phone and watch applications handle information when you enable their supported features. Features differ between Android, Wear OS, iPhone and Apple Watch releases. Cisr does not require a Cisr account or operate a cloud relay for notification content, media information, call controls or health data. Connections use Bluetooth and, for the paired Android companion, Google Play services. Google may route encrypted transfers through its servers; this is not a Bluetooth-only service.

1. What Cisr does

The Wear OS app can connect to an iPhone to show selected notifications, control supported media playback, provide supported call controls and transfer supported watch health values to the iPhone app. The Android phone app also supports explicitly enabled notification forwarding from the watch's existing Android companion, local media controls and an optional view of the latest watch health values.

The current two-phone feature lets one supported Wear OS watch receive notifications from an iPhone and its existing paired Android companion. Each source is registered separately. Cisr-rendered notifications can identify their source phone; native watch-companion notifications use the operating system’s presentation. This does not establish two native operating-system pairings or provide the same feature set for both phones. This feature is not currently offered for an Apple Watch receiving Android notifications.

2. Device and Bluetooth information

Cisr uses Bluetooth and supported companion-device services to discover, connect and reconnect compatible devices. It stores selected device names, Bluetooth addresses or companion node identifiers, connection preferences and enrollment state locally. These identify the authorized source and support reconnection. Connection checks exchange identifiers, request tokens, availability and enabled-feature status. Device names and radio identifiers are not automatically uploaded to a Cisr-operated server. Subscription verification and user-submitted support reports are separate and described below.

Phone and watch battery percentages and connection/registration status are exchanged through the watch so supported enrolled phones can display the same device roster. A cached roster can remain during a temporary disconnection. A phone removed from the watch cannot receive later roster updates until it is added again. Battery values can be unavailable or stale; an indicator is not a delivery guarantee.

3. Notifications

With the user's permission, the Wear OS app can receive selected iPhone notification information through Apple's Bluetooth notification service. Depending on the notification and the user's settings, this may include the source application, title or sender, and message preview. Notification information is processed on the user's devices to display and manage the notification. It is not uploaded to a Cisr-operated server. The user can disable notification mirroring, message previews, vibration, or individual applications in Cisr settings.

With Android Notification Access granted, Cisr reads eligible notifications and forwards their application identifier/name, sender/title, text, timing and supported actions from the enrolled Android phone to the Wear OS watch through Google Play services. Where a notification supplies an image, Cisr can transfer a reduced image for display on the watch. It does not browse the phone gallery or provide manual photo/video sending. iPhone ANCS does not provide other apps’ photo/video attachments to Cisr; video playback is not implemented.

Cisr settings control forwarding, previews, vibration and individual applications, including enable-all/disable-all. Android’s application chooser can include installed apps; the iPhone chooser is based on applications observed through the watch, not an inventory of all installed iPhone apps. These app lists are handled locally. Native watch-companion notification delivery may also operate separately; its settings and behavior are controlled by the platform/manufacturer.

Where a supported notification offers a reply action, the text you enter is sent back to the source phone/application to perform that action. Availability differs by platform and source app. Cisr does not provide a universal reply capability. Notification image data and live action handles are used locally for current display/actions, not sent to the support or subscription server automatically.

Cisr’s Wear OS Today’s Inbox stores an encrypted local daily notification history, including source phone, source app, title and permitted preview. Phone Inbox screens request pages from that watch; these can include notifications originally received on the other enrolled phone. Only pair devices you are authorized to share this information with. Phone Inbox pages are held in memory, not a separate persistent phone archive. Privacy settings are applied to the page shown. Inbox is not a complete backup or delivery record. Apple Watch does not expose other apps’ notification history to this Cisr Inbox.

4. Media controls

When supported by the iPhone and media application, Cisr can receive playback status, track title, artist name, and player name through Apple's Bluetooth media service. Cisr can send previous, play/pause, and next commands. Cisr does not access or upload the audio content itself, and media information is not uploaded to a Cisr-operated server.

With Android Notification Access enabled, the Android phone app can read active media-session metadata and send playback commands to a supported player on that same phone. Compatible newer Cisr phone and watch releases also exchange supported media metadata and controls through the enrolled Android companion connection. Notification Access, an enabled media setting and a compatible active player are required. Media metadata is used for the current interface, not a listening-history archive.

5. Call controls

When supported by the iPhone, Cisr can show an incoming-call notification and send answer, decline, or end-call actions from the watch. Cisr does not route call audio to the watch, access the call microphone or speaker stream, record calls, or upload call audio. Caller information shown in a notification is handled in the same way as other notification information.

6. Health and fitness data

With the user's permission, the Wear OS app can access heart-rate measurements and daily step counts provided by Wear OS Health Services. The latest health values and update time may be stored locally on the watch to show current information and maintain the daily step total.

The Wear OS app can send heart rate, step count, and measurement time directly to the Cisr iPhone app over a paired Bluetooth connection. The health-transfer characteristic requires Bluetooth link encryption. With separate Apple Health permission from the user, the iPhone app can save supported heart-rate and step samples to Apple Health. Cisr may store limited local state on the iPhone, such as the last transferred daily step total and date, to avoid duplicate step entries.

The Cisr developer does not receive or store health or fitness data on a Cisr-operated server. Health data is not used for advertising, marketing, profiling, or sale. Users can revoke health permissions at any time in the device settings or Apple Health settings.

If you enable the Android app's watch-health view, it requests the latest available heart rate, daily steps and update time from the enrolled watch while the phone interface is active. These values are held in memory for display and travel through Google Play services as described below. The current Android app does not write to Health Connect or maintain a background health archive. Turning this view off stops its requests; watch sensor permissions and iPhone health-transfer choices are managed separately.

Cisr is intended only for general wellness and fitness purposes. It is not a medical device, does not provide medical advice, diagnosis, treatment, or emergency monitoring, and should not be relied on for urgent or clinical decisions.

On Apple Watch, Cisr requests HealthKit read permission for the latest available heart rate and today’s steps and displays those values locally. This is separate from the Wear OS-to-iPhone health writing path. Its paired-iPhone control, battery, Find phone and subscription state use Apple WatchConnectivity; this does not provide an Android second-phone channel or access to other apps’ notification history.

7. Data not automatically collected by the developer

The feature relay does not automatically upload the following to a Cisr-operated server. Information you choose to type into a support report is an exception and is handled as support correspondence:

  • A mandatory Cisr account/profile (support does request a reply email)
  • Notification content
  • Media titles, artist names, player information, or audio content
  • Call audio
  • Heart rate or step data
  • Precise location
  • Advertising identifiers
  • Automatic analytics or crash-reporting feeds (limited user-submitted support diagnostics are described below)
  • Payment-card or bank-account credentials (purchases are handled by the app store)

Cisr does not sell personal information and does not use third-party advertising SDKs in the current release.

Find phone

On supported paired devices, Find phone sends a request identifier and command to make the target phone play an alert, and returns an acknowledgment/status. It does not locate the phone by GPS or upload a location. Sound and background availability depend on device settings and platform permissions. This is separate from device-discovery controls labelled Find phone during setup.

8. Permissions

Depending on the device and operating-system version, Cisr may request:

  • Nearby devices and Bluetooth permissions for discovery, pairing, connection, and data transfer
  • Notification permission to show connection, mirrored notification, call, media, and health status on the watch
  • Android Notification Access to read eligible phone notifications for forwarding and access supported active media sessions; this is separate from permission to display notifications
  • Foreground-service or background-operation permission to maintain the Bluetooth connection and supported health updates
  • Physical activity or step permissions for daily step data
  • Body sensor or heart-rate permissions for heart-rate measurements
  • Background health-data permission for permitted health updates while the watch app is not in the foreground
  • Location permission on older Android versions where the operating system requires it for Bluetooth scanning
  • Apple Health permission on iPhone to save supported heart-rate and step samples, and HealthKit read permission on Apple Watch to show supported values

The user can deny or revoke permissions in device settings, but the related feature may then stop working.

9. Platform services

Cisr relies on operating-system and platform services supplied by Google, Samsung, and Apple, including Google Play, Wear OS Health Services, Bluetooth services, Apple Notification Center Service, Apple Media Service, and Apple Health. Those providers may process information under their own privacy policies independently of Cisr.

The paired Android connection uses the Wear OS Data Layer in Google Play services. Transfers can use Bluetooth or a network route through Google servers, depending on available connections. Google documents end-to-end encryption for cloud-routed Data Layer transfers. Nearby-device checks do not guarantee Bluetooth-only delivery. Platform processing may occur outside your country and is subject to the provider's practices and applicable safeguards. See https://developer.android.com/training/wearables/data/overview and https://policies.google.com/privacy for further information.

10. Local storage and deletion

Connection preferences, notification settings, recent notification state, and limited health-transfer state may be stored locally on the user's devices. Users can remove this local Cisr data by clearing the app's storage or uninstalling Cisr. Health samples already saved to Apple Health can be viewed or deleted using Apple Health controls.

The daily watch Inbox is stored in the app’s no-backup directory using Android Keystore-backed AES-GCM encryption. Entries from another calendar day are deleted on the next Inbox read/write; deletion is not guaranteed to run exactly at midnight if the app is inactive. Clear Today deletes that shared daily archive for subsequent watch/phone reads, not the original phone notifications. Live notification details and image/action state have a separate display lifecycle. Clearing app storage or uninstalling removes local app storage; offline phone views may remain until refreshed or closed. Cisr does not keep a server-side copy. Subscription records are separate from notification content and are described below. Requests concerning data controlled by the developer can be sent to the privacy contact above.

On the watch, tap a phone to manage that source. Disconnect pauses its Cisr connection but keeps the registration. Remove phone asks for confirmation, clears that source's Cisr registration on the watch and removes its mirrored alerts; adding it again requires setup. It does not remove the operating system's Bluetooth pairing, delete original phone notifications, revoke phone permissions or erase health samples already saved elsewhere. An offline phone may not immediately receive the pause request, although the watch stops accepting that removed source. Manage the other device's Cisr settings and system permissions separately when needed.

Support reports are not erased by uninstalling the app; see the support section. Removing a phone removes its registration and mirrored alerts, but should not be treated as a guaranteed purge of the separate daily Inbox: use Clear Today for that archive.

11. Legal basis and user choices

Where the GDPR, UK GDPR, KVKK, or similar laws apply, Cisr processes device, notification, media, call, and health information only to provide features deliberately enabled by the user and on the basis applicable in the user's jurisdiction, including consent for health permissions where required and performance of the service requested by the user. Permissions are optional and may be withdrawn in device settings. Withdrawing a permission disables the related feature and does not affect processing that was lawful before withdrawal.

12. User rights

Depending on local law, users may have rights to request information about processing, access, correction, deletion, restriction, objection, portability, or withdrawal of consent, and to complain to a competent data-protection authority. Requests may be sent to [email protected]. Cisr will respond as required by applicable law and may need limited information to verify and complete a request.

13. Security

Cisr uses operating-system protections, app sandboxing, platform permission controls, paired Bluetooth security, and encrypted Bluetooth access for the health-transfer characteristic. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

14. Children's privacy

Cisr is not directed to children under 13, and the developer does not knowingly collect personal information from children through a Cisr-operated server.

15. Changes to this policy

This policy may be updated when Cisr's features, permissions, or data practices change. The effective date at the top of this page will be revised when an update is published.

16. Independent status and trademarks

Cisr is an independent application and is not affiliated with, sponsored by, endorsed by, or approved by Apple, Google, Samsung, or any device manufacturer. Product and trademark names are used only to describe compatibility. All trademarks belong to their respective owners.

17. Website and support correspondence

The public cisr.watch pages do not intentionally add advertising trackers or analytics SDKs and do not require a customer account. The support administration area has a separate staff login. The hosting service may process standard web-request information, such as IP address, request time, requested page and browser information, to serve and secure the site. This is separate from device-to-device app data. If you email support, the developer and email provider process your email address and the information you send to answer your request. Do not send passwords, private messages or health records. You may contact us about deletion of support correspondence, subject to applicable retention obligations.

18. Subscriptions and purchase verification

In versions with Premium purchasing, Apple App Store or Google Play processes the payment. Cisr uses RevenueCat to retrieve offers, verify purchases and determine subscription access. RevenueCat processes an automatically generated app user identifier, purchase receipts or purchase tokens, product and transaction identifiers, subscription status and relevant app, platform and technical request information. The developer can access subscription records through RevenueCat for service administration and support. An automatically generated identifier is not the same as fully anonymous data.

Cisr does not send notification contents, media titles or health values to RevenueCat. The subscription integration does not request a Cisr email login or send payment-card credentials to Cisr. Purchase verification requires network requests and is separate from device-to-device feature transfers. See https://www.revenuecat.com/privacy for RevenueCat's practices; processing may take place outside your country.

Subscription records may need to remain available to restore access, handle refunds, prevent fraud and meet legal obligations. Uninstalling Cisr does not cancel a store subscription or automatically delete store or subscription-provider records. Contact [email protected] about records administered by the developer; manage subscriptions through the store where you purchased. Mandatory retention requirements and the stores' independent records may limit deletion.

Premium sharing does not require an email or Cisr account. To share an active subscription through a compatible Wear OS watch, Cisr sends a pseudonymous watch public key, signed ownership challenges, store purchase proof and subscription identifiers to a Cisr-operated verification server. The server checks the purchase with Apple or Google, stores the purchase proof encrypted, and records its association with the watch and expiry. Phones and the watch exchange signed, short-lived access records; they do not exchange payment credentials. Test purchases and production purchases are verified in separate environments.

The verification server does not receive notification contents, media information, health values or the watch’s Bluetooth address. Its hosting provider processes network requests needed to serve and protect the service. Purchase records and the associated watch identifier are retained for restoration, subscription administration and fraud prevention; you can contact [email protected] to request deletion, subject to applicable retention obligations. Restoring on the purchasing platform can move the subscription association to a replacement watch. Existing signed access on the previous watch can remain valid for at most one hour.

Verification and subscription providers may process data outside your country. Cisr does not use these records for advertising or cross-app tracking.

19. Support reports, replies and service operations

When you choose Report an Issue, you submit an email address, your description and a limited diagnostic summary (app/OS versions, platform and connection/Premium status). Cisr does not automatically attach notification bodies, personal messages, health readings, purchase tokens, Bluetooth addresses or media files. Do not include passwords, payment details or sensitive message/health content in the free-text report.

The report and replies are stored in the Cisr support database hosted on Alibaba Cloud and viewed by authorized support staff in a protected admin panel. Staff replies and support notifications are sent through the support mail provider, GoDaddy; the sender/contact is [email protected]. The emailed private conversation link permits access to that ticket: do not share it unless you intend to share the conversation. Replies through that link appear in the same ticket. Ordinary replies sent directly to the mailbox are not automatically imported into the ticket history.

Support records include email, correspondence, diagnostic summary, ticket state/timestamps and mail-delivery records. They remain until removed following a request or a support-retention review; the current service does not implement an automatic ticket-expiry period. Operational backups rotate through 14 daily copies; deleted records may remain in a backup until it rotates out. Contact [email protected] for access/correction/deletion requests, subject to applicable obligations. Email-provider copies and records are also subject to that provider’s retention practices.

The website, support and verification hosting providers process network/operational information needed to deliver and secure requests. Support rate limiting uses the request IP for short-lived counters. Admin access uses authentication/session cookies; a private ticket link is an access credential. These services are separate from the notification/health relay, and providers may process information outside your country. Support processing is for handling the request and service security, with applicable legal bases including the requested service and legitimate security interests where permitted.

20. Contact

Cisr privacy contact
Email: [email protected]