Privacy Policy

1Who we are

XiteAI Operating System One (XOS1) is provided by XiteAI Technologies Private Limited (CIN U72900UP2026PTC000000), whose registered office is at Amity Incubation Centre, M Block, Amity University, Sector 125, Noida, Uttar Pradesh 201313, India. For privacy questions, contact [email protected].

2What we collect, and where it lives

XOS1 runs mostly on your own computer. The distinction above is the most important thing in this policy.

Local records. XOS1 stores conversation history, memories, notes, calendar entries, wallet records and generated files on your computer. Voice transcription and biometric-template processing take place locally in the reviewed release. Local storage does not mean that the text is excluded from cloud AI processing.

AI requests. Conversation text and relevant context pass through XiteAI’s gateway to the configured AI provider. Context can include saved memories, app activity, notes or text extracted from an open workspace document. The reviewed gateway relays requests and responses without saving their content as company conversation logs. Temporary processing is distinct from storing an archive.

Service records. Basic check-ins report an install identifier, signing public key, build and app version, operating-system version, device type, language, time zone, update status and crash counts. Network addresses and request metadata may also be processed for access control, security and service operation. Profile sharing can send a name and date of birth; usage sharing can send tool names. Those two optional controls default to off.

Download counters record a timestamp, a hashed network address, available country information and the referring page. These records do not contain your AI conversations.

Information you submit. Support requests contain the contact details, install code and message you provide. Careers applications can include your contact and address details, date of birth, photograph, education, experience, skills, work samples, links, application answers and emergency-contact details. Company accounts also generate authentication and security records. These are company-held records, not an automatic upload of your XOS1 conversation history.

Search terms, market symbols and location queries are sent to the relevant external services when used. The reviewed desktop release does not send raw microphone audio, camera frames or biometric templates through its AI gateway.

Age and guardian information. The intended age-based experience uses the recorded date of birth to choose the appropriate configuration and recognise age transitions. Optional profile sharing with XiteAI is a separate setting; it is not a verified age-check or guardian-consent process. A release must explain whether age and guardian information stays on the device or is sent to XiteAI or a verification provider, and collect only what is needed for the stated purpose. Guardian contact details, consent evidence and activity-access records are not represented here as data already collected by a released parental-control feature.

3Voice and face recognition

XOS1 can learn to recognise you by voice and, when camera features are enabled, by face. It creates mathematical templates rather than storing the template as a raw recording or photograph. Templates can identify a person and must still be treated as sensitive information.

These templates are biometric identifiers and are treated as sensitive personal data. They are:

• stored on your device only, never transmitted to us or anyone else;
• never sold, leased, traded or used for advertising;
• removed by the app’s factory-reset function; this is not a secure wipe of external backups or your disk;

The camera is off by default. With it off, it is never opened, sampled or read.

A recognised name or label may be included in AI context. The voiceprint or faceprint used to make that recognition stays on your device. A recognition label and a biometric template are different kinds of information.

For the beta launch, we intend to make biometric recognition optional, with a separate choice before enrolment and controls to disable recognition or delete templates. These controls must be implemented before the features are enabled for customers. The development build currently learns a voiceprint during onboarding without a separate opt-in, so it does not yet meet that intended launch design.

A child’s biometric enrolment requires its own review of applicable permissions and consent. Accepting general terms, enabling parental controls or allowing microphone transcription does not by itself authorise biometric recognition. A child-facing release must verify the necessary choices and a non-biometric alternative before enabling enrolment.

4Emotional state and tone

The reviewed release analyses characteristics of spoken turns to estimate indicators such as tiredness or energy. The audio analysis runs locally; an interpretation or summary may be included in the cloud AI context. These estimates can be wrong and are not measurements of your mental health.

Separate Emotional Presence and Pulse typing features are built but off by default. Pulse, when enabled, measures timings and counts in XOS1’s own chat box, not a system-wide record of keystrokes. Its local typing profile is separate from a short summary that can accompany an AI request. Planned long-term inference features are not represented as active here.

XOS1 uses AI. It is not a person or a therapist, and its responses are not clinical judgements about your mental state.

Age-appropriate language does not make emotional or behavioural inference lawful for every child or jurisdiction. Before offering these features to children, we must check the applicable restrictions and disable processing that is not permitted. Optional parental visibility is not permission for unrestricted tracking or profiling of a child.

5Who else sees your data

The following services appear in the reviewed development build. This is not a confirmation of the final production provider list. DeepInfra is used for development testing; Cerebras and Groq are being evaluated for the beta launch.

We do not sell your personal data, and we do not share it for advertising.

Our provider requirements. XiteAI’s planned production policy requires zero retention of customer prompts and responses. We will not use customer content for model training or authorise our providers to do so. We are still confirming the applicable agreements, features and account controls, so zero retention is not yet a verified guarantee across every provider we use.

DeepInfra’s published data policy describes no training on ordinary inference content and temporary in-memory processing. It lists separate treatment for some model providers, image-generation outputs and bulk inference. The protections applicable to a request depend on the model and features used, not just the provider’s name.

Cerebras and Groq are candidates, not confirmed production recipients. We will identify the providers used by the customer release and update this notice before enabling those cloud features. Provider selection does not by itself confirm an agreement or an account’s retention settings.

