Privacy Policy

Quantx is responsible for the personal information described here. Our address is 4805 Green Belt Dr, Cedar Falls, IA 50613. Contact support@getquantx.com for privacy questions or requests. This notice covers the Quantx website, consumer apps, account services, and mesh features actually available to you. Proposed products are not described as collecting data before they exist.

1. The distinction between local and remote processing

Local processing means a specified task runs on your device. It does not necessarily mean an entire application is offline or that account, update, diagnostic, or network metadata stays on that device. Remote processing means information needed for a task is sent to another device or service. The recipient and data depend on the route.

The deployment currently supports on-device processing with Quantx Core, processing on your own connected devices, Quantx mesh nodes, and Quantx-operated cloud infrastructure with approved AI infrastructure providers. The interface identifies the applicable route using the mode and status labels shown in the chat and search interface. A request uses remote processing only under the disclosures and permissions applicable to that feature. If a local-only option is offered, its interface explains whether it fails or waits when local resources are insufficient; it must not silently fall back to remote processing.

2. Information we collect and where it comes from

Account information. When you register or manage an account, we collect your email address, password (stored only as a secure hash), optional display name, and account preferences from you and, where you select a sign-in provider, no additional information, because Quantx currently offers only email and password or one-time email code sign-in from that provider. We use this information for access, account administration, communications, and security.

Content and instructions. We process the prompts, selected files, attachments, outputs, and other content you provide. The content sent to our systems or another processor is the prompts, attachments, and outputs of chats and searches that are not run entirely on your device, together with saved chat history for your account. Content that remains exclusively on your device is prompts and outputs processed by Quantx Core on-device mode, which are not sent to Quantx servers. Selecting one file does not authorize collection of unrelated files. Files may include personal information about you or others.

Voice or images. If you activate supported microphone, camera, or photo features, the information collected is only the audio or images you choose to capture or attach, used for answering the specific request you make with them, and processed by Quantx and the AI infrastructure providers listed in this policy, or your device alone when on-device mode is used. Collection begins only after the relevant disclosure and permission. retained only as part of the chat in which you used them, and deleted when you delete that chat or your account describes whether recordings or transcripts are stored. We do not infer that permission to transcribe audio is permission to perform biometric identification.

Device and contribution information. Mesh operation uses a device identifier, device public key thumbprint, platform, software version, and job status, which may include device class, operating-system version, supported runtime, available computing capacity, software version, connectivity, and job status only where actually collected. We collect the confirmed fields to route eligible tasks, enforce resource limits, and maintain reliability. Background access and collection are described in the in-app disclosure before activation.

Network and security records. Connecting to the service can disclose your IP address to Quantx, our hosting and content delivery providers, and our authentication provider, including any peer, relay, or infrastructure recipient actually involved. Our records include sign-in events, IP address, user agent, timestamps, device registrations, and request errors. We use those records for service delivery, fraud prevention, security investigation, and troubleshooting. Approximate location derived from IP differs from precise device location; precise location is collected only when you allow location in your browser or device for location-aware search, used for that request, and not stored with your account.

Usage and diagnostics. We collect error reports, page and feature usage counts, AI action counts, and performance data using our own server logs and hosting provider logs for operating, securing, troubleshooting, and improving the Services and enforcing plan limits. Optional analytics and content-bearing crash reports follow the choices described at Settings, under Data & privacy. The treatment of prompts, files, or outputs in diagnostics is excluded from diagnostics by default. We do not treat removal of a name alone as making a record anonymous.

Payments. Stripe and, for in-app purchases, Apple or Google handle the financial information submitted through their payment interfaces. Quantx receives your plan, subscription status, billing period dates, customer and subscription references, and the country of purchase, such as a purchase reference, subscription state, and information needed for invoices, only where provided. Full payment-card handling by Quantx is Quantx never receives or stores full card numbers. App stores may act independently for their own billing and account operations.

Support and communications. We receive information you send in support requests, privacy requests, feedback, waitlist forms, and other correspondence, together with records of our responses. Avoid attaching sensitive documents unless needed to resolve your request. We use waitlist information for the requested updates and any separately selected marketing purpose.

