Privacy policy

This policy explains how JS.GRIPE handles website visits, optional discussions and analytics, and how to change your choices or ask us to remove information.

Operator: 技述 / JS.GRIPEPrivacy contact: helper@js.gripe

Reading and searching

The website serves static pages and files. Requests disclose your IP address, requested address, time and browser headers to Cloudflare for delivery, security and troubleshooting.

Reading articles and using local search do not require an account, discussions or analytics. Your search terms are processed in your browser. External links contact their destination when you follow them.

Optional services and your choices

iask at iask.js.gripe provides discussions independently from the static website. Its module, interface and API requests load only after you enable that service on a page that uses it. Requests disclose network information and the article identifier to the service and its host.

Cloudflare Web Analytics loads only after you separately enable analytics. It measures visits and performance using page address, referrer, browser/device details and timings; requests also disclose network information to Cloudflare. Declining analytics does not prevent discussions.

You can reopen Privacy settings at any time. Withdrawing a service refreshes the page to stop loading it. Withdrawal does not erase previously published comments or information already sent.

  • Cloudflare Web Analytics

    Purpose: Measure visits and page performance to improve this site, only after you opt in.

    Data used: Page URL, referrer, browser and device information, and performance timings; network requests also disclose your IP address to Cloudflare.

    Recipient: Cloudflare, Inc.

    Retention: Cloudflare controls analytics retention; this site has not verified a fixed retention period.

    Privacy information

  • iask

    Purpose: Load page discussions and let you sign in with GitHub to comment, only after you opt in.

    Data used: Network information and article identifier when loaded; GitHub account ID, login and avatar on sign-in; comment text and selected images on submission.

    Recipient: GitHub, Inc.

    Retention: Comments remain until the author or an administrator removes them; session cookies last one day. Uploaded images remain until separately removed.

    Privacy information

  • ishare

    Purpose: With your permission, load an ishare post inside this article.

    Data used: Requested share URL, IP address and browser information.

    Recipient: ishare

    Retention: The site keeps the consent choice for 180 days; ishare follows its linked privacy policy.

    Privacy information

  • YouTube

    Purpose: With your permission, load YouTube media and its player on request.

    Data used: Requested content URL, IP address, browser information; provider cookies may be used after loading.

    Recipient: YouTube

    Retention: The site keeps the consent choice for 180 days; provider retention follows its linked privacy policy.

    Privacy information

  • X

    Purpose: With your permission, load X media and its player on request.

    Data used: Requested content URL, IP address, browser information; provider cookies may be used after loading.

    Recipient: X

    Retention: The site keeps the consent choice for 180 days; provider retention follows its linked privacy policy.

    Privacy information

GitHub sign-in and public comments

If you choose GitHub sign-in, GitHub processes the login request and iask receives your public account ID, login name and avatar information to verify identity. We do not request access to your personal repositories. The access token used for identity verification is discarded afterwards.

Publishing sends your text and selected images to iask and its GitHub storage repository. Your account name, avatar, comment, attachments and publication time are public. Authorized administrators and GitHub repository readers may also access stored content.

Comments remain until you or an administrator removes them. Sign in with the original account to delete your own comment; closed discussions still allow that deletion. After its comment or discussion is removed, the service stops providing attachment access. Stored attachment files require separate removal; contact us for assistance. Downloaded copies cannot be recalled.

Login, drafts and saved choices

A login session lasts up to 24 hours; temporary login verification lasts up to 10 minutes. The service uses a secure login cookie and tab-scoped login state. Signing out clears the login state used by the interface.

Unsent text drafts stay in the service’s browser tab storage so a refresh can restore them. A successful submission clears the draft. Signing out does not clear drafts; remove them or clear site data on a shared device.

The website saves privacy choices for the period shown below. Clearing website data removes those choices. Clearing iask site data separately removes its saved login state and drafts.

Saved on
This device
Preference expiry
180 days after saving
Notice proposed
October 4, 2026
Notice effective
October 4, 2026

Providers, retention and international processing

Cloudflare hosts this website and the iask service. GitHub supplies sign-in and stores published discussions and images. The configured optional services and recipients appear above.

Provider logs and analytics retention depend on their account and service settings. We have not verified a fixed retention period; this policy does not promise automatic deletion after seven days.

Cloudflare and GitHub may process information outside your country. Their privacy information is linked below.

Contact, removal requests and policy changes

Email the operator above for access, correction or removal assistance and identify the page or comment. We may need enough information to verify that a request concerns your own data. Emailing us sends your address and message to us and our email provider.

Rights under applicable law may include access, correction, deletion and withdrawal of consent. You may also contact your competent data-protection authority.

We update this policy when information handling changes. Substantive changes to optional processing require an updated notice and renewed choices. The notice dates and preference period are generated from the website configuration.