Privacy Policy
Last updated: August 9, 2026
Quick Summary
PodSetup is a local-first mobile studio assistant. Equipment, recording locations, setup notes, room photos, audio recordings, spectrograms, and generated guidance stay on your device unless you choose a feature that requires backend processing.
When you choose an AI assist, PodSetup asks before sending the setup details, room images, audio recordings or audio-derived analysis, and request metadata needed to generate the requested result. Product analytics and crash diagnostics do not include your recording content.
What PodSetup Does
PodSetup is an Infral Labs LLC app that helps podcasters and creators manage equipment, save recording locations, plan setups, scan gear, capture room photos, record short audio samples, and receive practical recording recommendations.
This policy explains what the PodSetup iOS app and backend service collect, how AI assists are processed, what stays on your device, how subscriptions and quotas work, and how analytics and diagnostics are handled.
Setup Inputs You Choose To Analyze
You may create equipment records, location names, setup notes, setup checklists, cable routing guidance, equipment positions, camera photos of gear or rooms, and short audio samples for acoustic review.
When you use AI equipment scanning, room photo analysis, setup recommendations, or audio analysis, PodSetup may send the required photo, audio recording, audio-derived data, setup context, service identifiers, and request metadata over HTTPS to the PodSetup Railway AI backend.
Before PodSetup sends setup content for AI processing, the app asks for consent. You can reset that choice in Settings by choosing to ask again before the next AI assist. If you do not want a particular setup input sent for AI processing, do not use an AI assist for that input.
Local Data On Your Device
PodSetup stores structured app data locally using SwiftData. Photos, audio recordings, spectrogram images, generated setup guidance, media paths, onboarding state, AI consent state, and other larger media files are stored locally using FileManager paths and app preferences.
Deleting local app data from Settings clears local SwiftData records, local media files, AI consent state, subscription usage counters, and onboarding state. It does not cancel subscriptions, change real App Store entitlement state, or automatically erase backend quota, entitlement, rate-limit, or service-protection records.
AI Processing
The iOS app does not call OpenAI or any model provider directly and does not contain private model provider API keys. The Railway backend may process requests with OpenAI or another configured model provider solely to generate the requested app result.
Each backend AI result counts as one Pro AI assist. This includes equipment scanning, equipment-library matching, setup recommendations, room-photo acoustic recommendations, and audio analysis guidance.
Acoustic analysis is practical recording guidance, not calibrated lab-grade measurement. PodSetup does not provide true RT60 measurements or absolute SPL values. Scores, settings, and recommendations are starting points for improving podcast and creator recordings.
Anonymous Service Profile And Usage Records
PodSetup does not require a sign-in or named user account. When PodSetup connects to the Railway backend, it creates or refreshes an anonymous service profile so the backend can authorize AI requests, enforce free and Pro usage limits, prevent abuse, and keep subscription access working across service sessions.
This service profile uses random technical identifiers, including a generated service subject ID, quota principal ID, quota credential, access tokens, refresh tokens, and App Attest proof values used to confirm requests come from an authentic PodSetup app. PodSetup stores service tokens, the quota credential, and App Attest key references in the iOS Keychain.
The Railway backend stores hashed credentials, refresh-session records, subscription entitlement snapshots, entitlement lookup times, subscription expiration status when available, AI-assist quota usage, and AI-assist reservations in Railway Postgres, and uses Redis for short-window rate limits.
The backend may use request metadata such as IP address, platform, app version, build channel, subscription tier, service-session timestamps, and Railway operational logs to operate sessions, troubleshoot reliability, protect the service from abuse, and enforce rate limits. These records are not used for advertising or tracking across other companies' apps or websites.
Product Analytics
PodSetup uses TelemetryDeck for privacy-focused product analytics so Infral Labs can understand which parts of the app are used, where people need help, and whether the app is working as expected.
TelemetryDeck receives limited behavior signals, such as app sessions, onboarding progress, paywall views, purchase-flow outcomes, settings opens, AI consent changes, and whether an AI feature completed or failed. These signals may include a privacy-preserving installation identifier, session identifier, rounded timestamp, app version and build, build channel, device model, operating system version, language or region, screen characteristics, and similar technical context added by the TelemetryDeck SDK.
PodSetup does not send equipment names, location names, setup notes, photos, audio recordings, spectrograms, generated setup guidance, service profile identifiers, access tokens, refresh tokens, quota credentials, App Attest proof values, support-message content, or other user-provided recording content to TelemetryDeck. PodSetup does not use TelemetryDeck for advertising or tracking you across other companies' apps or websites. It also does not use TelemetryDeck for replay, screen recording, or keystroke recording.
Crash And Error Diagnostics
PodSetup uses Sentry for crash reports, serious app hang reports, watchdog termination diagnostics, and limited non-fatal error diagnostics so Infral Labs can find and fix app stability problems. Sentry may receive diagnostic details such as a stack trace, app version and build, build channel, timestamp, operating system version, device model, session status, and technical event identifiers.
PodSetup configures Sentry without default personal information, user identity, screenshots, view hierarchy capture, session replay, profiling, performance tracing, logs, metrics, network failed-request capture, or network URL/header breadcrumbs.
PodSetup does not send equipment names, location names, setup notes, photos, audio recordings, spectrograms, generated setup guidance, service profile identifiers, access tokens, refresh tokens, quota credentials, App Attest proof values, support-message content, or other user-provided recording content to Sentry.
Purchases And Subscriptions
PodSetup Pro subscriptions are purchased and managed through StoreKit and the Apple App Store. Apple processes payment information and provides subscription status to the app.
PodSetup may use RevenueCat to read App Store subscription status and may identify RevenueCat requests with the anonymous quota principal ID so backend quota enforcement matches the active entitlement. The app may cache subscription tier state locally so features can render quickly, but subscription purchases, renewals, cancellations, and refunds are handled by Apple.
Deleting the app or resetting local app data does not cancel an Apple subscription. If you have an active subscription, manage or cancel it through Apple Subscriptions.
Local Reset And Retained Service Records
Settings lets you reset local app data on this device. Local reset removes local equipment records, saved locations, setup notes, media files, generated setup guidance, onboarding state, usage counters, and the ask-before-sending choice. It does not cancel Apple subscriptions.
After local reset, the Railway-hosted PodSetup backend may retain limited quota, subscription, rate-limit, and service-protection records where needed to prevent abuse, enforce free and Pro AI-assist limits, preserve active Pro access, resolve entitlement or billing support issues, comply with legal or accounting obligations, and protect the service.
Those retained records are technical records and are not intended to include your equipment names, location names, photos, audio recordings, spectrograms, setup notes, or generated setup guidance.
Camera, Microphone, Photos, And Files
PodSetup requests camera access only when you choose to take a photo for gear scanning or room review. It requests photo library access only when you choose an image from Photos. It requests microphone access only when you choose to record an audio sample.
Photos, recordings, and generated media remain local unless you choose an AI assist that requires backend processing for that input.
Third-Party Services
PodSetup uses OpenAI or another configured model provider through the Railway backend for AI assists, Apple and StoreKit for subscription purchases, RevenueCat for subscription entitlement handling, TelemetryDeck for privacy-focused product analytics, and Sentry for crash and error diagnostics.
PodSetup uses Railway for backend hosting, managed Postgres database storage, managed Redis rate-limit storage, and operational logs needed to run and protect the service.
No Sale Or Tracking
PodSetup does not sell your information. The app does not use collected data for third-party advertising or cross-app tracking.
The retained service records described above are not intended to include your photos, audio recordings, setup notes, or generated setup guidance.
Children's Privacy
PodSetup is not directed to children under 13, and we do not knowingly design the service to collect personal information directly from children through a registration or account-creation flow.
International Users
PodSetup is offered by a U.S.-based company, Infral Labs LLC. If you use the app from outside the United States, your information may be processed in the United States or other countries where PodSetup or its service providers operate.
Data-protection laws may differ from those in your home country. By using PodSetup, you understand that information may be transferred and processed as needed to provide the service.
Policy Changes
PodSetup may update this Privacy Policy as the product, vendors, or legal requirements change. If we make a material change, we will update the policy with a revised last-updated date.
You should review this policy periodically for the latest version.
Contact
For privacy questions, support requests, or data requests, contact podsetup@infrallabs.com.
