This Privacy Policy explains what information Amble processes, why it is used, and how to contact us about your information. It covers both the website and the app, whose data practices differ.
1. Who we are and what this covers
InterX Network Inc., registered in Delaware, United States (“InterX,” “we,” “us,” or “our”), develops and provides Amble. We are responsible for the purposes and means of processing we control. You can contact us at lukeyang@intermix.space or the address in section 11.
Viewing the website does not create an app account, activate a microphone, authorize Google access, or upload an app conversation. The app is intended for adults aged 18 or older in the United States.
Amble is currently in development. Public app registration and Google and Apple sign-in are not yet available in the current build. Section 2 describes the limited sign-in integration we are preparing and applies when that option is offered. A description of a feature does not mean it is available today.
2. Google sign-in and account information
Information used for Google sign-in
When Google sign-in becomes available and you choose it, Google authenticates you and provides information used to create or access your Amble account. The integration is limited to the basic openid, email, and profile permissions. These can provide:
- A stable Google account identifier, used to associate the sign-in with the correct Amble account.
- Your email address and its verification status.
- Your name and other basic profile information, when Google supplies them.
- Authentication tokens and token metadata needed to validate the sign-in and establish a session.
Google’s response or sign-in software may also include basic profile fields such as a profile-picture URL. We do not need your Google photo for authentication: our sign-in design does not download it or save a profile-picture URL to your Amble account. Receiving a field temporarily is different from keeping it in an account record.
We do not receive your Google password. Basic sign-in does not authorize access to your Gmail messages, Google Drive files, Google Calendar events, contacts, or photo library. We do not request those permissions for sign-in.
How Google information is used
Google account information is used for identity verification, account creation and access, account information shown to you, and account security. We do not use it for advertising, sell it, or use or voluntarily provide it to train general-purpose AI or machine-learning models.
We do not automatically send Google-provided account identifiers, email addresses, names, or profile data into AI conversation prompts. A name or other information you choose to provide within Amble can become part of your conversations and be processed for that purpose, as explained in section 3. Signing in does not itself supply your Google profile as conversation context.
Authentication providers, our account infrastructure, and necessary service providers process relevant account information to deliver and protect sign-in. We limit that use to the purposes described here. Google also processes your sign-in under its own Privacy Policy.
Amble’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including applicable Limited Use requirements. If we introduce another use or request additional Google permissions, we will explain it and obtain any required authorization before doing so.
Other account information
Amble account records can contain an internal identifier, sign-in provider and provider identifier, display name, email when available, account time zone, device identifier, and session information. Preferences include appearance, companion name, personality and communication settings, and other selections you make in the app.
If Apple sign-in is offered, Apple may provide an account identifier, a name, and an email address, including an Apple relay address. We do not receive your Apple password. Account information is used to provide and protect your account. We do not automatically merge different provider accounts solely because their email addresses match.
3. Conversations, memory, and information you share
Live audio and conversation text
When you permit microphone access and activate an audio session, your speech is transmitted and processed to generate real-time conversation. Generated audio is returned for playback. The current Amble application does not persist raw audio recordings in its own storage. Temporary processing and transmission still occur, including processing by external AI services.
Amble saves text representing both your speech and Amble’s replies, with conversation and timing information. A transcript is a machine-generated interpretation and may be inaccurate. Text can remain after an audio session ends. Our application not storing raw audio is not a promise of zero retention by every provider.
Memory, notes, and inferences
Amble processes conversations to maintain selected facts, preferences and ongoing topics, create daily notes, and retrieve relevant context. Retrieval indexes may contain numerical representations of text, called embeddings. These are associated account data, not automatically anonymous information.
Conversations may include sensitive information such as relationships, emotions, health, or beliefs. That information may also appear in memories, notes, and inferences. Inferences can be inaccurate. Relevant saved text, memories, and preferences may be supplied to an AI provider as context for a later reply.
Queries and support
If you request outside information, we process the query and relevant details, such as a city mentioned in a weather request. Answers, source links, and task status may be saved with the conversation.
If you email us, we process your contact details and the contents of your message to respond and handle the request. Avoid sending unnecessary sensitive information, passwords, or sign-in tokens. The website has no account-registration, newsletter, content-upload, or contact form.
4. Technical information and website visits
The app maintains operational information such as session identifiers, activity dates and durations, selected settings, task outcomes, errors, and usage accounting. This supports reliability, security, service allowances, and prevention of duplicate work. Limited account and session information may also be stored on your device.
Network, hosting, and delivery services receive connection information such as IP address, browser information, request time, and requested address when serving a page or handling a connection. Operational or security records may be processed for delivery, troubleshooting, and abuse prevention.
The website serves its own fonts and visual assets. It does not add advertising pixels, third-party analytics, tracking cookies, fingerprinting, or cross-site advertising identifiers. Animation does not access your microphone or app account. Browser preferences such as reduced motion are used locally to adapt presentation.
The current app does not request access to your contacts, photo library, camera, system calendar, or precise GPS location. Amble’s calendar view indexes its own conversations and notes. A location you share in a conversation can still be processed as conversation content and used for a relevant query.
5. Purposes and limits on use
We process relevant information to:
- Provide account access, maintain account records, and protect sessions.
- Generate voice replies and maintain continuity across conversations.
- Create notes, maintain memories and preferences, and retrieve context.
- Carry out requested searches or weather lookups.
- Maintain reliability and security, apply service allowances, and respond to support and privacy requests.
- Comply with legal obligations and address lawful requests or disputes.
We do not sell private conversations or Google account information, use them for advertising, or voluntarily provide them to third parties for general-purpose model training. Remembering information for your own conversations is a service function, distinct from training a model for general use. Amble has no voluntary conversation-donation or model-training program.
Microphone or sign-in permission does not authorize unrelated uses. Where additional notice or consent is required, this policy does not replace it. We will explain material changes in data use and obtain required consent before introducing them.
6. Providers and other disclosures
Service providers
The current implementation uses OpenAI for AI processing, including live conversation and functions supporting notes, memory, retrieval, and public-information search. Requests can include audio, relevant conversation text, selected memories, and preferences needed for the requested function. The Google account-data limits in section 2 apply separately from information you voluntarily share in a conversation.
The weather implementation can use Open-Meteo for place lookup and forecasts. A weather provider receives relevant query information, such as the requested place, rather than needing an entire conversation.
Authentication, hosting, storage, network delivery, and email services may process relevant information needed to provide their functions. If you contact the listed email address, the email services involved process your message. We limit disclosures to what is needed for the relevant purpose, subject to applicable law and service arrangements.
Providers may retain some data for service operation, security, abuse prevention, or legal compliance under their applicable terms. We do not promise zero provider retention or that no authorized person can ever access information. Necessary personnel access for service delivery, support, security, or legal obligations must be limited to the relevant purpose. It does not permit advertising or unrelated model-training use by InterX.
Legal, safety, and business circumstances
We may disclose information when legally required or when permitted and reasonably necessary to investigate misuse, protect rights, or address a serious safety threat. This is not a promise of continuous monitoring or an emergency-response service.
If a merger, acquisition, financing, or similar transaction involves information, appropriate protections and applicable legal requirements continue to apply. A transaction does not itself authorize a new, incompatible use of private conversations or Google data. Required notices and permissions must be addressed.
7. Retention and deletion
Account identifiers, profile fields used for the account, and preferences are retained while needed to provide and protect the account. Authentication information is used for validating sign-in, maintaining sessions, and security; it is not retained for unrelated use. Conversation text, memories, notes, and retrieval indexes are designed to remain available until deletion is requested or they are otherwise removed under applicable retention requirements.
Support correspondence and operational records are retained only as needed for the request, service operation, security, or a legal obligation. Retention depends on the type of record, its purpose, and applicable law. We do not promise a single retention period for all records.
You can request deletion by emailing lukeyang@intermix.space. In-app self-service deletion and export are not currently available. We may need to verify your identity or authority and clarify the request before acting. We will respond in accordance with applicable law and explain the request’s status, any lawful exceptions, and relevant next steps. Sending a request does not itself confirm that deletion has completed.
Deletion must address relevant account records, source conversation text, notes, derived memories and indexes, and pending processing. Copies on an offline device may require that device to reconnect. Where backup copies exist, removal may follow the backup lifecycle rather than occur at the same time as active-record deletion. Backup and exception handling must remain limited to their lawful purpose; they are not permission to retain conversations for unrelated use.
Limited records may be retained when required by law or reasonably necessary for security, fraud prevention, or resolving a dispute. Where an exception applies, we will explain it as required by law. Deletion is not instantaneous; timing depends on identity verification, the records involved, and applicable legal requirements.
8. Your choices and requests
You can control microphone permission through device settings and pause an active conversation. These controls affect future audio activity, not information already saved.
You can manage a Google sign-in connection through your Google Account’s third-party connections. Removing that connection does not itself delete your Amble account or data. Signing out or uninstalling Amble also does not erase server records. Contact us separately for a deletion request. If Google is your sign-in method, removing the connection can affect how you access the account.
Depending on your location and applicable law, you may have rights to know about or access information, obtain a copy, correct inaccuracies, request deletion, limit certain processing, or appeal a decision. You can submit these requests, or an appeal where applicable, to lukeyang@intermix.space. State the type of request and enough information to identify your account without including a password or token.
We may verify identity or an authorized agent’s authority using information proportionate to the request. We will respond within the periods required by applicable law and explain any permitted extension or refusal. An unfinished self-service feature does not remove rights provided by law. We will not discriminate unlawfully against you for exercising a privacy right.
9. Adults and sensitive information
The app is intended for adults aged 18 or older, with the United States as its initial market. We do not knowingly offer it to minors. If you believe a minor has provided information through the app, contact us so we can assess and address it, including removal where appropriate.
Conversation can reveal sensitive information even when Amble is not providing healthcare. Applicable protections for that information still apply. Additional notices or permissions may be required for particular uses or locations and will be provided where required.
Information may be processed in locations where InterX and its service providers operate, including the United States. We do not promise U.S.-only processing or storage. Applicable legal requirements continue to govern transfers and processing.
10. Security and policy updates
We use account separation, access controls, and restricted handling of service credentials to help protect information. Provider keys are handled by backend processes, not included in the website or app client. We work to apply safeguards appropriate to the information and service, including protection of data in transit and at rest. No system guarantees absolute security.
Amble is not end-to-end encrypted between you and the AI: external services must process relevant content to provide the described features. We do not claim that providers cannot access information they need to process.
We may update this policy as the Services change. The date above identifies the latest revision. Material changes will be communicated through suitable notice, and we will obtain additional consent where required before using information for a new purpose. Updating this page alone does not authorize an incompatible use of previously collected information.
11. Contact
InterX Network Inc.
Registered in Delaware, United States.
Mailing address: 125 Avento, Irvine, CA 92602, United States.
Support email: lukeyang@intermix.space
Privacy requests email: lukeyang@intermix.space