Connected accounts and workspace data. If you activate an integration or join an organization, we receive the specific data and permissions shown in that connection flow. Tokens, scopes, administrator access, and disconnection behavior are described at Settings, in the connection details for each integration. We do not obtain access to an entire external account merely because you link one feature.

3. How we use information

We use the confirmed categories above to authenticate users; deliver requested AI processing; coordinate supported devices; route and account for eligible mesh workloads; provide outputs and synchronization where enabled; administer subscriptions; respond to requests; prevent abuse; maintain and improve software reliability; meet legal obligations; and communicate service changes.

Optional marketing, analytics, or research uses are limited to service emails you request; Quantx does not currently run optional marketing, analytics, or research programs using your content. We do not use a general reference to service improvement as an undisclosed authorization to train models or expose private content to community nodes.

4. Processing routes and recipients

Your device. Information confined to local processing is not received by Quantx solely because that task runs. Account or network communications related to that session follow the separate practices described above.

Your connected devices. Where enabled, selected information moves between the devices you authorize. Pairing, transfer protection, and removal of a lost or shared device are described in Settings, under Devices, where you can review and remove any device. Other people with access to those devices may have access according to their operating-system and application permissions.

Approved infrastructure and AI providers. The list of providers at getquantx.com/legal identifies confirmed recipients, functions, and processing locations. The information each receives, including any provider retention or model-training use, is limited to the request being processed, under contracts that prohibit using your content to train their models. A compatible API format does not identify the provider or establish its privacy practices.

Community or independent mesh nodes. If this route is enabled, the information sent to those nodes is encrypted, redacted task shards with personal information removed, never your account identity; node operators can access no account identity and only the redacted shard needed for the assigned task; execution and stored-copy protections are signed job assignments, per-device keys, result verification, and automatic deletion of shards after completion; and the participating locations are the countries in which participating devices are located. Read this disclosure before authorizing remote processing. Transport encryption does not by itself prevent an executing device from accessing data it must process. Dividing a job or removing direct identifiers does not by itself establish anonymity. We do not send a class of personal information to this route unless the disclosed legal and technical conditions for that class are satisfied.

Retries and failover. Where enabled and authorized, a task can be retried or duplicated across approved destinations for reliability. The applicable route permissions, retention limits, and deletion requirements continue to apply to those copies.

Public sharing and integrations. When you deliberately publish content or instruct an integration to send it, the named audience or recipient receives it. Such recipients may process it independently. A private session does not become public merely because it uses distributed computation.

5. Other disclosures

We disclose information to vendors performing confirmed functions such as authentication, hosting, support, payments, communications, diagnostics, and security, under appropriate arrangements. Organization administrators receive the access described during workspace enrollment. We may disclose information when required by valid legal process, to protect legal rights or safety where permitted, or in connection with a lawful business transaction subject to continuing safeguards and required notice. We do not disclose an entire account merely because someone submits an unverified complaint.

Our actual sale, sharing for cross-context behavioral advertising, and targeted-advertising practices are none: Quantx does not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. If any such processing occurs, the affected categories, recipients, and opt-out mechanism must be stated here: not applicable, because no such processing occurs. The Privacy Rights page explains applicable choices. We do not equate all operational transfers with advertising sharing, or assume that peer transfers are exempt from statutory definitions.

6. Model training and human access

Our use of Input and Output for training, fine-tuning, evaluation, or general model improvement is none by default: Quantx does not use your Input or Output to train or fine-tune models unless you opt in to a separate program. The practice for external providers is prohibited by contract. Where a separate optional program is offered, its notice identifies the information used, purpose, recipients, retention, withdrawal mechanism, and effect on future use before enrollment.

Human access by support, security personnel, contractors, reviewers, or node operators is limited to authorized Quantx personnel when you ask for support, when needed to investigate abuse or security incidents, or when required by law. Access required for support or abuse investigation is limited to the applicable purpose and controls. Do not interpret a private chat interface as proof that no authorized person or executing node can ever access its content.

7. Retention

Our confirmed retention schedule is:

