1. Who is responsible
Meetigen is operated by Saamoja Technologies Limited. Saamoja determines how and why personal data is used for Meetigen’s platform accounts, Event discovery, security, ticketing records, payment orchestration, support, and platform safety.
For a particular organiser-controlled operation, Saamoja may process information on an organiser’s documented instructions. The applicable role and responsibilities depend on the operation and the relevant agreement.
2. Accounts and profiles
- Authentication identifiers and enabled email or phone contact details.
- Name, username, avatar, language, currency, country, optional biography, verification state, and optional birth year.
- A limited set of Event-interest categories used to support discovery.
- A public profile may show name, username, avatar, biography, verification state, joined date, and public counts. Contact details, precise location, preferences, and birth year are not public profile fields.
- An official phone number collected as a private contact is separate from an Auth identity, payout destination, and marketing consent.
3. Age and dependant attendance
Meetigen accounts are for people aged 18 or older. A parent or guardian may manage a dependant ticket for a person under 18; that ticket does not create a child account.
For an approved Event involving minors, Meetigen and the organiser may use limited admission, guardian-consent, emergency, check-in, and release information appropriate to the disclosed attendance arrangement.
4. Location and discovery
When a local feature is used, Meetigen may store one latest precise location point and its update time. It replaces the previous point, can be cleared, is not movement history, and is not exposed to an organiser as a member location list.
Bounded discovery activity may include Event and category identifiers, activity type, account identifier, and time. Meetigen does not intentionally record an IP address, device fingerprint, or raw search phrase for this feature.
5. Events, messages, and communications
- Event details, registrations, organiser information, attendance settings, venue or online-access details, and Event messages.
- Direct conversations, notifications, support correspondence, and delivery records.
- Information needed to manage Event changes, capacity, rescheduling, postponement, cancellation, and attendee notices.
6. Tickets, attendance, and payments
Meetigen processes buyer, holder or dependant, ticket type, quantity, amount, currency, transfers, ticket state, attendance scans, refund and dispute evidence, and provider references. Accepted admission is represented by the canonical ticket status USED. QR credentials are designed not to contain attendee personal data.
Paystack processes supported payments and settlement where enabled. Provider confirmation controls payment, ticket fulfilment, refunds, and payouts. Meetigen does not offer a wallet, stored value, lending, foreign exchange, or peer-to-peer transfers.
Meetigen retains provider references, statuses, reconciliation evidence, and masked destination labels rather than card credentials, full bank details, or seller identity documents where those are held by the provider.
7. Safety and enforcement
Meetigen may use reports, blocks, content snapshots, moderation actions, reasons, and audit evidence to investigate safety, prevent fraud, enforce platform rules, and respond to lawful requests. Reporting does not by itself establish wrongdoing.
Meetigen may restrict an account, Event, ticket, seller capability, or related content where reasonably necessary for safety, fraud prevention, law, provider requirements, or the Terms.
8. Cookies and device storage
- Authentication cookies and locale or currency preference cookies.
- Local storage for preferences, public-share measurement, bounded discovery signals, and a scanner device identifier.
- IndexedDB for limited PWA snapshots and account-scoped provisional scanner attempts.
- Session storage for sampled, bounded operational telemetry without content, coordinates, search text, authentication material, or secrets.
9. Providers and transfers
Meetigen uses service providers for hosting, authentication, database and storage operations, maps and geocoding, email delivery, payment processing, settlement, payout, and currency-rate support as applicable to the enabled product features. Saamoja limits provider access and disclosures to the purposes for which providers are used and applies appropriate contractual, security, retention, and transfer safeguards.
10. Retention
Meetigen keeps personal data only for as long as needed for the stated purpose, safety, support, contractual and financial records, legal obligations, dispute handling, or documented claims. Information is deleted or de-identified when it is no longer needed, subject to lawful retention requirements and applicable legal holds.
11. Rights and contact
Subject to applicable Kenyan law, you may request access, correction, restriction, objection, portability, or erasure where applicable. Saamoja may verify your identity, retain information where lawfully required, and explain any limitation or refusal.
Send privacy, complaints, account requests, and policy enquiries to contact@saamoja.com.
12. Security and changes
Meetigen uses server-side authorisation, role-based access, private storage for restricted material, signed ticket credentials, bounded device storage, audit evidence, and provider verification for commerce states. Saamoja applies proportionate technical and organisational safeguards and limits access according to operational need.
A material change will be reflected in a new version and last-updated date.