toCar Privacy Policy
Effective
Hangzhou Qingzhou Technology Company Limited (“toCar,” “we,” “us,” or “our”) operates the toCar iPhone app. This Privacy Policy explains how we handle personal information when you use the app, visit these legal pages, or contact us for support.
1. Information stored on your device
You can use toCar without registering or signing in. To organize your library and resume playback, the app stores the media and subtitles you import, source addresses, playlists, library metadata, favorites, bookmarks, and viewing records such as titles and playback positions. It also saves app preferences, onboarding progress, and the policy version recorded when you agree to the Terms of Use and acknowledge this policy.
toCar encrypts saved media-server credentials and private media-source locators in app storage, with the encryption key kept in the iOS Keychain. This does not mean all library metadata, webpage addresses, or viewing records are separately encrypted by toCar. iOS provides additional device and file protection. App data may be included in device backups, depending on your settings; credentials may need to be entered again after restoration to another device.
2. Connections you choose
Media sources and playback progress
When you add a playlist, streaming address, or server, toCar connects to the source and its media hosts to sign in, load the library, or play the media. The services involved can receive your IP address, request details, and any credentials, tokens, or identifiers needed for the connection. Plex sign-in and discovery contact Plex and can use a connection identifier generated by toCar.
Supported Plex, Jellyfin, and Emby servers can receive the item you play, your playback position, and events such as starting, pausing, and finishing. toCar may hold an update on your device and send it to that server when the connection returns. You can remove the source to stop future synchronization through that connection.
Browser and website video
Websites and their embedded services can receive your IP address, browser information, cookies, and what you submit on their pages. Address bar searches send your search terms to Google. toCar uses Apple WebKit to keep website cookies and sign-in sessions on your device. When you open a video in toCar’s player, it requests the stream from the media host and may send matching site cookies and browser information. toCar can save the original webpage address, title, viewing mode, and playback position in Recent on your device. An original webpage address can itself contain query parameters or other private information. Recent does not store the resolved media-stream address, cookies, or request headers; browser cookies and sign-in data are stored separately. Sites you visit handle their own tracking and privacy signals under their own policies.
Local network, casting, and screen sharing
With Local Network permission, toCar can communicate with servers and compatible devices. When the cast receiver is enabled, casting apps can send playback commands and media addresses. Devices on the network can request playback status and the active cast address. That address may contain access information supplied by the casting app. Connected displays may receive video, audio, titles, playback positions, and information needed to retrieve the selected media when you choose a supported output. Use a trusted network and display, and disable the cast receiver when you no longer want it to accept commands.
Where screen sharing is available, it starts through Apple’s broadcast control and processes your screen and available app audio, which may include notifications, messages, or other personal information visible or audible during the broadcast. The stream is intended for your local network and uses unencrypted HTTP. A device that can reach the active session link may be able to see or hear what you share. toCar does not capture microphone audio or send the stream to us. Stop the broadcast through the system control or toCar’s stop control; closing a page is not the same as stopping a broadcast. Recent stream fragments may remain on your device after it ends and are cleared when the next broadcast starts.
3. App Store purchases and diagnostics
When paid offers are available, Apple processes payments, renewals, and refunds through your Apple Account. toCar reads StoreKit transaction and entitlement information on the device to check the product, recognize eligible access, and restore purchases. If Apple sends us purchase or subscription notifications, we use transaction identifiers, product information, and purchase, renewal, or refund status to verify purchases, investigate billing issues, and maintain records. Apple handles your payment details.
Apple may make sales, performance, and crash reports available to us through its developer tools. Crash reports may be shared based on your device settings or your participation in TestFlight. We use reports we receive for accounting, maintaining the app, and troubleshooting.
Apple’s App Store privacy notice
4. Support, feedback, and visits to these pages
If you email us, we receive your email address, message, and any attachments you choose to send. If you use the in-app feedback form, we receive your email address and message, plus a name and an image if you choose to include them. We use this information to respond, investigate issues, improve toCar, or handle a privacy request. Please omit passwords, access tokens, private stream links, and payment card information from support messages and images.
When you send feedback in the app, toCar creates or reuses a session that does not require a name or sign-in. Our service assigns a random account identifier, associates it with your feedback, and uses it to authenticate the request and limit abuse. Session credentials are kept in the iOS Keychain. Our service stores session records and a hash of the refresh token. Technical execution logs may contain request and session details. Our feedback service stores the submitted message and contact details and processes any image you attach.
When you visit these legal pages, our web server can receive and log your IP address, browser information, request time, and the page requested. We use request data to serve the pages, troubleshoot failures, and protect the site. These pages contain no scripts, remote fonts, advertising, or analytics.
5. Who receives information
Our email, hosting, and feedback service providers process information to run our support mailbox, handle feedback and attachments, and serve these pages. Providers acting on our behalf must use that information for the services they provide and protect it to a standard at least equivalent to this policy. We may disclose information we hold when required by law or when a disclosure is lawful and necessary to address a security incident or protect legal rights.
Apple and the media services, websites, and playback devices you choose process information for their own services under their respective policies. Support, feedback, and website request records may be processed in countries where we or our providers operate. You can contact us with questions about where information we hold is processed.
Product analytics
When enabled, PostHog and Google Analytics for Firebase help us understand onboarding, feature use, playback reliability, CarPlay compatibility, and purchase conversion. App events can include the feature or onboarding step, playback source and output categories, startup timing, error categories, and the plan and outcome of a purchase attempt. We keep a limited number of first-run events on the device and send them only after the published policy is accepted. The app discards first-run events older than seven days when it next opens. The providers can receive app and device information, event times, IP addresses, and analytics installation identifiers. The custom events use categories and timings while keeping media links, titles, search terms, credentials, viewing history, and transaction identifiers out of their payloads. Firebase may also record standard app and in-app purchase events. See the PostHog privacy policy and the Firebase privacy information.
Meta ad measurement
After you allow tracking in the iOS prompt, toCar uses the Meta SDK to send install, app activation, and verified App Store purchase events to Meta. Meta can receive device and app information, such as the advertising identifier, IP address, app version, and event timestamps, and associate that information with activity on its services to measure toCar advertising. Purchase events include the product identifier and, when available, the purchase amount and currency. toCar does not send your media library, viewing history, browser addresses, or media-source credentials to Meta. See Meta’s Privacy Policy for how Meta handles data it receives.
If you decline tracking, toCar still works. Apple’s SKAdNetwork may separately report a privacy preserving install to the ad network without sharing your advertising identifier.
6. Retention and deletion
- On your device. Library records and preferences remain until removed through the available app controls or by deleting the app. Removing a Recent entry removes the visible viewing record; a local marker containing its webpage address and deletion time can remain to prevent an older playback update from restoring it. Temporary media, broadcast fragments, website cookies, and sign-ins are managed separately. Recovery copies of encrypted source data may remain in app storage after a storage-recovery operation.
- Support and feedback. We retain messages, attachments, and related records while we handle the request and for as long afterward as needed to follow up, resolve a dispute, prevent abuse, or meet a legal obligation. You can ask us to delete feedback and related session records using the contact below.
- Diagnostics and product analytics. We retain reports and event data as needed to investigate issues, verify fixes, and evaluate feature and performance trends. Retention in our analytics providers is governed by the settings and terms of each service. We may keep aggregate statistics that do not identify you.
- Technical logs. For these pages, the web server normally keeps the current access log and up to 14 daily rotated logs. The feedback and session services keep technical execution logs under their automatic cleanup settings. Records relevant to a specific security investigation, dispute, or legal obligation may be retained for as long as needed for that purpose.
- Sales records. We retain personal information in sales records as needed to meet accounting and tax obligations. The law may require us to retain certain records longer.
7. Your choices and privacy rights
Use the app’s controls to remove sources and imported media or clear viewing entries in Recent. Clearing Recent is not a browser-data reset and does not erase viewing records already sent to a media server. Website sign-ins, your original files, backups, and records held by connected services are managed separately. Choose Delete App in iOS to remove the app’s local container; offloading keeps app data. A Keychain encryption key may persist separately, and deleting toCar does not delete backups or third-party accounts.
To change access for optional features, turn off toCar’s Local Network permission in iOS Settings, disconnect a source, sign out of a website, or stop a broadcast. You can change tracking permission in Settings → Privacy & Security → Tracking and review Apple’s diagnostic sharing choices in iOS Settings.
Depending on applicable law, you may have rights to access, correct, delete, or receive a copy of information we hold, restrict or object to processing, or withdraw consent where processing relies on it. To make a request or appeal a decision where an appeal is available, email us at the address below. Include the email address you used for feedback if your request concerns a submission. We may ask for information needed to verify the request and will retain information only where necessary for the purposes above or as required by law. You may also have the right to complain to your privacy regulator. For data held by a service you connected, use that service’s privacy controls or contact it directly.
8. Children’s privacy
toCar is intended for a general audience. We do not direct the app to children under 13 or knowingly collect their personal information. Parents or guardians can contact us if they believe a child under 13 provided personal information to us. We will investigate and delete the information where required by law.
9. Changes to this policy
We post updates on this page with a new effective date. We will give any additional notice or obtain consent when required by applicable law.
10. Contact
Hangzhou Qingzhou Technology Company Limited
Privacy questions and requests
support@tsingzhou.art