6Why we are allowed to process it

We must provide the notices and obtain any consent required by applicable law before the relevant processing. Listing a lawful basis here does not replace a consent control in the product. India’s DPDP framework has phased commencement; applicable obligations depend on the provisions in force and the processing involved.

Contract acceptance, optional website storage, guardian consent and optional recognition are separate decisions. No single checkbox authorises every purpose. For children, the appropriate basis, notice and any required verifiable guardian consent must be assessed for each relevant data flow, including cloud AI processing.

7How long things are kept

On your device: records follow the app’s local storage and deletion behavior. Factory reset clears the app’s user state, including its conversation history, memory records and biometric templates. It does not securely wipe your disk or erase exported copies or external backups.

With our AI providers: our planned production requirement is zero retention of customer prompts and responses. We are still verifying this for each provider and account. Zero retention of conversation content does not mean that account, billing or service-usage metadata is never retained.

DeepInfra’s published policy separates inference content from operational metadata and describes exceptions for particular models and features. We do not treat a published provider policy as proof of an unverified account setting or an enterprise agreement.

With us: the reviewed gateway does not save request or response bodies as conversation logs. Install/check-in, support, application, account and security records are separate. A single retention schedule for those records and backups has not yet been confirmed; we do not promise automatic deletion after an invented period.

Turning profile sharing off clears the optional profile fields at the next successful check-in. Turning usage sharing off stops future tool reports but does not automatically erase historical check-ins. For deletion requests, see Data Deletion.

Any child-data, guardian-verification or parental-activity records introduced by a release must have a stated purpose and a retention and deletion schedule before collection begins. They must not be kept indefinitely simply because an account remains available. That schedule and the corresponding controls have not yet been verified for the planned parental-control feature.

8Your rights

You can manage local records on your computer separately from requesting access to or deletion of company-held records.

Depending on applicable law, you may request access, correction, deletion, portability or restriction of personal information, withdraw consent, object to processing, or complain to a competent authority. These rights can have conditions and exceptions. We do not sell personal information or share it for advertising; no advertising opt-out is needed for a sale or advertising-sharing practice we do not undertake.

Write to [email protected]. We will respond within the period required by applicable law and may need to verify your identity before acting on a request. We will not treat you differently for exercising your privacy rights.

A parent or guardian may request access, correction or deletion of a child’s company-held information, or withdraw consent, where applicable law gives them that authority. We must verify the requester’s identity and authority before disclosing information or acting on their behalf. Paying for an account does not by itself grant access to its conversations. Required verification must be proportionate to the request; do not send identification documents unless we explain why they are needed and how to supply them safely.

9Security

Data in transit is encrypted with TLS. Your local data sits in your operating system’s user profile, protected by your device’s own account security. Which means anyone who can log into your computer can read it. Put a password on your machine, and encrypt the disk if the contents matter.

If a breach affects your personal data we will notify the relevant regulator within 72 hours where required, and tell you without undue delay.

10Children and age-appropriate experiences

XOS1 is designed for people of all ages, with an age-appropriate experience.

• Under 13. Age-appropriate AI with respectful boundaries. The intended design includes optional parental controls; when enabled, they are intended to give a parent or guardian visibility into the child’s XOS1 activity.
• 13–17. Age-appropriate AI with respectful boundaries. The intended design does not include parental activity-monitoring controls for this age band.
• 18 and over. The full adult configuration, with its broader execution capabilities. The transition is intended to happen automatically when the recorded age reaches 18.

Parental controls and parental consent are separate. Where applicable law requires parent or guardian consent for a child’s personal information, that consent must be obtained before the relevant processing. The absence of parental monitoring for an age band does not remove a legal consent requirement.

The parental-control design concerns activity in XOS1. Before it is enabled in a release, the notice must explain which information a parent or guardian can see, how their access is verified, where the information is processed and retained, and how the control can be disabled. This policy does not promise visibility into everything a child does across their devices.

Children and guardians must receive an understandable explanation of any activity visibility before it is enabled. Turning monitoring off is separate from withdrawing legally required consent or deleting records. If required consent is refused or withdrawn, the affected processing must not start or must stop, subject to applicable legal exceptions; this may make the affected feature unavailable.

An age transition must not automatically enable a camera, enrol biometrics, expand file permissions, turn on optional reporting, authorise a new payment or provide consent for a new use of personal information. A birthday does not automatically erase existing records; their retention and deletion remain subject to the Privacy Policy. The release must also verify that parental activity access ends when the user leaves the under-13 band. Legal guardian-request rights are assessed separately from a product monitoring setting.

Age-specific model boundaries, parental controls and automatic adult-mode switching are part of the intended product design. Their implementation has not yet been verified in a customer release. The Minors Policy gives the full scope. Contact [email protected] about consent, access or deletion of a child’s information.

11Contact, and changes

For privacy requests or complaints, contact [email protected]. Our Grievance Officer is Suraj Verma, reachable at [email protected].

No EU or UK representative has been appointed. This policy does not claim that representative requirements, where applicable, have been satisfied.

We will explain material changes through an appropriate notice before new processing begins and obtain fresh consent where required. Continuing to use XOS1 or browse this website does not by itself provide consent to a new data-processing purpose. An updated notice does not substitute for the controls required in the release.