Device and Workload Privacy Notice

This notice explains privacy boundaries for Safeera Intelligence Units, marketplace workloads, private AI, support and authorized testing. The responsible company is Safeera, 101 Jefferson Dr., Menlo Park, CA 94025, United States. Contact privacy@safeera.ai. The selected service and configuration determine the actual data flows; publication of this notice does not activate a feature or grant access to a device.

1. Different responsibilities

The account holder controls account permissions, the equipment owner holds the rights stated in the equipment agreement, and a workload customer controls the data it lawfully submits. Those roles may belong to different people. Owning, hosting, leasing or financing a Unit does not automatically confer access to private files, another tenant’s workloads or robot recordings.

For workload information processed on a customer’s instructions, the service agreement and Data Processing Addendum govern Safeera’s role. Account, billing, legal and necessary business-contact records are handled under the Safeera Privacy Policy. A third-party application, lender or independently engaged installer remains responsible for its own activities.

2. Device and service records

When a connected service is enabled, the agreed scope may require the Unit identifier, configuration and software version, connectivity and fault status, operating temperatures, electrical or energy readings, resource availability, allocated usage and service history. These records support scheduling, billing, support, safety and security. A device identifier linked to a household or individual is not automatically anonymous.

Before activation, the service description must explain which categories leave the Unit, their purposes, recipients and retention. Necessary service telemetry is distinct from optional diagnostics and from workload content. A permission to meter GPU-hours is not permission to collect documents, voices or camera feeds.

3. Private and marketplace workloads

Private prompts, documents, models, weights, inputs and outputs remain subject to the customer’s rights and instructions. Local execution means the selected processing occurs on the Unit; it does not imply that every enabled feature is offline. A cloud fallback, external model, remote storage or third-party integration must be disclosed and authorized for the feature before information is sent to it.

Marketplace scheduling authorizes only the accepted workload and data flows. A host must not inspect or retain another tenant’s content. Processing locations, site classes, tenant protections and any authorized subprocessors must match the accepted service. The customer must not send data with restrictions that the selected deployment cannot meet.

Safeera does not receive a general model-training license to private customer content. Any optional program using that content for improvement requires a separate, specific explanation and permission. Refusing such optional use does not remove a service benefit unrelated to it.

4. Remote support and diagnostics

Support access is limited to what is needed for the authorized issue. Additional diagnostic content must be identified before collection, with instructions to remove unnecessary personal information where practicable. Access should be time-limited and attributable to an authorized person or process. A general service visit is not permission to inspect unrelated household data or activate microphones or cameras.

If immediate action is necessary for a legitimate safety or security purpose, it must be limited to that purpose, documented and notified as law and the circumstances permit. Billing or account suspension does not justify unrestricted content access.

5. Robots, cameras and affected people

The person deploying a robot or sensor is responsible for the legal authority, notice and permissions required for its use. A homeowner cannot give blanket consent on behalf of every visitor, worker, neighbor or other person recorded. Limit fields of view, audio collection, retention and access to the authorized purpose.

Facial recognition, biometric identification, clinical processing or collection involving children is not authorized merely by enabling a camera or buying a Unit. Such functions require the applicable specific agreement, legal basis and validated safeguards. Do not upload sensitive information through a general support or contact form.

6. Demonstrations and development testing

Before a Safeera-controlled test involving identifiable people, the test notice must identify the activity and location, sensors or information collected, purpose, recording period, recipients, retention and a contact for questions or rights. Obtain participant consent where required and take lawful steps to minimize bystander collection. Property access permission alone is not consent to indefinite recording or training use.

Research or validation recording must not be silently combined with ordinary customer telemetry. Any use for training must be specifically disclosed and lawfully authorized. This notice does not state that a particular recording program or facial-identification system is operating. A test may not begin without the necessary activity-specific notice and authority.

7. Retention, transfer and removal

The accepted service identifies any stored workload’s persistence, retrieval period and deletion process before use. Ephemeral execution may not retain data after a session; a backup or recovery capability is included only if agreed. Operational, financial and safety records may have different lawful retention periods from private content and must be handled separately.

On return, resale, lease termination or reassignment, remove account access and perform appropriate sanitization before another user receives the equipment. Required safety or legal records may be retained with restricted access; they do not justify keeping unrelated content. International transfers require the applicable safeguards before they occur.

8. Requests, incidents and changes

For account or device information within Safeera’s responsibility, contact privacy@safeera.ai. For a customer’s controlled workload, contact that customer; Safeera will route and assist with requests as its agreement and law require. Identity or authority may need proportionate verification. Applicable rights and response periods are described in the Privacy Policy and law.

Report suspected compromise to security@safeera.ai. Material changes to data purposes, recipients or permissions require notice and any necessary new authorization before activation. A software update cannot silently convert private content into a general training dataset or expand surveillance permission.