Privacy

Privacy Policy

This policy explains analytics and browser preferences on the Just One API website and documentation, including your choices and the information used to understand visits and article referrals.

Last updated: November 11, 2026

Scope

This policy covers optional public-page analytics and shared browser choices on justoneapi.com, docs.justoneapi.com and dashboard.justoneapi.com. Account, billing, and API-request processing in other Just One API services also use operational systems. Refusing analytics does not prevent login, registration, payments, or API use and does not delete business records already created.

Links on this website can take you to the Dashboard, documentation, GitHub, Telegram, email, and other external services. Those destinations may apply their own privacy notices.

Information collected

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.

Basic advertising registration attribution allows Google to process advertising cookies, click identifiers, IP addresses, device information and page/registration events, and allows GA4 registration events to be shared with our existing linked Google Ads account. The advertising choice is separate from ordinary analytics and depends on analytics also being allowed. This choice does not authorize enhanced matching of email, phone, name or address data. Existing Google automatic-detection configuration is retained; this release does not enable a new user-provided-data or enhanced-conversion receiver, accept additional data terms, create customer lists or enable personalized advertising. The application page/sign-up payloads do not contain form values. Ordinary analytics may still produce Google analytics or restricted cookieless signals when advertising is refused; refusal is not a promise of zero Google requests or zero modeled reporting.

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.

Cookies and browser storage

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.

How information is used

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.

Data transmission and external services

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.

Google may process measurement information outside your country. Google Analytics standard terms identify Google LLC as the service provider. Details of Google services, receiving entities, processing and privacy-rights contacts are available in the Google Analytics terms and Google privacy policy.

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.

Retention

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.

The shared joa_measurement_choice cookie stores only notice version, selection/expiry timestamps and analytics/advertising purpose bits for up to 180 days; the legacy preference coordinated by a new explicit choice uses the same lifetime. It contains no IP, country, account identity or click ID. A small same-origin policy read returns only the applicable purpose rules, receiving eligibility and versions, uses no browser credentials or referrer, and is not stored by the endpoint. Unknown regions are not treated as globally approved defaults.

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.

Your choices

For source attribution, public-page/article statistics, GA4 and documentation Clarity managed by this panel, visitors classified by the platform as being in the EEA, UK or Switzerland are asked for explicit choices before the corresponding optional measurement runs, including a separate advertising choice for basic registration attribution. In mainland China, ordinary analytics and basic Google advertising registration attribution are enabled by the site's regional default settings unless you have refused or another safeguard applies; no automatic choice prompt is shown. You can change or reject these purposes through Privacy and statistics. Other recognized regions retain the existing ordinary-analytics rules without a new advertising default. Unknown or failed region-policy responses do not grant permission. Region classification is not stored in the shared choice cookie.

Use Privacy and statistics to accept all, reject optional measurement or manage analytics and advertising purposes separately. Each purpose follows its own rules. A single prompt is shown only when an active purpose requires your current choice; a Google advertising referral alone does not trigger it. Ordinary analytics follows its existing rules and saved preferences. Unverified advertising rules or receiving conditions keep advertising off or paused without, by themselves, stopping otherwise allowed analytics. A disabled advertising purpose remains off even if an advertising preference is saved. If the complete policy is unavailable or the shared choice cannot be validated, the applicable safeguards keep collection paused. A regional default is a site setting, not a record of visitor consent. Browser Do Not Track, Global Privacy Control and prior refusal take precedence. Old analytics permission is not consent to new advertising purposes. 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 and a sign-in link. After signing in, return to that panel and retry; signing in alone does not confirm that an account choice was saved.

Allowing browser analytics later does not undo an account refusal that was saved. Contact support for help reviewing an account preference; signing in alone does not confirm or revoke an account refusal. 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.

Security

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.

Updates and contact

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.