Privacy Policy
Effective and last updated: October 22, 2026
This policy explains information handled when you visit quantaphi.org or use QuantaPhi services, including research and media tools, Bubbles AI, and wallet/token features. The site is operated as the QuantaPhi project. Different features have different data flows; some features are experimental or depend on third-party providers.
Important: QuantaPhi uses Google Analytics and includes Google AdSense advertising code. A page may contact Google even if no advertisement is visible. This privacy notice is not a cookie-consent control.
1. Information we handle
- Visits and technical logs: IP address, browser and device type, approximate region inferred from network information, URLs requested, timestamps, referrer, errors and security signals may be processed by our hosting/CDN services (including Cloudflare) and analytics providers.
- Searches and interactions: Searches, refinements, selected cards, media actions, favorites/collections and related research metadata may be sent to search, AI, content and ledger services to return results, restore history, prevent duplicate credits, or calculate activity-linked tokens. Exact handling varies by feature.
- Account and wallet activity: If you connect a wallet or account, QuantaPhi services may process account/device identifiers, authentication tokens, wallet IDs, balances, ledger events, timestamps, receipts and transaction references to identify the correct account and maintain history. These records may be stored in Cloudflare-hosted databases.
- Bubbles AI and creative content: Messages, prompts, context supplied to assistants, notes, selected files, media and tool requests may be transmitted to AI or infrastructure providers to provide the requested service. If you enable Bubbles memory, conversation history and notes may be stored locally and, when you separately enable connected private sync, in a wallet-associated cloud memory service. Do not include secrets or sensitive personal information unless needed and you accept the risks.
- Browser-stored information: QuantaPhi uses browser local storage and IndexedDB for preferences, drafts, saved cards, images, pending activity receipts, wallet connection state, and optional Bubbles memory. Some data stays on that device; other data is synced only by the particular feature's network behavior.
- Permissions and media: Microphone, camera, screen capture, recordings, device storage, notifications or Android accessibility features may be used when a corresponding feature is enabled and the device grants permission. Access to a device capability is separate from whether a recording, transcript or chosen file is sent to a cloud service. Review the feature's controls before enabling it.
- Messages to the project: If you contact the operator or submit feedback, the information you choose to send and necessary reply details may be used to respond and investigate issues.
2. Why information is used
Information is processed to deliver searches, research, AI answers, media playback and creation; preserve account, token and saved-work records; synchronize user-requested data; secure systems against abuse; monitor errors and usage; improve functionality; and, where enabled, display and measure advertising. Not every feature is fully deployed or available to every visitor.
3. Google Analytics, AdSense and advertising cookies
QuantaPhi includes Google Analytics measurement code and Google AdSense advertising code. Google and other third-party vendors may use cookies, web beacons, IP addresses and other identifiers to collect information when people use this site, including information about visits and ad interactions. Google uses advertising cookies to serve or measure ads based on a person's previous visits to this site or other sites. Depending on settings, advertising may be personalized or contextual. Advertising providers may place and read their own cookies or use comparable technologies.
You can manage Google ad personalization through Google My Ad Center / Ads Settings, and may opt out of participating third-party vendors' interest-based advertising through AboutAds. Learn how Google uses information from partner websites and read Google's Privacy Policy. Browser settings may also block or delete cookies, but doing so can affect website features. Non-personalized advertising can still use identifiers for measurement, fraud prevention or frequency limits.
If other ad or affiliate networks are enabled later, their data use and choices must be disclosed before use. Advertisements and sponsored offers are not the same as users' wallet transactions.
4. Services that may receive data
Depending on the action taken, data may be shared with hosting providers such as Cloudflare; Google Analytics and Google advertising services; search and AI model providers; media hosts; account/wallet integrations; and services you explicitly choose to connect, such as GitHub. Opening external content or following an external link makes that provider's own terms and privacy practices applicable. QuantaPhi does not control those independent services. Data supplied to an AI service may be processed according to that provider's terms and configuration.
Features exploring token exchange or business-use research data do not by themselves establish consent to share a private profile. Check the details of any future opt-in sharing or marketplace feature before using it; this policy does not promise that all submitted data always stays solely on your device.
5. Storage, security and retention
Locally stored data can remain until you clear it, remove the app, or a feature deletes it. Cloud wallet/ledger records, synced Bubbles history, service logs and backups may be retained for operational, security, accounting or recovery needs. Retention periods differ by system and are not represented here as having one universal automatic deletion deadline. We use available platform security and access controls, but no service can guarantee absolute security. Do not expose wallet credentials or private authentication tokens.
6. Your choices and requests
- Use browser settings to manage cookies or delete local website data, knowing that doing so may remove local drafts or sign-in state but does not necessarily delete records stored in cloud ledgers or third-party systems.
- Use available Bubbles memory settings to disable saving or request deletion of stored memory where that feature supports it. Local deletion and cloud deletion are not always the same action.
- Disconnect optional integrations and revoke microphone, camera, screen or other device permissions in browser or Android settings.
- Ask the operator about access, correction or deletion of personal information, subject to account verification, legal requirements, and technical limitations. Some immutable transaction or security records may need to be retained.
- Use the Google and AboutAds choices linked above for personalized advertising. Where consent is required by applicable law, the site must also provide the necessary consent controls; publication of this policy alone does not provide them.
7. Children
QuantaPhi is not directed to children under 13. Children should not submit personal information or use connected account, wallet or advertising features without appropriate adult supervision and any consent required by law. If you believe a child has submitted personal information, contact the project operator.
8. Privacy questions and contact
For project information, see About QuantaPhi. The project is maintained through the QuantaPhi project owner's GitHub profile. Use a private contact option offered by the operator for sensitive privacy requests, if available; do not post personal data, account credentials or private transcripts in public GitHub issues. A dedicated privacy-request email or secure form has not yet been published.
9. Changes to this policy
This policy may change when QuantaPhi adds or changes data practices. Material updates will be reflected here with a new effective date. If a feature requires a separate notice or legally required consent, that notice or consent must be provided in the feature itself.