Privacy Policy

Effective during the UNALGORA public Beta.

What UNALGORA stores

UNALGORA stores the account information you provide, including your email address, username, display name, password hash, profile text, location, website, profile picture, cover picture, selected interests, and an optional birth date. Birth dates are hidden by default and omitted from public profile output unless the account owner explicitly enables profile display. New accounts must complete email verification during registration. Accounts that predate email verification remain usable and are invited to verify.

Private messages

One-to-one text messages are available only between current accepted friends. Message transport uses the site's HTTPS/TLS connection. Message text is encrypted at the application layer before database storage using AES-256-GCM authenticated encryption. Encryption keys are held in server secret configuration, not in the database or browser. Key identifiers are stored with messages so an operator can retain prior keys while rotating to a new active key.

UNALGORA messages are not end-to-end encrypted. The server decrypts message text to deliver the service and may technically access it when necessary for service operation, security, abuse investigation or moderation, support, or legal compliance. This does not mean employees routinely read private messages.

Messages are stored on UNALGORA infrastructure without an invented fixed retention period. Unfriending or blocking prevents new messages but does not erase existing history. Clearing a conversation removes it from your own account view only; it does not remove the other participant's copy. A later message can make the conversation reappear from that new point. When an account is permanently deleted, its own access ends and retained messages in the other participant's copy use the neutral “UNALGORA ex user” identity without a profile link or deleted profile information.

The service stores content and relationships needed to operate the social network: posts, comments, post edit history, photos, Likes, friendships, friend requests, and notifications. Audience settings and friendship rules are used when deciding who may retrieve a post or its media.

Circles

Circles store their name, description, rules, visibility, images, memberships, roles, invitations, join requests, posts, comments, notifications, and administrative audit history. Circle Owners, Admins, and Moderators have local responsibilities described in the interface, while UNALGORA site administrators retain separate platform-operation and safety authority.

Public Circle pages and content may be visible without membership and may be indexed where the application marks them indexable. Private Circle posts and member-only details are restricted by the application to active members; pending invitations and join requests do not grant access. Private does not mean end-to-end encrypted or inaccessible to platform operators when access is reasonably necessary for operation, moderation, security, support, or legal compliance.

Authentication and security information

Passwords are processed with bcrypt and are not stored as plaintext. Authentication uses a session cookie. Login throttling stores a one-way hash derived from the attempted identity and available network address; it does not intentionally store the raw address in that throttle record. Password-reset and account-action tokens are stored as one-way hashes, expire, and are single-use. Sensitive administrator password assistance is recorded in an audit log without exposing passwords or reset tokens.

Photos and link previews

Uploaded images are decoded, resized, stripped of unnecessary metadata, re-encoded as WebP, and stored in the server's configured media directory. Giant originals are not retained by the current implementation. When a post contains an HTTPS link, UNALGORA may retrieve and cache a limited title, description, domain, and image reference from that site. Feed pages use cached metadata and do not contact the linked site to build the preview.

Cloudflare Turnstile

Login and registration use Cloudflare Turnstile for bot protection. The browser loads the Turnstile challenge from Cloudflare, and the server sends the challenge token and, when available, the connecting address to Cloudflare for validation. Cloudflare handles that data under its own terms and privacy practices.

Ko-fi support widget

UNALGORA loads an optional floating support widget from Ko-fi after the main page becomes usable. Loading or opening that widget sends a request to Ko-fi and may allow Ko-fi to process technical request information under its own terms and privacy practices. UNALGORA does not use the widget as an analytics system. The official widget also requests its styles and images from Ko-fi and may request the DM Sans font stylesheet and font files from Google Fonts. UNALGORA continues to work if any of these third-party resources are unavailable.

Advertising, analytics, and selling data

The current application contains no advertising, paid reach, third-party analytics package, tracking pixel, or code for selling user information. The disclosed Ko-fi support widget, external links, and the optional YouTube thumbnail can make a request to the named third party when that resource is loaded, displayed, or opened.

Email delivery

UNALGORA sends transactional messages for registration, email verification, password recovery, account deletion, and account reactivation through the configured SMTP provider. Messages contain no advertising, tracking pixels, or analytics assets.

Deactivation, deletion, and retention

Deactivation retains account data but blocks normal use and hides the account from normal profile, search, and feed discovery until credential login and email-confirmed reactivation succeed. Permanent deletion requires a short-lived email confirmation and deletes the profile, owned posts and their histories, comments, reactions, relationships, received notifications, event data, and locally uploaded media associated with the account. Historical notifications, revisions, and the other participant's message copy may remain where needed to preserve retained content, but deleted attribution is replaced with “UNALGORA ex user” and no deleted profile link or personal identity is returned. Shared groups remain for other members with the former owner removed. Security and administrator audit records may be retained with the deleted account reference cleared.

Legal requests and safety

UNALGORA may preserve or disclose information when required by applicable law or valid legal process, or when reasonably necessary to protect users, the service, or others. Prohibited material may be removed and accounts may be suspended or deleted. Evidence may be preserved or reported where applicable law requires it.

Changes

This policy will be revised when the implementation or its service providers change. Material changes should be described plainly; the policy must not claim features or safeguards the code does not provide.