Privacy Policy

Promptside · Effective date: September 14, 2026 · Last updated: November 14, 2026

Promptside (bundle identifier xyz.bogtsi.promptside) is made by Bogdan Tsiganiuk, an individual developer. Contact: bogdan.tsiganiyk@gmail.com.

The short version: Promptside has no account or sign-in. Your scripts, folders, settings, rehearsal history and recorded audio/video are processed locally, not uploaded as part of purchase management or app updates. Apple processes purchases, RevenueCat receives purchase information and an anonymous app user ID to manage Promptside Pro, and Expo receives technical information when the app checks for and downloads software updates. Files you export or share, system backups, and messages you send to support are separate disclosures described below.

Purchase information and support messages

Promptside uses RevenueCat to manage purchases and Pro access. The SDK creates an anonymous app user ID; the app does not supply your name, email address or a custom account ID. RevenueCat processes that ID, purchase receipts and transaction/purchase history, including subscription and entitlement status, to validate purchases, restore access and provide purchase reporting and analytics. The SDK can communicate with RevenueCat when the app checks access or loads purchase options, not only when you buy something. Apple handles payment; we do not receive your payment-card details.

RevenueCat does not receive your script text or recorded audio/video from Promptside. See RevenueCat's privacy policy and Apple's privacy policy for their handling of purchase information.

If you email support, we receive your email address and whatever you choose to include, and use that information to respond to your request. Please do not send scripts, recordings, payment-card details or other sensitive information unless it is necessary for the issue you want help with.

App updates through Expo

Promptside uses Expo's hosted update service at u.expo.dev to check for compatible app-code and asset updates when the app launches. When an update is available, the app can download it in the background and use it on a subsequent launch. These requests can happen without a purchase or any action to share your content.

Update requests include the app's Expo project ID, platform, runtime version (based on the app version), and a technical installation identifier sent as EAS-Client-ID, along with identifiers for the current or embedded update. The installation ID is a randomly generated UUID saved on the device and reused across requests; it is not generated from your account or a hardware identifier. Update recovery can also send recent failed-update identifiers and technical launch-error information. Like other HTTPS services, Expo and its delivery infrastructure receive the network request, including its source IP address.

Expo processes update-request records to deliver compatible updates, manage rollouts, report update installations and failures, and measure service usage, including installation-based usage for billing. A random installation ID still identifies an app installation; it is not a claim that no data is collected. This update information is distinct from your local script text and recorded media, which the update flow does not upload. See Expo's privacy policy and Expo's update privacy disclosure for its data handling.

What stays on your device

This content is written to your device's local app storage using on-device storage and file-system APIs, not a cloud database operated by us. Deleting the app removes its local data, but does not delete copies in Photos, exported files, system backups or purchase records held by Apple and RevenueCat.

Camera, microphone and Photos

Camera and microphone access are used in Record mode (Promptside Pro), not for ordinary script reading. When access is missing, Record mode shows an explanation; tapping Grant access requests camera and microphone permission. If iOS will no longer ask, the card offers Open Settings instead. After camera access is granted, the camera preview can be active while Record mode is open, before you start a take. Starting a recording captures video and audio into a local file; Promptside does not upload it, and the scrolling script overlay is not embedded in the video. The app stops an active recording when it goes into the background.

Promptside asks to add to your Photos library only when you tap Save to Photos on a finished take. That permission is add-only — Promptside never reads your existing photo or video library back, and never asks to.

Sharing, backups and other disclosures

  1. You export a file. Export backup in Preferences → Data builds a JSON file containing scripts, folders, settings, rehearsal history and take metadata, then opens the iOS share sheet. It does not contain the recorded video files. Script export also uses the system share sheet. The destination you choose, such as Files, iCloud Drive, Mail or another app, handles that copy under its own terms; we receive no copy.
  2. You share or save a take. Tapping Share on a recorded take opens the iOS share sheet the same way; tapping Save to Photos writes the file to your Photos library through Apple's own API.
  3. System backup and Photos services. If you enable iCloud Backup or iCloud Photos, Apple may store eligible app data or videos you save to Photos under your device settings and Apple's terms. Cached take files are not a reliable backup. Promptside does not implement its own cloud sync.
  4. Purchase services. Apple and RevenueCat process the purchase-related data described above, including when you restore purchases or the app checks Pro status.
  5. App-update services. Expo receives the technical update and network information described above when the app checks for or downloads software updates.
  6. Support and external links. Sending email shares the information you include with us and your email provider. Opening a web link uses your browser and the destination site's own privacy practices.

Children

Promptside is not directed at children. We do not ask for a date of birth or knowingly request personal information from children. If you believe a child has sent personal information to support, contact us so we can address it.

Your rights

You can export your local scripts and settings through Preferences → Data → Export backup, and delete local content in the app or by deleting the app. Keep separate copies of recordings you want to retain. Copies you save or share must be managed at their destinations. Deleting the app does not cancel a subscription or erase Apple or RevenueCat purchase records. For questions about support correspondence or purchase-related data, or to request access, correction or deletion where applicable, email bogdan.tsiganiyk@gmail.com. We may need enough information to locate the relevant record; legal and purchase-record retention requirements may apply.

Changes

If this policy changes, the date at the top changes with it, and Preferences → Support & legal links to the current one.