Account and payment records
The service stores your email address, password hash, API key hash and prefix, credit usage, abuse-related information including IP information, and payment transaction records. These support account access, retrieval authentication, credit accounting, abuse prevention and payment verification. Passwords and API keys are not stored as plaintext account credentials. Describing these stored categories does not make the individual hash values public, and hashing does not amount to a guarantee against unauthorized access.
Browser state and account sessions
The account widget uses localStorage on each hostname to retain an invoice identifier and user identifier for recovery of invoice state. It does not save the raw API key there. Account authentication uses a Secure HttpOnly session cookie, separately from the key header used for retrieval. HttpOnly applies to that cookie, not to localStorage. Save the once-shown key in storage you control and keep it out of public examples or shared browser code.
Analytics and retention scope
Pages include Statinside analytics counter 43 for website analytics; this is separate from any conversation analysis you perform on retrieved comments. No fixed account-data retention deadline is established. This does not promise automatic deletion at a particular date or permanent storage, and it says nothing about how long a Reddit record will remain available in the archive. Local research annotations belong to your workflow; they should be distinguished from the service's account and payment records.
