Privacy Policy

What SharedMorrow collects

Account registration uses a display name, username and password. Passwords are stored as salted hashes rather than readable text. Profiles may include a bio, interface language, avatar and cover image.

The service stores posts, replies, follows, bookmarks, reading history, discussion subscriptions, in-app notifications, reports, moderation decisions and audit records needed to operate the community.

First-party measurement records visits and selected product events with account or anonymous session identifiers, source category, landing path, timestamps and limited event metadata. It does not use a third-party advertising or analytics provider at this stage.

Cookies, logs and uploads

After sign-in, SharedMorrow uses an essential secure HttpOnly session cookie. Browser storage remembers interface preferences and temporary session continuity. The current session cookie expires after 30 days unless it is revoked earlier.

Network addresses are used for rate limiting. Security and request logs use a keyed, shortened client hash instead of writing the raw address into application log events. When a browser does not provide its normal anonymous session identifier, the service may derive a fallback visit identifier from connection and browser information.

Avatar and cover uploads are validated, stored in the dedicated SharedMorrow upload area and governed by media status and privacy controls.

How information is used and shared

Information is used to provide accounts and community features, keep sessions secure, prevent abuse, moderate reports, measure reliability and participation, and create service backups.

Hosting infrastructure and Cloudflare process technical request data to deliver and protect the site. Opening a Telegram link is a separate action governed by Telegram; SharedMorrow does not mirror website posts or account data to Telegram.

Email delivery, advertising analytics, payments and commerce are not enabled. SharedMorrow does not claim to sell member information.

Member controls and retention

Signed-in members can download the current account view and submit export or deletion requests from Settings. Deletion handling revokes sessions and anonymizes the account; public contributions and necessary audit evidence may be retained to preserve discussion and safety records.

Backups, security logs, audit records and request records are retained for operational and safety needs. A final jurisdiction-specific retention schedule and legal-rights wording remain pending Owner and legal review.

Contact and legal identity

Use the in-product report control for a visible discussion and the account-request controls in Settings for export or deletion requests. A separate public contact method has not yet been approved.

OWNER LEGAL-IDENTITY DECISION PENDING: the public legal operator identity, governing jurisdiction and any jurisdiction-specific privacy rights will be added before search indexing is authorized. No company, address, DPO, telephone number or email address is implied by this page.