• Account and profile records: kept while your account is active and deleted within 30 days after account deletion.
• Remotely stored prompts, files, and outputs: kept until you delete the chat or your account.
• Peer job data and temporary caches: deleted immediately after a task completes and in all cases within 24 hours.
• Logs, diagnostics, and security events: up to 90 days, or longer when needed for an active security investigation.
• Billing and tax records: up to 7 years to meet tax and accounting obligations.
• Support and waitlist records: up to 2 years after your last contact, or until you ask us to delete them.
• Backups: overwritten within 30 days.

We retain limited information longer where a specific legal obligation, valid hold, or necessary security purpose requires it; the relevant information remains restricted to that purpose. Deletion from active systems and expiry from backups may occur at different times. On restoration, applicable deletion instructions must be reapplied. A deletion request does not erase copies you exported, lawfully published, or placed under another controller's authority.

8. Choices and privacy requests

Use getquantx.com/contact (topic: Privacy) or contact support@getquantx.com to request access, correction, deletion, or other applicable rights. Account deletion is available through Settings, under Data & privacy, Delete account and getquantx.com/data-export. We verify requests proportionately and do not request unnecessary identity documents. Authorized-agent and appeal instructions appear on the Privacy Rights page.

You can manage supported device permissions through your operating system and revoke integrations through Settings, under Connections. Available contribution controls are described in the Mesh Participation Terms. Stopping new work does not erase records already lawfully retained. Marketing messages include an unsubscribe method; necessary transactional notices are handled separately. Cookie choices are described in the Cookie Policy.

9. Security

The safeguards actually in operation are encryption in transit (TLS), encryption of stored credentials, row-level access controls on account data, hashed passwords, non-extractable per-device signing keys, signed and verified mesh results, and restricted administrative access. They must reflect the information processed, access privileges, and risks of the enabled routes. No system guarantees absolute security. We do not describe general encrypted transport as end-to-end confidential execution or advertise certifications that have not been obtained. Report suspected security issues to support@getquantx.com. We will provide incident notices where required by applicable law or a binding agreement.

10. Children and sensitive information

The service is intended for adults 18 and older. We do not intentionally invite children to create accounts. If you believe a child submitted personal information, contact support@getquantx.com so we can investigate and take appropriate action. This age rule is not a substitute for additional duties if we actually obtain knowledge of children's data.

Do not submit protected health information requiring a business associate agreement, biometric identification data, payment credentials, government identifiers, or other specially regulated data unless an expressly approved feature and the necessary agreement cover it. Incidental sensitive information must still be handled lawfully; a terms prohibition does not remove our responsibilities for information we receive.

11. International use and legal grounds

The service is offered in the United States and other countries where the Services are made available. Storage and processing occur in the United States. Geographic restrictions for mesh work are applied where a feature or workspace requires a location restriction; otherwise tasks may be routed to eligible devices in any supported country. A global network description is not a representation that data can lawfully be transferred to any country.

If EEA, UK, or Swiss data-protection law applies, the confirmed purposes and legal grounds are contract necessity to provide your account and requested features; legitimate interests for security, fraud prevention, and service operation; legal obligation for tax and billing records; and consent for optional features such as location or mesh contribution. Contract necessity applies only to processing objectively necessary for the requested service; legitimate interests require an applicable assessment; consent applies only where valid and can be withdrawn for future processing. International-transfer mechanisms, where required, are the European Commission's Standard Contractual Clauses and the UK addendum, copies of which are available from support@getquantx.com. Applicable representative and DPO details are not appointed at this time; contact support@getquantx.com.

The Privacy Rights page describes regional rights. No statement here waives mandatory protections or declares universal compliance with every privacy law.

12. Changes and contact

We will update the effective date when this notice changes and give additional notice or obtain permission where law requires. We will not treat a website update alone as permission to use previously collected data for an incompatible purpose.

Privacy contact: support@getquantx.com. Postal address: 4805 Green Belt Dr, Cedar Falls, IA 50613. If your issue concerns an organization-controlled workspace, we may need to direct the request to that organization while assisting as required.