Privacy policy
Information collected by JANHS, its purposes, account security, retention and personal information requests
Scope
This policy explains how JANHS handles information during search, account use, detailed web views, API calls, top-ups and enquiries. Search needs no account. See Pricing & billing for charging rules.
Information collected
- Search and browsing: search terms are used to return results and may appear in the browser address and necessary server access records. Do not enter personal or sensitive information in search.
- Security and access: servers receive IP addresses and request information. IP addresses are used to limit request frequency. Hosting and network services may also generate access logs.
- Accounts: email address, display name, password hash, verification status, language and optional avatar. External sign-in links, security challenges and audit records are also stored. Passwords are not stored in plain text.
- Usage and API: records of detailed views and API calls include the time, target, funding source, charge or credits used. Pack, balance and API key management records are also stored. Full API keys are shown only once, when created.
- External sign-in: only when enabled and selected, Google or GitHub supplies an identifier and authorised details such as an email address.
- Account emails: information needed for verification and security messages, and delivery status, is stored.
- Payments: top-up orders, payment customer identifiers, checkout and credit status, receipt references and payment events are stored. Stripe handles card details; this site does not receive full card numbers.
- Enquiries: contact information, questions and attachments you send by email.
Purposes
Information supports search and account functions, usage calculation and display, top-ups and receipts, account emails, security, abuse prevention, incident investigation, enquiries and legal obligations. The site does not integrate advertising or third-party analytics tools.
Service providers and disclosure
Account emails can be sent through the configured email provider. Stripe handles top-up payments. Google or GitHub handles external sign-in only when that feature is enabled and you choose to use it.
Hosting, databases, logs, backups and the support mailbox may also involve information processing. Necessary information is shared with providers or authorities to deliver the service, handle your request or meet legal requirements. Processing locations depend on the providers used.
Cookies and browser storage
The site uses sign-in, security and language cookies, and stores your theme preference in the browser. Purposes and controls are described in the Cookie policy.
Retention and security
Account details and operational records are stored in the service database. Account settings let you manage your display name, avatar, password and sessions. Access controls, password hashing, token checks and audit records help protect accounts but cannot guarantee absolute security.
There is no single automatic deletion period for accounts, usage, audit records or support email. Retention and deletion depend on purpose, applicable law and operational needs. Payment event cleanup periods do not apply to all information.
Under current cleanup rules, processed or ignored payment events are deleted after 180 days and their non-pending raw payloads are cleared after 30 days. Some accepted or expired account email records are deleted after 30 days. Failed or pending records, receipt references, usage, audit records and backups do not share those deadlines.
Personal information requests
For information, access, correction, deletion or restriction requests, see the contact page. Include the request type and relevant account; do not send passwords or full payment details. Identity checks, legal retention duties and others' rights may affect handling. There is currently no self-service account deletion screen.
Minors
Before using account features, minors should have a guardian review the conditions and information handling.
Changes and contact
Revisions and update dates are published here. Material changes to purposes or handling require any notice or consent procedures mandated by applicable law. For questions, see the contact page.
The JANHS Operations Team receives enquiries at [email protected].