Privacy
This is the simple privacy picture right now: what your account stores, what stays out, and how support and linked installs work.
Chummer keeps only the account, install, help, and feedback details needed to run the product, answer you, and retire temporary logs on schedule.
Public pages can mention known issues and fix availability.
Stored: case timeline and user-visible status events: retain for 18 months after the last state change public known-issue linkage and closure records: retain for 18 months after public closure raw attachments that are no longer needed for open investigation: summarize or redact within 90 days
Hidden: remove secrets, local paths, and unrelated identity data from user-visible case history preserve limited install/channel/version status needed for honest fix-availability notices
Your account can show your own help history and follow-up.
Public pages show release status and install help.
Stored: pending claims and install-link events: retain for 365 days after last install activity durable install identity, channel status, and last-seen release status: retain while the install relationship remains active older claim files should collapse into one current install record plus limited historical records
Hidden: never persist personalized binary data because the binary remains standard and signed keep person, install, device-role, and campaign scopes explicit instead of flattening them into a single sync blob
Your account can show linked installs and recovery context.
Public routes may summarize learned product changes after review.
Stored: post-fix follow-up invites and answer summaries: retain for 365 days raw free-text survey answers: summarize or redact within 180 days unless still tied to an open product decision
Hidden: keep survey status out of public guide copy until synthesized into source redact install/account data that is not required for the follow-up question being answered
Signed-in routes may show that follow-up happened without replaying raw survey text.
Public help may show short answers and source links, not raw transcripts.
Stored: raw outside-service request and response logs: retain for 30 days unless a narrower service contract says less service comparison notes and answer summaries: retain for 180 days promoted help, support, and public answers must be rebuilt from Chummer sources, not from indefinite outside-service transcripts
Hidden: no unbounded personal data spill into prompts, logs, or review traces answer notes should prefer case numbers, release numbers, and calculation records over raw user text where possible
Signed-in help may show the answer path without becoming the account record.
may expose support status, known issues, release status, compatibility, origin, and channel-aware fix availability
may not expose private case notes, raw crash reports, outside-service logs, or private survey text
may expose case timeline, install status, claimed-device state, and the user-safe slice of crash/support data
may not expose unrelated reporter data, maintainer-only notes, or private moderation notes
must ground answers in curated standard sources, current records, or support-case status
must not become the system of record for support or release state
Privacy summary
Start with the short version: the app file stays the same for everyone, and telemetry or diagnostics stay explicit about what they capture.
The download file stays the same for everyone
Open sectionYour account stores sign-in and help history
Open sectionPasswords and access keys stay out of your account record
Open sectionAccount record
Your Chummer account keeps your basic profile, linked sign-in methods, device access, support history, and preferences together so you do not have to rebuild that history by hand.
Install linking
When Chummer publishes a download, everyone gets the same file. Chummer does not build a private installer just for your account. If account linking is available, the account step is a short-lived code that reconnects a local copy back to your account.
What stays out
Short-lived third-party access stays on the machine or service using it. Your account keeps consent, help history, and access records, not passwords or access keys.
Privacy and recognition
Participation and recognition remain optional layers. Private product use, private support, and a quiet account setup remain valid even while community pages exist.