> For the complete documentation index, see [llms.txt](https://docs.askdodo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askdodo.com/legal/privacy-policy.md). # Privacy Policy Information processing, current authentication boundaries, and your choices. Effective Date: August 17, 2026 Technical description updated: October 5, 2026. This update corrects the descriptions of account authentication, Credits, and browser storage; it does not introduce a new legal entity or change the rights described below. This policy explains the information askDodo processes, the boundaries of our privacy architecture, and the choices available to you. ### Scope and who we are This Privacy Policy explains how askDodo (“askDodo,” “we,” “us,” or “our”) handles information when you use askdodo.com, our APIs, account and payment surfaces, and related services (the “Services”). askDodo separates upstream AI request payloads from account and payment information. The gateway still receives the authentication needed to admit and bill a paid request. The exact privacy properties of an AI request depend on the model route used and the live privacy metadata published for that route. ### Information we collect Depending on how you use the Services, we may process: * Content you submit. Prompts, files, tool inputs, and other content you choose to send, together with generated responses and request metadata needed to provide the request. * Account and support information. Email address, authentication data, communications, and information you provide when requesting support. * Payment information. Purchase, balance, billing, and transaction records. Card details are handled by our payment processor when card payments are offered; askDodo does not receive full card numbers. * Device and usage information. Browser and device type, approximate location derived from IP address, referrer, coarse page paths, and interaction events. Our first-party analytics event code is designed not to include prompt text or local conversation identifiers. * Device-local information. Encrypted conversation history, drafts, preferences, and recovery state may be stored locally in your browser or device. The current Account Credits balance is maintained by the service, not by browser-held spending proofs. * Guest-device identifier. Where guest requests are enabled, a pseudonymous guest-device identifier is stored locally and sent with those requests for quota and abuse prevention. It is not an account identifier. ### How we use information * Provide, secure, maintain, and troubleshoot the Services. * Route AI requests, calculate usage, settle Credits, and prevent fraud or abuse. * Process purchases, respond to support requests, and communicate service changes. * Understand site performance and improve product usability. * Comply with law and enforce our Terms of Use. ### AI requests and privacy boundaries When you submit a request, the content is transmitted to askDodo’s gateway and to the model or tool route needed to complete it. Website account session cookies remain at the same-origin authentication boundary. Paid Web Auto requests send an Account access JWT to gateway ingress for admission and billing; omitting browser cookies does not mean that the gateway receives no account authentication. The inference contract excludes account identity, payment information, and authentication credentials from upstream model/provider payloads. This is not a guarantee that all gateway, operational, or billing records are unlinkable. askDodo publishes two route privacy tiers—“anonymized” and “private”—and separate capabilities such as TEE attestation or E2EE. One field should not be inferred from another. On “anonymized” routes, upstream providers process the request content without receiving an account identity from askDodo’s inference request. The “private” tier is separate. Review the [live model catalog](https://gateway.askdodo.com/v2/models) and the [documented evidence boundary](https://docs.askdodo.com/guides) before relying on a privacy claim. A tier or capability label alone is not cryptographic verification. ### How we disclose information We may disclose information to: * AI model and tool providers required to complete a request. * Hosting, security, analytics, support, and payment service providers. * Authorities or other parties when required by law or needed to protect rights and safety. * A successor in connection with a merger, financing, acquisition, or sale of assets. Our first-party analytics event code is designed not to include prompt contents. Advertising and analytics technologies may be considered “sharing” under some privacy laws; see our [Cookie Policy](https://docs.askdodo.com/legal/cookie-policy) for the tools currently used and the browser or provider controls available to you. ### Retention and security Device-local information remains on your device until you remove it, clear browser data, or replace the device. Clearing local history does not itself delete the server-managed account balance. We retain account, billing, support, security, and operational records only for as long as reasonably needed for the purposes described here, including legal, accounting, dispute, and abuse-prevention requirements. Supported document parsing can transmit an original file to the parsing service. Temporary-file cleanup is not a promise of zero retention across every proxy, log, backup, generated asset, or provider. We use technical and organizational safeguards designed to protect information. No system is perfectly secure, and you are responsible for safeguarding account access, device-local recovery material, and access to your devices. ### Your choices and rights Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing, or to receive a portable copy of personal information. You may also withdraw consent where processing relies on consent. You can clear device-local data through the product or browser controls and manage cookies as described in our Cookie Policy. To make a privacy request, email . We may need to verify your request. ### International use and changes The Services and our providers may process information in countries other than where you live, where different data protection rules may apply. We will use transfer mechanisms required for a particular transfer before making it. We may update this Policy as the Services or law changes. We will update the date above and provide additional notice when required. Questions can be sent to .