Privacy Policy
Dokumen ini belum tersedia dalam bahasa Anda, sehingga versi bahasa Inggris yang ditampilkan. Hanya teks berbahasa Turki yang mengikat secara hukum.
Effective date: 15 November 2026 Last updated: 15 November 2026
1. Who we are
This Privacy Policy explains how Bitte Limited ("we", "us") processes personal data in the Dricast app (iPhone, iPad, Mac,
Apple TV and CarPlay) and on https://dricast.app (together, the "Service").
- Contact: [email protected] (support)
- Users in Türkiye: see also our KVKK Information Notice (Turkish).
2. Summary
- No account required. You can use the app and make purchases without an account. Purchases made without an account are still reported to our server as Apple's signed record, together with a pseudonymous install ID (see 3.4).
- We do not provide content. The IPTV playlists and links you add are yours. Addresses containing credentials are stored encrypted on our server.
- Your precise location is not sent to us. With your permission ("While Using the App") the app uses your location for navigation and nearby charging stations. Map, search and routes are provided by Apple Maps; your device sends the location data they need directly to Apple. To find nearby chargers, only a coordinate rounded to about 1 km reaches our server; it is not stored or linked to you. Video on the car screen is shown only while parked.
- Ads are shown only to free users: Google AdMob on iPhone, iPad and Mac, and a Google Interactive Media Ads (IMA) video ad when a channel opens on Apple TV. There are no ads on CarPlay. Personalised ads need your permission.
- Ad measurement (Meta): we advertise Dricast on Meta (Facebook, Instagram). To measure how many installs and purchases these ads lead to, the iPhone and iPad app uses the Meta SDK; the advertising ID (IDFA) is sent only with your permission, and nothing is sent to Meta if "Send Analytics Data" is off (see 3.2A).
- Your devices: you can be signed in on up to 5 app devices at once; when a new device signs in, you get a notification and an email.
- No third-party analytics. To fix errors per device and car model and to improve the app we collect pseudonymous usage and analytics data (device/car model, CarPlay, mirroring, playback and browser usage) on our own server, even without an account, and with the same setting anonymous crash reports (Apple MetricKit). No advertising ID, no tracking. On by default; turn it off in Settings › Privacy › "Send Analytics Data" (see 3.9).
- You can delete your account in the app and on the web.
3. What we process and why
3.1 Location, navigation and Park Mode
- Permission: the app asks for location access "While Using the App". Location is used in the background only while turn-by-turn guidance is active; it stops when guidance ends. You can change or revoke the permission at any time in iOS Settings › Privacy & Security › Location Services › Dricast. Without it, search and the rest of the app still work, but guidance and "nearby" lists are unavailable.
- Why: (a) navigation — your position on the map, routes, turn-by-turn guidance, rerouting and arrival; (b) nearby charging stations. Park Mode does not use location: video on the car screen opens only with your "I'm Parked" declaration, which is your responsibility and can be revoked from the iPhone at any time.
- Not sent to us: your precise location and speed never reach our servers (for Apple Maps see below). Your "I'm Parked" confirmation (until you revoke it from the phone), saved places (Home, Work, saved and recent destinations) and the voice-guidance setting are kept only on your device and are not sent to us.
- Nearby charging stations: to list chargers near you, the app sends our server a coordinate rounded to about 1 km (two decimal places) and a search radius. The server uses it only to answer that request: it is not stored, not linked to your account or install ID and not written to our logs. The answer is cached for at most 5 minutes, keyed only by the rounded point.
- Apple Maps (MapKit): the map, place search, route calculation, travel-time estimates and Apple Maps points of interest (including charging stations) are provided by Apple. For this, your device sends your searches, your position and your route's start and destination directly to Apple, which processes them under its own privacy terms (https://www.apple.com/legal/privacy/). We do not receive this data.
- Not used for: advertising, analytics or profiling. We do not build a location history.
- Legal basis: performance of a contract for the navigation and charging features you use (GDPR Art. 6(1)(b)).
- Charging station data (sources and licences): station details come from public open data and contain no data about you — Germany: Bundesnetzagentur charging point register (CC BY 4.0); France: data.gouv.fr (IRVE) consolidated dataset (Licence Ouverte / Etalab 2.0); other countries: Open Charge Map (under its data licence; some records carry their original source's licence); and Apple Maps points of interest. Data is refreshed periodically; it does not show real-time availability.
- Note: our ad partner Google may infer approximate location from your IP address when serving ads (see 3.2).
3.2 Advertising (Google AdMob), IDFA, ATT and UMP consent
- Who sees ads: free users only — Google AdMob on iPhone, iPad and Mac (the iPad app), and on Apple TV a Google Interactive Media Ads (IMA) video ad when a channel opens. No ads on the CarPlay screen. Pro users see no ads. Rewarded ads (e.g. "+15 minutes of CarPlay time") play on the phone only when you choose to watch one.
- Data: the Google Mobile Ads SDK may collect device information, IP address (approximate location), ad interactions (impressions, clicks), diagnostics and, only if you allow it, Apple's Identifier for Advertisers (IDFA).
- Apple TV: Apple's tracking prompt (ATT) appears when the app first opens; an ad is requested only when a channel opens, after that prompt. If you decline, only non-personalised ads are requested; in the EEA, the UK and Switzerland always non-personalised.
- Consent flow (iPhone, iPad, Mac): no ad or permission prompts on first launch. On the second launch, after a short explanation screen, Apple's App Tracking Transparency (ATT) prompt appears. The IDFA is used only if you tap "Allow". In the EEA, the UK and Switzerland, Google's User Messaging Platform (UMP) consent form is also shown, where you can accept, reject or choose per purpose.
- If you decline: ads may still be shown without personalisation (contextual/limited ads); the IDFA is not used.
- Changing your mind: iOS Settings › Privacy & Security › Tracking; for UMP choices, in the app under Account › Privacy › Ad Preferences.
- Legal basis: consent for personalised advertising and profiling; legitimate interests for non-personalised ads (funding the free tier). Google's practices: https://policies.google.com/technologies/partner-sites
- Sponsored content measurement: impressions and clicks on "Sponsored" home cards are counted as aggregate counters (item, platform, country, day) with no user identifier. The app sends them only while "Send Analytics Data" is on (see 3.9).
3.2A Ad measurement (Meta) — iPhone and iPad only
- Why: we advertise Dricast on Meta's platforms (Facebook, Instagram). To measure how many app installs and Dricast Pro purchases these ads lead to, the iPhone and iPad app uses Meta's SDK (Facebook SDK; app events only — no Facebook Login, no sharing). It is not used on Mac, Apple TV or CarPlay. No Meta ads are shown in the app.
- What: app opens ("app activation"; the first one counts as an install) and Dricast Pro purchases or free-trial starts (product ID, amount, currency, transaction ID); technical data such as the pseudonymous app ID generated by the SDK, device model, OS and app version, language, time zone and IP address; the advertising ID (IDFA) only if you tapped "Allow" in the ATT prompt. Channels you watch, your sources, searches, location and screen contents are not sent; the SDK's screen-title and app-layout collection features are turned off.
- If you don't allow tracking: no IDFA is sent; measurement relies on Apple's privacy-preserving SKAdNetwork and Meta's Aggregated Event Measurement.
- EEA, UK and Switzerland: data is sent to Meta only if you consented in the consent form (UMP) to the purposes "store and/or access information on a device" and "measure advertising performance"; otherwise nothing is sent.
- Pro users: although they see no ads, a purchase is the result of an ad, so it is measured too; the settings below apply equally.
- Turning it off: if Settings › Privacy › "Send Analytics Data" is off, no events are sent to Meta. You can withdraw IDFA permission in iOS Settings › Privacy & Security › Tracking.
- Recipient: Meta Platforms Ireland Ltd. (and its affiliate Meta Platforms, Inc.); data may be transferred to the USA. Meta may also process this data under its own terms: https://www.facebook.com/privacy/policy
- Legal basis: consent for measurement with the IDFA and in the EEA/UK/Switzerland; otherwise our legitimate interest in measuring the effectiveness of our ad spend (GDPR Art. 6(1)(f), KVKK Art. 5/2-f); you can object at any time with the switch above.
3.3 Sign in with Apple and accounts
- Optional. An account lets us recognise your Pro membership on the web and other devices and sync your sources and favourites.
- What: the unique user identifier Apple gives us, your email address (Apple's private relay address if you choose to hide it) and the name you choose to share on first sign-in. With email registration: name, email and password (stored only as a one-way hash).
- Sign in with Google (optional): the account identifier Google gives us (Google account ID), your verified email address and the name and profile photo on your Google profile. We do not receive your contacts or other Google data. You can unlink Google on the Account page (if another sign-in method remains); deleting your account also deletes the Google account ID.
- Profile photo (optional): taken from your Google account or uploaded by you; a downscaled copy (without metadata) is stored on our server, you can remove it at any time and it is deleted with your account.
- Session token and Your Devices: an access token stored in your device's Keychain. For each sign-in our server stores the device type (iPhone/iPad, Mac, Apple TV), an automatic or custom device name, and when it signed in and was last used. You can be signed in on up to 5 devices at once; under Your Devices in the app and on the web you can see them, rename them and sign them out. When a new device signs in, your other devices get a notification and your email address gets a notice (for security).
- Notifications (optional): if you allow Dricast notifications on a device while signed in, our server stores the device's Apple push token (APNs), device type, language/region setting and environment. We use them for match reminders, security notices and service announcements; promotional notifications (new features, offers) are only sent if you also turn them on in the app. You can turn notifications off at any time in iOS Settings › Notifications › Dricast; signing out deletes the token from our server.
- Legal basis: performance of a contract.
3.4 Purchases (StoreKit) and membership sync
- Payments are processed by Apple; we never see your card details.
- Purchase record: the app sends Apple's signed record of the valid App Store purchases on your device (product ID, transaction ID,
original transaction ID, purchase/expiry dates, amount paid and currency, offer/code type used, environment, storefront) to our
server, where its Apple signature is verified.
- If you are signed in, the record is sent with your account and your membership is attached to it (so the web and your other devices recognise it).
- Also without an account or while signed out (app 1.2 and later), the same record is sent together with the app's pseudonymous install ID (see 3.9): when your purchases change and at most once a day. The server stores only a one-way hash of the install ID. This happens regardless of the "Send Analytics Data" setting. Such a record belongs to no account and grants nothing by itself; it is attached to an account when you later report the same purchase while signed in, or when the purchase was made with a Dricast account (the account token Apple adds to the purchase).
- Purpose: seeing every App Store purchase (offer codes included), accounting for revenue and refunds, preventing abuse, providing support and answering Apple's refund questions (below). If "Send Analytics Data" is on, the install-ID hash matches the same device's usage summary record (3.9); we use this match internally and only for these purposes, never for advertising or tracking.
- Apple notifies our server of subscription changes (renewal, cancellation, refund, expiry) via App Store Server Notifications; these notifications are logged, even for purchases the app never reported to us (e.g. an offer code redeemed in the App Store).
- Refunds: when Apple reports a refund or a refund reversal, the refund record (transaction, product, amount, storefront, date and the reason Apple gives) is stored with the account and install hash the purchase is linked to, and sent to our administrators by e-mail/notification.
- Deletion: if you delete your account, purchase records are unlinked from your account and install hash. For records without an account you can ask us to remove the install-hash link (see 3.12). The records themselves are kept for accounting/tax (see 6).
- Refund requests: When you ask Apple for a refund of a Dricast purchase, Apple may ask us for consumption information about that purchase. If we have enabled this feature, we tell Apple only whether the purchase was delivered (based on the app having reported the purchase to us or the app having been used after it) and whether a free version/trial was available before the purchase. To determine this we review, internally only, a pseudonymous usage summary of the accounts and devices linked to that purchase (time since purchase, viewing, CarPlay and mirroring use, number of sources, earlier purchases and refunds); what you watch, source addresses, location and contact details are not sent to Apple. Apple processes this information under its own privacy policy and only to review the refund request; you can submit access or deletion requests for this data at Apple via privacy.apple.com. If you do not want this information sent to Apple for your refund requests, write to us (see 3.12) and it will not be sent from then on.
- On iPhone and iPad, a purchase or free-trial start (product, amount, currency, transaction ID) is also reported to Meta for ad measurement (see 3.2A).
- Legal basis: performance of a contract; legal obligations (accounting/tax) and legitimate interests (fraud prevention).
3.5 Your sources (IPTV playlists, Xtream credentials) — encrypted
- The M3U/Xtream addresses you add, including any username/password inside them, are stored on your device.
- iCloud: source definitions are stored in Apple's iCloud Key-Value Store so they appear on all your Apple devices. This data lives in your iCloud account, is governed by Apple's privacy terms, and we cannot access it. Turn off iCloud for the app to stop syncing.
- Account sync (if signed in): source and favourite addresses are stored on our server encrypted (AES-256 with the application key) and are returned only to your own devices.
- You and your provider are responsible for the content and the provider's service (see Terms of Use).
- Personal media servers (Jellyfin, Emby, Plex): the address of a server you connect and your username are stored with the source definition and may be synced with your account. The access key issued by the server is kept only in this device's Keychain; it is never sent to iCloud or to our server (you sign in again on your other devices). Your password is not stored. When you sign in with a Plex account, your device talks directly to plex.tv (Plex's privacy terms apply). Movie/show titles in your library and your watch position stay on your device and your own server; playback progress is reported directly to your server. Anonymous usage data contains only the server type, never content titles.
3.6 Favourites
- Stored on your device and, if signed in, on our server (addresses encrypted).
3.7 Local videos, browser and screen mirroring
-
Videos you add stay on your device (
Files › Dricast › Videolar) and are never uploaded. -
Websites you visit in the in-app browser apply their own cookie and privacy rules; we do not collect your browsing data.
-
Browser history, favorites and website data (cookies) are stored only on your device and are not synced; you can clear them from the browser menu or Profile › Privacy & Diagnostics.
-
For screen mirroring and the browser's "Send to Car" (in-app screen capture), frames are passed to CarPlay over a local, on-device connection only; they are not recorded and never leave the device.
-
Online subtitle search (optional): If you use "Search Subtitles Online" in the player, your search text (title), the language you choose and, for local videos, a file fingerprint computed from the file's contents (the video itself is never sent) go directly to OpenSubtitles, which sees your IP address. Downloaded subtitles are stored only on your device. If you don't use this feature, nothing is sent to OpenSubtitles.
3.8 Region and app configuration
- To show a home page for your country, the app sends the App Store storefront, device region, language and platform. Our server may also use the country code Cloudflare derives from your IP address. This is not linked to your identity.
3.9 Usage and analytics data (first-party analytics)
- We do not use third-party analytics tools. Even if you have no account, while the setting is on (the default) the app sends
the following data to our own server only:
- Pseudonymous install ID: a random ID generated on your device; the server stores only a one-way hash of it. Deleting the app resets it. The advertising identifier (IDFA) is not used.
- Device and app: platform, device model, OS and app version, language, country/region.
- Car: the car make and model reported by CarPlay (normalised, e.g. "Volkswagen Golf"), the CarPlay connection type and whether the car screen supports video. No licence plate, VIN or car location is sent. If you optionally pick your car in Settings › My Car, the brand and model you chose (a typed model is at most 30 characters) are sent with this data too; you can remove it there.
- Feature usage: CarPlay connections and session length, Park Mode on/off, reaching the free time limit; screen mirroring (start/stop, duration and error types); IPTV and other playback (stream type, start-up time, stall count, error code, name and category of the channel watched); the in-app browser (sessions and the domain of sites on a fixed list of known domains only, e.g. youtube.com — other sites and full addresses/pages are never sent); screens opened, features used, in-app searches and their result count, app launches and unexpected terminations.
- What we never send: stream addresses (URLs), login details such as usernames/passwords, full addresses of pages you visit, location, e-mail address, advertising identifier. For playback errors the server name is sent only as a one-way hash.
- Purpose: finding and fixing errors per device and car model (e.g. a mirroring problem in a specific car), measuring compatibility and improving the product. This data is not used for advertising, profiling or tracking (combining it with other companies' data), is not sold and is not shared with third parties.
- Sponsored card measurement: impressions and clicks on "Sponsored" home cards are also sent only while this setting is on (item, platform, country). To remove duplicates and limit abuse, the install ID or IP address is used for at most one hour, only as a one-way hash; only aggregate counters are stored (see 3.2).
- Link to your account: detailed events (searches, channels, domains, errors) are not linked to your account. If you are signed in, your device's summary record (device model, versions, country, last car model and when CarPlay/mirroring/playback/the browser were last used) is linked to your account for support and troubleshooting.
- Retention: raw events 30 days; daily aggregates and the device summary record 13 months (400 days; for the summary record counted from last use), then deleted automatically. The monthly install count (one number per month, platform and country; no device identifier) is aggregate and anonymous and kept indefinitely.
- Opt-out: Settings › Privacy › "Send Analytics Data". When off, no new data is sent and data queued on the device is deleted; data sent earlier is deleted at the end of the periods above.
- Deletion: if you delete your account, the device summary record is unlinked from it. Because the install ID is stored only as a hash, we cannot find detailed events by person; deleting the app resets the ID. Requests: [email protected].
- Legal basis: legitimate interest in improving the service and fixing errors (GDPR Art. 6(1)(f)). You can object at any time with the switch above (GDPR Art. 21).
3.10 Crash and diagnostic logs
- If "Share Analytics" is on, Apple shares anonymous crash reports with developers (Xcode Organizer). Apple collects this data and it is not linked to you.
- The app's own crash reports (MetricKit): if "Send Analytics Data" (3.9) is on, the app sends the crash and hang diagnostics that iOS prepares on your device (Apple MetricKit) to our own server: report type (crash/hang), time, exception type/code and signal number, hang duration, the call stack (only binary name, build UUID and memory offsets — to find the failing line of code), app and OS version and device model.
- What we never send: account ID, install ID, email, stream addresses, screen content or free text. The server drops anything outside the allowed fields and does not store your IP address with a report (the IP is used only transiently for rate limiting against abuse), so reports cannot be linked to a person.
- We do not use third-party crash reporting tools (Sentry, Crashlytics, etc.).
- Retention: 90 days. Opt-out: the same switch as in 3.9; turning it off also deletes queued reports.
- Legal basis: legitimate interest in fixing errors (GDPR Art. 6(1)(f)).
- The Google Mobile Ads SDK may collect its own diagnostics (see 3.2).
3.10A Problem reports
- When you use Report a Problem in the app, only the report you send reaches our server: the category you chose, your optional description and technical diagnostics (app/OS version, device model, language and region, network type, Pro status, whether CarPlay is connected, playback error codes and bitrate/stall counts, stream type and address pattern, recent app events). You can see the full list in the form before sending.
- Never sent: stream address, server name (only a salted one-way hash), username, password, token, channel name, local file name, media server address. Addresses and e-mails in the description are removed on the server. The report is not sent with account details and is not linked to your account; if analytics is on, a one-way hash of the install ID groups reports from the same device (if you are signed in, that device's summary record is linked to your account, see 3.9, so support can see the report through the device).
- Support replies: if a report reaches us linked to your account (sent by the app while you were signed in), we may reply to you about that report only (for example that the problem is fixed, which update fixes it, or that we need more information): by email to your account's email address and/or as an app notification to your devices that allow notifications. These replies contain no marketing; the app notification does not depend on the promotional notifications setting. We keep a record of each reply (channel, type of ready-made message, language, time, delivery result; the text if it was written by hand) with the report and delete it together with the report. If you answer a reply by email, your message is handled as described in 3.12.
- Retention: 180 days, then deleted automatically. Legal basis: handling your request and our legitimate interest in fixing bugs.
3.11 Server and security logs
- The website and API are served through Cloudflare. For security (DDoS, abuse, rate limiting), technical logs such as IP address, user agent and request time are processed briefly by Cloudflare and our hosting provider.
- Sign-in attempts are rate limited, for which IP address and email are processed temporarily.
- Account and security event log: events such as signing in on Apple TV with a code, account deletion, takeover of an unverified account and Apple account notifications (e.g. Sign in with Apple being revoked), as well as actions taken in our admin panel (including changes to your account or membership), are written to an audit log: event type, time, the record concerned, where relevant the account email, and IP address. We keep it for security, abuse prevention and accountability (legitimate interest). IP addresses are removed after 30 days; user-originated events are deleted automatically after 90 days and admin action records after 2 years.
- When one of our short links in ads or profiles (
/go/…) is clicked, we keep only aggregate counters (link, day, country, device type and type of referring site, e.g. TikTok, Instagram); no IP address, full user agent or cookie is stored, and you are not identified. If you arrive on the website through a campaign link, the campaign name is kept only in that visit's session and added to the App Store link.
3.12 Contacting us
- If you email support, we process your email address and message to reply.
4. Who we share data with
We do not sell your data. We share it only with service providers, as needed to run the Service:
| Recipient | Purpose | Location |
|---|---|---|
| Apple Inc. | Sign in with Apple, App Store payments, consumption information for refund requests (see 3.4), iCloud KVS, crash reports, Apple Maps (MapKit: map, search, routes — sent by your device directly to Apple) | USA / global |
| Google LLC / Google Ireland (Sign in with Google) | Authentication (only if you choose this method) | USA / EU / global |
| Google LLC / Google Ireland (AdMob, UMP, Interactive Media Ads) | Ad serving (iPhone, iPad, Mac, Apple TV), consent management | USA / EU / global |
| Meta Platforms Ireland Ltd. / Meta Platforms, Inc. | Ad measurement: app installs and Pro purchases (iPhone/iPad only; see 3.2A) | EU / USA |
| Cloudflare, Inc. | CDN, security, DNS, email routing | USA / global |
| Hetzner Online GmbH (Almanya/Finlandiya) | Server and database hosting | England and Wales |
| YouTube (Google) | Official embedded player (youtube-nocookie) for free channels and videos | USA / global |
| OpenSubtitles (Opensubtitles.com) | Online subtitle search and download (only when you search; search text, language, file fingerprint, IP) | EU / global |
| Public authorities | Where legally required | — |
5. International transfers
Some providers are outside the UK/EEA/Türkiye. Transfers rely on adequacy decisions, the UK IDTA/Addendum or EU Standard Contractual Clauses, and for Türkiye, the safeguards in Article 9 KVKK (standard contracts) or your explicit consent.
6. Retention
| Data | Period |
|---|---|
| Account details, sources, favourites | Until you delete your account |
| Session tokens and device records (Your Devices) | Until sign-out, device removal or expiry; expired tokens are purged within 24 hours |
| Purchase, refund and App Store notification records (including purchases reported without an account) | Unlinked from your account and install hash on account deletion; kept 6 years for accounting/tax |
| Sponsored-content counters | Aggregate and anonymous; indefinitely |
| Web channel-list cache | Up to 15 minutes |
| Server/security logs (Cloudflare and hosting provider) | Up to 30 days |
| Account and security event log (TV sign-in, account deletion/takeover, Apple account notifications) | 90 days; IP address removed after 30 days |
| Admin panel action log (including admin changes to accounts and memberships) | 2 years; IP address removed after 30 days |
| Crash and hang reports (MetricKit, anonymous) | 90 days |
| Usage and analytics data — raw events | 30 days |
| Usage and analytics data — daily aggregates and device summary record | 13 months (400 days) |
| Monthly install count (month, platform, country; no device identifier) | Aggregate and anonymous; indefinitely |
| Problem reports (Report a Problem) and the record of support replies to them | 180 days |
| Ad-measurement events sent to Meta | Not stored on our servers; subject to Meta's own retention terms |
| Server backups (database + uploaded images; encrypted fields stay encrypted) | Last 7 nights; off-site copies at most 30 days per bucket lifecycle rule |
| Support correspondence | 2 years after the request is closed |
| Parking confirmation, precise location, saved places | Not stored on our servers (on your device only, until you revoke/delete them or delete the app) |
| Rounded location for nearby chargers (~1 km) | Not stored; the server's answer is cached for at most 5 minutes |
7. Deleting your account and data
- In the app: profile icon › Account › Delete Account.
- On the web: sign in with Apple or Google at
https://dricast.appand choose Delete Account in the account menu at the top right. - By email: [email protected].
- Deletion permanently removes your account, your server-side sources and favourites, and your sessions, and revokes the Sign in with Apple link with Apple; the Google link (Google account ID) is deleted from our server. Records we must keep by law are retained for that purpose only, with restricted access.
- Deleting your account does not cancel an App Store subscription. Cancel it in iOS Settings › [your name] › Subscriptions.
- To remove on-device data, delete the app; to remove source definitions from iCloud, use Settings › [your name] › iCloud › Manage Storage.
8. Your rights
Under UK/EU GDPR, KVKK (Article 11) and other applicable laws you may have the right to access, rectify, erase, restrict, object, data portability, withdraw consent and complain. Contact [email protected]. You may complain to your data protection authority (UK: ICO; Türkiye: the Personal Data Protection Board).
9. Children
The Service is not directed to children and we do not knowingly collect personal data from children under 13 (or under 16 where required in the EU). Parents showing content to children in the car should manage the device themselves. If you believe a child has given us data, contact [email protected] and we will delete it.
10. Security
Data is protected in transit with TLS; source/favourite addresses are encrypted at rest; passwords are hashed; admin access is limited. No system is 100% secure; we will notify breaches within the legally required timeframes.
11. Changes
We may update this policy. We will announce material changes in the app or by email. The current version is always at
https://dricast.app/privacy.
12. Contact
Bitte Limited — [email protected]