Privacy notice
How the implemented features are designed to handle account, listing, communication and security information.
Who this draft covers
This draft describes the platform currently presented as Carbomi. The final responsible legal entity and privacy contact have not been supplied. Provider names, processing locations, applicable legal bases, international-transfer arrangements and regulator contacts must be confirmed for the actual deployment before final approval.
Information used by the features
Depending on what you use, information can include phone or Google sign-in details, account and device/session records, organisation membership, listing fields and photos, saved searches, enquiries, messages and support submissions. Security, consent and configuration changes also create limited operational records. Avoid putting unnecessary personal information in listings or support questions.
Why information is processed
The implemented purposes include account access, listing publication, search, buyer-seller communication, requested notifications, support and abuse prevention. Marketing notifications have separate preferences and consent controls. A new purpose or provider should be reviewed and disclosed before the relevant feature is activated; this draft is not blanket permission for unrelated reuse.
Public and private information
Published listing fields and processed photos can be public and indexed. Account credentials, sign-in codes and private conversations are not intended as public listing content. Seller contact access uses a separate permitted action. Once information is made public, visitors or search engines may keep copies that the platform cannot directly control.
Service providers and optional AI
Storage, sign-in and notification providers may receive information needed for a service you use. Optional AI support and image analysis have separate consent and processing controls. Do not send credentials or unnecessary sensitive data to them. The actual provider list, processing locations and relevant transfer safeguards must be confirmed before those services are activated.
Cookies and browser preferences
The web application uses cookies for sessions and, when used, short-lived Google or editorial flows. A locale cookie remembers language and browser storage remembers the theme. These have different purposes from advertising trackers. Third-party sites opened from external links manage their own cookies and privacy notices; opening their home page is not contacting an official platform support profile.
Photos and record retention
Photos are processed into optimised images for publication. Original uploads are intended for removal after controlled processing, rather than permanent public storage. Account, communication, consent and security records have different retention purposes. The final schedule must also cover backups and any required record holds. A single deletion deadline is not promised for every type of information.
Choices and privacy requests
Use available account and notification settings to update preferences, withdraw optional messaging consent and manage access. For access, correction or deletion questions, use signed-in support when available or an official contact channel. Your identity and authority over the information must be checked before disclosure or a sensitive change.
Security and changes to this notice
Safeguards include access permissions, protected sessions and checks on submitted information. No system is promised to be risk-free. Report concerns through official support without sending passwords or sign-in codes. The final notice must identify the approved operator, applicable rights and contact routes, an effective date and a reviewed version before it replaces this draft.