1. Storage actually used
DataXAPI uses browser storage for authentication and continuity, including localStorage, which can survive browser restarts, and sessionStorage, which normally belongs to a tab session. These differ from cookies and server-side Usage records.
| Category | Content and purpose | Retention and clearing |
|---|---|---|
| Authentication | Supabase session and refresh information to maintain sign-in | May survive restarts; removed by sign-out, authentication-library cleanup or manually clearing site data. The authentication service determines continuing validity |
| Playground operation | Submitted request text and idempotency identifier to continue an operation after refresh | Tab sessionStorage; relevant sign-out flows clear it, as can clearing site data. Browser session restoration may preserve it |
| Top-up operation | Selected quote/amount and original-order idempotency identifier to avoid accidental repeat orders | Tab sessionStorage; cleared when handling payment-return state or relevant account sign-out, or manually |
| Security verification | Browser, network and verification signals when Cloudflare Turnstile is enabled, to resist automated abuse | Managed by the actual security and authentication services; not DataXAPI advertising cookies. Refer to the applicable service information |
| Payment pages | Data needed by Stripe and the selected method for payment, security and fraud prevention | Governed by those payment pages’ actual cookie/storage rules, not falsely assigned DataXAPI retention settings |
Playground text can include your queries and links. Do not enter secret credentials or unnecessary personal information. On shared devices, sign out and clear site data after use. Closing a page alone does not guarantee deletion of persistent session information.
2. Analytics and advertising
The current website has no advertising tracking or browser behavioral analytics and does not set the corresponding non-essential tracking cookies. When configured, the API server may send redacted call events to PostHog, such as endpoint, duration, result category and charge status. This server-side processing does not automatically stop when browser cookies are disabled. See the Privacy Policy.
If future non-essential browser storage requires consent, we will disclose its purposes, recipients and duration and provide choices and withdrawal. Continued browsing will not be misrepresented as a legally required separate choice.
3. Controls
Use browser settings to inspect, block or clear cookies and storage. Clearing authentication storage signs you out or requires verification again. Clearing playground or top-up storage can remove information needed to continue an operation. For an unknown payment result, check the order first rather than clear storage and pay again. Clearing browser data does not revoke server-side API keys, cancel orders or request refunds. Global sign-out revokes refresh sessions, but issued access tokens may remain valid until expiry. Separately revoke API keys if you suspect exposure.
Contact privacy@dataxapi.com about storage or personal information.