Skip to content
Menu

CamRelay / Privacy

CamRelay Privacy Policy

How CamRelay handles device connections, recordings and local data.

Initial effective date
Last revised
Operator
Zhengkuan Wang
Privacy and support contact
service@damnvisible.com

1. What this policy covers

This policy describes the free initial version of CamRelay for iPhone and iPad, a product in the Damn series. CamRelay lets one device act as a Camera and another as a Monitor using a local connection. This version has no CamRelay account, advertisements, in-app purchases, subscriptions or third-party analytics or advertising SDKs.

2. Camera, microphone and recordings

CamRelay requests camera access when you use this device as a Camera. It requests microphone access when you enable live audio metering in the video viewfinder or start recording video with sound. Metering displays current levels and does not save a separate audio recording. If you decline microphone access, you can choose to record without sound. The Monitor does not automatically receive original photos or recorded videos.

New photos and videos are first saved in the Camera device's app storage. CamRelay attempts to add completed recordings to that device's system Photos library. Once that save is confirmed and its receipt is stored, CamRelay removes the app's temporary original. If saving to Photos fails or permission is denied, the app keeps the original for retry in Recovery Files. Do not delete the app while it contains recordings you have not saved elsewhere.

CamRelay does not upload recordings to the operator or a CamRelay server. During a paired session it sends a live video preview directly to the connected Monitor. Anyone who can see that Monitor's screen can see the preview. Use pairing only with devices and people you trust, and obtain any permissions needed to record others.

3. Photos library access and sharing

Adding captures to Photos and browsing Photos are separate permission requests. Browsing access is requested when you open the gallery. The gallery displays photos and videos that you allow CamRelay to access, including existing items not created with CamRelay. You can use limited Photos access and change the selection in system settings.

When you view, play or export a Photos item whose original is in iCloud, Apple's Photos services may download it over the internet. CamRelay may create a local temporary copy for a share or export operation. CamRelay attempts to delete its temporary export files when the share sheet closes. If sharing ends abnormally or cleanup fails, a temporary file may remain until the system clears temporary storage or the app is deleted; the app does not currently offer a separate temporary-export deletion control.

Sharing happens when you choose a destination in the system share sheet. The selected app, service or person then receives the item, which may include metadata already present in the original, such as its capture date or location. Their handling of the item is governed by their own practices. CamRelay does not request location permission.

4. Nearby discovery and device connections

CamRelay uses Apple's local networking and Bonjour services to discover nearby devices and establish a connection over a shared local Wi-Fi network or supported Apple peer-to-peer Wi-Fi. Local network permission is needed for discovery and communication. This capture and control path does not require a CamRelay cloud service.

Before pairing, CamRelay advertises your chosen device nickname, discovery service information and the device's public hardware model code (such as iPhone16,2) to nearby devices through Bonjour. The code is used to display the specific device model, such as iPhone 15 Pro Max; it is not a serial number or UDID. Do not put private information in the nickname. Neither the nickname nor the advertised model proves device identity. Initial pairing uses a four-digit code; subsequent remembered connections verify device identity. Authenticated sessions use encrypted control and preview channels.

Connected devices exchange information required to operate the session: roles, supported capture settings, recording and saving state, control commands and results, and Camera battery level, charging state and scalar live audio levels for display. They also exchange public device identity information to authenticate and remember each other. Network addresses are necessarily used to make the direct connection. This information is processed by the participating devices, rather than sent to the operator. Live levels contain limited scalars rather than audio samples and are not kept in diagnostic history.

The Camera checks available storage for safe saving and displays an estimated remaining recording duration for the current video settings. This is not a recording-time guarantee. Before first sharing with an authenticated, trusted Monitor, the Camera asks you to explicitly confirm that you operate both devices and allow sharing in future authenticated local connections with that Monitor. The Camera remembers your choice: allowing enables automatic sharing on later authenticated reconnections; declining still allows full capture and does not cause repeated prompts. Disconnecting or backgrounding ends the current transmission without erasing that choice. Each device acting as Camera needs its own permission; it does not authorize another Camera, and new devices or changed identity keys do not inherit permission. To revoke it, choose Forget for that trusted device in the Camera’s Settings. The estimate is not shared over the internet. This additional permission concerns the derived estimate; the battery, charging and audio-level status described above is part of the paired session.

Raw capacity values, detailed capture diagnostics and free-text capture notices are not sent to the Monitor. If a Camera operation fails, the Monitor shows a general failure message and asks you to check the Camera for details.

5. Local settings and remembered devices

