Data we handle
- Account profile, plan, active-device, security, and account-request records.
- Videos and metadata you explicitly upload, plus sharing and view activity.
- Publishing, Team, Course, billing-entitlement, and learning records you create.
- Support details and diagnostics only when you submit or consent to them.
- Illegal-content notice contact details and evidence when you report a public share.
Local recording
Desktop drafts and exported MP4 files remain on the selected device until you delete them. TechCast does not receive the original recording merely because you record or export locally. Upload, phone, Live, AI, publishing, and sharing actions use network services only after you choose those workflows.
Why data is used
Data is used to authenticate accounts, provide requested recording and hosting workflows, enforce access and plan limits, deliver integrations, prevent abuse, troubleshoot failures, and meet billing or legal obligations. TechCast does not sell personal data or use private recordings for advertising.
Service providers
Depending on configuration and your actions, data may be processed by Vercel and Neon for hosting and storage, Google for sign-in, Gemini or another configured AI provider, Stripe for billing, and publishing destinations you connect. Provider credentials are encrypted and are excluded from account exports.
AI-assisted features
Local automation does not send content to an external AI provider. When you enable a configured external provider, TechCast sends the selected title, transcript, or content needed for the requested draft. The result is labelled as AI-assisted and requires your review before publishing. TechCast does not use private recordings to train its own model. Account-private activity can retain bounded visible provider output and reported token usage. Minimal request and operation records enforce usage limits and prevent duplicate requests.
Cookies and device storage
The current beta uses an essential signed session cookie and local device storage for settings and drafts. Google AdSense integration is disabled until publisher, ad-slot and consent-platform configuration is supplied. When enabled, optional Free-plan ads appear only on Dashboard and Library after both your account advertising preference and cookie choices allow them. You can withdraw the preference in Settings. Google may process page, device and network information; recordings, transcripts and prompts are not provided as ad-targeting parameters. Non-essential behavioral analytics are not loaded by this integration. An essential first-party opt-out remembers advertising withdrawal on this browser, including when a server save fails.
Retention
| Category | Current retention |
|---|---|
| Local recordings | Until you remove them from the device. |
| Hosted content | Until owner deletion or fulfilled account deletion. |
| AI activity and drafts | Bounded recent response and draft payloads, removed with related source or fulfilled account deletion; a legal hold can defer removal. Minimal usage and replay records remain until fulfilled account deletion. |
| Security and share events | 90 days. |
| Privacy-request history | Up to two years after cancellation or completion. |
| Illegal-content notices | Retained while the notice, appeal, legal duty, or limitation period requires it. A country-specific schedule remains a public-launch gate. |
Your controls
Settings provides a portable JSON export, active-device revocation, and a durable account-deletion request with cancellation. Deletion is not presented as immediate: hosted media, billing, connected providers, shared workspaces, and legal obligations are reviewed before completion, normally within 30 days.
Depending on applicable law, you may also request access, correction, restriction, portability, or object to processing. The beta account export and deletion controls are engineering tools; verified controller identity, supervisory-authority details, legal bases, and a formal request-response channel remain launch requirements.