Privacy Policy - QuickCast

Last updated: 14 July 2026

QuickCast (“the App”) is developed by Data Consulting Services. This Privacy Policy explains how we handle your information when you use our app.

Our Privacy Commitment

QuickCast is designed with privacy as a core principle. Your audio recordings, transcripts, and webhook configurations stay on your device and only go where you tell them to go. The only data ever transmitted to us is anonymous usage events and optional crash & error diagnostics — and only if you explicitly opt in.

Information We Do NOT Collect

We do not collect personal information (no name, no email, no phone, no address)
We do not have user accounts or registration
We do not track your location — and we never receive it. (You can optionally attach location to uploads sent to your own webhooks; see “Optional Capture Metadata” below. That data goes only to endpoints you configure, never to us.)
We do not use advertising identifiers
We do not store your recordings, transcripts, or webhook URLs on our servers
We do not share your content with third parties
We do not use third-party advertising or marketing SDKs

Anonymous Usage Analytics (Opt-In)

QuickCast 1.5 introduces an optional, anonymous usage analytics feature powered by Aptabase, an open-source, privacy-focused analytics provider hosted in the European Union.

What we collect (only if you opt in)

App launches
Recording started / stopped
Recording upload outcome (success, partial success, failure)
Approximate recording duration bucket (short / medium / long)
Screen / feature opens (e.g. settings, history)
App version, OS version, device model, locale

What we never collect

Audio content
Transcripts
Webhook URLs, names, headers, or payloads
File names or recording metadata
IP addresses (Aptabase explicitly does not log them)
Advertising identifiers (IDFA / IDFV)
Persistent device IDs
Any account or contact information

How it works

Analytics is off by default. The first-launch onboarding flow asks you explicitly whether to enable it.
A rotating session ID (a fresh UUID) is generated locally each time you use the app, and resets after one hour of inactivity. It is never linked to your identity, your device, or any account.
Events are sent over HTTPS to https://eu.aptabase.com. Aptabase’s data processing happens entirely within the EU.
You can turn analytics off (or back on) at any time in Settings → Privacy → Anonymous Analytics. Disabling it stops all event transmission immediately.
Opting out is permanent across launches until you opt back in.

Crash & Error Diagnostics (Opt-In)

QuickCast 1.5.2 introduces an optional crash & error diagnostics feature powered by Sentry, hosted in the European Union. It helps us find and fix problems faster by reporting what the app was doing when something goes wrong.

What we collect (only if you opt in)

Error and crash-adjacent events (e.g. a recording that failed to start or finished unsuccessfully)
A short trail of recent in-app actions leading up to a problem (“breadcrumbs”) — for example “recording started”, “Siri stop received”, or “audio session interrupted”
Technical error details (error type and message)
App version and build, OS version, device model, and the build channel (App Store / TestFlight)

What we never collect

Audio content
Transcripts
Webhook URLs, names, headers, or payloads
File names or recording metadata
IP addresses (we have configured Sentry not to store them)
Advertising identifiers (IDFA / IDFV)
Persistent device IDs
Any account or contact information

How it works

Diagnostics are off by default. You enable them explicitly in Settings → Privacy → Crash & Error Diagnostics.
A rotating session ID (a fresh UUID) is generated locally each time you launch the app. It is never linked to your identity, your device, or any account.
Reports are sent over HTTPS to Sentry’s EU region (ingest.de.sentry.io). Data processing happens entirely within the EU.
No audio, transcripts, or webhook data is ever included in a diagnostic report.
You can turn diagnostics off (or back on) at any time in Settings → Privacy → Crash & Error Diagnostics. Disabling it stops all report transmission immediately.

Optional Capture Metadata (Per-Webhook Opt-In)

QuickCast 1.7 can optionally attach a small amount of context metadata to uploads — so your own automations can auto-categorize captures. This is off by default, configured separately for each webhook, and the data is sent only to that webhook — never to us, and never to other webhooks.

What can be attached (each field has its own toggle)

Network type — WiFi / Cellular / Ethernet at the moment of upload
Battery — charge level and charging state
Location — GPS coordinates and accuracy from a single one-shot fix at upload time

How it works

All three toggles are off by default for every webhook. You enable them per webhook in the webhook’s settings, where the app states exactly what will be sent and where.
Enabled fields are added to the upload as a separate JSON form field (default name metadata); for text-mode sends they are embedded as a JSON object inside the message body. Disabled fields are omitted entirely — not sent as empty values.
Location requires the standard iOS location permission (When In Use). If you decline, or no fix is available within a few seconds, the upload simply goes out without location — enrichment never blocks or fails an upload.
You can revoke location access at any time in iOS Settings, or turn the toggles off per webhook in the app.
None of this metadata is ever sent to us. Like your recordings, it travels directly from your device to the webhook endpoint you configured.

