Legal & privacy

Imprint

Jevdit is created and operated by Tom Nick. The operator and data controller is:

These contact details are adapted from the operator’s imprint. This is an independent project; Jev and TypeSafe are not the operators of Jevdit.

What the service stores

An account stores a username, creation date, and, if you choose email sign-in or claim an anonymous account, your email address. Posts, comments, subjevdit descriptions, and usernames are public. Voting records associate a vote with your account; the interface displays aggregate scores.

When you browse without a valid session, the service automatically creates an anonymous account with a generated username and an authentication cookie. “Anonymous” means no email is required and your real identity is not displayed; it does not mean untraceable. Losing the cookie before claiming an account can mean losing access to it.

Membership records connect your account to joined subjevdits and personalize your frontpage. Public counts distinguish email-verified and anonymous accounts; a badge means only that an email address has been verified. Rules discussions store support/opposition ballots and one readership record per member account, excluding the proposer. The interface shows aggregate counts. Leaving removes your active ballots and readership records for that subjevdit.

Essential cookies and sign-in

The jevdit_session cookie keeps you signed in for up to 30 days. The jevdit_csrf cookie protects forms for up to 24 hours. Both are essential to the requested service. There are no advertising cookies or analytics scripts in this application.

Magic links expire after 15 minutes and can be used once. Only hashes of magic-link and session tokens are stored in the database. Expired credential records are cleaned up at startup and periodically. Sign-in emails are sent through Zoho CPaaS using its EU service. Zoho receives the recipient email address, message content (including the single-use link), and delivery metadata. Open and click tracking are disabled. Local development writes email files on the operator’s machine. See Zoho’s privacy policy.

Browser verification before publishing or voting

Website requests pass through Cloudflare before reaching our server. Cloudflare processes request data, including IP addresses, URLs, HTTP headers, and submitted data, to deliver the service and protect it against denial-of-service attacks and other abuse. This also applies when you only read the site.

Cloudflare Turnstile helps protect posts, comments, votes, rules ballots/proposals/reviews, and subjevdit creation from automated abuse. Its script loads when you try to publish or vote. Reading and sign-in do not load it. The check requires JavaScript. Your browser connects to Cloudflare, which receives your IP address and browser/device information to evaluate the request. See Cloudflare’s privacy policy.

Our server sends the challenge token to Cloudflare for verification; it does not include your post, email address, authentication cookie, or an additional copy of your IP address. After a successful check, an essential jevdit_browser cookie records verification for up to 30 minutes and is tied to the current session. Changing sessions or restarting the service requires a fresh check before publishing or voting. Failed checks leave content unpublished and explain how to retry.

Automated moderation

Submitted text, chosen usernames, subjevdit rules, relevant discussion context, URLs, and downloaded webpage text are sent to TypeSafe’s Jev API for classification. Your account email, session cookies, and IP address are not included in moderation requests. Do not submit information you are not entitled to share.

Jev’s categories and confidence determine whether a submission is published. Uncertain or failed checks block publication. Rejected text is not stored in the application database; moderation records store a content hash, account identifier when present, category, model, policy version, and decision data for up to 30 days. The provider may process data under its own terms, described in TypeSafe’s legal and privacy documents.

For rules-change reviews, Jev also receives account identifiers within the discussion, membership and participation counts, discussion age, popularity, and the complete published comments. We retain the review evidence and decision with the proposal, including unsuccessful reviews, to explain how the rules were decided. This is a snapshot of already-published proposals and discussion, not unpublished rejected drafts. Approved changes have a public before/after history. Review snapshots remain with the discussion even if a member subsequently leaves.

Technical operation and retention

Connections expose an IP address and ordinary HTTP metadata to the server. IP-based request counters are kept in memory to protect the service against abuse. Application error logs may contain technical failure details; request bodies, email addresses, and sign-in tokens are not intentionally logged. Fetching a submitted link sends a request from our server to the linked website.

Account information and published contributions remain until removed in response to an applicable request or for operating the service. The public service is hosted in Railway’s Amsterdam region by Railway Corporation, which processes application data and connection metadata to operate its infrastructure. Railway is a US provider, and its operations and service providers may involve processing outside the European Economic Area. See Railway’s privacy policy and data processing terms.

Purposes and legal bases

Account management, authentication, and publication provide the service you request (Article 6(1)(b) GDPR). Abuse prevention, service reliability, and moderation support the legitimate interest in operating a safe discussion service (Article 6(1)(f) GDPR). Contact messages are used to respond to your request, on the basis appropriate to that request.

Your rights and contact

Where applicable, you may request access, correction, erasure, restriction, portability, or object to processing. You may also complain to a data protection supervisory authority. Send privacy requests, reports of unlawful content, or questions about a moderation decision to [email protected]. Include the relevant account or content URL, but never send passwords or sign-in links.

Using Jevdit

Follow the discussion guidelines and only publish material you have the right to share. You retain rights to your contributions and permit their storage and display as part of this service. Automated moderation is fallible, and availability is not guaranteed. External websites are operated independently and can change after a link check.