Information BEYLE handles

• Account and sign-in details: your email address and display name. If you create an account with a password, BEYLE stores a salted password hash, not the original password.
• Google or GitHub sign-in: if you choose a provider, BEYLE receives your provider account identifier, verified email address, display name, and profile image URL when available. Google sign-in requests the basic OpenID Connect scopes openid, email, and profile. GitHub sign-in requests read:user and user:email. BEYLE uses a temporary provider access token only to retrieve your identity details and does not store that token. BEYLE does not request Gmail, Google Drive, or GitHub repository access.
• Profile and location: information you choose to add, such as a biography, profile image URL, city, latitude and longitude, search radius, and interests. Location and interests help BEYLE rank nearby events and recommendations.
• Events and activity: events you create, including their title, description, category, tags, time, city, and any event coordinates; events you join or leave; in-app invitations; ratings and comments; and recommendation status.
• Technical request information: BEYLE's server and reverse-proxy logs may record information such as your IP address, request method and path, response status, and request time. This information is used to operate, protect, and troubleshoot the service.

How BEYLE uses this information

BEYLE uses account details to create and authenticate your account, maintain your session, show your profile, find events that match your interests and location, provide recommendations, manage event participation and invitations, calculate ratings, keep clients in sync, and protect or troubleshoot the service.

When you invite someone by email, BEYLE uses the address to find an existing BEYLE account. Invitations are in-app; BEYLE does not send an invitation email.

What other people can see

BEYLE profiles can show your display name, biography, profile image, city, interests, and rating summary. Your account email and profile coordinates are not shown on the public profile. Public event pages may show event details and coordinates, the creator's display name, and participant display names. Private events are restricted to the creator, invited users, and participants.

Information you put in a public event description can be seen by other people. Avoid adding information you do not want shared.

When information is shared

• With other BEYLE users: information visible on your profile, public event pages, and event participant lists is shared as described above. Private event information is available to the people allowed to access that event.
• With sign-in providers: when you choose Google or GitHub, your browser communicates with that provider to authenticate you. Each provider handles information under its own policy.
  Google Privacy Policy GitHub Privacy Statement
• With infrastructure providers: BEYLE runs on hosted server and database infrastructure. Those providers process information needed to operate the service.
• For legal or safety reasons: BEYLE may disclose information when reasonably necessary to comply with law, protect users, or secure the service.

When you choose Google sign-in, Google account data is used only to verify your sign-in and provide the BEYLE account and profile features described in this policy. It is not used for advertising or to train generalized AI models.

BEYLE does not sell or rent your personal information.

Cookies and device storage

The website uses an essential session cookie to keep you signed in. It is configured as HttpOnly and SameSite=Lax, Secure when served over the production domain, and expires within seven days. The Android app stores a sign-in token on the device so your session can continue between app launches; signing out removes that token.

Retention and deletion requests

BEYLE keeps account, profile, event, and activity records while your account is active. The app does not currently include a self-service account deletion control. To request access, correction, or deletion, use the contact email below from the email address associated with your account, and describe your request. BEYLE may ask for reasonable information to verify that you control the account.

After a verified deletion request, BEYLE will delete or de-identify account information where appropriate, subject to information that must be retained for legal, security, or abuse-prevention reasons. Nightly backup copies may retain deleted records for up to 14 days before rotation.

Security and storage location

BEYLE uses HTTPS for network connections and stores passwords as salted hashes. No online service can guarantee perfect security. BEYLE's server and backups may be located in a country different from yours, so information may be processed across borders.

Children

BEYLE is not directed to children under 13, and BEYLE does not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact BEYLE so it can be reviewed.

Changes to this policy

BEYLE may update this policy when the service or its data practices change. The effective date at the top of this page shows when the current version took effect.