Privacy Policy
Last Updated: November 17, 2026
This Privacy Policy describes how Edge Case Software, LLC ("we," "us," or "our") handles information in connection with Letheca (the "Service"). We built Letheca with privacy as a core design principle. Our goal is simple: collect as little as possible, retain as little as possible, and be transparent about both.
1. Our Privacy Philosophy
Letheca is anonymous by design. The Service does not require registration, login, or any personally identifiable information to use. We do not build profiles of our users. We do not sell data. We do not run targeted advertising.
2. Information We Do Not Collect
For visitors, Letheca does not collect your name, email address, or phone number, and does not require account credentials, device identifiers or advertising IDs, or precise location data. As described below, self-hosted analytics records aggregate pageviews and may estimate approximate location from request IP addresses. The Service also temporarily records IP addresses for security and abuse response and does not build cross-site browsing profiles. If the administrator connects a ChatGPT account, Letheca stores that administrator account's email address and identity identifier for connection management.
3. Information We Do Collect
3.1 User-Submitted Content. A Drop and its reply normally remain available until the Drop expires. We also store the submitting IP address and creation/expiration timestamps in a private database record. A brief summary may be permanently preserved as a Ghost Trace if a Drop accumulates sufficient Echoes. When a post receives a serious safety or privacy report, the report, a snapshot of the post and reply, and associated private safety metadata may instead be retained after the Drop expires. Preserved records are accessible only to authorized administrators, are excluded from public archives, and remain until an administrator deletes the report, subject to applicable legal requirements.
Mixed feed ordering uses a private source group derived from the submitting network address and a daily rotating value. The group expires with the post. People sharing a network may be grouped together. Feed pagination temporarily stores ordered post identifiers for up to 24 hours.
3.2 Echo Interactions. When you Echo a post, we increment a counter. Your browser creates a random Echo identifier and sends it with Echo requests. The server stores only a one-way keyed fingerprint associated with that post, for no longer than the post itself, to reject repeated Echo requests.
3.3 Server Logs. Our web server may generate standard access logs including IP addresses and timestamps. These are used solely for security monitoring and are retained for no more than 30 days.
3.4 Analytics. We use a self-hosted Umami Analytics instance hosted by Edge Case Software at analytics.edgecasesoftware.dev to understand aggregate pageviews, referring domains, and general site usage. Analytics is not used to identify confession authors or associate browsing activity with individual Drops or Replies. Individual Drop pages are not tracked, URL query strings are omitted from pageview data, and Drop or Reply text is not intentionally sent as analytics data. Standard Umami pageview measurement does not require analytics cookies. Umami may process IP addresses and browser information to group pageviews into anonymous sessions and estimate location; raw IP addresses are not stored as fields in standard analytics records. Request metadata may also be processed or recorded in operational logs by the analytics host or its infrastructure.
3.5 Safety and Moderation Reports. If you flag a post, we store the selected reason, any details you provide, the post slug, report timestamp, and a snapshot of the reported post and reply in a private database record for administrator review. Safety assessment classifies self-harm or immediate-danger risk as LOW, MODERATE, HIGH, or CRITICAL. A separate policy assessment evaluates possible privacy exposure and other content-rule violations; these classifications are independent. HIGH and CRITICAL safety reports are privately preserved. CRITICAL reports are hidden automatically, and the administrator may configure HIGH-risk auto-hide. Clear, high-confidence PII exposure and doxxing may also be automatically preserved and hidden regardless of safety risk. High-confidence identification numbers and payment-card numbers that pass checksum validation may be contained by deterministic checks before AI analysis completes or if it is unavailable. A reply-only violation may remove the reply while the original post stays public; if the reply cannot be safely isolated, the complete post is hidden. Possible or uncertain PII and harassment without a serious threat are sent for human review and do not by themselves cause automatic hiding. Spam follows existing filters and is reviewed by the administrator. A hidden post cannot be viewed, replied to, echoed, reported again, searched, or found in public archives. An administrator can restore hidden content or a contained reply only before the original expiration time, which is not extended. Preservation is private retention for review; hiding changes public visibility; permanent deletion removes preserved evidence and is available only to the administrator. We do not store a reporter account or profile, and reports are never displayed publicly. An administrator may write a short public explanation of a review on a live post. Reports and snapshots remain until administrator deletion, subject to applicable legal requirements. Report notification previews redact values recognized by deterministic PII filters and omit post/reply IP addresses; full evidence and private metadata remain in the authenticated admin interface.
3.6 Optional ChatGPT Safety and Policy Analysis. If the administrator enables this feature, Letheca sends the reported post and reply, selected report reason, optional reporter comments, and content/report timestamps to OpenAI for an advisory assessment. Values matching Letheca's deterministic PII filters are replaced with category redaction markers, and only the matching categories are sent as evidence. IP addresses, browser metadata, and reporter identity information are excluded. The connection uses the administrator's Sign in with ChatGPT authorization; it does not use API-key billing. Requests use OpenAI's no-storage request setting, but the content is transmitted to OpenAI and is subject to the applicable OpenAI service terms and data-handling policies. If analysis is unavailable, the administrator still receives the report for human review. Deterministic containment of sensitive identification or checksum-valid payment-card numbers does not depend on AI.
4. Cookies and Local Storage
Letheca does not use tracking cookies or advertising cookies. We use browser localStorage to store a random Echo identifier, local Echo history, your board layout preference, and your acceptance of the current community agreement. The random identifier is sent only when you Echo a post and is not used for advertising or cross-site tracking.
5. How We Use Information
The limited information we collect is used exclusively to operate and display the Service, enforce our Terms of Service, and monitor security and performance. When enabled by the administrator, report content is also processed by OpenAI to produce the advisory safety assessment described above.
6. How We Share Information
We do not sell, rent, or trade user information. We may share information with infrastructure providers who assist in operating the Service, including OpenAI when the administrator enables report analysis and Cloudflare when bot protection is enabled, in response to legal requirements, or to protect the rights and safety of our users and the public.
When bot protection is enabled, pages that accept new posts or replies load Cloudflare Turnstile. Cloudflare processes security signals such as your IP address, browser user agent, TLS fingerprint, and the site origin. Letheca sends the challenge token to Cloudflare for verification and records only the action and outcome in its verification logs. Letheca does not send post or reply text to Turnstile. See Cloudflare’s Turnstile Privacy Addendum.
7. Data Retention
- Drops and ordinary post safety metadata: Retained until the Drop expires. Content included in a serious safety report may be preserved privately beyond expiry until its report is deleted.
- Ghost Traces: Retained indefinitely; associated safety metadata may be retained privately
- Safety and moderation reports, content snapshots, and associated private post safety metadata: Accessible only to authorized administrators and retained until administrator deletion, subject to applicable legal requirements; high- and critical-risk reports and automatically hidden privacy violations may be preserved after the Drop expires
- Server Logs: Maximum 30 days
- Echo fingerprints: Retained in Redis no longer than the associated Drop
8. Data Security
We implement industry-standard security measures including encryption in transit (TLS/HTTPS) and access controls. No method of electronic storage is 100% secure, and we cannot guarantee absolute security.
9. Age Requirement
Letheca requires all users to be 18 years of age or older. Users must confirm this via a clickwrap agreement on first access. Because we require users to be 18 or older, COPPA does not apply to the Service.
10. GDPR (European Users)
Because Letheca does not require account or profile information and does not attach safety metadata to a public identity, our ability to fulfill data subject requests that require identifying a specific individual is limited. Contact contact@edgecasesoftware.dev for inquiries.
11. CCPA (California Residents)
Letheca does not sell personal information. Because we do not require account or profile information and do not attach safety metadata to a public identity, our ability to identify a specific user is limited. Contact contact@edgecasesoftware.dev for inquiries.
12. Third-Party Links
The Service may contain links to third-party websites. We are not responsible for the privacy practices of those third parties.
13. Changes to This Policy
We may update this Privacy Policy from time to time. Your continued use of the Service constitutes acceptance of the revised policy.
14. Contact Us
If you have questions about this Privacy Policy, contact us at:
Edge Case Software, LLC
Email: contact@edgecasesoftware.dev