Privacy policy
VisiCasts is operated by RegAtlas, LLC. This policy took effect on November 16, 2026. Questions: support@visicasts.com.
What this covers
VisiCasts provides a podcast website, browser player and hosted library sync. This policy describes the data handled by those services. Listening state is personal data: your subscriptions and listening positions can reveal your interests.
What the service stores
- Account details
- Your email address, account name or label, account ID and default-library ID.
- Devices and browser sessions
- Device IDs, names, device type, linked library, creation and last-seen times, and whether access has been revoked. Browser sessions also have creation, last-use and expiry times.
- Sign-in credentials
- The database stores SHA-256 hashes of one-time email tokens, pairing codes, browser session tokens and device tokens, not their original values. Email-token records include expiry and use times; pairing codes include expiry and an optional library. The usable token still appears in the sign-in email, the browser’s session cookie, or the paired device, as appropriate.
- Library and listening state
- Library IDs, names, creation and deletion markers; subscriptions and feed addresses; saved and current/archived episode flags; played/unplayed state; queue entries and order; playback positions, speeds and playback-session IDs; and settings sent by a client. Sync records include operation IDs, originating device IDs, sequence/version information and timestamps. The server retains an operation history, not just the latest screen you see.
- Podcast catalogue
- Feed addresses and show/episode identifiers, titles, authors, descriptions or plain-text summaries, artwork and audio addresses, media types, duration and publication dates, plus chapter and transcript references. Feed refresh records include validators, fetch status, the last error and refresh/retry timing. Feed admission records link an account to a feed and admission time. Catalogue metadata is shared internally between accounts; catalogue reads are restricted to that account’s subscribed shows.
- Request bookkeeping
- Device/library/request IDs and creation times prevent repeated browser actions from being applied twice. Sign-in rate limits use IP addresses and hashed email addresses in server memory. Recent unsent listening checkpoints are also held temporarily in memory before sync.
Feed addresses may contain private subscription tokens. They are stored as part of subscriptions and catalogue records; opaque display IDs do not remove those tokens from the stored address.
Data kept in your browser
The web app uses a visicasts_session cookie for sign-in. It is HttpOnly and SameSite=Lax, and is marked Secure with the HTTPS production origin. Its configured maximum age is 90 days; server sessions also expire and can be renewed during use. The selected library ID is saved in local storage. The browser may keep its ordinary page and media cache and the sign-in link in browsing history.
These are functional storage uses, not advertising cookies. Signing out revokes the browser session and clears its sign-in cookie; it does not delete your account or synced library.
Where information is sent
- Amazon Simple Email Service (SES): sign-in mail is sent through SES. It receives your recipient email address, the sender address, and the message content, including the one-time sign-in link. An optional SES configuration-set name can accompany a message.
- Cloudflare: serves the landing site and browser app. The web Worker proxies API requests to the backend, so Cloudflare processes request addresses and headers, cookies and API content in transit, including sign-in and library actions. The Worker forwards the visitor address for server-side abuse limits.
- Backend hosting: the backend and PostgreSQL run on Hetzner. That database holds the account, device, library and catalogue records described above.
- Apple podcast directory: when you search or browse in Discover, the apps (including the web app) send your search term or the show's directory ID straight from your device or browser to Apple's podcast directory. No account details or library data are included; Apple receives the request and ordinary connection information such as your IP address.
- Podcast publishers and their delivery providers: the backend requests subscribed feeds and redirects from their hosts. The browser requests episode audio and artwork directly from their supplied addresses. Those hosts receive the requested address and ordinary connection information, including the requesting browser’s or backend’s IP address. They may use their own delivery, advertising and logging systems. The catalogue stores metadata and addresses rather than a copy of episode audio.
Sign-in mail is sent through Amazon SES in the United States (Oregon). The backend and its database run on a Hetzner server in the United States (Oregon). Cloudflare serves requests from its network location nearest to you. Only the operator has administrative access to the server and database.
What this code does not collect
The landing site and web app include no advertising or behavioural analytics SDK, fingerprinting script or crash-reporting integration. The web app does not request microphone, camera or precise-location access. There is no email-inbox connection, contact-list access, password-based account sign-in or payment-card collection in this server/web code.
This does not mean there is no network or listening information: sync records listening activity, and hosting and podcast providers process requests as described above.
This describes the website and web app. The desktop and iPhone apps contain no advertising, analytics or crash-reporting SDK either.
Retention, backups and deletion
Email sign-in links expire after 15 minutes and work once. Pairing codes generated in the browser expire after 10 minutes and work once. Expiry prevents authentication; it does not by itself erase all database rows. Revoked device records can remain, and removing a subscription does not automatically erase earlier sync operations or the shared catalogue.
Deleting a library clears its sync log, revokes devices attached to that library, and marks the library deleted; the record can remain. The last library cannot be deleted through that operation. There is currently no self-service account-deletion endpoint.
The backup script keeps compressed database backups for a rolling 14 days, pruning old files after a successful backup. Copies contain account and library data.
To delete your account, email support@visicasts.com from the address on the account. We confirm the request by replying to that address, then delete the account, its libraries, devices and sessions within 30 days. Backups made before the deletion expire within 14 days after it. Shared podcast catalogue entries (public feed information not tied to you) may remain.
Questions or requests
See support and contact details to ask about your data or request account deletion.