Privacy Notice

Effective 3 September 2026

This notice describes Komvia as it operates today. It has not yet received external legal review. We do not claim privacy protections that the product or infrastructure cannot prove.

What we collect

• Private account information such as email address, account name, password hash, verification records, and sessions.
• Your separate public identity, including display name, username, and the profile words you choose.
• Posts, replies, acknowledgements, memberships, blocks, mutes, and reports.
• Private product feedback associated with your account so the owner can review and respond to patterns.
• Limited security, operational, and aggregate usage information needed to prevent abuse, understand the signup journey, diagnose failures, and keep the service available.

Why we use it

We use this information to provide and secure accounts, operate community conversations, enforce rate limits, deliver essential emails, respond to safety reports and product feedback, understand aggregate use, and maintain the reliability of Komvia.

Visibility

Your account email and authentication data are not part of your public identity. Your public identity and contributions are visible to people who share the relevant Komvia spaces. Blocks and mutes are private to the person who creates them.

Stay, Fade, reports, and deletion

Stay content remains available until it is removed through an account, community, or moderation process. When you delete your own contribution it disappears from member views immediately and is retained privately for up to 30 days for safety, moderation, and audit needs. Fade content is excluded from normal reads when its expiry time arrives and is scheduled for physical deletion afterwards. A report made before deletion or expiry may preserve limited safety context for review. Backups may retain deleted data for a bounded recovery period set by the database provider.

Komvia disables caching and public indexing on private community routes and provides no bulk content export. A web app cannot reliably prevent screenshots or copying on every device. Members are asked to obtain consent before sharing another person’s words outside their original context.

Service providers

Komvia currently relies on Vercel for hosting, Neon for PostgreSQL, and Resend for transactional email. They process only the information needed to provide those services under their own security and data-processing terms.

Analytics

Komvia uses Vercel Web Analytics for privacy-conscious, aggregate information about visits to public pages, such as page views, referrers, device category, and approximate country. It is configured not to send private application URLs, form values, community content, account details, tokens, or session secrets. Vercel describes this service as cookieless and based on anonymous, aggregated data, so Komvia does not currently load an analytics consent banner. We also store a small allowlisted set of account-funnel events in our own database, linked internally to an account where needed, without event payloads or private content.

Your choices

You can control what you publish, use mute and block tools, report a contribution, and send private product feedback. Contact the Komvia owner for access, correction, or account-closure requests. A dedicated privacy contact and self-service deletion flow remain planned.

Changes

We will update the effective date and explain material changes when this notice changes. Continued participation will not be treated as consent where the law requires a separate choice.