Everything you might ask before you sign up.

Community organizers, conference organizers, meetup groups, alumni networks, certification programs, and anyone who runs recurring events and wants the audience to stick around between them.

No. Sign-up is free and never asks for a card. Gathin has a free plan to get started, plus a paid Pro plan as your community grows — see the /pricing page for what each plan includes and current prices.

Yes — a native Gathin app for iOS and Android is on the way and coming soon. Until it lands, the web app works on any phone, tablet, or computer screen: it runs in every modern browser and adjusts to whatever screen you open it on, so every attendee flow already works on your phone.

The interface is fully localized into English, Turkish, German, French, Spanish, and Italian. Content you type (event titles, descriptions, community pages) stays exactly as you wrote it — we do not auto-translate user content.

Every event gets its own public web address at /events/<name> with a cover image, date and venue, a capacity counter, RSVP or ticket options, speakers, sponsors, a schedule, and a photo gallery. Google can find it, and when you share the link on LinkedIn, WhatsApp, X, or Slack it shows a clean preview with the title and cover image.

Yes. Mark the event as online and either paste your own meeting link — Zoom, Google Meet, whatever you use — or create a built-in video room in one click. Attendees see the link on the event page once they have joined.

Yes. The schedule editor works day by day: add a day, add parallel tracks (rooms) within it, then add sessions with a title, time, description, and speakers. Everything you save appears on the public event page.

Turn the gallery on in the event admin and upload your photos and videos. They appear on the same public event URL after the event, so members return to the same page to relive the moment — no second link, no third-party host.

Yes. In the event details, add another community as a collaborator. The event then shows as co-hosted on its public page, and collaborators can see the attendee and waitlist — but only the community that created the event can edit it.

Yes, indefinitely. Past events keep their public URL, photo gallery, and speaker list. They are excellent for SEO and for new members discovering what your community has done.

Yes. In the event admin, add tickets and set a price for each — 0 makes it free, anything above is paid. You can build tiers (Standard, VIP, Early Bird), set a per-ticket sale window, add a quota, and configure VAT. The public page updates with the new tickets instantly.

Attendees pay securely by card at checkout. Prices are shown in Turkish Lira (TL). The money is collected through the platform and lands in your community's Revenue balance, ready to withdraw.

Yes — a commission (a payment-processing fee) is taken from each paid ticket before the rest lands in your balance. Rather than quote one fixed rate, we show the exact rate on each payment's row on your Revenue page. Note that a payment's rate may change once 45 days have passed since the payment.

RSVP is a free reservation — members tap once to say they are coming and still get a QR ticket, but no money changes hands. Ticketing is for paid entry, with tiers, checkout, and a quota. You choose which one per event.

For a free event, an attendee can simply give up their spot from the event page. Paid tickets are non-refundable by default. There are two exceptions: if the organizer cancels or postpones the event, and where the law gives you a right of withdrawal (mainly non-dated or online on-demand offerings). In those cases the refund goes back to your original card and is handled by the platform — you do not have to chase the organizer for it. The full terms are on the Cancellation and Refund page (/iptal-iade).

Yes. The Participants area of each event lists every attendee with their ticket, the amount they paid, and their check-in status, and you can export the whole list as a file for your own records.

A cover image, logo, description, social links, city and category, member count, and a live feed of upcoming and past events. It lives at its own web address, /communities/<name>, that Google can find like any real website — not a profile locked inside an app.

Go to /communities/create and fill in a name, description, city, category, and images. Once you create it you become the owner, with an admin panel to manage members, run events, and enter the bank details your payouts go to.

The communities directory at /communities ranks by activity and popularity, with categories and one-click join for any public community. It is a free discovery channel for organizers.

Yes. Tag members into segments — VIP, volunteer, speaker, alumni, whatever fits — from the Members page, one at a time or in bulk. Each segment shows its member count, and you reuse the same segments across events.

Yes. On the community settings, set visibility to public or private. A private community is invite-and-approve: people join only when you invite them or approve their join request, which waits for you in the Pending Requests tab.

Every member has a public profile at /@username with a cover, avatar, an "About" text, social links, and tabs for events attended, communities, certificates, and badges — plus follower counts. Members share it like a CV, which gives your community free distribution.

On your own profile, tap "Edit Profile". You can change your photo and cover, write the "About" text that introduces you, set your username, and add social links. Save, and it is live on your /@username page.

Yes. Every public page has its own web address that Google can find, and it shows a clean preview when shared on WhatsApp, LinkedIn, or Slack. Past events and communities build up as a search-friendly archive of what your network has done.

Profile URLs follow the /@username pattern, where the username is your chosen handle. Clean, shareable, and the same on every page that links to you.

A single admin panel where every community function lives — members, segments, events, revenue, gallery, and settings. The same panel works whether you run a 20-person book club or a 20,000-person network.

Ticket money is collected through the platform and lands in your community's Revenue balance. From the Revenue page you request a withdrawal, and the amount is transferred to the community's registered bank account (IBAN). Each payment moves through three states — In Balance, Withdraw Requested, Transferred — and everything is in Turkish Lira (TL).

Yes. Sponsor payments reach you exactly like ticket income — they land in the same Revenue balance, move through the same payment statuses, and pay out to the same bank account. You do not track sponsor money separately or arrange it off-platform.

Yes. Every member has a role — Owner, Admin, or Member. Switch a member to Admin from the Members page and they get the full organizer panel; the owner has every permission and cannot be removed.

Yes. From the community settings you control the logo and banner, name and username, short and detailed description, city, category, social links, and privacy level — all from one place. These are the first things people see when they discover you.

You do. Your members, your events, your photos, your community content — all exportable, all yours. We are a tool, and we do not lock your data in.

Yes. What we collect and how we process it is documented on our Privacy Policy (/privacy) and KVKK (/kvkk) pages, and we honor data export and deletion requests. For a request or a data-processing agreement, write to info@lodos.io.

Gathin runs on Lodos infrastructure. Details about where your data is stored are available on request.

Write to us at info@lodos.io or use the contact page, and we handle the deletion (or a copy of your data) for you. There is no separate self-serve delete button in the app — reaching out is the right way, and we usually reply within a business day.

Gathin has a free plan to start, plus a paid Pro plan as your community grows. See the /pricing page for what each plan includes and current prices. Sign-up itself is free and asks for no card.

The full user guide lives at /guide, with step-by-step articles on events, tickets, communities, profiles, and getting paid. This FAQ is part of it, at /guide/faq.

Write to us at info@lodos.io or use the /contact page. We read every message and reply fast — usually within a business day.

Bugs and feature requests go to info@lodos.io with a screenshot and the page URL. We look at critical issues the same day.