01Scope and operator
Updated and effective November 3, 2026. CarRim is operated by BendarySiu. For support and privacy inquiries, contact bendary@foxmail.com.
This policy explains information handling in the CarRim iOS/iPadOS app. It covers existing versions and features actually provided and enabled in newer versions. Availability and processing depend on your version, region and choices; mentioning a feature does not mean it is available to everyone. Website browsing is covered by the separate website privacy notice.
Local editing does not require a CarRim account. The existing iOS implementation and the newer candidate reviewed for this policy have not enabled CarRim sign-in, Plus/Pro subscriptions or cloud garage syncing. Purchases and restoration through your Apple Account are separate. If accounts or cloud syncing become available, their processing and choices will be explained before activation.
02Photos and local editing
Vehicle photos you choose or take, custom wheel/texture images, masks and editing parameters are used for wheel or body detection, color changes, compositing, local plans and export. Detection and compositing run on your device, and your local garage stays in app storage. These editing workflows do not automatically upload those images or plans to CarRim services, advertising services or model-training services.
Local processing does not mean the entire app stays offline. Asset downloads, advertising, purchases, analytics or diagnostics you enable, and feedback or sharing you initiate involve the separate processing described below. Imported originals may contain capture or other metadata. Check image content and associated information before sharing.
03Camera, photos and system permissions
Newer versions receive images you select through the system photo picker; older versions may request photo-library read access. Taking a vehicle photo requires camera permission, while saving to Photos requires the relevant permission to add photos. These permissions have different purposes and scopes and can be managed in iOS Settings.
If you decline camera access, you can import an existing image. If you decline saving to Photos, use a system sharing option where your version provides one. Core photo editing does not require precise location, microphone or contacts permissions. System tracking permission and choosing an ad-supported export are separate choices; follow the requirements shown by the actual export flow.
04Assets, model resources and network requests
When requesting remote wheel or texture catalogs, asset images, resource versions or available model updates, CarRim asset APIs and their hosting/CDN services receive network information needed for the request, such as an IP address, requested catalog or asset identifiers, versions, time and client connection information. This supports content delivery, troubleshooting and service security. These downloads do not require your vehicle photos or plans as request content.
Versions supporting resource updates verify and use downloaded content on the device; recognition still runs locally. Download capability does not mean a model in training has been released. If a network or service is unavailable, asset availability depends on local or cached content already on your device.
05Advertising and ad privacy choices
Free versions use Google AdMob/Google Mobile Ads. Depending on the version and enabled placements, ads may include banners, native, interstitial, app-open or rewarded ads, including rewarded interstitials in some versions. Advertising services can process IP addresses (which may indicate a general area), device or app identifiers, ad/product interactions and diagnostics for ad delivery, measurement and fraud prevention. Requests do not use your vehicle photos as advertising content.
Newer versions supporting Google User Messaging Platform (UMP) update ad consent status and provide consent forms and privacy options when applicable. Updating choices may itself contact Google. Newer versions set non-personalized ad requests when Apple cross-app tracking authorization is absent. Older privacy controls may differ, and non-personalized ads still process necessary ad and network information.
Ad privacy choices, Apple tracking settings and usage analytics are managed separately. Use the ad privacy entry provided by your version and iOS Settings. See the Google Privacy Policy and Google ads SDK data disclosure.
06Exports, ad support and purchases
Some newer versions check device network status and show an ad confirmation before a free user creates a new export or sharing output. Canceling that action creates no new output. Local editing and saving do not therefore require a rewarded ad. Ad availability, reward outcomes and export behavior follow the prompts in that version. Local image processing does not mean all exports work offline or without ads.
The iOS purchase reviewed for this policy is a one-time ad-removal product. Apple handles payment and your Apple Account. CarRim uses transaction and entitlement status to provide or restore the benefit and does not receive payment-card numbers or your Apple Account password. Newer versions stop showing ads and making subsequent ad requests while valid ad-removal access applies; older coverage follows the purchase description and actual entitlement.
Ad removal or a valid temporary ad-free status does not retract information already processed by an ad service or replace your separate analytics, diagnostics or asset settings. Purchases and restoration may use the network. See the Apple Privacy Policy.
07Optional usage analytics
Newer versions with Usage & Diagnostics settings offer Firebase Analytics and crash diagnostics as separate choices, both initially off. You can change them independently. Keeping them off does not affect local editing, saving, purchasing or the export flow provided by that version, and does not replace ad privacy choices.
With usage analytics enabled and a working production configuration, the app can record fixed categories for screens, import sources and results, recognition results, wheel sources, saving, exports, purchases/restoration, ads and resource updates. Ad revenue events can include value, currency, precision and ad format. These app-defined events do not attach photos, garage/plan names, file paths or arbitrary error text, and the app does not set a personal user ID.
The SDK may still process app instance identifiers, device/system information, a general area and automatic events; this should not be treated as fully anonymous. Turning analytics off stops subsequent analytics collection and resets local Analytics data, without automatically deleting previously uploaded records. See Firebase Privacy and Security.
08Optional crash diagnostics
In newer versions with this setting, enabling Firebase Crashlytics separately, with a working configuration, can send crash stacks, app versions, device, system and runtime information to diagnose faults. When analytics is also enabled, diagnostics may include activity leading up to a crash. The app does not deliberately attach vehicle photos or set a personal crash user ID; the SDK can still process crash, installation or session identifiers to associate reports.
Turning diagnostics off stops subsequent automatic reporting and requests deletion of unsent local reports. It does not automatically retract uploaded reports. Older versions may lack these separate switches. The Firebase diagnostics switch also does not turn off diagnostics handled by the Google advertising SDK itself.
09Announcements, version checks and online feedback
Announcements, online version checks and online feedback apply only when your version actually provides and enables the relevant service. Announcement and version requests can send the platform, app version, build number and distribution channel, alongside ordinary connection information. The app may also use the OS version and Apple storefront locally to decide applicability; local evaluation does not mean every such field is uploaded.
When you submit online feedback, it can send a category, description, optional contact details, app version/build and request identifiers. Ad feedback may include a placement and approximate time you enter or confirm. A version supporting this service may first establish a random installation identifier and access credential, storing the credential in the system Keychain for authentication, retry deduplication and abuse prevention. It is not a personal login account.
Online feedback does not automatically attach vehicle photos or logs. Discarding a local draft or canceling a wait cannot retract feedback already delivered to a server. If the service is unavailable or has not opened, you can use support email.
10Email and system sharing
If you email bendary@foxmail.com, the operator and relevant email services process your sender address, message, attachments you add and information needed to reply. Some versions prefill feedback emails with a device model, OS version and app version; review or edit them before sending. Send only what is needed, avoiding identity documents, passwords, payment information or original photos you do not wish to share.
Saving to Photos, using system sharing, emailing or using another app gives your chosen content to the relevant system service or recipient. Photo syncing, system backups, email and recipients’ copies are managed through their own settings and policies.
11Storage, deletion and backups
Local plans, originals, masks, custom assets and caches are stored on your device for the relevant features. Use deletion or cache controls provided by the app. Deleting one plan does not delete other plans, asset libraries, copies imported from an older version or exported photos. Importing an older garage reads and converts data on the device; it is not a cloud garage upload. Keep your own backups of important work.
Support communications and enabled online records are retained as needed for service delivery, issue handling, security and applicable requirements. Retention and deletion depend on the purpose of the records, service configuration and applicable requirements. Third-party SDK data is governed by the relevant service settings and notices.
Deleting local content or uninstalling the app does not automatically retract feedback, emails, advertising, analytics or diagnostics already sent. Exports, shared copies and backups must also be managed separately. Contact us below about retention or deletion requests.
12Recipients and processing locations
Depending on the features you use, recipients include the operator and relevant support email services, hosting and network services for CarRim asset/business APIs, Google advertising/consent services and Firebase services you enable, Apple system and purchase services, and recipients you choose when sharing. Only information relevant to a feature should be provided through that flow; controls for one service do not substitute for another’s.
Network services and their providers may process information outside your country or region. Accessing a nearby asset endpoint does not mean all SDK and support records are stored in the same location. See the Google Privacy Policy, Firebase Privacy and Security and Apple Privacy Policy. Contact bendary@foxmail.com about CarRim’s actual services, processing locations and information requests.
13Your choices and information requests
You can manage camera/photo/tracking permissions, applicable ad privacy options and newer analytics/diagnostics switches, and decide whether to submit feedback or share content. Withdrawing a choice generally affects subsequent processing; it does not automatically delete information already lawfully processed or sent.
Subject to rules applicable where you live, contact bendary@foxmail.com to request access, correction or deletion of records involving us, withdraw consent, or request limits on or object to particular processing. Describe your request and relevant app version, ticket ID or support exchange so we can locate records and make necessary checks. Do not send identity documents or payment credentials in your initial message. We will handle requests under applicable requirements and explain how to manage third-party or local data that we cannot directly control.
14Minors and information security
Minors should use the app and manage permissions, ad choices and purchases with a parent or guardian. An App Store age rating does not establish parental consent or determine a user’s age. A guardian who believes a child has provided inappropriate personal information can contact the privacy email address.
Information security depends on devices, networks and services together. Protect your device and system accounts, share only what is necessary and back up important work. Report suspected disclosure or other privacy problems through the email above without sending passwords or keys.
15Policy updates
We will update this policy when information handling or actually enabled features materially change, providing notice and necessary choices where applicable. Descriptions of newer features or publication of this policy do not mean a new app version has shipped on the App Store. Available features depend on your installed version and what is actually enabled.