Privacy

Privacy without fairy tales.

Last updated: October 12, 2026

This website is designed to collect as little personal information as reasonably possible. It does not require a public user account. That said, no public website can promise perfect anonymity, and your hosting provider, network provider, browser, external websites, or an AI provider may process technical information outside this website’s direct control.

Anonymous community posts

Community posts are public after moderation. Do not submit names, addresses, emails, phone numbers, Social Security numbers, account numbers, payment-card numbers, court case numbers, children’s identities, medical details that identify a person, or confidential documents.

The website automatically attempts to remove common email addresses, phone numbers, Social Security numbers, payment-number patterns, and case-number patterns. Automatic redaction is imperfect. A moderator should review posts, but moderation also cannot guarantee that every identifying fact will be caught.

The website does not store a raw IP address inside the community-post record. For rate limiting and duplicate-report control, it creates a one-way HMAC fingerprint from the connection address and browser user agent. The fingerprint rotates monthly. The hosting server may separately retain ordinary access logs, which can include IP addresses and request details.

Resource database searches

Resource searches are processed against the website’s SQL knowledge database or its generated read-only fallback. The application does not intentionally save search terms. A hosting provider, database server, security service, or access log may still record request metadata. Resource entries are public-source research and do not contain community-post or document-generator submissions.

Temporary Research and Legal Workbench sessions

Research collections, notes, Workbench documents, facts, timelines, form answers and drafts are held in the open page's memory. They are not automatically saved in localStorage, sessionStorage, IndexedDB or a server collection database. Reloading, navigating away or closing the page discards the active workspace. Use an explicit download to keep anything.

Clear session now clears open Navigator sessions on the same origin. A 15-minute inactivity timeout also clears them; if the browser suspends a tab, the timeout is checked when it resumes. Browser back/forward restoration starts a fresh session. This is application-level clearing, not a guarantee of forensic erasure from the browser, operating system or device.

Research requests send collection content to this server for temporary in-memory processing. The server returns encrypted session state held only in page memory and does not write collection content or analysis caches to disk. External AI calls for research and source chat are disabled. Chat content audit recording is disabled. CSRF cookies and rate-limit metadata may still be used; hosting access/security logs are outside the application's session-clearing control.

The old private research database is cleared when the updated research API first runs. Legacy Navigator browser storage and encrypted PDF browser checkpoints are removed when the privacy runtime loads. Operator backups, previous deployment copies, exports and host logs require separate operator cleanup; this feature does not erase them.

Exports and original forms

PDF form browser autosave and resume are disabled. Explicit PDF, Word, JSON, text and encrypted backup downloads remain available. Downloaded files remain on your device after clearing a session. Workbench and Research handoffs open a new tab with a one-time in-memory transfer, not a persisted browser record. Each open page has its own temporary work; clearing sessions clears all participating tabs.

Navigator organizer and FOIA tracker

The case organizer, evidence organizer, and FOIA request tracker hold their contents in temporary page memory. They do not automatically save those records in browser storage or upload them to the website server. Export before refreshing, leaving, closing, or clearing the session. Offline preview posts and unsent offline maintenance reports also disappear when their page closes or refreshes.

Someone with access to the open page can see its contents. Exported backups are ordinary files on your device; session clearing does not remove them. Browser, operating-system recovery and hosting logs are outside the application’s clearing control.

Screeners, deadline estimates, and court routing

The benefits screener, legal-issue classifier, deadline estimator, court finder, complaint navigator, and appeal navigator process answers in the browser or through the site’s structured navigation database. The application does not intentionally create a user profile from those answers. The server and hosting provider may still log ordinary request metadata when a server API is used.

Donations and external links

Donation payments are handled by the external donation service selected by the site owner. This website should not collect payment-card information directly. Every external court, agency, nonprofit, payment provider, and resource site has its own privacy practices.

Cookies

The website uses a session cookie for security features such as CSRF protection and administrator authentication. Research collections and the selected collection ID stay in page memory; no persistent research access cookie is created. Interface preferences, such as accessibility settings, may use browser storage. The site does not include advertising trackers or analytics scripts by default. A future site owner who adds analytics or other services should update this notice.

Deletion and corrections

A moderator can hide or permanently delete community posts through the private moderation page. Public posts also include a report button for privacy and safety concerns. Because no public account is attached to a post, the website may not be able to verify that a person requesting removal authored it.

Children

This website is not designed to collect personal information from children. Do not identify a child in a community post or AI question. Suspected child abuse in Arkansas should be reported through the official hotline at 1-800-482-5964; call 911 for immediate danger.

Security limits

The website includes security headers, CSRF protection, server-side secrets, moderation, rate limits, output escaping, and restricted storage directories. These reduce risk but do not make the system invulnerable. Keep PHP and the hosting environment updated, use HTTPS, back up carefully, and review server logs and permissions.