In the professional capture interface, you can choose a `.cube` LUT through the system file picker. CamRelay stores the selected file, its display name and your declared input color encoding on that device for live preview display. CamRelay does not bake the LUT into original photos or recordings, transmit the LUT to the other device, or upload it to the operator. Camera and Monitor manage their LUTs independently. You can disable or delete imported LUTs in professional settings. The local library holds at most 20 files, each up to 16 MB. If you choose a file from iCloud Drive or another file service, the system file provider may download it over the internet in response to your action; that service's practices apply.

CamRelay stores the nickname, pairing rate-limit state and app preferences, including your language choice, locally on that device. The language preference is not sent to the operator or the connected device. CamRelay stores its device identity and remembered-device records in Apple’s Keychain. Remembered-device records include a public identity key, nickname, pairing or connection dates, and the choice to allow or decline sharing the recording-time estimate from this Camera to that Monitor. Both choices are stored against the peer’s actual public identity key and removed when you Forget that device; an older record without a choice does not mean permission was granted. These Keychain items are configured for this device and are not configured for iCloud Keychain synchronization.

You can remove a remembered device in Settings by choosing Forget. Do this on both devices if you want both to forget the relationship. Removing a remembered-device record does not reset the app's own device identity. Keychain items may survive app deletion; deleting the app alone should not be relied on to remove remembered relationships.

6. Local technical diagnostics

CamRelay keeps technical diagnostics locally to help investigate connection, capture and performance problems. They include timestamps, app and protocol versions, random session, command or media identifiers, authentication mode, connection results, capture settings, recording and save state, and performance measurements such as preview timing, device/system information, thermal state and battery level.

The diagnostics record technical metadata, rather than photo, video or audio contents, pairing codes or secret keys. Device labels and free-text capture notices are removed from persisted session snapshots. They are not automatically uploaded to the operator. There is a latest snapshot, up to 20 recent session records and up to 256 performance-session records; older history is pruned as new sessions are recorded. Pairing and disconnection summaries are also kept locally.

If you choose to send a report, screenshot or recording to support, review it first and remove information you do not want to share. Files you send may contain personal information even when the app's technical report does not contain media.

7. Apple services, other apps and backups

Apple provides system permissions, Photos, Keychain, operating-system diagnostics and App Store distribution. Photos synchronization, device backups, Apple's diagnostic sharing and internet use by other apps depend on your system settings and those services' policies. CamRelay does not operate those services or receive their contents automatically. Local app files may be included in a device backup according to your backup settings.

CamRelay uses Apple's open-source Swift Crypto, including its packaged cryptographic dependencies, for local authentication. These libraries are not advertising or analytics services. Their license notices are bundled with the app. CamRelay's product, policy and support pages are publicly available on DamnBase without a DamnBase account. The app does not automatically load these webpages.

The public CamRelay webpages are served through Vercel. Opening a webpage sends request information, such as your IP address, requested URL, time and browser information, to the website infrastructure needed to deliver that page. Vercel's data handling is described in its privacy notice: https://vercel.com/legal/privacy-notice. This website activity is separate from the app's direct local capture connection. The support-email deletion period below does not establish a retention period for website or hosting-provider logs and backups. If you follow links to other DamnBase products or Account Center, their own data handling applies.

8. Retention and your choices

You can stop a session, change permissions in system settings, change the advertised nickname and forget remembered devices. Manage or delete items saved in Photos using the system Photos app. Deleting an item from Photos does not automatically delete an unsaved recovery copy still held by CamRelay. CamRelay currently has no in-app control to delete recovery originals; save any needed files before removing app storage by deleting the app.

Deleting the app normally removes its local recordings, preferences, temporary files and diagnostics from that installation. It does not delete items already saved to Photos, copies shared elsewhere, existing backups or Keychain records. Deleting those copies requires the controls provided by the relevant system or service.

9. Contact and policy updates

For privacy questions or support, contact service@damnvisible.com. If you contact us, we receive the address, message and attachments that you choose to send through your email provider. We use that correspondence to handle your request. We do not automatically receive your recordings or app diagnostics. We use Alibaba Cloud (Aliyun) for our support mailbox. We delete the support emails and attachments we manage within 90 days after your issue is resolved; you may contact us to request earlier deletion. This period applies to our support correspondence, not to independently retained provider security logs or backups, which are governed by the provider’s practices.

If data handling changes, we will update this policy and its effective date. New functionality that changes data handling, including any future paid version, requires a corresponding policy review before release.

Contact CamRelay

service@damnvisible.com Return to support