Privacy Policy for BersihNowBot
This policy explains data practices for BersihNowBot, a provider of smart cleaning robots and AI home helpers. It covers examples and real-life scenarios to help users understand how device mapping, scheduling, voice commands, and remote support interact with personal data. For instance, when a robot maps a living room layout to optimize cleaning routes, anonymized spatial data may be stored short-term for navigation accuracy. When a user schedules recurring cleaning via the app, minimal account details and scheduling metadata are processed to deliver the service. We describe what is collected, how it is processed, and practical steps users can take to manage settings and privacy in everyday scenarios such as multi-occupant homes, rental properties, or small offices.
Definitions
This section explains key terms used in the policy with concise examples tied to household deployments and device interactions.
- Personal data means any information that can identify an individual, such as name, contact details, device identifiers linked to an account, and location data associated with cleaning schedules. Example: account email used to set up a recurring cleaning schedule.
- Processing refers to any operation performed on data, including collection, storage, analysis, anonymization, and deletion. In practice, this includes generating optimized cleaning maps and creating logs for troubleshooting.
- User refers to any individual who owns, controls, or uses BersihNowBot services or devices in a home or small business environment. Example: a tenant who configures an automated cleaning routine.
- Service denotes the robotics hardware, mobile applications, cloud features, and customer support provided under the BersihNowBot brand, including scheduled cleaning, remote diagnostics, and firmware updates.
- Cookies are small files used by our website and app to remember preferences and manage sessions. For instance, cookies allow the web dashboard to maintain a logged-in session for managing robot schedules.
Data Collection
We collect data necessary to operate devices, improve navigation and reliability, provide customer support, and comply with legal obligations. Below are typical categories collected in real-world deployments with examples.
Data You Provide
Data users actively provide when creating accounts, configuring devices, or contacting support. Example case: entering an apartment layout preference during setup.
- Account information: name, email address, and password provided during registration to manage device access and communication.
- Address details: service address such as Asam Kumbang, 34000 Taiping, Perak, Malaysia used for warranty, shipping, and localized feature settings.
- Device configuration: room names, cleaning schedules, and zone preferences entered in the app to tailor device behavior to household routines.
- Support communications: messages and diagnostic logs sent by users when requesting assistance, which help resolve specific issues.
- Payment and billing details: when users select paid plans or maintenance, payment processor details are used to complete transactions (handled via third-party processors).
- Consent and preference settings: opt-ins for features like performance analytics or firmware beta programs which enable feature-specific data collection.
Automatically Collected Data
Data collected automatically as devices and apps operate in real homes. These items support navigation, safety, and service reliability.
- Device telemetry: battery status, motor runtime, error codes used to schedule maintenance and improve product resilience.
- Mapping and spatial data: anonymized floor maps and obstacle positions used to plan cleaning routes and reduce collisions. Maps tied to a device ID and not shared publicly.
- Usage metrics: frequency of cleaning cycles, duration, and feature usage to inform product improvements based on aggregate patterns.
- Connectivity logs: timestamps and anonymized connection quality metrics for remote support and diagnostics.
- Voice command metadata: command text or intent labels to perform actions when the user enables voice control; raw audio is processed locally where possible and only retained when explicitly needed for support.
- System-level identifiers: device model, firmware version, and app version to ensure compatibility and deploy targeted updates.
Third-Party Data Sources
We may receive data from third parties that enhance service delivery or assist with features such as payments and cloud hosting.
- Payment processors: transaction confirmations and limited billing data required to process purchases and refunds.
- Cloud hosting providers: secure storage of anonymized maps and telemetry to ensure scalability and uptime for remote services.
- Integration partners: selected smart-home platforms when users link accounts to enable coordinated scenarios (e.g., pause cleaning during video calls).
Purposes of Processing
We use collected data to operate devices, support users, improve services, and comply with law. Below are practical purposes tied to everyday scenarios.
- Provide core device functions: navigation, scheduled cleaning, obstacle avoidance, and localized routines configured by users.
- Customer support and diagnostics: analyze device logs and communication history to resolve faults in cases such as a stalled motor or navigation anomaly.
- Product improvement: aggregate anonymized usage data to refine algorithms for route optimization and battery efficiency across households.
- Safety and security: detect malfunction patterns that could present safety risks and take preventive measures such as firmware updates.
- Billing and transactions: process payments and refunds related to hardware purchases, subscriptions, and maintenance services.
- Legal compliance: retain records required by law or to respond to lawful requests from authorities.
- Feature personalization: adapt cleaning modes and schedules to demonstrated household patterns when users opt in.
- Communications: send account-related notices, maintenance alerts, and localized tips for optimal device use in Malaysian homes.
Legal Basis for Processing
We rely on appropriate legal bases for data processing depending on the context and user choices, with examples for everyday use.
- Performance of a contract: processing required to deliver features the user requested, such as executing scheduled cleaning.
- Legitimate interests: processing for product improvement, fraud detection, and security measures, balanced against user privacy expectations.
- Consent: where users opt-in to optional features like advanced analytics or voice recording for improved recognition.
- Legal obligations: processing necessary to comply with applicable laws or respond to lawful requests from government authorities.
Cookies and Similar Technologies
We use cookies and similar technologies on the website and web dashboard to support sessions, preferences, and analytics. Practical examples include remembering locale settings and keeping a user logged in for faster device management.
Types of cookies include session cookies for login continuity, preference cookies for language and display settings, and analytics cookies that collect aggregated usage trends.
Cookies are categorized as necessary (core site functions), preferences, performance (analytics), and marketing (third-party integrations). Users may disable non-essential categories via the cookie settings interface.
Manage cookies via your browser settings or the cookie consent manager on BersihNowBot.best. Disabling certain cookies may affect features such as saved schedules or dashboard convenience.
Read the detailed cookie policy at BersihNowBot.best/cookies
How We Share Data
Sharing occurs only when needed to deliver services, support devices, or comply with the law. Examples below show typical recipients and why sharing is required in real cases.
- Service providers: cloud hosting, analytics, and payment processors who act on our instructions to deliver services and maintain uptime.
- Integration partners: smart-home platforms and voice assistants when users choose to link accounts for coordinated behavior.
- Support partners: authorized repair centers that need device logs and warranty information to diagnose hardware faults.
- Legal and safety obligations: disclosures required to respond to lawful requests or to prevent imminent safety issues in household deployments.
- Business transfers: in the event of a merger, acquisition, or asset sale, relevant account and device data may be transferred subject to appropriate safeguards.
- Aggregated and anonymized datasets: used for research and product improvement without identifying individual users or households.
International Data Transfers
Some services operate on global infrastructure, which may involve transferring data to servers in other countries to provide reliable cloud features. Transfers are governed by safeguards such as contractual clauses and industry-standard controls to protect personal data.
We implement contractual protections, encryption in transit and at rest, and limit access to authorized personnel. When transferring data outside Malaysia, we apply appropriate safeguards aligned with applicable regulations.
Data Retention
Retention periods depend on the data type and purpose. Below are practical examples for common categories in household deployments.
Account information is retained for the duration of account activity and for a reasonable period after account closure to support legal obligations and dispute resolution.
Support messages and diagnostic logs used to resolve a specific issue are retained for a limited period (e.g., months) after resolution unless longer retention is necessary for legal reasons.
Telemetry and performance logs used to maintain reliable service are retained in aggregated or pseudonymized form for analysis; detailed logs are kept only as long as needed for troubleshooting.
Users may request deletion of their account and associated personal data. We will remove or anonymize data in line with retention obligations and operational needs; certain records required for legal compliance may be retained longer.
Security Measures
We apply industry-standard security measures appropriate to the sensitivity of data and the operation of robotics and cloud services. Security controls are implemented with a focus on practical outcomes in household scenarios: protecting device access, securing firmware updates, and limiting exposure of mapping data.
- Encryption in transit and at rest for sensitive data such as account credentials and stored maps.
- Access controls and role-based permissions for personnel who manage services or respond to support requests.
- Regular software updates, vulnerability scanning, and incident response procedures tailored to minimize disruption to devices in active home deployments.
User Rights and Controls
Users have rights over their personal data. Below are practical steps and examples for exercising those rights in everyday scenarios with a BersihNowBot device.
- Access: request a copy of personal data associated with your account, such as registered email and device identifiers.
- Correction: ask us to correct inaccurate account details, for example an outdated service address.
- Deletion: request deletion of personal data tied to an account, subject to retention needs for legal or operational purposes.
- Portability: request a machine-readable extract of data you provided, such as configuration and scheduling preferences.
- Restriction: request temporary suspension of processing in certain circumstances, for example during an account dispute.
- Objection: object to processing based on legitimate interests when you believe processing unduly impacts your privacy.
- Withdraw consent: withdraw previously granted consent for optional features like analytics or voice data collection.
- Complaint: lodge a complaint with local authorities if you believe your data rights were not respected; we provide cooperation details for such processes.
How to Make Rights Requests
To exercise any rights, contact [email protected] or use the privacy request form on BersihNowBot.best/privacy. Include your name, account email, device identifier, and a clear description of the request. For requests related to devices in a shared household, specify whether you are the device owner or an authorized user.
We aim to acknowledge requests within 10 business days and provide a substantive response within 30 calendar days. Complex requests may require additional verification and could take longer; we will communicate expected timelines and any required information to proceed.
Compliance and Legal Basis
This privacy addendum explains how BersihNowBot collects, uses and stores personal data when you interact with our smart cleaning robots and AI home helper services in Malaysia. It outlines lawful bases for processing, retention practices, and how we respond to individual rights requests using practical scenarios and case examples drawn from real customer interactions.
- Data we collect: contact details, device identifiers, cleaning schedules, home layout metadata, and anonymized performance logs used to improve navigation and efficiency.
- Purpose of processing: device operation, maintenance scheduling, service notifications, and personalized cleaning routines based on household preferences and past usage patterns.
- Lawful basis: processing is performed to fulfill service contracts, manage customer relationships, and pursue legitimate interests such as product improvement and fraud prevention.
- Retention: transactional records and diagnostic logs are retained for defined periods to support troubleshooting, warranty claims, and compliance; aggregated data retained longer for analytics.
- Data sharing: with trusted third‑party service providers (payment processors, cloud hosting, logistics partners) under contractual data protection terms and for case‑by‑case support with explicit customer consent.
- Rights and requests: customers can request access, correction, restriction, or deletion of personal data. We provide examples and step‑by‑step scenarios to help users exercise these rights.
If you have unresolved concerns about personal data handling, you may contact our Data Protection Officer at the BersihNowBot office address below; for regulatory queries in Malaysia, you may also consult the Malaysian Personal Data Protection Department. Example case: a user requests deletion after activity-in — we outline verification steps, timelines, and records removed.
Marketing communications and preferences
We use contact details to send service notifications and optional marketing about product updates, maintenance offers, and relevant accessories. Marketing messages are based on your explicit preferences and on anonymized usage patterns of your BersihNowBot device. Example scenario: if a household opts in to firmware update alerts, we will send targeted messages about compatibility and scheduling.
To opt out of marketing, use the unsubscribe link in any marketing email, update preferences in your account dashboard, or contact our support team. Case example: unsubscribing via the dashboard takes effect within 48 hours and you still receive essential service and safety notifications.
Children and household members
Our services are not intended for users under 13. We do not knowingly collect personal information from children under that age. In household scenarios involving minors, guardians control device settings and data sharing preferences; example: a parent can restrict mapping data sharing for a device operating in a room used by children.
Third‑party links and integrations
BersihNowBot.best may contain links or integrations with third‑party platforms (voice assistants, smart home hubs, payment gateways). These parties have separate privacy practices. Practical case: linking to a voice assistant enables voice control but sharing of short command transcripts may be required — review the third party's privacy policy before enabling.
Changes to This Policy
We update privacy materials when product features or legal requirements change. Each update includes an effective date; for reference, this version is effective 11-01-2026. Example: when adding a new remote diagnostics feature, we published an FAQ and a migration plan explaining data flow changes and opt‑out options.