Privacy policy

This policy covers Eventus at eventusapp.duckdns.org, operated by George Barsukov. In this policy, “we” means the operator of this Eventus service. Questions and privacy requests can be sent to Georgebarsukov@gmail.com.

Information we collect

• Account information: your name, email address, profile image, optional profile details, sign-in methods, and preferences. If you use a password, we store a password hash, not the readable password.
• Google or Facebook sign-in: the provider's account identifier and the name, email address, and profile image it makes available. We also store authentication tokens and related sign-in records. We do not receive your Google or Facebook password.
• Community activity: groups and memberships, invitations, event registrations and attendance, group-scoped player records, team assignments, match results, ratings, tournament participation, and uploaded images.
• Communications: messages, reactions, read receipts, notifications, friend relationships, blocking preferences, and information you send when asking for help.
• Organizer records: authorized organizers may add participant names, attendance, ratings, and private notes or tags, including for people who do not have an Eventus account.
• Technical and discovery information: session identifiers, timestamps, connection information such as IP addresses and browser details, security and error logs, timezone, selected city, and search preferences. With your browser's permission, your location can be used for nearby results. Eventus does not maintain a continuous device-location history.
• Payments and imports, when used: order amounts, payment status and provider references, and event or attendee information supplied through an organizer's import. Payment-card details are handled by the payment provider rather than stored as card numbers in Eventus.

How we use information

We use information to create and secure accounts, operate groups and events, manage participation, generate teams and competitions, keep results and ratings, deliver messages and notifications, personalize discovery when enabled, process configured payments, provide support, and investigate errors, abuse, and disputes. Session and audit records help protect accounts and explain changes made by organizers and participants.

Who can see information

Profile, group, and event visibility settings determine what other visitors can see. Public pages and public participation records may be viewed by people who are not signed in. Group owners and event hosts can access information needed for their authorized activities. Private organizer notes and tags are restricted to authorized organizers. Messages are available to participants with access to the conversation.

The operator can access stored information for administration, support, security, and handling privacy requests. Other participants may keep copies of information you share with them; Eventus cannot remove screenshots or copies held outside the service.

Services used by Eventus

Choosing Google or Facebook sign-in sends you to that provider, which processes the login under its own privacy policy. Eventus requests basic identity and email information for sign-in; it does not request permission to read Facebook posts or friends lists, or Google mail or contacts. Profile images may be loaded from the provider that hosts them.

When enabled, Cloudflare Turnstile processes browser and connection information to help prevent automated abuse. Configured email, file-storage, address-search, and payment services process the information needed for those features. A feature that is not configured does not send data to that provider. Following a map or other external link takes you to a separate service.

See the privacy policies for Google, Meta, and Cloudflare for their practices. Eventus does not currently include advertising or third-party analytics trackers.

Cookies and preferences

Eventus uses cookies to keep you signed in, protect sign-in flows, and remember your timezone. Your browser provides controls for removing or blocking cookies. Blocking essential cookies can prevent sign-in or other features from working. Third-party sign-in and anti-abuse services may use their own cookies when you interact with them.

Storage and retention

This Eventus service is currently hosted on an operator-managed computer. Account and application records are stored by the service, with uploaded files held locally or by the configured storage provider. HTTPS protects connections to the public website, and server-side permissions restrict access. No storage or transmission method can eliminate every security risk.

Account and activity records generally remain while your account or the related community history is in use. Leaving a group, hiding a conversation, or deleting an item from a screen does not necessarily erase its underlying record. Eventus preserves historical results and certain revisions and audit records. Saved discovery searches are cleared when personalization is disabled or you clear the history; searches older than 90 days are removed by cleanup tasks.

You can request deletion using the process below. We review what can be erased or anonymized and whether limited records need to remain for security, disputes, obligations, or the integrity of shared event history. We explain retained information and the reason when responding to a request.

Your choices and requests

Use Profile to edit your details and visibility, and Settings to manage messages, notifications, and other preferences. You can decline browser location access, use another sign-in method, or change permissions in your Google or Facebook account. Removing provider access does not by itself delete Eventus data.

To request access, correction, or deletion, contact George Barsukov at Georgebarsukov@gmail.com. We may need to verify that the information belongs to you. See User data deletion for the information to include and what happens next.

Changes to this policy

We will update this page when the service's data practices change and revise the date above. Contact us if you have a question about this policy or a previous version.