Privacy Policy

When analytics is allowed on a public page, we may read or create random browser identifiers and record the public destination path, a landing URL with permitted campaign parameters, the origin of an external referrer, source and campaign classifications, and a capture time. Sensitive account or authorization pages do not create new source or article activity records.

Landing URLs retain only permitted campaign parameters. Attribution fields can include utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, fbclid, and ttclid. The website preserves first-touch and last-touch attribution snapshots in browser cookies.

Google Analytics 4 receives permitted public-page views, browser/session identifiers, a sanitized page address and referrer, and a title derived from the public path. Article statistics sent to our API contain a published article ID, slug, language, event type, random event/page-view identifiers, browser identifier, and time. They record article views and selected documentation, Dashboard, and registration link clicks, without full URLs or form contents.

The documentation can use Microsoft Clarity to understand public-page interactions. The API tester and generated-code dialog are masked for Clarity. Masking does not mean a page produces no technical analytics data; recording is also governed by your analytics preference and sensitive-page controls.

When you select a language, the website stores that preference in your browser. If you contact us through email, Telegram, WeChat, or another linked channel, you choose what information to provide and that communication also passes through the selected provider.

The website uses the first-party cookies visitor_id, joa_utm_visitor_id, joa_utm_attr_first, and joa_utm_attr_last. They identify a browser for source attribution and preserve first- and last-touch details.

joa_utm_attr_ack and joa_utm_attr_retry store delivery acknowledgements and retry metadata. A saved analytics preference is shared across Just One API subdomains. Google Analytics and Clarity can use their own analytics cookies when allowed. Website article events can temporarily use localStorage keys beginning with joa_article_event:, limited to 100 pending events and 30 days.

These cookies are configured with a browser lifetime of up to 365 days, SameSite=Lax, and Secure when the page uses HTTPS. On Just One API hosts they can be scoped to .justoneapi.com. Your browser settings or manual deletion can remove them earlier. This browser lifetime does not state how long any server-side record is retained.

The website stores a language you explicitly select in the host-only first-party Cookie joa_website_locale. It is configured with a browser lifetime of up to 365 days, Path=/, SameSite=Lax, and Secure when the page uses HTTPS. If this Cookie is absent, a request to the root URL uses the browser's Accept-Language header to choose a localized page without saving the inferred language.

Earlier versions stored the language preference under justoneapi:preferred-language in localStorage. If that legacy value exists and no language Cookie has been set, the website can read it once, copy a valid preference to the Cookie, and remove the localStorage value after the Cookie is saved.

Visit-source and attribution records are used to understand how visitors reach the website, associate a browser with first- and last-touch campaign information, distinguish direct and referred visits, and evaluate acquisition paths. The saved language value is used to choose or preserve your preferred localized experience.

The website also uses the destination path and attribution context to keep source records consistent as you navigate. This policy does not claim that the collected fields are used for purposes not reflected in the website behavior described above.

The website sends visit-source and attribution payloads to API endpoints hosted at api.justoneapi.com. Cookies scoped to .justoneapi.com can be available to Just One API subdomains according to browser cookie rules.

When you follow an external link or use an external communication provider, that service receives the request and may receive referrer or other technical information according to your browser and the provider's rules. Review the relevant provider's privacy information before submitting sensitive data.

Attribution and language-preference cookies are configured for up to 365 days. Pending article events are limited to 30 days and 100 events. Refusing browser analytics removes analytics identifiers and unsent browser queues; choosing to allow later begins future activity without replaying those removed events. Information already sent and business records are not automatically erased by this browser preference. Server-side retention and deletion requests are handled separately.

For current information about a server-side record or a retention request, contact support and include enough context to identify the relevant browser identifier or communication, without sending passwords or API tokens.

Use Analytics preferences in the website or documentation footer to allow or refuse analytics without leaving your current work. Browser Do Not Track and Global Privacy Control refusal signals take precedence. An undecided or unavailable consent state pauses collection; when no refusal or pending signal is present, the current default remains allowed. Allowing again affects future activity only.

You can also block or delete cookies through your browser. Language, authentication and other storage needed for a requested service are separate from analytics. Your analytics choice does not alter Cloudflare edge security or operational logging.

A browser refusal on the website or documentation also attempts to save a refusal of account recharge analytics through a restricted Dashboard connection using your existing Dashboard login session. This connection sends a refusal instruction, without visit-source or analytics identifiers, and does not carry the current page address as a referrer. Browser refusal takes effect immediately; an account refusal is confirmed only when the Dashboard reports that it was saved. If you are signed out, the connection is blocked, or a request fails, the preference panel keeps the account status unconfirmed and offers a retry or a Dashboard confirmation link.

Allowing browser analytics later does not undo an account refusal that was saved. To re-enable account recharge analytics, sign in and explicitly confirm the account setting in the Dashboard. Business history remains separate from these analytics choices.

Removing campaign or click-ID parameters before visiting limits what appears in a new landing URL, but it does not undo information already sent when a page loaded. Subject to applicable law, you may contact us to ask about access, correction, or deletion of information associated with you; we may need enough information to locate and verify the request.

No browser storage, network transmission, or server system can be guaranteed completely secure. Do not place passwords, API tokens, or other secrets in landing-page query parameters or messages sent through an inappropriate channel.

We may update this policy when the website or its information-handling behavior changes. The date at the top identifies the latest posted version.

For privacy questions or requests, contact support@justoneapi.com or use the contact page. You can also review the Terms of Service.