01. Scope and operator
This draft covers the NiceCast website and the iPhone app being developed. Android and Mac are planned and require separate verification before release. The operator and privacy contact are listed above.
02. Your photos, videos and TV connection
NiceCast is designed to let you choose media on your device and send it to a compatible TV. The app uses local-network discovery and pairing to find and connect to receivers. A selected TV may receive the media, a media URL and playback metadata needed for the requested session.
[VERIFY BEFORE RELEASE: describe media processing, any temporary HTTP serving or caching, receiver access controls, any developer-side uploads, and exact deletion behavior.]
03. Permissions you control
Local Network permission supports TV discovery and communication. Photos permission supports media you choose to share. You can review these permissions in iOS Settings. If a released screen-mirroring feature uses screen capture or a microphone, explain that feature and its separate system consent before enabling it.
04. Third-party SDK information
The development build uses Google Cast SDK. Its inspected privacy manifest lists Device ID, Product Interaction and Other Diagnostic Data for analytics and app functionality, marked as not linked to identity and not used for tracking. A manifest alone does not establish all actual network behavior.
[VERIFY BEFORE RELEASE: list the exact SDK versions, all recipients and purposes, relevant provider policy links, transfer locations, and any choices users actually have. Reconcile this section with the final app and App Store privacy answers.]
05. Web video and external services
Websites opened in an in-app browser and TVs receiving content may process information under their own policies. Video access, cookies and playback restrictions can depend on those services.
[COMPLETE: disclose browser history/bookmark storage, cookies, website requests, URL/metadata sharing, clearing controls, and any extra SDKs in the final browser implementation.]
06. This website
The current website does not set application cookies or use local storage, and its page source does not include an analytics tracker, signup form or advertising script. Hosting and access-control providers can process request data such as IP addresses and access logs.
[COMPLETE: identify the actual hosting/access providers, purposes, log retention and applicable policy links before making this a final public notice.]
07. Retention, deletion and support
[COMPLETE: specify what is stored on-device, on receivers, by the developer and by providers; give actual retention periods and deletion procedures. Add a working privacy/support contact and explain any optional diagnostic attachments. Do not promise that uninstalling the app deletes provider logs.]
08. Rights, children and international processing
[COMPLETE FOR ACTUAL MARKETS: applicable legal grounds, user access/correction/deletion/objection options, consent withdrawal, complaint contacts, international-transfer safeguards and children’s privacy approach. Confirm the intended audience and the browser-related age rating. Preserve mandatory rights.]
09. Updates and contact
The final policy should state how material changes are communicated and show its effective date. For privacy questions, use the verified contact listed at the top of this page once it has been completed.
Reference for completion
Apple — App privacy detailsUse the source as a reference; this draft does not claim approval by Apple or completed legal review.