Photos and location (automatic protection)

Separately from the toggles above: when you send an image from your photo library (see “Image Sending” below), QuickCast strips embedded GPS/EXIF location data from the photo before uploading — at every quality setting. A photo’s hidden location tag never reaches a webhook unless you explicitly enabled the location metadata toggle for that webhook.

Data That Stays on Your Device

Audio Recordings

All audio recordings are stored locally on your device in the app’s private storage. Recordings are only uploaded to webhook endpoints that you explicitly configure. You have full control over your recordings and can delete them at any time from within the app.

Images

QuickCast 1.7 can also send images (from your photo library or camera) to your webhooks. Images follow exactly the same model as recordings: stored locally in the app’s private storage, delivered directly to webhooks you configure, deletable at any time. Embedded photo location data (GPS/EXIF) is stripped before upload.

Delivery Audit Log

The app keeps a local log of delivery attempts (which webhook, when, HTTP status, errors) so you can debug your own endpoints. This log exists only on your device; you can export it yourself as JSON or CSV. It is never transmitted anywhere by the app.

Settings & Webhook Exports

You can export your app settings and webhook configurations to files for backup or migration. These exports are created on demand, saved only where you choose, and are never transmitted by the app. If you choose “Include Headers” when exporting webhooks, the file will contain any authentication tokens stored in those headers — treat such files like passwords.

Webhook Configurations

Your webhook URLs, custom headers, and settings are stored locally on your device using Apple’s SwiftData framework. This data never leaves your device except when making requests to your configured webhooks.

Recording History

Your recording history, including file names, durations, upload status, and transcripts, is stored locally on your device. This information is not transmitted anywhere except to webhooks you configure.

App Settings

Your preferences (audio format, quality settings, auto-upload preferences, etc.) are stored locally using Apple’s standard UserDefaults system.

Permissions We Request

Microphone Access (Required)

QuickCast requires microphone access to record audio. This is the core functionality of the app. Audio is captured and stored locally on your device, and is only uploaded to webhook endpoints you configure.

Speech Recognition (Optional)

QuickCast offers optional live speech-to-text transcription using Apple’s Speech framework.

Important details about speech recognition:

All speech processing occurs entirely on your device. The app explicitly requires on-device recognition and will not fall back to server-based recognition.
No audio is ever sent to Apple or any third party for transcription
Transcription works offline (for supported languages). If on-device recognition is unavailable for your language or device, transcription is simply disabled — your audio is never sent off-device as a fallback.
Transcripts are stored locally with your recordings
Transcripts are only sent to webhook endpoints you configure
You can disable transcription at any time in webhook settings

Camera & Photo Library (Optional)

If you use the image-sending feature, QuickCast asks for camera access only when you choose “Camera” as the source. Photo library picking uses Apple’s out-of-process picker, which shows you your library without giving the app access to it — the app only receives the single photo you select. Images are stored locally and sent only to webhooks you configure, with embedded GPS/EXIF location stripped first.

Location (Optional, Per-Webhook)

QuickCast asks for location permission (When In Use) only if you enable the location metadata toggle for at least one webhook. Location is captured as a one-shot fix at upload time and attached only to uploads for webhooks where you enabled it. It is never sent to us. See “Optional Capture Metadata” above.

Network Access (Required)

Network access is required to upload recordings to your configured webhook endpoints. The app also monitors network connectivity to queue uploads when offline and retry when connection is restored.

How Your Data Flows

[Your Voice] → [Device Microphone] → [Local Storage]
                                           ↓
                              [Your Configured Webhook(s)]

[App Open / Recording Started] → [Anonymous Event] → [Aptabase EU]
                                  (only if you opted in)

[Something Goes Wrong] → [Anonymous Diagnostic Report] → [Sentry EU]
                          (only if you opted in)

You record audio using the app
Audio is saved locally on your device
If transcription is enabled, text is generated on-device
When you upload (manually or automatically), the recording and transcript are sent directly to YOUR webhook endpoint(s) — including in parallel to multiple webhooks if you use the multi-recipient feature
We never see, access, or store your audio, transcripts, webhooks, or recording metadata
Separately, and only with your explicit consent, anonymous usage events (e.g. “recording started”) are sent to Aptabase so we can understand which features people use. These events contain no audio, no transcripts, no webhook data, and nothing that identifies you.
Also separately, and only with your explicit consent, anonymous crash & error diagnostics are sent to Sentry when something goes wrong, so we can fix it faster. These reports contain no audio, no transcripts, no webhook data, and nothing that identifies you.

