A first-session guide to Joinory

Public beta · updated 7 September 2026

For organizers

  1. Open the Joinory Main Mini App and choose Create event. You do not need to start inside a group.
  2. Enter a clear venue, time, duration, capacity, level and price. You can add a map and payment instructions. Costs and private player notes are shown only to you.
  3. Choose Create event & share, then Share to Telegram. Select any group where you can post; the destination group does not need the Joinory Bot.
  4. Players tap Join Event on the shared card. If full, they can join the waitlist.
  5. Open My events → Organizing to edit, record paid/unpaid/refunded status and check attendance.
  6. After the event starts, record actual attendance and choose Complete event. Players can then rate their experience and submit feedback. Use Create next weekly session to prepare another occurrence.

Optional enhanced mode: add Joinory to a Telegram group, send /new, and publish a canonical card whose participant count updates automatically.

For players

Open an event card, review the venue, time, requirements and fee, then tap Join. A waitlist place is not a confirmed playing place. When somebody leaves before the start, the first waiting player is promoted. Enable reminders if you want Telegram messages.

Your organizer handles payment and refund arrangements. “Paid” and “Refunded” mean the organizer recorded a confirmation. Check My events → Attending for your events and current status.

Payments, cancellations and beta limits

Joinory does not collect, hold or transfer money. It records manual payment confirmations. No bank connection, payment guarantee or automatic refund is provided. Agree on fees and cancellation terms directly with your organizer before paying.

Pre-payment is an organizer requirement. An unpaid joined player still reserves a place until they withdraw or the organizer cancels the event. There is no automatic unpaid-slot expiry. An exit within 12 hours before the start is recorded as a late cancellation for that organizer. Past and completed events retain their records.

Use is free during this beta; an organizer may still charge an activity fee. Features may change, and interruptions may occur. Keep venue arrangements and essential contact details available in your group. This beta is intended for small groups; large-scale load and broad device coverage have not been established.

Feedback and support

Open Joinory and select Send feedback or report a bug. You receive a reference and can read its status and the team's response under Your recent reports. Reports are visible only to you and the Joinory team.

If the app will not open, message @joinoryAppBot privately with /feedback followed by your question, bug or privacy request. Include what you tried and what happened. Do not include passwords, login codes, bank credentials or other people's private information. Screenshots are not accepted by the beta feedback form; describe the screen in text.

If a personal creation session expires, return to My events and choose Create event again. For enhanced group mode, send /new again. If enhanced-group delivery is uncertain, inspect the group before using recovery; the card may already exist.

How this beta uses data

Joinory stores the Telegram account ID, display name, username and language information received at login, plus optional enhanced-group records, activities you create or join, participation and attendance records, reminder permission, payment-status records, private organizer notes, event-share platform/source and referral attribution, and feedback you submit. Login data is verified by the server. Session credentials are kept in app memory and expire after one hour.

People with the event link who sign in can view its details and active participant names. The organizer can see participants' payment status, their own private notes and participation history for events they organize. Costs and profit calculations are organizer-only. Feedback and replies are available to the submitting user and authorized Joinory operators. Operational logs and aggregate activity counts help maintain the service.

Joinory records the user who initiates a share, its channel/source, an opaque referral code, Telegram's prepared-message identifier, whether Telegram confirms a send, and whether the resulting app session joins. Joinory does not receive the selected destination chat from the Mini App share callback and does not read the message content in that chat.

Data is stored on the production server and in encrypted off-host backups. Activity, payment and feedback records remain available for follow-up. Routine session, old analytics and job cleanup is available to operators. Joinory uses Telegram to authenticate users and send requested event messages. No advertising or external analytics service is embedded in this beta.

For access, correction or deletion requests, use Privacy / data request in feedback, or the private bot /feedback command. The team handles requests manually and verifies account ownership. Backup copies expire under the backup retention policy; requests do not instantly erase existing backup archives. Avoid recording sensitive personal information in event notes.

Growth & sharing

On an upcoming published event, expand Share this event to send a prepared event card, copy its invitation, or copy its link. Nothing is sent automatically. Telegram asks you to choose and confirm a destination. Anyone with the link who signs in can see the event and active participant names; drafts are not shareable. The invitation excludes player lists, payment instructions and private organizer costs.

The prepared card's displayed count is a snapshot. Its Join Event button always opens live availability. Enhanced-group cards can update automatically because the Bot is installed there.

Use Add Joinory automation to a group only when you want enhanced mode. Signed-in share attempts, Telegram send confirmation, referral opens and referred joins are used for aggregate statistics. Clipboard contents, destination chats and Telegram messages are not collected. A cancelled share is not counted as sent; if Telegram cannot confirm the result, check the destination before retrying.