Information used to operate the account
We retain your email address, a hash of your password (not the plaintext version), and a hash of your API key. We also store IP information for abuse prevention and records of your payment transactions. These data points support account access, authentication, credit accounting, and payment verification purposes.
The service also stores the API key prefix and credit-usage records. Storage of hashes does not mean that individual hashes are published or that encryption-at-rest is promised. Keep the actual key and password out of shared query worksheets and support material.
Browser state and page analytics
The site uses a Secure HttpOnly session cookie. The widget keeps user ID and invoice ID in localStorage per hostname for recovery; it does not persist the raw key, password, transaction hash, amount or full invoice there. A saved identifier is not authority to access another user’s invoice. Pages include Statinside counter 65, without a claim about specific event fields or cookie-free analytics.
Retention and research copies
No fixed retention period for account, personal or payment information is specified, and no automatic deletion deadline is promised. This is separate from how long archive records remain available. If you retain responses or annotate community statements in your own tools, define access and retention rules for those copies. Respect applicable law and third-party rights, and avoid including unnecessary contributor details in a shared worksheet.
