Privacy Policy
This notice describes current GrapeCat Chem behavior and must be updated if data collection practices change.
01Information Currently Processed
Browsing and analytics information
GrapeCat Chem has no customer account requirement. When first-party analytics is enabled, we process exact search text, visited paths, result and directory interactions, Chemical section exposure and engagement, evidence and external-link selections, event times, anonymous visitor/session correlation, direct server IP, user agent, referrer, request status, and anomaly signals. Server request records and browser-reported interactions carry separate trust classifications.
Inquiry information
When you submit a support or About-page form, we store your name, email address, message, inquiry type, subject, optional organization and reference URL, submission time, current page path, page type, a sanitized referrer, user-agent information, a coarse device category, the direct network IP visible to our server, and—on a Chemical page—the canonical Chemical identity associated with your inquiry. We use these details to receive, secure, review, route, and understand inquiries. When email notification is enabled, the submitted business context and reply email are sent to the configured GrapeCat Chem team mailbox; delivery status is retained with the inquiry.
Local file processing
CSV, XLS, and XLSX files are parsed locally in the browser. Files are not uploaded to a GrapeCat Chem server in the current implementation.
02Bulk File Processing
Bulk processing is client-side only. File names, spreadsheet contents, procurement quantities, and non-CAS columns are not sent to GrapeCat Chem analytics. This notice must be updated before any future server-side processing is introduced.
03Analytics
The first-party tracker sends bounded event batches to the public GrapeCat Chem Go API when enabled. Random HttpOnly analytics visitor and session cookies correlate an anonymous journey; stored analytics identifiers are one-way hashes of those cookie values. Browser events are not treated as authoritative server request facts. Event storage currently applies a 400-day technical TTL in the production ClickHouse schema, subject to deployment policy and legal review.
04Cookies and Identity
Analytics uses separate random, first-party, HttpOnly visitor and 30-minute session cookies. They do not identify a verified person and are not browser fingerprints. Public data requests do not create an access-token session.
The inquiry flow uses its own random browser identifier. We normalize email addresses by trimming and lowercasing them and create server-secret HMAC values for repeat-email and auxiliary repeat-IP analysis. We do not treat a shared IP address as proof that inquiries came from the same person.
05Location
Country, region, and city are not currently derived or collected for inquiries because no trusted location source is connected. These fields remain empty. GrapeCat Chem does not call a third-party geolocation service during submission.
06Third-Party Services
The implemented analytics path is first-party and does not require Google Analytics or another browser analytics provider. Infrastructure providers such as a future CDN/security edge or managed storage must be reflected here before production use.
07Contact
You can contact GrapeCat Chem through the support-cat inquiry form displayed on this site.