Webhook Uploads

When you upload a recording or image to a webhook:

Audio file or image: Sent as multipart form-data to your webhook URL (photo-library images have GPS/EXIF location stripped first)
Transcript (if enabled): Sent as a text field alongside the audio
Capture metadata (only fields you enabled for that webhook): Sent as a JSON form field
Custom headers: Any headers you configure are included in the request
Request signature (if you set a signing secret): An HMAC signature and timestamp header let your server verify the request really came from your app. The secret itself never leaves your device — only the signature does.

Your responsibility: You are responsible for the security and privacy practices of the webhook endpoints you configure. We recommend:

Using HTTPS endpoints for encrypted transmission
Using authentication headers for secure endpoints
Only configuring webhooks you trust
Reviewing the privacy policies of services receiving your data (Zapier, Make, n8n, etc.)

Offline Queue

When you’re offline or a webhook is temporarily unavailable:

Recordings are queued locally on your device
The app automatically retries when connection is restored
Queued items remain on your device until successfully uploaded
You can view and manage the queue within the app

Data Retention and Deletion

Your Control

Delete individual recordings anytime from Recording History
Clear all recordings using Storage settings
Recordings are permanently deleted from your device when you delete them
Uninstalling the app removes all local data

Automatic Cleanup (Optional)

You can configure automatic cleanup in Settings to remove old recordings based on:

Age (e.g., delete recordings older than 30 days)
Storage limits (e.g., keep only most recent 100MB)

iCloud and Backups

Device Backups

If you back up your device using iCloud or iTunes/Finder, app data may be included in those backups. This is controlled by your device backup settings, not by QuickCast.

iCloud Sync

QuickCast does not currently use iCloud sync. Your webhooks and recordings do not sync between devices.

Children’s Privacy

QuickCast does not knowingly collect any information from children under 13. The app does not require any personal information to function.

Third-Party Services

QuickCast does not integrate with any advertising, marketing, or behavioral tracking services.

QuickCast uses two optional, EU-hosted, privacy-focused services, both off by default. No data is sent to either unless you have explicitly opted in:

Aptabase — anonymous usage analytics (see the section above). Privacy policy
Sentry — anonymous crash & error diagnostics (see the section above). Privacy policy

When you configure webhooks to services like Zapier, Make, n8n, Slack, or custom APIs, your recordings (and optionally transcripts) are sent directly to those services from your device. Please review their respective privacy policies:

Security

We implement the following security measures:

All data is stored in the app’s private sandboxed storage
Recordings and images are encrypted at rest with Apple Data Protection: each file gets its own hardware-backed encryption key and cannot be read while your device is locked (QuickCast 1.7)
Network requests support HTTPS for encrypted transmission
Optional HMAC request signing so your server can reject requests that didn’t come from your app (QuickCast 1.7)
Embedded GPS/EXIF location data is stripped from photo-library images before upload (QuickCast 1.7)
No data is stored on our servers (nothing to breach)
Optional WiFi-only uploads for sensitive recordings
Optional review-before-send mode: recordings are held on-device until you explicitly release them

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by:

Updating the “Last Updated” date at the top
Posting the new policy on this page

We encourage you to review this Privacy Policy periodically.

Your Rights

Depending on your jurisdiction, you may have rights regarding your personal data. Since QuickCast does not collect personal data, most data protection requests are not applicable. However:

Access: All your data is already accessible to you within the app
Deletion: You can delete all data directly within the app
Portability: Recordings are standard audio files you can access and export

Contact Us

If you have questions about this Privacy Policy or QuickCast:

Email: support@dataconsultingservices.net

Website: https://dataconsultingservices.net/apps/quickcast/

Summary

Question	Answer
Do you collect personal information?	No
Where are recordings stored?	On your device only
Do you track my location?	No. Location can optionally be attached to your own webhook uploads — per webhook, off by default, never sent to us
What about location hidden in photos?	Stripped automatically before any image upload
Is speech recognition online?	No, it’s on-device
Do you sell my data?	No, we don’t have personal data to sell
Can I delete my data?	Yes, anytime in the app
Do you use analytics?	Only anonymous usage events, opt-in, off by default
Can I disable analytics?	Yes, in Settings → Privacy → Anonymous Analytics
Do you collect crash diagnostics?	Only anonymous crash & error reports, opt-in, off by default
Can I disable diagnostics?	Yes, in Settings → Privacy → Crash & Error Diagnostics
Do you show ads?	No
Do you use tracking SDKs?	No

QuickCast - Record. Send. Done. Your voice, your webhooks, your control.